[Mailman-Users] Re: AOL list member not receiving list traffic
I'm having a similar struggle with sbcglobal.net & ATT.net addresses - They are rejecting our list mail with a reject notice, but let individual messages through. I have different outgoing server for mailman. My servers are hosted at Dreamhost, who generally has very helpful support, but in the past 3 weeks they are not able to convince sbcglobal & att to let our mail through because they banned our IP block. I did set Mailman to give me notice for each bounce notification so I could see what was going on, and when the bounce counters were incremented. That helped me be more aware. Immensely frustrating, as almost half of our list members have sbcglobal or ATT & are losing contact with our group. Best, Dave Nathanson Mac Medix > On Aug 26, 2022, at 10:36 PM, Jayson Smith wrote: > > Hi, > > Yesterday I received a report from an AOL user that she's not receiving > traffic from one of my lists. The problem here is that my server logs show > outgoing mail being accepted by AOL's incoming mail servers, and of course > after that it's anyone's guess what happens to them. She says she's checked > her junkmail folder and the messages aren't there. Does anyone have any > thoughts on this? Is AOL known to silently discard mail they think is spam > for some reason? I replied to her message from the same server and she did > receive that reply, so they haven't outright blocked my IP or something. Even > if I could contact someone who knows what they're doing at AOL, there are no > error logs for me to show. > > > Jayson > > > -- > 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] Making a Case for Upgrading MailMan from 2.1.17
I'd like some help in making a case to convince my hosting company to upgrade from Mailman 2.1.17. I run several email lists for clubs, these are discussion lists that get up to 20 messages per day, and include up to 150 members. Replies are directed back to the list. My primary issue with MM 2.1.17 is about list messages from members who don't have their human names configured into their email clients, resulting in a list message from an unknown. It is just from "via listname <listn...@example.com>" Since I'm still stuck on 2.1.17. I don't know what I am missing in the newer versions. I just know that it's been over 2 years since 2.1.17 which has an annoying omission due the the whole DEMARC thing. What are the advantages of upgrading beyond 2.1.17? How best to make a good case to convince them to upgrade their MailMan? What version should I ask for? Thanks! Dave Nathanson Mac Medix -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Erratic mail delivery times
Hi Peter, To answer your question, Dreamhost has the *almost* newest version of MailMan 2.1.17. They upgraded just as 2.1.18 came out and had already tested 2.1.17 so they went with that. And this version does have the most important DMARC mitigation features. So it is working for us. I have never had any problem with DreamHost imposing a message sending cap on their 1-Click installs of Mailman. I run several discussion lists there completely without incident, for 8 years Until this whole Yahoo/demarc mess. And we are back to normal. No host is perfect, but considering the low price all the unlimited everything they offer, I'm very happy with mine. Considering the price you have been paying, you will most likely need to pay more to get out of this problem, but maybe not much more. http://www.dreamhost.com/r.cgi?250640/hosting.html Best, Dave Nathanson Mac Medix On Jul 20, 2014, at 1:35 PM, Peter Shute psh...@nuw.org.au wrote: No, it's all hosted via cpanel. Does this mail per hour limit seem odd with that sort of setup? Does dreamhost keep their mailman up to date? We're still on 2.1.15, and when I asked about upgrading, they wouldn't commit to any date, only that it would be more likely to be months than a month. Peter Shute Sent from my iPad On 21 Jul 2014, at 1:35 am, Dave Nathanson dave.li...@nathanson.org wrote: I'm surprised that any web/email host would apply a rule intended for a personal email account to a listserve. I'm guessing that you are running MailMan on your own computer, then using mail server provided by your email hosting company to send the messages. So to the email host, you do look like a very busy personal account. As I see it, your options include: * Discuss this limitation with your email host see if they will waive the message sending cap for your listserv. * Use a mailman installation hosted by your email hosting company, which is not subject to a message sending cap. * Changing email hosts using a mailman installation hosted by your email hosting company, which is not subject to a message sending cap. No need to change registrars. NameCheap is a good registrar, better than many. I haven't used their web/email hosting. My email lists are all running on Mailman provided by my email host. You don't even need to install it, just choose a dedicated subdomain for it to run on. They do NOT limit message flow from Mailman, although they do limit the number of messages per hour sent from a personal mail account. No web/email host is perfect, but I'm pretty happy with DreamHost. Especially for about $100 a year for more services than I can possibly use. (And I'm giving it a good go!). Here is a Dreamhost Coupon code link that will give you $10 off now, plus 1 free LIFETIME domain registration. So that's a savings of about $11 a year for life. MACMEDIXFREEDOM What else is included? Tons! Check it out. http://www.dreamhost.com/r.cgi?250640/hosting.html Best, Dave Nathanson Mac Medix On Jul 20, 2014, at 4:38 AM, Russell Woodford rdwoodf...@gmail.com wrote: Hi Peter, Mark and all I think I may have the solution now (Peter is one of our list moderators). My web host is now telling me that there is a 200 emails per hour limit for my hosting plan. We have 1140 subscribers. That means we blow the limit out of the water EVERY time someone posts! I'm not sure why they have taken so long to tell me this, as we've been running on this host for over 7 months, but it seems they throttle the outgoing mail volume, so it can take a while for all those recipients to get each message. I suppose it depends on overall server activity - if nothing else is happening, then maybe a new message does get straight to 1140 recipients. Looks like we will need to shift to a new listserver and maybe even a new webhost - and maybe even a new domain registrar (I've had all my eggs in the Namecheap basket for some years now). Somehow I don't think I am going to get away with this volume of mail for the $50 a year I'm currently paying :-( Russell Woodford Geelong, Australia birding-aus.org On 18 July 2014 11:20, Mark Sapiro m...@msapiro.net wrote: On 07/17/2014 05:01 PM, Peter Shute wrote: I've now enabled protocol logging on our Exchange server, a new world for me. I can see several possibly relevant events in yesterday's logs that look like this: 2014-07-17T07:02:03.914Z,NUWVICMS2\Default NUWVICMS2,08D145520008BC68,24, 192.168.0.36:25,192.64.112.70:38732,,550 5.7.1 Requested action not taken: message refused, This is a 550 (extended 5.7.,1) status which is a permanent failure. This is a bounce and will (should) not be retried by the sending server. I doubt that this specific log message has anything to do with your delayed messages. But if the antispam software is refusing the messages, how do they eventually get through? Exactly. You
Re: [Mailman-Users] Erratic mail delivery times
I'm surprised that any web/email host would apply a rule intended for a personal email account to a listserve. I'm guessing that you are running MailMan on your own computer, then using mail server provided by your email hosting company to send the messages. So to the email host, you do look like a very busy personal account. As I see it, your options include: * Discuss this limitation with your email host see if they will waive the message sending cap for your listserv. * Use a mailman installation hosted by your email hosting company, which is not subject to a message sending cap. * Changing email hosts using a mailman installation hosted by your email hosting company, which is not subject to a message sending cap. No need to change registrars. NameCheap is a good registrar, better than many. I haven't used their web/email hosting. My email lists are all running on Mailman provided by my email host. You don't even need to install it, just choose a dedicated subdomain for it to run on. They do NOT limit message flow from Mailman, although they do limit the number of messages per hour sent from a personal mail account. No web/email host is perfect, but I'm pretty happy with DreamHost. Especially for about $100 a year for more services than I can possibly use. (And I'm giving it a good go!). Here is a Dreamhost Coupon code link that will give you $10 off now, plus 1 free LIFETIME domain registration. So that's a savings of about $11 a year for life. MACMEDIXFREEDOM What else is included? Tons! Check it out. http://www.dreamhost.com/r.cgi?250640/hosting.html Best, Dave Nathanson Mac Medix On Jul 20, 2014, at 4:38 AM, Russell Woodford rdwoodf...@gmail.com wrote: Hi Peter, Mark and all I think I may have the solution now (Peter is one of our list moderators). My web host is now telling me that there is a 200 emails per hour limit for my hosting plan. We have 1140 subscribers. That means we blow the limit out of the water EVERY time someone posts! I'm not sure why they have taken so long to tell me this, as we've been running on this host for over 7 months, but it seems they throttle the outgoing mail volume, so it can take a while for all those recipients to get each message. I suppose it depends on overall server activity - if nothing else is happening, then maybe a new message does get straight to 1140 recipients. Looks like we will need to shift to a new listserver and maybe even a new webhost - and maybe even a new domain registrar (I've had all my eggs in the Namecheap basket for some years now). Somehow I don't think I am going to get away with this volume of mail for the $50 a year I'm currently paying :-( Russell Woodford Geelong, Australia birding-aus.org On 18 July 2014 11:20, Mark Sapiro m...@msapiro.net wrote: On 07/17/2014 05:01 PM, Peter Shute wrote: I've now enabled protocol logging on our Exchange server, a new world for me. I can see several possibly relevant events in yesterday's logs that look like this: 2014-07-17T07:02:03.914Z,NUWVICMS2\Default NUWVICMS2,08D145520008BC68,24, 192.168.0.36:25,192.64.112.70:38732,,550 5.7.1 Requested action not taken: message refused, This is a 550 (extended 5.7.,1) status which is a permanent failure. This is a bounce and will (should) not be retried by the sending server. I doubt that this specific log message has anything to do with your delayed messages. But if the antispam software is refusing the messages, how do they eventually get through? Exactly. You could look at the logs on the 192.64.112.70 sending server to see what that server did with this message after it was bounced by the exchange server. If the Mailman server is sending directly to the exchange server and that is where the delays are occurring, you need to look at the MTA logs of the Mailman server and see what's there relevant to sending failures and resends. But, this thread no longer has anything to do with Mailman. Perhaps you could find another list/forum to discuss this that might be able to provide more expertise in this area. -- -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/dave.lists%40nathanson.org -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Who authored the message?
Hi Mark, We've got Mailman 2.1.17 at Dreamhost. List Settings: from_is_list = Mung From anonymous_list = No first_strip_reply_to = Yes reply_goes_to_list = Explicit address reply_to_address = almosteveryb...@example.com (without subdomain) Include_sender_header = Yes In this case, the message author MUA does not provide their display name, and the list _does_ have a real name for that person, but Mailman did not insert it. So after going through Mailman, the From header said only: Via almosteveryb...@list.example.com. Today I experimented with first_strip_reply_to set to No. This means that a reply is addressed to both the list and to previous author. If nodups = Yes. Then the previous author will get only 1 copy of the message. But the copy they get is the direct mail (including senders email address), not the list mail. When that person replies to the message, it will only go to the most recent previous author, not to the list. Maybe this is acceptable(?), since most of the time people don't reply to their own list messages? Im my experience, the majority of users are incapable of adding or deleting anything from the Reply-To or To field. That's why up to now, I've opted for the Reply-To to only contain the desired list address. Best, Dave Nathanson Mac Medix On May 12, 2014, at 9:32 PM, Mark Sapiro m...@msapiro.net wrote: On 05/12/2014 08:45 PM, Dave Nathanson wrote: I saw a message today sent to a list named AlmostEverybody. The message author did not properly configure their MUA (Verizon webmail) with their proper name, so the only identifier is their email address. Which is of course now deleted as part of DEMARC compliance. Leaving us with a message and no indication of who sent it. The From was merely Via almosteveryb...@list.example.com. No name, no author email address. Of course no sig either. What Mailman version are you using? In the current version (2.1.18-1) you should be seeing the either the author's display name from her From: header or if none and From: a list member, the members real name from the membership list, or if none, at least the local part of the email address. Also, the author's original From: will be in Reply-To: in every case, except see bug https://bugs.launchpad.net/mailman/+bug/1318025. List members are unable to reply off-list to the author, and they don't even know who the author is. Again, what is your Mailman version and what are your Reply-To munging settings. In versions older than 2.1.18, I think you should still see the author's address in Reply-To: if first_strip_reply_to is No. Would it be a reasonable feature request to add the author's name email address as a X-Header? Some of us not only read the headers on a regular basis, but we even configure our MUA to display certain message Headers. (My favorites are Reply-To, X-Mailer, and User-Agent). I don't think it's necessary. If the author's address isn't in Reply-To:, it should be, and the absence is a bug. Is that not sufficient? -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/dave.lists%40nathanson.org -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Who authored the message?
Since DEMARC we don't know who is authoring list messages anymore. I saw a message today sent to a list named AlmostEverybody. The message author did not properly configure their MUA (Verizon webmail) with their proper name, so the only identifier is their email address. Which is of course now deleted as part of DEMARC compliance. Leaving us with a message and no indication of who sent it. The From was merely Via almosteveryb...@list.example.com. No name, no author email address. Of course no sig either. List members are unable to reply off-list to the author, and they don't even know who the author is. Would it be a reasonable feature request to add the author's name email address as a X-Header? Some of us not only read the headers on a regular basis, but we even configure our MUA to display certain message Headers. (My favorites are Reply-To, X-Mailer, and User-Agent). I'd rather not add the author's email address to the top or bottom of the message body, but it seems that some method of identifying the message author is in order. Even if depreciated, X-Headers are obviously still in use, and better then nothing. At the very least adding one more message header won't cause any complaining. Thoughts? Best, Dave Nathanson Mac Medix -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Reply-To Munging - Feature Request
I appreciate that the MailMan team is awesome doing the best that can be expected given the new DMARC restrictions being forced on us all. Thanks guys! FEATURE REQUEST: A setting to configure the new From line. Instead of FROM: Author_Name via ListName listn...@lists.example.com I want to request that MailMan let the list admin config the text after the author's name in the FROM line. I would use this setting to say: FROM: Author_Name via Club Name listn...@example.com * substituted test string Club Name for List Name * substituted explicit reply_to_address instead of list address. More details: DreamHost just installed 2.1.17 so that's what I have to work with. I don't know why they didn't go all the way to the newest version this week. My email lists are served from a sub-domain that I don't use for anything except lists. lists.example.com That is a given, not my option. I have things figured out as well as can be for my situation. The settings we are going to use are: reply_goes_to_list = Explicit address reply_to_address = everyb...@example.com (as opposed to everyb...@lists.example.com ) from_is_list = Mung From first_strip_reply_to = Yes The only difference is from_is_list = Mung From. The other settings are the same as before DEMARC. This makes it almost as good as before Yahoo ruined all mailing lists worldwide. Differences before After DEMARC BEFORE: FROM: Author_Name aut...@example.com TO: ListName everyb...@example.com REPLY-TO: ListName everyb...@example.com We liked it like that. Everything was fine. AFTER DEMARC, using the best settings for us that we can: FROM: Author_Name via ListName everyb...@lists.example.com TO: ListName everyb...@example.com REPLY-TO: ListName everyb...@example.com This is *pretty good* except that * I don't like the via list name in the from header, even though I understand that is the new reality. * I don't like the lack of an author email address. I also tried: first_strip_reply_to = No But that means a normal reply will go to both the list the author. So the author will get 2 copies, and I don't feel that is desirable, even though it seems to be the only way to include the author's email address. FEATURE REQUEST: A setting to control the new From line. Instead of FROM: Author_Name via ListName everyb...@lists.example.com I want to request that it offer the option to let the list admin config what goes there after the author's name. I would use this setting to say: FROM: Author_Name via Club Name everyb...@example.com substituted Club Name for List Name, and used explicit reply_to_address instead of list address. Best, Dave Nathanson Mac Medix -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Scrubbing attachments only if over size limit - Umbrella list
I've spent almost 2 whole days reading the MailMan FAQ, Googleing and testing theories/methods with a set of test-lists. I am using MailMan 2.1.12 installed at DreamHost.com. I do not have root access. Although I can ssh into the server, I'm not good at writing shell scripts. Sorry if this looks long or wordy, I'm trying to give enough info to get some help. What I am trying to do is allow list members to post plain text, or html messages, and attachments up to a set size. Any attachments larger than that size, I'd like to be scrubbed and a link url inserted so the list members don't have to download some stupid cat video just to unclog their mail delivery, but those who love cat videos can just click the link and get it. I understand the attachment scrubbing feature. It is useful. But it will only scrub ALL messages not just those over a certain size. And it takes out the html that people are using so much more than they used to. Ideally, I would love to have the attachment scrubbing feature operate only on messages larger than a certain size. That would solve my entire problem. One of the lists I admin includes decidedly non-technical people who think nothing of forwarding 12 mb attachments. They don't understand why this is not allowed, and I'm getting tired of explaining it again. These same people are not interested (or capable) of uploading their large attachment to a server and emailing a link to the list. So I'm trying to help them, but without relaying huge attachments to the list. So after much reading, I got the idea of using an umbrella list set to scrub attachments to give users the option of sending their huge attachments and it will auto-generate a link. Lovely. But I'm not having success in implementation. Perhaps you can help me with this. I made 2 MailMan lists: * regular_list (restricted by size less than 2 mb). Has membership. * big_list (no size restriction), set to scrub attachments. No members, should send to/from the members of the regular list. Set to be an umbrella list. THEORY: The way I expect this to work is the list member will send his huge attachment to the regular_list, it bounces back, and tells him to try sending it to the big_list instead. This ought to scrub the attachment, leaving a URL instead, and lets the msg continue to the regular_list where it will now be well under the size restriction and pass through to all the members of regular_list. Am I on track? I just want 2 lists, with the exact same membership list, one to scrub attachments, and the other to reject oversize attachments. Both should only accept postings from list members. The problem is that the regular_list is not accepting messages addressed to the big_list. I searched the list archives and found some interesting info, but maybe I've read so much that I can't see or think straight anymore. I read the articles: 3.5. What is an Umbrella list - and why doesn't it do what I want? 3.69. How do I set up an umbrella list? But I have not been successful in getting the umbrella list concept to work. What is the trick? Is this possible? Is there a better way? What needs to be typed where? Thanks, Dave -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
