Re: Comcast email issues...
Larry, if your store was sending emails to the notification address but using a "From" address of <name>@comcast.net, that would be an issue. Comcast would view that as a non-Comcast server trying to send their customers messages claiming to be from Comcast, which is considered mail forgery.
You may be experiencing, and inadvertently causing, the same issue Bill was experiencing. If a customer of ours sets up an email account that forwards to a Comcast address, what occurs is emails come into the server here, there is no filtering for spam, and they are relayed back out to the Comcast address. The original sender address is preserved. This can cause several issues:
All of these combined make forwarding mail to a Comcast address dangerous to everyone on the server and ideally it should not be done.
What Bill did to work around this issue is he turned off forwarding and instead enabled a feature in Hotmail where they will poll his account here and retrieve the email for him; so it shows up like a normal new message but it was retrieved by them instead of being forwarded to them.
Google and Yahoo also both offer this service. I like Google's implementation in particular because it runs every few minutes regardless of whether you're logged in or not, so if you have your gmail account mapped to any portable device, it will notify you of new mail just as if it had been sent to your gmail account.
Larry, if your store was sending emails to the notification address but using a "From" address of <name>@comcast.net, that would be an issue. Comcast would view that as a non-Comcast server trying to send their customers messages claiming to be from Comcast, which is considered mail forgery.
You may be experiencing, and inadvertently causing, the same issue Bill was experiencing. If a customer of ours sets up an email account that forwards to a Comcast address, what occurs is emails come into the server here, there is no filtering for spam, and they are relayed back out to the Comcast address. The original sender address is preserved. This can cause several issues:
- If it's a Comcast sender, then it goes back to Comcast claiming to be from Comcast and they can view it as a forgery.
- If it's from a sender whose email domain publishes an SPF (sender policy framework) record, which is a way for domain owners to provide a list of valid mail servers for a given domain to prevent forgery, and Comcast sees it coming from us, they will consider it forged.
- If it's just typical spam, it comes to them from our server, not the original spam delivery server or client, and if their spam filter flags it, they count it against our server. If the percentage of bad to good goes over a certain amount, the server gets blocked.
All of these combined make forwarding mail to a Comcast address dangerous to everyone on the server and ideally it should not be done.
What Bill did to work around this issue is he turned off forwarding and instead enabled a feature in Hotmail where they will poll his account here and retrieve the email for him; so it shows up like a normal new message but it was retrieved by them instead of being forwarded to them.
Google and Yahoo also both offer this service. I like Google's implementation in particular because it runs every few minutes regardless of whether you're logged in or not, so if you have your gmail account mapped to any portable device, it will notify you of new mail just as if it had been sent to your gmail account.
Comment