[Mailman-Users] Giving Non-Administrator Access To Simple Admin Functions
Hello, I am currently administering a small Mailman 2.11 list for our volunteer organization. Another individual needs the basic ability to subscribe, unsubscribe and possibly list members. This person thinks that they are a lot more computer literate than they are and I don't want to give them the password to the web configuration interface for fear that they will mess something up that will take me hours to figure out and fix. I am an embedded hardware engineer and not a programmer but I am careful enough not to change settings or list parameters without thoroughly testing the changes. So far I have managed to stay out of trouble! :-) Is it possible to do these rudimentary functions via the e-mail interface? If so can you point me to some documentation on how to do this? The only information I have found on the email interface seems to be directed to an individual user changing their own parameters and not to admin functions. Would I then have to add this person as an administrator and then just not tell them about the other email commands or the existence of the web interface? Any other suggestions? Thanks, Steve P.S. These admins and users are all on Windows boxes so any solution cannot be Linux specific. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Correct Syntax For SUBSCRIBE Email Command
Hello, Sorry for the stupid question but the documentation shows no examples and I am getting tired of playing 20 guesses with Mailman and always loosing. How do I make the following work? - subscribe address= "John Q Public" <[EMAIL PROTECTED]> YIELDS: The results of your email command are provided below. Attached is your original message. - Results: Bad digest specifier: "John - Done. According to the Help password and digest are optional yet it seems to want digest. Are commands case sensitive? Are extra spaces a problem and if so where? I want to include a name to go along with the email address. The web interface seems to be content with the above address format. Unfortunately, the user doing the subscribing will not be an administrator and will not have access to the web interface. Thanks, Steve -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Connecting Mailman to a Web Page
Mailman Gurus, I am currently doing volunteer work for a small non-profit organization. Our web site host (RTPnet.org) also offers Mailman e-mail lists as part of the hosting package. Therefore we don't have server access to Mailman other than as a user with lists setup. The organization has a "chat" Mailman list. Currently the list administrator is manually adding users to this list. However, we would like to allow the user to do this themselves by entering a name and email address in a box on one of the web pages. For Spam protection the list is setup to "confirm" all subscriptions. Can any of you offer suggestions or point to resources of how to do this from a web page? There doesn't seem to be any info or pointers to resources on the Mailman site as to how to do this. Thanks, Steve -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Connecting Mailman to a Web Page
Mark, Thanks for the pointer it does look pretty easy. Next stupid question... Are all of these Mailman variables and uses documented in one place somewhere or is it best to just reverse engineer an example web page that has the functionality that you need? Thanks, Steve At 08:32 AM 11/5/2008 -0800, Mark Sapiro wrote: Steve Lund wrote: > >Can any of you offer suggestions or point to resources of how to do this >from a web page? There doesn't seem to be any info or pointers to resources >on the Mailman site as to how to do this. See the FAQ at <http://wiki.list.org/x/hIA9>. -- Mark Sapiro <[EMAIL PROTECTED]>The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Mailing List Bounce Issues
Hello, I am the mailing list administrator for a charity cycling team. The list currently has about 150 members. The list and our website is hosted by a local ISP who is running Mailman 2.1.34. We seem to be having all too frequent occurrences of multiple bounces that seem to be related only to the domain of the address recipient. Previously we have had issues with AOL.com and Mindspring.com email domains. The main result of these are disabled subscriptions due to excessive bounces. The latest in this continuing saga occurred on Monday morning when I received notification that 12! list members with Yahoo.com email domain addresses had been unsubscribed from the list! I am assuming that this is the sum total of ALL yahoo addresses in our list. The interesting thing about this occurrence other than losing the name associated with the email address (since the members were unsubscribed not just disabled) is that I NEVER received ANY bounce notifications other than the unsubscribe notification. I find this quite odd and unsettling considering that the list shows that it IS configured to send earlier bounce notifications and I have received them in the past... just not leading up to this latest incident. The typical error message is: jonxx_daj...@yahoo.com has been removed from MSing-ride. (disabled address) So I guess that my question is whether or not these types of problems are now endemic to all email lists or ifOur ISP is technically "challenged" and 1. Doesn't know how to properly configure Mailman to send out the requested notifications. 2. Continues to get blacklisted for sending SPAM even though they don't. Thanks for any insight. Steve -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Re: Mailing List Bounce Issues
Mark, ...And everyone else who replied, yes, this does indeed look like a DMARC issue. I looked at the help pages and it looks like some things can be changed but from what I gather any changes would likely affect functionality for the users. I am a member of a different list that munged the FROM header to the list address with the down side that ALL replies had to go back through the list even if it was specific to one individual. Not a great experience just to pick up a few members who had AOL email domains. I'll forward the help pages to our ISP list admin to see if he has any thoughts on changes that might help but not restrict functionality. Thanks, Steve On Wed, Jan 27, 2021 at 2:12 PM Mark Sapiro wrote: > On 1/26/21 5:57 PM, steve lund wrote: > > > > We seem to be having all too frequent occurrences of multiple bounces > that > > seem to be related only to the domain of the address recipient. > > > As pointed out in another reply, this is likely a DMARC issue and MM > 2.1.34 has settings to mitigate this. > > > > The interesting thing about this occurrence other than losing the name > > associated with the email address (since the members were unsubscribed > not > > just disabled) is that I NEVER received ANY bounce notifications other > than > > the unsubscribe notification. I find this quite odd and unsettling > > considering that the list shows that it IS configured to send earlier > > bounce notifications and I have received them in the past... just not > > leading up to this latest incident. The typical error message is: > > > > jonxx_daj...@yahoo.com has been removed from > > MSing-ride. (disabled address) > > > That occurred after the users delivery was disabled by bounce and the > notices to the user were exhausted. When the delivery was first > disabled, (three weeks earlier with default bounce settings) there was a > notice sent to the list admins about the disable if the list's admin > Bounce processing -> bounce_notify_owner_on_disable setting is Yes. > > Also, you can set Bounce processing -> > bounce_notify_owner_on_bounce_increment to Yes to be sent a notice when > a bounce is received that increments the score. > > If one or both of these settings is Yes and you aren't receiving the > notices, that's between Mailman's MTA and you. > > > > So I guess that my question is whether or not these types of problems are > > now endemic to all email lists or ifOur ISP is technically > "challenged" > > and > > > > 1. Doesn't know how to properly configure Mailman to send out the > requested > > notifications. > > > Since you got the unsub notice, I'd expect that all requested notices > have been sent. > > > > 2. Continues to get blacklisted for sending SPAM even though they don't. > > > What are your settings under Privacy options... -> Sender filters for > dmarc_moderation_action and dmarc_quarantine_moderation_action? at a > minimum, they should be Munge From and Yes respectively. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, Californiabetter use your sense - B. Dylan > -- > Mailman-Users mailing list -- mailman-users@python.org > To unsubscribe send an email to mailman-users-le...@python.org > https://mail.python.org/mailman3/lists/mailman-users.python.org/ > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: > https://www.mail-archive.com/mailman-users@python.org/ > https://mail.python.org/archives/list/mailman-users@python.org/ > -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Re: Mailing List Bounce Issues
Mark, On Fri, Jan 29, 2021 at 10:36 AM Mark Sapiro wrote: > On 1/29/21 5:38 AM, steve lund wrote: > > > > ...And everyone else who replied, yes, this does indeed look like a DMARC > > issue. I looked at the help pages and it looks like some things can be > > changed but from what I gather any changes would likely affect > > functionality for the users. > > > > I am a member of a different list that munged the FROM header to the list > > address with the down side that ALL replies had to go back through the > list > > even if it was specific to one individual. Not a great experience just to > > pick up a few members who had AOL email domains. > > > Is this a Mailman list? Both Mailman 2.1 and Mailman 3 take pains to > create Munged From messages which exhibit the same behavior for 'reply' > and 'reply-all' as non-munged messages. Here's what we say: > I don't know if it was a Mailman list or not. This was 2-3 years ago. I looked at a current list message and there is no indication of the list sender. Is there any way that I can send a query to get this information? > > # MAS: We need to do some things with the original From: if we've > munged > > # it for DMARC mitigation. We have goals for this process which are > > # not completely compatible, so we do the best we can. Our goals > are: > > # 1) as long as the list is not anonymous, the original From: address > > #should be obviously exposed, i.e. not just in a header that MUAs > > #don't display. > > # 2) the original From: address should not be in a comment or display > > #name in the new From: because it is claimed that multiple > domains > > #in any fields in From: are indicative of spamminess. This means > > #it should be in Reply-To: or Cc:. > > # 3) the behavior of an MUA doing a 'reply' or 'reply all' should be > > #consistent regardless of whether or not the From: is munged. > > # Goal 3) implies sometimes the original From: should be in Reply-To: > > # and sometimes in Cc:, and even so, this goal won't be achieved in > > # all cases with all MUAs. In cases of conflict, the above ordering > of > > # goals is priority order. > > I.e. preserving 'reply' and 'reply all' behavior is goal 3, but note > that "this goal won't be achieved in all cases with all MUAs". > > I.e. some MUAs that don't follow RFC recommendations for replying may > not reply appropriately. This is an MUA issue. Mailman is doing the best > it can. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, Californiabetter use your sense - B. Dylan > -- > Mailman-Users mailing list -- mailman-users@python.org > To unsubscribe send an email to mailman-users-le...@python.org > https://mail.python.org/mailman3/lists/mailman-users.python.org/ > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: > https://www.mail-archive.com/mailman-users@python.org/ > https://mail.python.org/archives/list/mailman-users@python.org/ > -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Re: Mailing List Bounce Issues
ion: 2.1.34 Precedence: list List-Id: MSing Links Ride Announce / Chat List < msing-ride.lists.msinglinks.org> List-Unsubscribe: <https://lists.msinglinks.org/mailman/options/msing-ride>, <mailto:msing-ride-requ...@lists.msinglinks.org?subject=unsubscribe> List-Archive: <https://lists.msinglinks.org/mailman/private/msing-ride/> List-Post: <mailto:msing-r...@lists.msinglinks.org> List-Help: <mailto:msing-ride-requ...@lists.msinglinks.org?subject=help> List-Subscribe: <https://lists.msinglinks.org/mailman/listinfo/msing-ride>, <mailto:msing-ride-requ...@lists.msinglinks.org?subject=subscribe> From: Donald Belk via MSing-ride Reply-To: Donald Belk Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: msing-ride-boun...@lists.msinglinks.org Sender: MSing-ride = On Sun, Jan 31, 2021 at 12:46 PM Thomas Coradeschi via Mailman-Users < mailman-users@python.org> wrote: > > > On 30 Jan 2021, at 5:22 PM, steve lund wrote: > > > > Mark, > > > > On Fri, Jan 29, 2021 at 10:36 AM Mark Sapiro wrote: > > > >> On 1/29/21 5:38 AM, steve lund wrote: > >>> > >>> ...And everyone else who replied, yes, this does indeed look like a > DMARC > >>> issue. I looked at the help pages and it looks like some things can be > >>> changed but from what I gather any changes would likely affect > >>> functionality for the users. > >>> > >>> I am a member of a different list that munged the FROM header to the > list > >>> address with the down side that ALL replies had to go back through the > >> list > >>> even if it was specific to one individual. Not a great experience just > to > >>> pick up a few members who had AOL email domains. > >> > >> > >> Is this a Mailman list? Both Mailman 2.1 and Mailman 3 take pains to > >> create Munged From messages which exhibit the same behavior for 'reply' > >> and 'reply-all' as non-munged messages. Here's what we say: > >> > > > > I don't know if it was a Mailman list or not. This was 2-3 years ago. I > > looked at a current list message and there is no indication of the list > > sender. Is there any way that I can send a query to get this information? > > Look at the message headers - if it’s a mailman list, you should find > > X-Mailman-Version: xx.yy.zz > > > — > Tom Coradeschi > tjc...@icloud.com > > -- > Mailman-Users mailing list -- mailman-users@python.org > To unsubscribe send an email to mailman-users-le...@python.org > https://mail.python.org/mailman3/lists/mailman-users.python.org/ > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: > https://www.mail-archive.com/mailman-users@python.org/ > https://mail.python.org/archives/list/mailman-users@python.org/ > -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Re: Mailing List Bounce Issues
Mark, On Mon, Feb 1, 2021 at 12:18 AM Mark Sapiro wrote: > On 1/31/21 6:42 PM, steve lund wrote: > > Tom, > > > > Good point. It has been a LONG time since I wandered into attempting to > > read email headers. Here is a sample header from the list that recently > had > > the domain related bounce issue Let me know if you see anything that is > > mis-configured. BTW, the ISP is going to switch to the current Mailman > > version 3 fairly soon. I don't know if this is going to help the > situation > > or not. > > > Probably not. > > > > > > ... > > From: Donald Belk via MSing-ride > > Reply-To: Donald Belk > > And the From: is munged by the list and the original From: added to > Repty-To: > > > So this list is Munging From: headers, and if that was the case when the > bounces occurred (maybe 3 weeks before the unsubscribes), the bounces > probably weren't for DMARC reasons. > I don't believe that the ISP changed the list configuration recently. So if this is NOT a DMARC issue then any other thought as to what it could be? Also remember that for some unexplained reason I, as the list manager, didn't receive the intervening bounce messages either. I don't know if these tripped Gmail's "throw it out" SPAM filter or something else happened. While troubleshooting this the ISP guy subscribed one of his bogus email addresses to the list to see if I would get the bounce messages. So far I did get one of them but Gmail put it in my SPAM box. I drug the message to my Forums tab where hopefully when it happens again I will see it. Thanks, Steve -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Re: Mailing List Bounce Issues
Mark, On Mon, Feb 1, 2021 at 12:05 PM Mark Sapiro wrote: > On 2/1/21 6:07 AM, steve lund wrote: > > > > I don't believe that the ISP changed the list configuration recently. So > if > > this is NOT a DMARC issue then any other thought as to what it could be? > > > DMARC mitigations are list settings set by the list admin (you) via the > web admin UI, not by the ISP. > Found that page. It was set to Munge. > > > Also remember that for some unexplained reason I, as the list manager, > > didn't receive the intervening bounce messages either. I don't know if > > these tripped Gmail's "throw it out" SPAM filter or something else > > happened. > > > Go to the web admin UI Bounce Processing page. Are all the notifications > set to Yes? If so, and you are not receiving The notification on disable > or the notification on bounce increment if that is on, and your address > is correct for owner on the General Options page, then see below. > > > > While troubleshooting this the ISP guy subscribed one of his bogus email > > addresses to the list to see if I would get the bounce messages. So far I > > did get one of them but Gmail put it in my SPAM box. I drug the message > to > > my Forums tab where hopefully when it happens again I will see it. > > > So it seems the notices are being sent and delivered to your spam > folder. You will need to regularly check that folder for these messages, > or you MAY (I'm not an expert on this) be able to create a filter in > Gmail to deliver them to some other folder, assuming Gmail filters trump > `spam`. For purposes of filtering, these messages are > > From: mailman@ > To: -owner@ > Subject: Bounce action notification > Previously, i.e. 6 months ago I was getting these notifications just fine through my Gmail account. This tells me that the list config is correct. I can't explain why these went from no bounce notifications only unsubscribe to now being sent to SPAM folder. Seems like Google is mucking about with its filters! > These notices contain a copy of the bounce DSN and are the only way > short of MTA logs that you will know why the messages are bouncing. > > If I had to guess though, the next most likely thing after DMARC is the > sending server was blacklisted by some recipient domains. > This is what I was afraid of. Is there any way of confirming or denying that this is happening. ISP guy complained about having to tell Yahoo the mail server was a mail list and not SPAM. This would tell me that it was a blacklist problem. So how does an ISP keep their mail server OFF of the SPAM blacklist? Thanks, Steve > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, Californiabetter use your sense - B. Dylan > -- > Mailman-Users mailing list -- mailman-users@python.org > To unsubscribe send an email to mailman-users-le...@python.org > https://mail.python.org/mailman3/lists/mailman-users.python.org/ > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: > https://www.mail-archive.com/mailman-users@python.org/ > https://mail.python.org/archives/list/mailman-users@python.org/ > -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Re: Mailing List Bounce Issues
Mark, On Mon, Feb 1, 2021 at 10:14 PM Mark Sapiro wrote: > On 2/1/21 6:25 PM, steve lund wrote: > > On Mon, Feb 1, 2021 at 12:05 PM Mark Sapiro wrote: > >> > >> So it seems the notices are being sent and delivered to your spam > >> folder. You will need to regularly check that folder for these messages, > >> or you MAY (I'm not an expert on this) be able to create a filter in > >> Gmail to deliver them to some other folder, assuming Gmail filters trump > >> `spam`. For purposes of filtering, these messages are > >> > >> From: mailman@ > >> To: -owner@ > >> Subject: Bounce action notification > >> > > > > Previously, i.e. 6 months ago I was getting these notifications just fine > > through my Gmail account. This tells me that the list config is correct. > I > > can't explain why these went from no bounce notifications only > unsubscribe > > to now being sent to SPAM folder. Seems like Google is mucking about with > > its filters! > > > Probably so, but you can't control that. It may have to do with the > specific content of the notices or not. You could try setting up a gmail > filter on some of the above the put the message in another folder, or > just check your spam folder often. > > > >> If I had to guess though, the next most likely thing after DMARC is the > >> sending server was blacklisted by some recipient domains. > >> > > > > This is what I was afraid of. Is there any way of confirming or denying > > that this is happening. ISP guy complained about having to tell Yahoo the > > mail server was a mail list and not SPAM. This would tell me that it was > a > > blacklist problem. > > > > So how does an ISP keep their mail server OFF of the SPAM blacklist? > > > This is all up to the ISP. They can see in their mail logs if they are > being blocked and if they are competent, they will notice that and do > whatever need to be done to get the blocks removed. > Episodes like this last one make me question their competency. > The only thing you can do is report to the ISP if you get a bounce > notice that indicated the sending IP is blocked. > What does this message typically look like? I don't recall seeing "IP is blocked" in bounce messages. > I suggest you ensure that all the notifications including > bounce_notify_owner_on_bounce_increment are set to Yes and monitor your > spam folder so you will at least be aware of any issue before user's > delivery is disabled > This option is set correctly. I'll keep checking my SPAM folder. Thanks, Steve -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, Californiabetter use your sense - B. Dylan > -- > Mailman-Users mailing list -- mailman-users@python.org > To unsubscribe send an email to mailman-users-le...@python.org > https://mail.python.org/mailman3/lists/mailman-users.python.org/ > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: > https://www.mail-archive.com/mailman-users@python.org/ > https://mail.python.org/archives/list/mailman-users@python.org/ > -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Re: Mailing List Bounce Issues
Mark, On Wed, Feb 3, 2021 at 12:07 AM Mark Sapiro wrote: > On 2/2/21 4:58 PM, steve lund wrote: > > > > On Mon, Feb 1, 2021 at 10:14 PM Mark Sapiro wrote: > > > >> The only thing you can do is report to the ISP if you get a bounce > >> notice that indicated the sending IP is blocked. > >> > > > > What does this message typically look like? I don't recall seeing "IP is > > blocked" in bounce messages. > > > > The notices you get from Mailman about bounce scores being incremented > or delivery disabled due to bounce have the original delivery status > notification (DSN) attached. If the reason is that the sending IP is > blocked or on a block list, it will say that. Other possibilities > include that the recipient server refused to talk or the connection > timed out. > I'll keep a lookout for those and may return with specifics if /when this problem resurfaces. Thanks, Steve > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, Californiabetter use your sense - B. Dylan > -- > Mailman-Users mailing list -- mailman-users@python.org > To unsubscribe send an email to mailman-users-le...@python.org > https://mail.python.org/mailman3/lists/mailman-users.python.org/ > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: > https://www.mail-archive.com/mailman-users@python.org/ > https://mail.python.org/archives/list/mailman-users@python.org/ > -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Fatal Bounces ONLY on ATT (Bellsouth).NET
Hello, It appears to be starting again for our list. Fatal bounces but ONLY on ATT.net. Here is what Google says: DMARC and DKIM passed. However, this may have been the bounce message to me. Below is the bounce message to me. I see a DKIM Pass and a DKIM Fail. Can anyone shed any other light as to why these ATT addresses are ALL failing? Thanks, Steve = Delivered-To: slund...@gmail.com Received: by 2002:a50:379b:0:0:0:0:0 with SMTP id a27csp1420942ecc; Fri, 12 Mar 2021 08:50:47 -0800 (PST) X-Google-Smtp-Source: ABdhPJxug5H8zWZ5WehgGW9Eo2BCkOq6QQzbXrn/8EFInEkMsX0u4V54vXbKmVBEgeBkxHx/pQXm X-Received: by 2002:a25:3b04:: with SMTP id i4mr20275766yba.160.1615567847574; Fri, 12 Mar 2021 08:50:47 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1615567847; cv=none; d=google.com; s=arc-20160816; b=WmCMJ6Dp1O7rScSP4Bssq3+Fucf35qP2E92CDWxOyGylprCDHyG2yby3aL1qBG2YyN vItFfsISDwChuVWeg4ULb27WDDEVyDdYAKPcbEfoSyWxdJLUmPl2R4XpZr/Vw4/1U1eT MiW1Y3HLISbcOHLoVw3S2gFIY1bIrI8knZhUb4HGsXU6VvN/nLNQeRg0vMVJLKKw3m7v elEUTYotNQFApx/JLZzhrkoZgextRdvGaxOKC21yUWeaVoVc0P30pc00JNP/PdNlXQ0M Tyd0gIdrvzZSywS0lW33S/zwNklbBwONgRBC3tr23e2kBTKC8q+KI32JCXk9VHOsrHXH uejw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=sender:errors-to:list-id:precedence:date:message-id:mime-version:to :from:subject:dkim-signature:delivered-to:dkim-signature; bh=+KoYLe/u2BsMykVMJTWEbIVkHJSjKpwBokxJFqNz2Rc=; b=tRtbwMpdiAAHapKX3NhVtKYYQo5jZrWdMYymgFmWmi8XIh9w7Nv3slRD4C1x15xkI8 6OYzFWDkiKiXKC2uqN9zk0C/KGdhGciTAiUocBE9JpQbkUaDXHPb97v31dfSHu6rVVNN wn1o37HJcRqbD9to2sEfMR0izZzTIshSdLLDWeSj3S1Y9MVdZoV92eXNgeLQ9sIpn0Vz WSEPJALVxfxmZ00RGr+XyTbMpfs0Q+gpnfa+/QIltGIqU1WEDs0I23Flotp+LIRPwawG 6TDuAzIaBOJIo6Z4jM0ELWQGcKJSanQp1sq1OkoG+vfnVvy2dTwO/ie2wMN1NAS/iyiq 7vMg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@msinglinks.org header.s=201912 header.b=Opkav72l; dkim=fail header.i=@msinglinks.org header.s=201912 header.b=luOWzzsL; spf=pass (google.com: domain of mailman-boun...@lists.deltaforce.net designates 45.33.97.191 as permitted sender) smtp.mailfrom=mailman-boun...@lists.deltaforce.net; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=lists.msinglinks.org Return-Path: Received: from duke.deltaforce.net (duke.deltaforce.net. [45.33.97.191]) by mx.google.com with ESMTP id z131si5470913yba.182.2021.03.12.08.50.47 for ; Fri, 12 Mar 2021 08:50:47 -0800 (PST) Received-SPF: pass (google.com: domain of mailman-boun...@lists.deltaforce.net designates 45.33.97.191 as permitted sender) client-ip=45.33.97.191; Authentication-Results: mx.google.com; dkim=pass header.i=@msinglinks.org header.s=201912 header.b=Opkav72l; dkim=fail header.i=@msinglinks.org header.s=201912 header.b=luOWzzsL; spf=pass (google.com: domain of mailman-boun...@lists.deltaforce.net designates 45.33.97.191 as permitted sender) smtp.mailfrom=mailman-boun...@lists.deltaforce.net; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=lists.msinglinks.org Received: from duke.deltaforce.net (localhost [IPv6:::1]) by duke.deltaforce.net (Postfix) with ESMTP id CDD5B200BF for ; Fri, 12 Mar 2021 11:50:09 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=msinglinks.org; s=201912; t=1615567809; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:list-id; bh=+KoYLe/u2BsMykVMJTWEbIVkHJSjKpwBokxJFqNz2Rc=; b=Opkav72lpDlC1h0cnXJ0CHa+SFiP6Vkx2Lhpsq7N1eHULm2tXll7tWnFV5X1durZ+jA8C6 T5cRp+tdVf4VtlRexP1N9Wt3Owj+mGrSogLR1P5TyMqKe6A6d5Ig0L1pM8DLMIGEoSpa/1 NkgQPhsfgDKVtagW0D89jKBwbKL0lvU= X-Original-To: msing-ride-ow...@lists.msinglinks.org Delivered-To: msing-ride-ow...@duke.deltaforce.net Received: from duke.deltaforce.net (localhost [IPv6:::1]) by duke.deltaforce.net (Postfix) with ESMTP id 90BDF20082 for ; Fri, 12 Mar 2021 11:50:08 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=msinglinks.org; s=201912; t=1615567808; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:list-id; bh=+KoYLe/u2BsMykVMJTWEbIVkHJSjKpwBokxJFqNz2Rc=; b=luOWzzsLIEg5lxOvmSlgeC2wmzOQyuznZo9grRuS9Kduzw8JjY7Fp3VmadXRpWCVnGQzhU rxACCrJ6N7udOrBVG2Fwbu/lUwheDOGYB4J0fq5BPZO0Ti596Fp6o+XNMThfVZGak+LVBZ cCR4DZAfSeU6itv6ZSMb3fG8gV73rRk= Subject: Bounce action notification From: mail...@lists.msinglinks.org To: msing-ride-ow...@lists.msinglinks.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===0332406003479489569==" Message-ID: Date: Fri, 12 Mar 2021 11:50:06 -0500 Precedence: list X-Bee
[Mailman-Users] Re: Fatal Bounces ONLY on ATT (Bellsouth).NET
Mark, Thanks for your response. So ATT is apparently blocking the email server of our website host.I have notified our web host so hopefully something good will happen eventually. BTW, so what is this "Registering" an email server with an ISP domain? I assume that it is basically telling them that it is a legitimate email server. Is it worthwhile trying to get our web host to do this or a waste of time? I guess has anyone seen positive results from doing so? Thanks, Steve On Sat, Mar 13, 2021 at 11:00 AM Mark Sapiro wrote: > On 3/12/21 1:39 PM, steve lund wrote: > > Hello, > > > > It appears to be starting again for our list. Fatal bounces but ONLY on > > ATT.net. Here is what Google says: > ... > > > <...@att.net>: host ff-ip4-mx-vip1.prodigy.net[144.160.159.21] said: 553 > > 5.3.0 flpd599 DNSBL:RBL 521< 45.33.97.191 >_is_blocked.For assistance > > forward this error to abuse_...@abuse-att.net (in reply to MAIL FROM > > command) > > > It may be a coincidence, but I started seeing the same bounces on one of > my servers (thankfully not mail.python.org or lists.mailman3.org) about > two days ago. > > ATT is blocking your IP. > > In my case, I sent this to abuse_...@abuse-att.net. > > > You are blocking all mail from IP 138.68.52.125 per this log message. > > > > Mar 12 09:59:32 grizz postfix/smtp[10965]: D0CAF1F8123: > > to=<...>, > > relay=ff-ip4-mx-vip2.prodigy.net[144.160.159.22]:25, delay=0.38, > > delays=0.1/0/0.27/0.01, dsn=5.3.0, status=bounced (host > > ff-ip4-mx-vip2.prodigy.net[144.160.159.22] said: 553 5.3.0 flph832 > > DNSBL:RBL 521< 138.68.52.125 >_is_blocked.For assistance forward this > > error to abuse_...@abuse-att.net (in reply to MAIL FROM command)) > > > > This mail is from an opt-in email discussion list or other business > > related mail from a bicycle club. We do not send spam or unsolicited > > commercial email. Please remove this block. > > > I received this reply. > > > Thank you for contacting the AT&T Postmaster Staff. > > > > We investigate every block report and removal request we > > receive and take the appropriate action, of which you will > > be notified. It is never the intention of the AT&T > > Postmaster staff to block legitimate mail. It is a rare > > but unfortunate occurrence that legitimate correspondence > > is blocked as a result of careful yet vigorous anti-spam > > and abuse countermeasures. We would like to rectify your > > mail delivery issue as soon as possible with your help. By > > emailing this address you have already taken the first > > step in resolving this issue. > > > > When the AT&T Postmaster staff receives a request with the > > needed information requests are evaluated. If granted, the > > block will be removed within 24 to 48 hours. There are > > situations when mail interruptions or blocks are in place > > outside the AT&T domain. In these cases, we will attempt > > to make contact with the party initiating the block and > > seek a resolution. If there is no change after 48 hours > > please include the current and complete error message that > > you are receiving in your follow up email to > > . > > > > For more information about email best practices and mail > > delivery issues visit: > > > > https://www.att.com/esupport/postmaster/ > > > > We reserve the right to deny or turn down a request if our > > research shows the requested IP(s) being a violator of > > SPAM or abuse policies currently, or in the past. > > > > We at AT&T thank you for your assistance in reporting this > > matter and appreciate your patience while we investigate > > this issue. > > > > AT&T Postmaster Staff > > As of 03:30 PST this morning the block had not been removed. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, Californiabetter use your sense - B. Dylan > -- > Mailman-Users mailing list -- mailman-users@python.org > To unsubscribe send an email to mailman-users-le...@python.org > https://mail.python.org/mailman3/lists/mailman-users.python.org/ > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: > https://www.mail-archive.com/mailman-users@python.org/ > https://mail.python.org/archives/list/mailman-users@python.org/ > -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Re: Fatal Bounces ONLY on ATT (Bellsouth).NET
Steve, Thanks for the info. I'll check with out web host / mail provider. Thanks, Steve On Sun, Mar 14, 2021 at 10:46 AM Stephen J. Turnbull < turnbull.stephen...@u.tsukuba.ac.jp> wrote: > steve lund writes: > > > BTW, so what is this "Registering" an email server with an ISP > > domain? > > What it says. Other than putting your domain and IP on a list, I know > of no policy that's common to most such programs. :-( > > > Is it worthwhile trying to get our web host to do this > > In general, yes. Some ISPs have provided services such as reports on > issues related to your domain or IP as a sender, and while history > suggests that they think that their users get a lot madder about one > spam message than they do about one undelivered mail, users do care > about lost mail. I'm sure they genuinely intend these programs to > help your mail get through to subscribers at their services. (I don't > know if any currently offer such services to registered domains.) > > The ones that are reasonably good at this are providers like Gmail, > Yahoo!, and O365, whose business model (at least at one time) involved > provision of excellent email hosting. > > There is some administrative effort required, so you could check what > domains your subscribers are using and see if they have registration > programs, what information they want, and what benefits they offer > when you approach your host. This is the kind of thing that > experienced mail hosting services do for you; you may find that they > already do this "in general", and haven't registered with ATT only > because ATT doesn't have a program. :-( > > Steve > > -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
