Solved

Set Postfix to block fake emails

Posted on 2008-10-22
9
1,875 Views
Last Modified: 2013-12-19
I just want to set postfix to block fake emails that can just type:

MAIL FROM: someonefake@google.com
RCPT TO: user@inmydomain.com

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 ?
0
Comment
Question by:wilq32
  • 3
  • 2
  • 2
  • +1
9 Comments
 
LVL 5

Assisted Solution

by:ifreq
ifreq earned 100 total points
Comment Utility
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:

http://wiki.kartbuilding.net/index.php/Postfix_SMTP#Blocking_Spam_with_spamhaus_and_Postfix

0
 
LVL 4

Expert Comment

by:urgoll
Comment Utility
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:
http://www.howtoforge.com/postfix_spf

Hope this helps,
Christophe
0
 
LVL 5

Expert Comment

by:ifreq
Comment Utility
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.
0
 
LVL 31

Expert Comment

by:rid
Comment Utility
Have you set Postfix to reject rDNS failures and unknown hosts? That should take care of the scenario you outlined, I think.
/RID
0
Do email signature updates give you a headache?

Do you feel like all of your time is spent managing email signatures? Too busy to visit every user’s desk to make updates? Want high-quality HTML signatures on all devices, including on mobiles and Macs? Then, let Exclaimer solve all your email signature problems today!

 
LVL 4

Expert Comment

by:urgoll
Comment Utility
rid: the original question discusses someone spoofing gmail.com 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 :
                 reject_unknown_sender_domain,
                reject_invalid_hostname,
                reject_non_fqdn_sender,
                reject_non_fqdn_recipient,

to the smtpd_*_restrictions statements in the main.cf file.

Regards,
Christophe
0
 
LVL 31

Accepted Solution

by:
rid earned 200 total points
Comment Utility
Right you are! Sort of shortcut that part of the problem before i wrote....
/RID
0
 
LVL 18

Author Comment

by:wilq32
Comment Utility
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
ct_unknown_client

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  security@paypal.com).  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 paypal.com). 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 :)
0
 
LVL 4

Assisted Solution

by:urgoll
urgoll earned 200 total points
Comment Utility
What you are describing would completely break email. For example, if I send an email from my gmail.com account, I see that the sending server is "ey-out-2122.google.com". See, there's no mention of gmail.com 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.

0
 
LVL 18

Author Closing Comment

by:wilq32
Comment Utility
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
0

Featured Post

Better Security Awareness With Threat Intelligence

See how one of the leading financial services organizations uses Recorded Future as part of a holistic threat intelligence program to promote security awareness and proactively and efficiently identify threats.

Join & Write a Comment

Easy CSR creation in Exchange 2007,2010 and 2013
ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
In this video we show how to create a Distribution Group in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >>…
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…

744 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

17 Experts available now in Live!

Get 1:1 Help Now