Re: [Mailman-Users] Why some messages aren't distributed?

2003-03-16 Thread Marina Markus
Hello and thank you, But I checked both places and found nothing: Check to see if the messages have been shunted: ~mailman/qfiles/shunt/.. I didn't find those specific undistributed messages in this directory, although found some older ones. May I ask what this shunt directory serves

[Mailman-Users] Big Delays: 22hours in Mailman-Queue

2003-03-16 Thread Thomas Guettler
Hi! I have a problem with mailman. Some mails hang in the queue very long (See ** mark): Received: from pu.schlittermann.de (212.80.235.130) by mx0.gmx.net (mx002-rz3) with SMTP; 8 Mar 2003 11:30:53 - Received: from amavis by pu.schlittermann.de with scanned-ok (Exim 3.35 #1 (Debian))

Re: [Mailman-Users] Backing Up Lists

2003-03-16 Thread J C Lawrence
On Sat, 15 Mar 2003 09:45:39 -0800 Joseph Smith [EMAIL PROTECTED] wrote: Hello all, I am by nature the proverbial turd in the punch bowl and try and find holes with ideas. I asked a question to someone about a list backup in case of server down time. Please see the FAQ:

[Mailman-Users] Lock aquired in future

2003-03-16 Thread Thomas Guettler
Hi! The locks seem to be requested in the future. pu:~# ls --full-time /var/lib/mailman/locks total 8 -rw-rw-r--2 list list 44 Mon Mar 17 09:03:28 2003 qrunner.lock -rw-rw-r--2 list list 44 Mon Mar 17 09:03:28 2003 qrunner.lock.pu.22391 pu:~# date Sun Mar 16

Re: [Mailman-Users] Big Delays: 22hours in Mailman-Queue

2003-03-16 Thread Jon Carnes
IIRC, there is a known problem with Mailman version 2.0.11 with certain headers causing the queue to fall-over (and basically send mailman into a long spiral of inactivity). This prompted a quick release of 2.0.12 and then the eventual solid release of 2.0.13. You should at least upgrade to

Re: [Mailman-Users] Lock aquired in future

2003-03-16 Thread Jon Carnes
Just as a guess... but are you using GMT time on your machine and then using individual timezone settings for your users? On Sun, 2003-03-16 at 17:05, Thomas Guettler wrote: Hi! The locks seem to be requested in the future. pu:~# ls --full-time /var/lib/mailman/locks total 8 -rw-rw-r--

[Mailman-Users] Still can't get new installition to deliver mail

2003-03-16 Thread George Cohn
I'm running Mailman 2.0.13 with Postfix 1.1.11 on RH 8. Everything works in Mailman now except it still won't deliver a message to the subscribers (me) if I post a message. What I am getting back is this: Final-Recipient: rfc822; [EMAIL PROTECTED] Action: failed Status: 5.0.0 Diagnostic-Code:

Re: [Mailman-Users] Why some messages aren't distributed?

2003-03-16 Thread Jon Carnes
What are your Delivery defaults set to in ~mailman/Mailman/mm_cfg.py (or Defaults.py)? === #DELIVERY_MODULE = 'Sendmail' DELIVERY_MODULE = 'SMTPDirect' # MTA -- but then also see POSTFIX_STYLE_VIRTUAL_DOMAINS. MTA = 'Manual' POSTFIX_STYLE_VIRTUAL_DOMAINS = [] POSTFIX_ALIAS_CMD =

Re: [Mailman-Users] Still can't get new installition to deliver mail

2003-03-16 Thread Jon Carnes
Looks like a rights problem... In any case, check out FAQ 3.14 which covers this problem in detail. Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Good Luck - Jon Carnes === On Sun, 2003-03-16 at 22:13, George Cohn wrote: I'm running Mailman 2.0.13 with Postfix 1.1.11 on RH 8.

Re: [Mailman-Users] Lock aquired in future

2003-03-16 Thread Barry A. Warsaw
TG == Thomas Guettler [EMAIL PROTECTED] writes: TG The locks seem to be requested in the future. This is by design. The lock's atime/mtime specifies the point in the future when the lock would time out. By default the lock lifetime is 5 hours. This is normal. -Barry

[Mailman-Users] Message IDs in /var/log/smtp and smtp-failure

2003-03-16 Thread Thomas Guettler
Hi! Since I am using debian stable, I don't want to update the mailman. I like to narrow down the problem. How can Message IDs be displayed in /var/log/smtp and smtp-failure? It would be nice if the following line would contain message ID and the To-Header: Mar 17 06:46:56 2003 (14243) smtp