Re: Hyphenated Lists Stopped Working

Andrey Falko wrote:
>
>Lists with hyphens like, "-", no longer work. Postix has no trouble 
>delivering mail to these lists to the maildir, but the emails simply lie 
>in /var/lib/mailman/qfiles/maildir/cur/ and nothing appears to happen to 
>them..

The files in /var/lib/mailman/qfiles/maildir/cur/ probably have names
ending in '1:X' indicating a MaildirRunner processing error.

>Log files show nothing helpful:
>Aug 31 17:32:08 2007 (14022) 
><mailman.0.1188595927.11401.hyphen-ated <at> reservoir.com> smtp to 
>hyphen-ated for 1 recips, completed in 0.058 seconds
>Aug 31 17:33:12 2007 (14022) 
><mailman.0.1188595990.11581.hyphen-ated <at> reservoir.com> smtp to 
>hyphen-ated for 1 recips, completed in 0.040 seconds
>Aug 31 17:33:50 2007 (14022)
>Aug 31 17:33:10 2007 (11581) hyphen-ated: held subscription request from 
>falko <at> reservoir.com

There should be messages in Mailman's error log saying 'Message
apparently not for any list: %s' where the %s is replaced with the
name of the /var/lib/mailman/qfiles/maildir/cur/*1:X file.

The bottom line is there is a bug in MaildirRunner.py. It doesn't work
with hyphenated list names as it conflates the last part of the name
with the -bounces, -request, etc. suffixes.

--

-- 

Re: Hyphenated Lists Stopped Working

Mark Sapiro wrote:
>
>The bottom line is there is a bug in MaildirRunner.py. It doesn't work
>with hyphenated list names as it conflates the last part of the name
>with the -bounces, -request, etc. suffixes.

The attached MaildirRunner.patch.txt file contains a patch which I
think will fix this bug. I've tested the revised regexp somewhat and
it seems to work, but I would appreciate your trying the patch and
reporting the results.

Make a backup copy of Mailman/Queue/MaildirRunner.py, apply the patch
and restart Mailman.

--

-- 
Mark Sapiro <msapiro <at> value.net>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

--- MaildirRunner.py	2007-08-03 18:24:55.906250000 -0700
+++ MaildirRunnerx.py	2007-08-31 18:17:45.593750000 -0700
 <at>  <at>  -1,4 +1,4  <at>  <at> 
-# Copyright (C) 2002 by the Free Software Foundation, Inc.
+# Copyright (C) 2002-2007 by the Free Software Foundation, Inc.
 #
 # This program is free software; you can redistribute it and/or
 # modify it under the terms of the GNU General Public License
 <at>  <at>  -12,7 +12,8  <at>  <at> 
 #

Re: Hyphenated Lists Stopped Working

Karl Zander wrote:
>
>hummm...We have not had problems with hyphenated list 
>names.  Just about all of our lists have hyphenated names. 
> Currently running 2.1.9, but we did not have problems 
>with 2.1.8 or 2.1.7 either.

Neither did the OP have problems until he moved lists with hyphenated
names to a Mailman installation using maildir delivery to Mailman as
opposed to the normal piped delivery direct from the MTA.

The problem is in MaildirRunner.py which is "experimental for Mailman
2.1" and not used at most sites.

--

-- 
Mark Sapiro <msapiro <at> value.net>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

Re: Hyphenated Lists Stopped Working

On Fri, 31 Aug 2007 16:10:38 -0700
  Mark Sapiro <msapiro <at> value.net> wrote:

> The bottom line is there is a bug in MaildirRunner.py. 
>It doesn't work
> with hyphenated list names as it conflates the last part 
>of the name
> with the -bounces, -request, etc. suffixes.

hummm...We have not had problems with hyphenated list 
names.  Just about all of our lists have hyphenated names. 
 Currently running 2.1.9, but we did not have problems 
with 2.1.8 or 2.1.7 either.

--Karl

Comcast, Yahoo, Hotmail blocking us

Suddenly, these major ISP's were refusing our connections. We are not on
their blacklists. This all started on one day.

After a great deal of investigation by my sysadmin and my University IT guys
we have come to the conclusion that it might have been caused by updating
our mail gateway machine. We upgraded from an antiquated PIX to one that is
lightening fast. Plus we upgraded our bandwidth at the same time.

So, what is happening is we are delivering the mail so fast that these ISP's
are rejecting mail because they have thresholds in place that block large
quantities of mail coming in from the same server in a short time.

So, the question I have is - is there any way to set mailman so that it
doesn't send all its copies of a message to yahoo.com for instance all at
once? Can you break it up? We have 200 yahoo users which is over their
threshold.

We are grasping at straws on this one.

Also, is there a way to find out which major blacklists your server is on
and also a way to find the addresses you need to request whitelisting? I
have a feeling there is a repository for this that you can search, but I
don't know where to find it.

Thanks for your help.
Michael

Re: Message received by mailman and archives, but won't deliver

Just in case someone else experiences insanely slow delivery, DNS
verifies on mail from mailman turned out to be the problem in my case.
I turned that off and made sure I could relay from localhost, and
everything works great.

kyle

On 8/30/07, Mark Sapiro <msapiro <at> value.net> wrote:
> Kyle Banerjee wrote:
> >
> >I've sent a few messages to the lists over the past couple hours. Here
> >is what I'm seeing:
> >
> >1) The files are appearing almost immediately in qfiles/out/ where
> >they seem to stay. Nothing is in retry or the other qfiles
> >directories.
> >
> >2) Even a couple hours later, nothing shows up in post, smtp, or
> >smtp-failure. However, someone who belonged to one of the lists sent
> >one through. I found the entry
> >
> >Aug 31 02:18:53 2007 (40546)
> ><01F67337-E566-4AA4-B684-01C9E2F3F9FB <at> mac.com> smtp to innopac for
> >2014 recips, completed in 11231.212 seconds
> >
> >The amount of time for the transaction seems insane. Load is
> >practically nonexistent.
>
>
> Your SMTP delivery to sendmail is incredibly slow. This is your entire

Re: Hyphenated Lists Stopped Working

On Sep 1, 2007, at 5:00 AM, mailman-users-request <at> python.org wrote:

> Mark Sapiro wrote:
>>
>> The bottom line is there is a bug in MaildirRunner.py. It doesn't  
>> work
>> with hyphenated list names as it conflates the last part of the name
>> with the -bounces, -request, etc. suffixes.
>
>
> The attached MaildirRunner.patch.txt file contains a patch which I
> think will fix this bug. I've tested the revised regexp somewhat and
> it seems to work, but I would appreciate your trying the patch and
> reporting the results.
>
> Make a backup copy of Mailman/Queue/MaildirRunner.py, apply the patch
> and restart Mailman.

Is this bug only present in certain version of Mailman?  I have lists  
with hyphenated list names that do not exhibit this problem.

Re: Comcast, Yahoo, Hotmail blocking us

> Also, is there a way to find out which major blacklists your server is 
on
Try one of these:
http://www.mxtoolbox.com/blacklists.aspx
http://www.dnsbl.info/advanced.asp

You should probably check spamhaus.org directly here: 
http://www.spamhaus.org/zen/

If you find yourself on one or more blacklists, visit the blacklist's Web 
page for information on removal or whitelisting.

 -- Bob

mailman-users-bounces+bbrown=spsu.edu <at> python.org wrote on 09/01/2007 
12:48:06 PM:

> Suddenly, these major ISP's were refusing our connections. We are not on
> their blacklists. This all started on one day.
> 
> After a great deal of investigation by my sysadmin and my University IT 
guys
> we have come to the conclusion that it might have been caused by 
updating
> our mail gateway machine. We upgraded from an antiquated PIX to one that 
is
> lightening fast. Plus we upgraded our bandwidth at the same time.
> 
> So, what is happening is we are delivering the mail so fast that these 
ISP's

Re: Hyphenated Lists Stopped Working

Alan Sill wrote:
>
>> Mark Sapiro wrote:
>>>
>>> The bottom line is there is a bug in MaildirRunner.py. It doesn't  
>>> work
>>> with hyphenated list names as it conflates the last part of the name
>>> with the -bounces, -request, etc. suffixes.
>>
>>
>> The attached MaildirRunner.patch.txt file contains a patch which I
>> think will fix this bug. I've tested the revised regexp somewhat and
>> it seems to work, but I would appreciate your trying the patch and
>> reporting the results.
>>
>> Make a backup copy of Mailman/Queue/MaildirRunner.py, apply the patch
>> and restart Mailman.
>
>Is this bug only present in certain version of Mailman?  I have lists  
>with hyphenated list names that do not exhibit this problem.

The bug is in all Mailman 2.1.x versions but it only appears if you use
maildir delivery to Mailman which is not the default and which very
few sites use.

--

-- 
Mark Sapiro <msapiro <at> value.net>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

Re: Comcast, Yahoo, Hotmail blocking us

Michael Anderson wrote:

>Suddenly, these major ISP's were refusing our connections. We are not on
>their blacklists. This all started on one day.
>
>After a great deal of investigation by my sysadmin and my University IT guys
>we have come to the conclusion that it might have been caused by updating
>our mail gateway machine. We upgraded from an antiquated PIX to one that is
>lightening fast. Plus we upgraded our bandwidth at the same time.
>
>So, what is happening is we are delivering the mail so fast that these ISP's
>are rejecting mail because they have thresholds in place that block large
>quantities of mail coming in from the same server in a short time.

I suppose that's possible, but before going down that road, I would
make sure that the domain that the server identifies itself as in SMTP
HELO or EHLO is the same domain returned by an rDNS lookup of its IP
address.

I.e. if I connect from IP 10.0.0.1 and identify myself in HELO as
example.com, an rDNS lookup of 10.0.0.1 should return example.com. If
this is not the case, or if the rDNS returns a 'generic' name such as
DSL-10-0-0-1.example.com, this is sufficient reason for some ISPs to
block you.

>So, the question I have is - is there any way to set mailman so that it
>doesn't send all its copies of a message to yahoo.com for instance all at
>once? Can you break it up? We have 200 yahoo users which is over their
>threshold.