Thanks, Dave. How are you coping with yahoo emails if you've only got 2.1.17? I can't remember what changes it's got in it, but I thought the latest dealt with it better.
Peter Shute Sent from my iPad > On 22 Jul 2014, at 3:59 am, "Dave Nathanson" <dave.li...@nathanson.org> wrote: > > 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 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/archive%40jab.org
