Ufffff, indeed!! I almost looked letter-by-letter into the config and
didn't notice that I removed the part for static IPs.
Four eyes see more as my menthor would say back in the old days
Thanks!
On 2014-12-29 17:37, li...@rhsoft.net wrote:
Am 29.12.2014 um 17:25 schrieb Istvan Prosinger:
I'm trying to send a test mail to my postscreened server, and
postscreen
should naturally rejct it for the first time. My problem is that it
seems to be rejecting the mail forever even if it's comming from the
same IP adress
Dec 29 17:22:09 vs3163 postfix/postscreen[10262]: CONNECT from
[65.55.34.27]:53020 to [89.22.98.122]:25
Dec 29 17:22:09 vs3163 postfix/postscreen[10262]: WHITELIST VETO
[65.55.34.27]:53020
Dec 29 17:22:16 vs3163 postfix/tlsproxy[11833]: CONNECT from
[65.55.34.27]:53020
Dec 29 17:22:17 vs3163 postfix/postscreen[10262]: NOQUEUE: reject:
RCPT
from [65.55.34.27]:53020: 450 4.3.2 Service currently unavailable;
from=<pi...@live.com>, to=<ist...@prosinger.net>, proto=ESMTP,
helo=<COL004-OMC1S17.hotmail.com>
Dec 29 17:22:17 vs3163 postfix/postscreen[10262]: DISCONNECT
[65.55.34.27]:53020
Dec 29 17:22:17 vs3163 postfix/tlsproxy[11833]: DISCONNECT
[65.55.34.27]:53020
look at your config
postscreen_whitelist_interfaces = 127.0.0.1/32
you *explicitly* configured that behavior if the client is not
localhost
read again the docs of that parameter, a usage-sample below to have a
backup-MX on the same machine which *always* answers 450 to kill
zombies trying the backup-MX instead the primary
postscreen_whitelist_interfaces = !<ip-of-honeypot-mx>, static:all
