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
On Fri, 31 Aug 2007 16:10:38 -0700
Mark Sapiro [EMAIL PROTECTED] 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
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.
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 [EMAIL PROTECTED] wrote:
Kyle Banerjee
On Sep 1, 2007, at 5:00 AM, [EMAIL PROTECTED] 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
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
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
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
Just tried to upgrade by migrating our lists from mailman 1.0 to mailman 2.1.9
on new hardware. Pre-upgrade testing worked fine but after the real migration
I saw a lot of user unknown errors in postfix's maillog.After
investigating I found a lot of rejected mail destined for
1) Is there any problem with manually adding the extra alias
owner-listname for each migrated list and
2) Is is possible that mailman 2.1.9 is generating references to
owner-listname and if so, is that a problem?
I just found the answer to question 1. If you add the alias manually it will
Michael Anderson wrote:
I can't imagine that sending one message at a time to 1500 users on a real
busy listserv would be a good idea.. Could it not really be slow?
Well, you asked how to slow it down ...
OTOH, it won't be that slow. If your MTA as as blinding fast as you
say, I imagine that
We changed our Sendmail configuration to send out one message at a time and
it seems to be working fine so far. Thanks for all the help.
MA
From: Mark Sapiro [EMAIL PROTECTED]
Organization: Not Very Much
Date: Sat, 1 Sep 2007 15:02:12 -0700
To: Michael Anderson [EMAIL PROTECTED]
Cc:
[EMAIL PROTECTED] wrote:
1) Is there any problem with manually adding the extra alias
owner-listname for each migrated list and
2) Is is possible that mailman 2.1.9 is generating references to
owner-listname and if so, is that a problem?
I just found the answer to question 1. If you add
13 matches
Mail list logo
