Set Postfix to block fake emails

I just want to set postfix to block fake emails that can just type:


Of curse IP of sender is not even related with google's IP or their MX

I blocked almost all unwanted functionality in postfix, but I cant find proper information in documentation. I tried varies settings but all of them fails to prevent sending mail to mine server that way. I assume that this is a simple task, and you - experts - will get with this in 2 minutes... So can you help me ?
LVL 18
Pawel WitkowskiSenior Javascript DeveloperAsked:
Who is Participating?
ridConnect With a Mentor Commented:
Right you are! Sort of shortcut that part of the problem before i wrote....
ifreqConnect With a Mentor Commented:
There is no good proven way to validate sender of the email you receive, you would get a lot of better results by using some realtimeblacklist  like  Spamhaus.  Ive been using it over a year now with 0% false positive matches. And it drops about 80-95% of unwanted emails on the smtp-gateway level. Most  emails are originating from zombie bot-networks these days.

Installation instructions are here:

I second ifreq in adding the configuration to use spamhaus.

You could also setup your postfix to check SPF records before accepting incoming emails. While not 100% perfect, most big free email provider to use SPF to announce servers which are expected to send email from their domain, and thus cuts back on email spoofind. Instructions at:

Hope this helps,
7 new features that'll make your work life better

It’s our mission to create a product that solves the huge challenges you face at work every day. In case you missed it, here are 7 delightful things we've added recently to monday to make it even more awesome.

I second urgoll for SPF :-) Thought SPF is not so famous at the moment and it hasnt been goodly developed  in years anymore.  But thats one more thing you could add to your postfix installation too to make it more effective.
Have you set Postfix to reject rDNS failures and unknown hosts? That should take care of the scenario you outlined, I think.
rid: the original question discusses someone spoofing addresses - hostnames are good and the mail sender's domain are valid, it's just that the address used doesn't exists.

It is true that rejecting reverse DNS failures and invalid domains is a good idea and cuts down the overall volume of spam. For the record, this is done but using :

to the smtpd_*_restrictions statements in the file.

Pawel WitkowskiSenior Javascript DeveloperAuthor Commented:
Actually i think that i set postfix very restrictive:

smtpd_sender_restrictions = permit_sasl_authenticated,  reject_unknown_sender_do
main,  reject_non_fqdn_sender,  reject_unknown_address

smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,rejec
t_unauth_destination, check_policy_service unix:private/policy-spf, reject_non_f
qdn_sender, reject_non_fqdn_recipient, reject_unknown_sender_domain, reject_unkn
own_recipient_domain, reject_invalid_hostname, reject_unverified_recipient, reje

But i tried to find anything about my problem and ... cant find anything. As I said I can login into my server using my ISP IP by telneting to 25 port  then sending mail from even not fake mail but by spoofing someone (the problem is for example  I would like to restrict that if someone want to send mail to recipient in mine server (because I got relaying turned off and set sasl auth so only problem sending to my recipient) then his IP must got revDNS on domain from where mail was sent (so revDNS of IP should be Is that even possible?? Futher more is there possible to set EHLO to user IP revDNS rather that what he typed??

Actually only I received spoofed paypal mail, but mine users are more like "normal" people and could be confused with that type of spam :( I apprecieate any help from you side here guys :)
urgollConnect With a Mentor Commented:
What you are describing would completely break email. For example, if I send an email from my account, I see that the sending server is "". See, there's no mention of in the server name. This is why SPF was invented, to allow domain owners to announce which servers are authoritative for their domain.

You have put your finger on the great flaw of email as it is currently implemented, i.e. it is based on trust and good faith. All we can do now is use mitigating techniques, such as SPF, DKIM, doing rDNS checks and using anti-spam tools such as SpamAssassin to separate the wheat from the chaff.

Pawel WitkowskiSenior Javascript DeveloperAuthor Commented:
My problem is still not solved, but at least i know that this is impossible to do like I would think it could;) Poits here for you ppl for at least some light there
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.