A contractor just started getting bounce messages when he tries to email $DAYJOB -- the message is accepted by our Exim frontend but then rejected by our Exchange 2013 server with the error message below (example.com and example.net are placeholders for two different .com domains; outside sender is usern...@example.net and my recipient is u...@example.com):
Failed to deliver to 'u...@example.com' SMTP module(domain mail1.example.com:25) reports: return-path address <SRS0=g2..et=OB=example.net=usern...@eigbox.net> rejected by mail1.example.com:25: 501 5.1.7 Invalid address My immediate reaction is that the eigbox.net server is generating an invalid local-part when it VERPs the contractor's address (two dots together), but after reading RFC5322 I'm not 100% sure that's an invalid format. (Wikipedia says it's invalid, and that fits with my reading of 3.2.3 and its dot-atom-text definition, but I don't have complete faith in either my reading of RFC5322 or in Wikipedia.) So.... 1) Am I correct in believing that two dots with no intervening atext characters are illegal in a return-path? 2) If 1) is correct, does anyone have a good contact at eigbox.net that I can ask for help getting their VERP fixed? 3) If 1) is incorrect, does anybody have suggestions for telling Exchange 2013 to be more liberal in what it accepts? I know I can attack this with header rewriting rules in Exim if it comes to that, but I'd rather get the problem fixed than paper it over if possible. Any suggestions appreciated. -- Dave Pooser Cat-Herder-in-Chief, Pooserville.com _______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
