Re: [Mailman-Users] Mailman causing strange slowdown in SMTP

[Craig Pettersen]

Thanks for the response.  The slow down has continued and nothing I've tried
has helped.  I answer the questions put to me in context below.  Any further
ideas would be greatly appreciated.


>>Hi,
> >>  I have a mailman installation running on our qmail server that is
> involved in a >>slowdown in SMTP for the designated SMTPHOST in mm_cfg.py.
> I first noticed >>that the messages for the list go out very slowly...about
> 15 seconds per >>message.  I saw this in the mailman smtp log, and then I
> saw it in the the qmail >>smtp log as well, so I figured it was a problem
> with qmail.  As I looked through the >>qmail logs, I saw that all messages
> that connected to smtp via 127.0.0.1 were >>slow, averaging more than 15
> seconds, while those that connected from >>somewhere else were all a
> fraction of a second.  I discovered that if I changed >>SMTPHOST to our
> public IP in mm_cfg.py, any messages (from the list or >>elsewhere) using it
> would slow down as well, and any messages connecting via 
> >>127.0.0.1returned to normal speed.  If I shut down 
> mailman using mailmanctl >>stop,
> speed was normal for both localhost or the public IP, whichever had been
> >>used as mailman's SMTPHOST at the time returning to mormal speed.  That
> >>verified that mailman is directly involved in the slowdown in smtp.  If I
> telnet to the >>smtp and manually send a message, the hangup point is after
> entering 'data' - ie:
>
> >>helo test.com
> >>250 ok
>
> >>mail from: test.com
> >>250 ok
> >>rcpt to: 
> >>250 ok
> >>data
> <---after entering 'data' there is a 15 second + wait if mailman is 
> running
>
> >>354 ok
> >>etc...
>
>
>
>
>
> >>This mailman installation serves only one list, an announcement only
> > list,
> > >>of about 35,000 members, with over 10,000 disabled due to bounces that
> > send
> > >>once every 2 weeks or so. It invariably sends
> > >>several hundred to a thousand messages individually at the
> > +/-15sec./message
> > >>rate, then a big bulk mailing to most subscribers that's taking about
> > 3000
> > >>seconds for around 23,000, then a few score more of individual
> > messages
> > >>before it stops functioning.
> >
> >
> > >What exactly is in Mailman's smtp and smtp-failure logs (the
> > >'individual' messages are not the post).
>
>
>
> I figured out that the individual messages were messages left in
> qfiles/out.  When message are left like that they take around 15 seconds
> each to clear out. So this is reflected in the smtp log.  There are no
> unusual failures in smtp-failure.  It does appear from going through the
> logs that the problem happens when there are messages in qfiles/out.  When
> the list message goes out to the large list, qfiles/out begins to accumulate
> messages.  Those messages are taking the 15 seconds to go out.  Once
> qfiles/out clears up, the time appears to drop to normal, usually less than
> a second.
>
> >>Using ps aux, one can see that all the
> > >>qrunners are there and appear normal, but bin/mailmanctl must be used
> > to
> > >>stop and start things to get them going again.
> >
> >
> > >When things are not going, what is the contents of the queues
> > >(subdirectories of the qfiles/ directory)?
>
>
> So there are hundreds of messages backed up in qfiles/out, again each
> taking about 15 seconds , the vast majority not varying more than a second
> from that.
>
> >>  So my questions are...does anyone have any idea what mailman could be
> > >>doing to interfere with smtp on its SMTPHOST and how to fix it? and
> > does
> > >>anyone have any idea why mailman stops working shortly after sending
> > out the
> > >>big list?
> >
> >
> > >What are your various mm_cfg.py settings if any for the VERP settings
> > >and for SMTP_MAX_RCPTS and SMTP_MAX_SESSIONS_PER_CONNECTION.
> >
> > >You might try
> >
> > >SMTP_MAX_RCPTS = 10
> > >SMTP_MAX_SESSIONS_PER_CONNECTION = 1
> >
> > >To see if that makes a difference.
>
>
> I tried these settings and they don't make any difference.  I have no VERP
> settings in mm_cfg.py
>
> >If you restart both Mailman and qmail, does the first subsequent
> > >Mailman SMTP session exhibit the 15 second delay?
>
>
> If  I restart everything, invariably the first mesages is under 2 seconds
>
> >Have you seen
> > >< http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.011.htp
> > >?
>
>
> I have looked at that.  I see that my concurrency for qmail is at 400.
> Mostly the points there seem to be ways to get better performance on a
> normally functioning list.  I would like to try some of them but my main
> problem is this unusual slowdown.  Everything was working fine a few eeks
> ago.  One strange thing about this is that the logs show the time
> consistently at about 50ms above 15 seconds.  Once in awhile I see one that
> is about 50ms about 14 seconds. Here for ex. are the last twelve times-
> 15.058, 15.056, 15.051, 15.060, 15.055, 15.055, 15.051, 15.051, 15.054,
> 15.054, 15.055, 15.051, 14.055.  This is very repre

