Be Careful mxbw.lb.bluewin.ch seems to be an entry wich is load balanced with different A Records .
I've got a different IP after the TTL expired. So you are ending up on different server on the bluewin site.
maybe a server in the cluster which has a specific problem, just a guess.
Try telnet to the different server and if you can find the specific server -> then try to contact the mailmaster :-)
Has anyone else experienced this problem? According to our customer, it
occurred a couple of times in the last days:
Sender and Destinations are the same in all examples:
Our customer is sending an email to bluewin:
Jan 23 13:32:42 obelix postfix-submit.obelix/smtp[28721 C5015C0CE5: to=<****@bluewin.ch>, relay=mxbw.lb.bluewin.ch[188.8.131.52]:25, delay=57, delays=1.6/0.01/44/11, dsn=2.0.0, status=sent (250 2.0.0 mHh5gTobfzOqbmHhngLDSm mail accepted for delivery)
Bluewin Customer replies:
Jan 23 17:10:17 obelix milter-greylist: (unknown id): skipping greylist because address 184.108.40.206 is in DNSRBL, (from=<****@bluewin.ch>, rcpt=<****@breitband.ch>, addr=vimdzmsp-sfwd03.bluewin.ch[220.127.116.11]) ACL 196
Our customer replies:
Jan 23 17:24:38 obelix postfix-submit.obelix/smtp[12583 D0AE7C10EE: to=<****@bluewin.ch>, relay=mxbw.lb.bluewin.ch[18.104.22.168]:25, delay=101, delays=0.27/0.01/66/35, dsn=5.1.1, status=bounced (host mxbw.lb.bluewin.ch[22.214.171.124] said: 550 5.1.1 <*****@bluewin.ch> recipient rejected, address unknown (in reply to RCPT TO command))
Same IP Address of same bluewin server as before, not replies the
destination does not exist. I can assure you, it is the same address as
Our customer tries again:
Jan 23 17:32:23 obelix postfix-submit.obelix/smtp[26676 C9470C1271: to=<*****@bluewin.ch>, relay=mxbw.lb.bluewin.ch[126.96.36.199]:25, delay=3, delays=0.24/0.02/0.59/2.1, dsn=2.0.0, status=sent (250 2.0.0 mJApg3d9Gp4S3mJAqgsUex mail accepted for delivery)
Now the email is getting through!
Mit freundlichen Grüssen