Bill, I have extensive experience getting email delivered in a commercial setting for our product that sends 1000s of status and report emails per day. While it is wrong to blame the actual recipient, delivery problems are almost always related to the recipient's email service, often an ISP of company.
We see this every day where we can see that our email servers have delivered the email to the recipient's email server and yet the user never has it delivered to his or her inbox. The usual reason is related to anti-spam measures that ISPs employ. Most now discard a good percentage of inbound email without even bothering to place it in a spam folder. Sometimes, like gmail does all the time, the email is quarantined either for a period of time or indefinitely pending manual release. This is often done to see if this is a an email that is being sent to many other recipients at the ISP, in which case it is probably spam. Others are more helpful, sending our servers a rejection message saying things line "Blacklisted" or "violates local email policy" or something similar. Other times it is a temporary error of some sort and we get rejections saying "excessive email rate", "user not found" or "mailbox full". We can often see that this is an error, because after some number of attempts or a few days, the "User is again found". My point is that in all these cases, the delivery is failing on the "user's side of the internet" even if they have no direct control of the receiving email server. And short of coordinating with the ISP to get whitelisted, there is not a lot the sender can do. Regards, - Brendon KK6AYI On Sat, Mar 19, 2016 at 5:37 AM, Bill <[email protected]> wrote: > I always chuckle how it is always the user's fault When the ISP chokes on > an email - the message you get is to "resend the proper password" - or some > such indicator that it is the user's fault. That appears to be the attitude > with this list. The problem is with the user. At least, that is how I would > interpret all those direct emails I received from other users. > > Got news - in this case (and most cases) it was not. > > This morning the list spit a bunch of messages out - but is still not > completely up to date. Nothing was done here to cause this. Hence, the > problem lies some place between the mailman.qth.net and the local ISP. > Makes me think that mail-archive.com has a propagation problem. This is > not an issue that will ever be solved by the user. > > Bill W2BLC K-Line > > ______________________________________________________________ > Elecraft mailing list > Home: http://mailman.qth.net/mailman/listinfo/elecraft > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:[email protected] > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html > Message delivered to [email protected] > ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[email protected] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [email protected]