Re: [Mailman-Users] Problem with postfix: command died with status 1

[Niemi Hannu]

>>> Try disabling apparmor

>That did it :) Thank you very much Ralf

Well, now to think about it...any pointers how to change apparmor
profiles to allow this functionality while apparmor is running? ;)

Regards

hannu
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] Problem with postfix: command died with status 1

[Niemi Hannu]

>> < apps.rbm-toolbox.net #5.0.0 X-Postfix; Command died with status 1:
>"/usr/lib/mailman/mail/mailman post testplk-l"> 
>>  
>> In the mail log I also get a line:
>> fatal: execvp /usr/lib/mailman/mail/mailman: Operation not permitted

> Try disabling apparmor



That did it :) Thank you very much Ralf

Best regards

Hannu Niemi

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] Weird again!!

[Lawrence Bowie]

Lawrence Bowie wrote:
> One of my lists is discarding messages for some reason.
> THe vette file looks like the following ..
> 
> 
> Aug 10 18:52:42 2006 (5414) Message discarded, msgid: <[EMAIL PROTECTED]>
> Aug 10 18:55:43 2006 (5414) Message discarded, msgid: <[EMAIL PROTECTED]>
> 
> 
> I am subscribed to the list. I suspect someone reset something
> or set something I do not know about but I cannot find it.
> 
> ANy ideas?
> 
> LDB
> 
> --
> Mailman-Users mailing list
> Mailman-Users@python.org
> http://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe: 
> http://mail.python.org/mailman/options/mailman-users/ldb%40freestandards.org
> 
> Security Policy: 
> http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
> 
> 

Found it!! A spam rule 

LDB

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] Running Mailman software

[Brad Knowles]

At 10:49 PM +0100 2006-08-10, Martin Dennett (Gmail) wrote:

>  After having had 2 hosts for my mailing list in the last 3 months and
>  now being told that my list is "too big" for the host we currently use
>  (2000 members, approx ½ of whom don't actually receive any mail, just
>  choosing to read on the web, and half of those left being on digest), I
>  am seriously considering hosting the list myself. What I would like to
>  know, from those that have done it and are currently doing it, are the
>  positives and negatives of such a situation. If I choose to forge ahead
>  with this (and with other such alternatives as Yahoo & Googlegroups,
>  it's a definite possibility), I'd need *real* dummy instructions on how
>  to go about this.

Running your own mail server is a non-trivial task.  Go look at the 
FAQ and documentation at sendmail.org or postfix.org to get an idea 
of the level of complexity involved in that process.

Adding a mailing list server on top of that is also a non-trivial 
task.  Again, go look at the documentation and FAQ at 
 and 
, respectively.


First thing I'd recommend is for you to take a look at getting a 
better list hosting facility, starting with the information in 
. 
 From there you should have a better idea if you really want to do 
this yourself on your own machine, or if you want to use hosting 
facilities from somewhere else.

-- 
Brad Knowles, <[EMAIL PROTECTED]>

"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety."

 -- Benjamin Franklin (1706-1790), reply of the Pennsylvania
 Assembly to the Governor, November 11, 1755

  Founding Individual Sponsor of LOPSA.  See .
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

[Mailman-Users] Weird again!!

[Lawrence Bowie]

One of my lists is discarding messages for some reason.
THe vette file looks like the following ..


Aug 10 18:52:42 2006 (5414) Message discarded, msgid: <[EMAIL PROTECTED]>
Aug 10 18:55:43 2006 (5414) Message discarded, msgid: <[EMAIL PROTECTED]>


I am subscribed to the list. I suspect someone reset something
or set something I do not know about but I cannot find it.

ANy ideas?

LDB

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] Running Mailman software

