Tag Info

Hot answers tagged

3

Additionally to the explanations from masegaloeh, I want to point out, why the spammer got through in your case. Look at the following line in the logs: Jul 19 07:59:07 mail postfix/smtpd[15492]: NOQUEUE: reject_warning: RCPT from unknown[37.215.63.185]: 504 5.5.2 <37.215.63.185>: Helo command rejected: need fully-qualified hostname; from=<> ...


3

The quick search directs you to the AOL Postmaster where error 421 should have been followed by an additional error code indicating the actual reason your connection is (temporarily) rejected: 421 DNS:NR The Reverse DNS lookup for your IP address is failing. 421 RLY:B3 The IP address you are sending from has been temporarily rate limited due ...


2

The double-bounce messages are used by postfix for address verification. You may find more detail here... http://www.postfix.org/ADDRESS_VERIFICATION_README.html


2

The logs above is expected behavior from postfix and amavis. For after queue content filter like amavis, the filter needs reinject email to postfix. For more info please refers to official documentation. Here some explanation of postfix and amavis action. Jul 19 07:59:06 mail postfix/smtpd[15492]: connect from unknown[37.215.63.185] Client from ...


2

TCP port 25 is the default port for SMTP traffic and is the only accepted way to transmit e-mail over the internet. Postfix is correct in insisting to use that. Outgoing traffic over port 25 is commonly blocked by consumer ISP's, corporate, government and college networks etc. to prevent their users from transmitting unauthorised e-mail and SPAM. ...


1

Limitation: For this solution, you must list all your users and its md5. Except tcptable/external daemon solution, MD5 calculation doesn't supported by most postfix table You can user pcre table and header_checks feature to achieves that. Specify this line in your header_check table. I tested this expression in pcre-type table. /^(Received: .*Authenticated ...


1

There is no such generally-valid way. Not only would such a technique be of immense use to spammers, but in addition you can't know what happens to mail once it passes through a company's externally-advertised mail gateway. Perhaps it stays in spool on that box while it's checked for spam and viruses, then is delivered to an internal server for final ...


1

You should migrate sendmail's "direct delivery for other host in the same domain" hack to postfix. [You reported use of smart host in both configurations] sendmail sendmail.mc LOCAL_NET_CONFIG R$* < @ $* .$m. > $* $#smtp $@ $2.$m. $: $1 < @ $2.$m. > $3 postfix master.cf transport_maps = hash:/etc/postfix/transport ...


1

Yes, you need to make sure that Your HELO string is a domain that resolves to your IP. There is a PTR record for the IP of your sending mailserver that resolves to that domain. The domain in the PTR and your helo must correspond. It's not exactly according to RFCs, but large providers such as AOL have been expecting it for a long time. It does help spam ...


1

That's not exactly a bounce message, it's a temporary delivery failure message. The recepient's mail server is telling you that the problem is 421 Unexpected failure, please try later.. Your mail server says that it will keep trying to send the message until Sunday Jule 27. The reason for this temporary failure isn't possible for anyone other than the ...


1

If you will "Set the default gateway to the ADSL router", AFAIK this will cause all (not remaining!) traffic to go to the ADSL router. So the outgoing traffic from Postfix will also go through ADSL router. And this is probably not what you want... The answer on this question - Get linux to change default route if one path goes down? - contains a link on how ...



Only top voted, non community-wiki answers of a minimum length are eligible