Check your postfix configuration and make sure you have changed the
bounce code for local users. Postfix initially sets this to a "retry"
error code, which means that a errantly typed local username in a mail
will literally bounce forever. Get a few of those going, and you can
really peg the CPU.
Hi,
> Barry Warsaw did make a change in the CVS a short while ago to help deal
> with this class of problem. Take a look at:
> http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/mailman/mailman/Mailman/Queue/OutgoingRunner.py
I'm running mailman 2.1.2 and having serious problems with CPU usage, is
At 11:28 19/06/2003, foobar wrote:
> >= 0x40227000
> >read(9, "(cMailman.Message\nMessage\nq\1oq\2}"..., 4096) = 4096
> >
> >Could you tell what is wrong, no messages are going currently out or in,
> >MTA is working properly and bounces were handled correctly.
> >
> > PID USER PRI NI SIZE
> >= 0x40227000
> >read(9, "(cMailman.Message\nMessage\nq\1oq\2}"..., 4096) = 4096
> >
> >Could you tell what is wrong, no messages are going currently out or in,
> >MTA is working properly and bounces were handled correctly.
> >
> > PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME COM
At 07:36 19/06/2003, foobar wrote:
Hi,
Some strace:
-- Opening that db --
open("/opt/mailman-2.1.2/qfiles/out/1055856935.2792439+c164823523573087c71ed0088b9beb1dcc0c9698.db",
O_RDONLY|O_LARGEFILE) = 9
fstat64(9, {st_mode=S_IFREG|0660, st_size=2054, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRIT
Hi,
Some strace:
-- Opening that db --
open("/opt/mailman-2.1.2/qfiles/out/1055856935.2792439+c164823523573087c71ed0088b9beb1dcc0c9698.db",
O_RDONLY|O_LARGEFILE) = 9
fstat64(9, {st_mode=S_IFREG|0660, st_size=2054, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0
Thanks..
This episode does bring up some thoughts though. My problem was for the
most part that I didn't know where to look ("ps aux | grep mail" would
have made a good place to start, but that was my fault :o), and the logs
didn't give me anything. Failure to contact an smtp server should
perhaps
I'm sorry all.. the private mail I sent Tom was meant to go to the list
as well.. I'm simply used to mailing lists rewriting the Reply-To
header..
But here it is.. (one might think I didn't send this to the list from
embarassment .. :o):
F*ck.. I'm terribly sorry for wasting your time. I'm just st
In some cases this problem is caused by the way that the MTA handles
local deliveries (where there is a problem with the local user).
In postfix for example, the default install has local bounces
mis-identified so that Mailman will try, try again to deliver to a bogus
local user address. Nothing
Odd. I have the same problem! (postfix here, and it's fine)
-R
Arnar Birgisson wrote:
Something of the sort yes.. if I stop mailman, there is one message in
the out queue. However, using dumpdb reveals that this is just a normal
--
Mailman-Us
On Wed, 28 May 2003 09:15:45 -0700, Mark Dadgar <[EMAIL PROTECTED]>
wrote:
Arnar Birgisson at [EMAIL PROTECTED] wrote:
I'm running mailman 2.1 on a linux machine. My problem is that the
mailman qrunner daemon constantly consumes 65-95% of cpu time. Nothing
shows up in the logs while this goes on.
Arnar Birgisson at [EMAIL PROTECTED] wrote:
> I'm running mailman 2.1 on a linux machine. My problem is that the
> mailman qrunner daemon constantly consumes 65-95% of cpu time. Nothing
> shows up in the logs while this goes on. Any ideas of how to locate the
> fault?
Is there a massively large (l
On Wed, 28 May 2003 14:33:05 +, Arnar Birgisson <[EMAIL PROTECTED]> wrote:
Hi there..
I verified this.. the MTA seems to be configured correctly. Since
switching to Exim recently, mailman lists have worked as they should.
As I mentioned earlier, some files are constantly being created in the
On Wednesday 28 May 2003 10:16 am, Raquel Rice wrote:
> The FAQ that is included in the Mailman download indicates that it
> could also be a problem with your MTA. Make certain that your MTA
> isn't set up to do DNS lookups on each address.
Thank you for your suggestion.
I did read the FAQ and
Something of the sort yes.. if I stop mailman, there is one message in
the out queue. However, using dumpdb reveals that this is just a normal
message being posted to a list, not a confirm message. dumpdb on the .db
file gives (I have replaced @ with 'at' in email addresses..)
{ 'decorated': 1,
On Wed, 28 May 2003, Arnar Birgisson wrote:
> Sorry for replying to my own post.. but I just noticed by watching the
> $prefix/qfiles/out directory.. that files are being created and removed
> there constantly.. still, nothing in the logs. There is however no
> ongoing traffic at the moment, this
Hi there..
I verified this.. the MTA seems to be configured correctly. Since
switching to Exim recently, mailman lists have worked as they should.
As I mentioned earlier, some files are constantly being created in the
out queue directory. I wasn't right when I said earlier that there was
no traff
Sorry for replying to my own post.. but I just noticed by watching the
$prefix/qfiles/out directory.. that files are being created and removed
there constantly.. still, nothing in the logs. There is however no
ongoing traffic at the moment, this is a private server with few lists.
My MTA is Exim 4,
Hello.. and thanks for the response.
I probably should have mentioned that there is currently no traffic on
the server.. no messages are being sent and all queues are empty.
Arnar
>>> "Josep L. Guallar-Esteve" <[EMAIL PROTECTED]> 28.5.2003
13:46:01 >>>
On Wednesday 28 May 2003 09:24 am, Arnar B
On Wednesday 28 May 2003 09:24 am, Arnar Birgisson wrote:
> Hello
Hi
> I'm running mailman 2.1 on a linux machine. My problem is that the
> mailman qrunner daemon constantly consumes 65-95% of cpu time. Nothing
> shows up in the logs while this goes on. Any ideas of how to locate the
> fault?
Th
Hello
I'm running mailman 2.1 on a linux machine. My problem is that the
mailman qrunner daemon constantly consumes 65-95% of cpu time. Nothing
shows up in the logs while this goes on. Any ideas of how to locate the
fault?
Arnar
--
Mailman-User
21 matches
Mail list logo
