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 for
> "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
--
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.
>
> Every
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 = '/usr
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: X-
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
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 versi
[ bcc to the address in the SOA field ]
DNS for list.org seems to be messed up - there's still an MX record, but
no A record for list.org or www.list.org (at any of the 3 nameservers
for the zone). Is this intentional? Is there a new URL for the Mailman
site / FAQ?
aura% dig @NS4.BILOW.COM list.o
On Sat, 15 Mar 2003 14:54:49 -0500 (EST)
Elena Fraboschi <[EMAIL PROTECTED]> wrote:
> I believe the problem (and the fix) is far from transparent. I'll
> await eagerly the release of a future version of mailman where this
> problem (three pages of msgs in google about it...) might have been
> f
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 2
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:
http://www.py
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))
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
13 matches
Mail list logo
