Stopped Receiving Newsletters
-
Over the past few weeks I've stopped receiving all newsletters from The Code Project. I don't know if you've stopped sending them, if my ISP has hijacked them or if my mail reader (Thunderbird) has started to censor my email. My settings haven't changed. Any suggestions? .
-
Over the past few weeks I've stopped receiving all newsletters from The Code Project. I don't know if you've stopped sending them, if my ISP has hijacked them or if my mail reader (Thunderbird) has started to censor my email. My settings haven't changed. Any suggestions? .
Have you read the Code Project Member FAQ[^]?
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
-
Have you read the Code Project Member FAQ[^]?
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
Chris, I've at least read the FAQ specifically associated with newsletter problems. This was working just fine until sometime in the last few weeks. I did receive email notification of your response to my question. Do you have email logs that would indicate any possible email delivery failures? I logged into my webmail portal and found no spam in the spam folder. Thanks for your help. Ron
-
Chris, I've at least read the FAQ specifically associated with newsletter problems. This was working just fine until sometime in the last few weeks. I did receive email notification of your response to my question. Do you have email logs that would indicate any possible email delivery failures? I logged into my webmail portal and found no spam in the spam folder. Thanks for your help. Ron
Most likely it's an overactive spam filter. We send out forum notifications and newsletters from different servers, which can explain why you get one and not the other. If an ISP blocks an email they often don't say why, since this actually helps spammers. Have you added us to your whitelist? It may be worth contacting your ISP and seeing what they say. This is a never ending problem for us since ISPs often use email blacklists that are either out of date or are outright wrong. Of course, for a minor convenience fee we can be removed from some of these blacklists. Until next week, that is. :sigh:
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
-
Most likely it's an overactive spam filter. We send out forum notifications and newsletters from different servers, which can explain why you get one and not the other. If an ISP blocks an email they often don't say why, since this actually helps spammers. Have you added us to your whitelist? It may be worth contacting your ISP and seeing what they say. This is a never ending problem for us since ISPs often use email blacklists that are either out of date or are outright wrong. Of course, for a minor convenience fee we can be removed from some of these blacklists. Until next week, that is. :sigh:
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
Chris, I contacted my ISP and discussed the situation. The technician explained that when messages are blocked, an email is returned to the sender with specific information about why the message has been blocked and what can be done to get it unblocked. In order to anything from this end, I would need the IP address of the server that sends out the newsletters and possibly the email address of the sender. Getting my ISP to check its logs requires substantial evidence. Presumably, you have my email address and therefore know who my ISP is. You should be able to find evidence in your logs if the newletter emails are being rejected. Beyond that, you should be able to send a test message from the server and watch the specific response in isolation. I could use one of my other email addresses (same ISP) or use gmail to see if those options help.
-
Chris, I contacted my ISP and discussed the situation. The technician explained that when messages are blocked, an email is returned to the sender with specific information about why the message has been blocked and what can be done to get it unblocked. In order to anything from this end, I would need the IP address of the server that sends out the newsletters and possibly the email address of the sender. Getting my ISP to check its logs requires substantial evidence. Presumably, you have my email address and therefore know who my ISP is. You should be able to find evidence in your logs if the newletter emails are being rejected. Beyond that, you should be able to send a test message from the server and watch the specific response in isolation. I could use one of my other email addresses (same ISP) or use gmail to see if those options help.
I've asked Vince to follow up on this and get back to you. We'll see what we can untangle.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
-
I've asked Vince to follow up on this and get back to you. We'll see what we can untangle.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
Comcast put us on a block list a little while ago, I have been in contact with them about this and I am trying to get us removed. The orignial report from them was that we sent out too many emails and we sent them out too quickly...It's a good thing the mailers I setup only have 1 gb of ram. I have been trying to resolve this with comcast directly and hopefully it will be sorted out soon. We actively monitor our PTR, rDNS, Blacklists and other spam related concerns but it is rarely related to any of this. Typically its purely about volume or speed of delivery. We occaisonally trip AOL and Yahoo as well however they are a bit more sophisticated in that they will throttle our access so eventually everything gets through. When I hear back from comcast I'll post an update. Actually as I was typing this I just got a message back saying we were removed... I'll flush the mailqueue's and hopefully they will get through.
-
Comcast put us on a block list a little while ago, I have been in contact with them about this and I am trying to get us removed. The orignial report from them was that we sent out too many emails and we sent them out too quickly...It's a good thing the mailers I setup only have 1 gb of ram. I have been trying to resolve this with comcast directly and hopefully it will be sorted out soon. We actively monitor our PTR, rDNS, Blacklists and other spam related concerns but it is rarely related to any of this. Typically its purely about volume or speed of delivery. We occaisonally trip AOL and Yahoo as well however they are a bit more sophisticated in that they will throttle our access so eventually everything gets through. When I hear back from comcast I'll post an update. Actually as I was typing this I just got a message back saying we were removed... I'll flush the mailqueue's and hopefully they will get through.
Hmmmm Your not sending 2,000,000+ e-mails all at once are you? Back in the 1990's I was administering some high-load Unix servers and when I performed daily/weekly mailings to site members I would send A-D and wait 15 minutes then send E-H and so forth to avoid being blacklisted. When you send millions of e-mails all at once there is no way for the recieving end to distinguish a DOS attack from a legitimate mass mailing unless they have white listed the origin IP. Unfortunately it is easy to spoof the
From:e-mail address... so the only way for a systems administrator to 'white list' is to use the IP of the sending server. The addresses contained in the'Received: from'header can also be spoofed if passing through a relay. -
Hmmmm Your not sending 2,000,000+ e-mails all at once are you? Back in the 1990's I was administering some high-load Unix servers and when I performed daily/weekly mailings to site members I would send A-D and wait 15 minutes then send E-H and so forth to avoid being blacklisted. When you send millions of e-mails all at once there is no way for the recieving end to distinguish a DOS attack from a legitimate mass mailing unless they have white listed the origin IP. Unfortunately it is easy to spoof the
From:e-mail address... so the only way for a systems administrator to 'white list' is to use the IP of the sending server. The addresses contained in the'Received: from'header can also be spoofed if passing through a relay.With many of the big email providers they don't block on the basis of the number of messages per hour or minute or second, but by the concurrent connections. It’s a juggling act here to try and keep our addresses clean to make sure everything gets through. To answer your question though, no we don't send out to everyone at the same time. Although, I sure would like to send them out all at once. :) Yes, Server side whitelisting goes either by domain or more often by IP. Domain and email level whitelisting is still something that needs to happen on the user end though as most places have implemented user defined whitelists. These are typically not done by IP.