[Kevin A. McGrail]

Are you currently running a mail server at all because the nuances with 
doing so are not easy?  For example, if you aren't familiar with 
postmaster.aol.com and you have a substantial address base for @AOL.COM, you 
will notice that the rules are onerous for handling one list with 2000 
members.

Mailman just expands the issues beyond "normal" mailservers.

Regards,
KAM

- Original Message - 
From: "Martin Dennett (Gmail)" <[EMAIL PROTECTED]>
To: 
Sent: Thursday, August 10, 2006 5:49 PM
Subject: [Mailman-Users] Running Mailman software


Hi

After having had 2 hosts for my mailing list in the last 3 months and
now being told that my list is "too big" for the host we currently use
(2000 members, approx ½ of whom don't actually receive any mail, just
choosing to read on the web, and half of those left being on digest), I
am seriously considering hosting the list myself. What I would like to
know, from those that have done it and are currently doing it, are the
positives and negatives of such a situation. If I choose to forge ahead
with this (and with other such alternatives as Yahoo & Googlegroups,
it's a definite possibility), I'd need *real* dummy instructions on how
to go about this.


--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

[Mailman-Users] Running Mailman software

[Martin Dennett (Gmail)]

Hi

After having had 2 hosts for my mailing list in the last 3 months and 
now being told that my list is "too big" for the host we currently use 
(2000 members, approx ½ of whom don't actually receive any mail, just 
choosing to read on the web, and half of those left being on digest), I 
am seriously considering hosting the list myself. What I would like to 
know, from those that have done it and are currently doing it, are the 
positives and negatives of such a situation. If I choose to forge ahead 
with this (and with other such alternatives as Yahoo & Googlegroups, 
it's a definite possibility), I'd need *real* dummy instructions on how 
to go about this.

Comments please.

Rgds

Martin Dennett
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

[Mailman-Users] Strange behaviour after a file system filled up...

[Paul Armor]

Hi,
we had a problem a couple of weeks ago, and occasionally see some 
lingering side effects.

This is regarding mailman-2.0.13.

The file system that houses all of our mailman install filled up (both 
scripts and data).  We cleaned up the fs, and things seemed to keep 
plugging along.

I. Except, that I occasionally see I get email warnings of:

Traceback (most recent call last):
   File "/var/mailman/cron/checkdbs", line 92, in ?
 main()
   File "/var/mailman/cron/checkdbs", line 43, in main
 count = mlist.NumRequestsPending()
   File "/var/mailman/Mailman/ListAdmin.py", line 96, in NumRequestsPending
 self.__opendb()
   File "/var/mailman/Mailman/ListAdmin.py", line 69, in __opendb
 self.__db = marshal.load(fp)
EOFError: EOF read where object expected

I don't THINK I see these every day...


II. I find a LOT of .lock files in mailman/locks, all from during the time 
that the fs was full, most are 0 length files, a few contain the full path 
to and the name of the lockfile.



Are the presense of the lock files related to the pending-request checkdbs 
cron errors?

How can I clean this up?  I've poked around the archives here a bit, and 
google'd this, but can't seem to find an answer...

Thanks in advance!

Cheers,
Paul

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] Problem with postfix: command died with status 1

[Ralf Hildebrandt]

* Niemi Hannu <[EMAIL PROTECTED]>:
> Hello
>  
> I have just installed Mailman 2.1.8 on an OpenSuSE 10.1 running on AMD64 
> system.
>  
> I made the installation through YAST and it comes directly from the DVD 
> downloaded from OpenSuSE site.
>  
> The installation itself went quite easily and through the web interface I was 
> able to make a new list and even got the email saying so.
>  
> But (isn't there always a BUT?) then the problems started. When I try to send 
> email to the list the postfix gives the following problem:
>  
> < apps.rbm-toolbox.net #5.0.0 X-Postfix; Command died with status 1: 
> "/usr/lib/mailman/mail/mailman post testplk-l"> 
>  
> In the mail log I also get a line:
> fatal: execvp /usr/lib/mailman/mail/mailman: Operation not permitted

Try disabling apparmor

-- 
Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED]
Charite - Universitätsmedizin BerlinTel.  +49 (0)30-450 570-155
Gemeinsame Einrichtung von FU- und HU-BerlinFax.  +49 (0)30-450 570-962
IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED]
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

