Nightly thread update mails bouncing... :(
#1
Original Poster
Join Date: Apr 2007
Location: 42mi from AMS
Programs: UA 1K 1MM, Marriott LT Au, Hilton C, IHG PtA
Posts: 576
Nightly thread update mails bouncing... :(
In case you're wondering why you didn't get your digest mail...
Seems the admins made a change to the way the nightly thread update e-mails are send out, instead of the previous "[email protected]" as SMTP sender (not the From: !), they used "[email protected]".
Well, that host or domain ("flyertalk4.flyertalk.com"), does not exist in DNS (up to this moment), and as such neatly configured mailservers will have told the offering mailserver to take a hike, since Spammers use(d) similar techniques for ages. As did mine of course...
I'm starting to think I know what mild withdrawal symptoms look like by now...
Seems the admins made a change to the way the nightly thread update e-mails are send out, instead of the previous "[email protected]" as SMTP sender (not the From: !), they used "[email protected]".
Well, that host or domain ("flyertalk4.flyertalk.com"), does not exist in DNS (up to this moment), and as such neatly configured mailservers will have told the offering mailserver to take a hike, since Spammers use(d) similar techniques for ages. As did mine of course...
I'm starting to think I know what mild withdrawal symptoms look like by now...
#2
Join Date: Feb 2009
Posts: 959
In case you're wondering why you didn't get your digest mail...
Seems the admins made a change to the way the nightly thread update e-mails are send out, instead of the previous "[email protected]" as SMTP sender (not the From: !), they used "[email protected]".
Well, that host or domain ("flyertalk4.flyertalk.com"), does not exist in DNS (up to this moment), and as such neatly configured mailservers will have told the offering mailserver to take a hike, since Spammers use(d) similar techniques for ages. As did mine of course...
I'm starting to think I know what mild withdrawal symptoms look like by now...
Seems the admins made a change to the way the nightly thread update e-mails are send out, instead of the previous "[email protected]" as SMTP sender (not the From: !), they used "[email protected]".
Well, that host or domain ("flyertalk4.flyertalk.com"), does not exist in DNS (up to this moment), and as such neatly configured mailservers will have told the offering mailserver to take a hike, since Spammers use(d) similar techniques for ages. As did mine of course...
I'm starting to think I know what mild withdrawal symptoms look like by now...
Like I said, we're still working on the problem, but it should be pretty transparent to the end user. Yes, sending email as a domain that doesn't have an MX record can be bad, however it's exactly what the site's been doing for years, so it's not like it is going to make anything worse.
I'm very impressed that you noticed.
#3
Original Poster
Join Date: Apr 2007
Location: 42mi from AMS
Programs: UA 1K 1MM, Marriott LT Au, Hilton C, IHG PtA
Posts: 576
Hey, I didn't get my digests, and checked my logs.
Occupational hazard for a mail/sys/network engineer.