Rick, Since this topic is not all that relevant since it is being worked on, I just want to say that I would never advocate someone click on a link within an email. A link can say one thing and do something completely different. This is less true, though, when you reply to an email. It is good to double-check the address in the "TO" field of the message to which you are replying, but addresses in the "to" field are pretty much what they say they are. If a link within a message said "Click here to confirm," one should never do that. The mailman confirmations I have seen, though, don't do that. I will write more to you off list.
Best regards, Steve Jacobson -----Original Message----- From: Rick Thomas [mailto:[email protected]] Sent: Saturday, August 29, 2015 4:57 AM To: 'Steve Jacobson' <[email protected]>; 'Window-Eyes Discussion List' <[email protected]> Subject: RE: Anyone heard from AI Squared about their e-list problems and the detailed postings about potential causes and resolutions Hi Steve: First, For me clicking the Reinstate link in the e-mail telling me my account had been disable seemed to work. That said, it is risky to ever click on anything inside a e-mail message unless you are 100 percent sure who the sender was. Financial institutions include enough partial information in such a e-mail to ensure it is related to the actual sender and your account to avoid bad guys from spoofing, fishing or even trying to impart a virus on your machine in their name. After talking on list I was pretty sure the message was from AI Squared so did that after having tried to do it via the Website which I couldn't get to work - at least not quickly. Next,there is a process where the providers like Comcast, Brighthouse, Yahoo and most others will ping back any messages sent to them to see if it was sent from a valid, active, e-mail address and this, I think, is a part of the DKIM standards put in place and adopted since think around 2005. If a valid return is not received they will bounce back the message to your provider, usually also sending it through to the end point but sometimes flagging it as spam, sometimes not before it gets to the endpoint client. Your providers Mailman will get the postbacks, bounces, as a warning that there was a potential security issue with the message sent from your Mailman server and check the settings to see how to handle them. Unless setup to handle these bounces your providers Mailman will increment a counter depending on the bounceback level, hard or soft, for the person who tried to send the message through the providers Mailman server. If Mailman is configured to disable an account after a certain number of bounces your client will then be automatically disabled when that threshold has been reached. The bouncebacks your Mailman Provider is getting is thus likely due to the fact it is not setup to handle the ping backs, security tests, that the big providers use, gets their bounces even if they send the message through to the end user marked as spam, not marked as spam or the big provider might not even send it through but they all will generate a bounce back to your Mailman Provider if Mailman and your Host Provider are not setup properly. Of course, without having access to your providers hardware and software there is no way for me to either verify this nor fix it. This is what several folks have told me they have encountered in the past and others have told me the same thing and to look into the Domain thingy - I forget exactly what it is called but think the acronym was DKIM.This is not in my programming wheelhouse so I had to dig to find out what may be going on via the symptoms reported by everyone. It is a standard all the big e-mail host providers agreed to use from what I remember about that article I posted here much like the w3c standards or iso standards with a governing body and all that jazz. I know you are a pretty good programmer so take a look at things, Mailman Documentation and see what it says about bouncebacks and automatic removel of clients and settings, then read up on the DKIM thing, I will go find the actual name if you get stuck but the document was in one of my prior postings. If this is not the problem let me know so I wont be barking up the wrong tree. I wont get mad or hurt feelings, I just want to get the job done. Your fault, my fault, nobodys fault - just get it done is my philosophy. This may mean tweaking the software or even finding a new provider but many of us are on several other high traffic lists and don't have these problems. One other thing to look at not mentioned is that someone may have put your lists on a BlackList which some of the list providers look at - remember that hacker who didn't seem to like you guys? So you might peek at them to ensure your lists are not being black listed before stranggling your list provider. That's all I have unless there is anything I can look up or ask folks who actually know about this stuff, I don't know much myself but enough to ask questions that usually get answered by the folks I need to talk to. Rick USA _______________________________________________ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