[Mailman-Users] Problem with postfix: command died with status 1

[Niemi Hannu]

Hello
 
I have just installed Mailman 2.1.8 on an OpenSuSE 10.1 running on AMD64 system.
 
I made the installation through YAST and it comes directly from the DVD 
downloaded from OpenSuSE site.
 
The installation itself went quite easily and through the web interface I was 
able to make a new list and even got the email saying so.
 
But (isn't there always a BUT?) then the problems started. When I try to send 
email to the list the postfix gives the following problem:
 
< apps.rbm-toolbox.net #5.0.0 X-Postfix; Command died with status 1: 
"/usr/lib/mailman/mail/mailman post testplk-l"> 
 
In the mail log I also get a line:
fatal: execvp /usr/lib/mailman/mail/mailman: Operation not permitted
 
I have digged quite a lot of net and found out that others have had the same 
problem, but either there's no solution given or the solutions don't help.
 
Though this is a new installation, I have been running mailman on other servers 
and never earlier bumped into this kind of problem.
 
I will be providing more information if needed.
 
Looking for your help
 
Hannu Niemi
 
 
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

[Mailman-Users] Encoding scrubbed attachment

[Bausch, Jean]

Hi,

I am running Mailman 2.1.8 on a Solaris system and I have activated 
scrub_nondigest for three lists - but the attachments can only be 
correctly viewed for one of them.

When sending a mail with an attached .jpg, two of the lists 
generate an encoded attachment leading to 
- the display of something like
/9j/4AAQSkZJRgABAQAAAQABAAD/2wBDAAEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEB
AQEB
AQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQH/2wBDAQEBAQEBAQEBAQEBAQEBAQEB
AQEB
AQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQH/wAARCAHCAl4D
ASIA
when the URL is used in IE
- the display of a page containing only the URL with Firefox.

The third list stores an attachment which can be correctly viewed with
any browser.


I have compared the stored attachments and found that in the first case
the 
attachment contains only printable text:

od -xc attachment.jpg | head
000392f2f6a413451416b534a5a67524241
   /   9   j   /   4   A   A   Q   S   k   Z   J   R   g   A   B
020514141415141424141412f4477324442
   A   Q   A   A   A   Q   A   B   A   A   D   /   2   w   B   D
04041414245514142455141424551414245
   A   A   E   B   A   Q   E   B   A   Q   E   B   A   Q   E   B
06051414245514142455141424551414245
   A   Q   E   B   A   Q   E   B   A   Q   E   B   A   Q   E   B
100514142455141424551414245410a4551
   A   Q   E   B   A   Q   E   B   A   Q   E   B  \n   A   Q   E

whereas the same command for the correctly working attachment gives the
following:

 od -xc attachment.jpg | head
000d8ffe0ff1000464a4649010000010100
 377 330 377 340  \0 020   J   F   I   F  \0 001 001  \0  \0 001
0200100dbff43000100010101010101
  \0 001  \0  \0 377 333  \0   C  \0 001 001 001 001 001 001 001
04001010101010101010101010101010101
 001 001 001 001 001 001 001 001 001 001 001 001 001 001 001 001
*
1200101010101010101ff0100db01430101
 001 001 001 001 001 001 001 001 001 377 333  \0   C 001 001 001
14001010101010101010101010101010101

The .jpg file was the same in all the experiments, and I can't find any
difference in the list configurations which could explain this
behaviour.

The only difference between the lists that I can think of is that the
third
has been created after my update to Mailman 2.1.8, the other two are
much
older.

Thanks for helping,

Jean Bausch
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp