On 05/20/2013 12:41 PM, David Josephson wrote:
> Thank you. /etc/hosts contained a line
>
> 127.0.0.1 localhost.localdomain
>
> Previously that was enough for Mailman. Adding 'localhost' on that line
> fixed the problem. What would have changed to cause this?
Possibly you had previously set
S
On 5/20/2013 11:12 AM, Mark Sapiro wrote:
On 05/20/2013 11:05 AM, David Josephson wrote:
Yes... but nothing changed on the server in /etc ... it worked fine a
couple of days ago, then there was a disk full, now it doesn't. Nothing
has changed in /etc for several months, and regular mail client w
On 05/20/2013 11:05 AM, David Josephson wrote:
> Yes... but nothing changed on the server in /etc ... it worked fine a
> couple of days ago, then there was a disk full, now it doesn't. Nothing
> has changed in /etc for several months, and regular mail client works.
Yes, but read the FAQs and do s
Yes... but nothing changed on the server in /etc ... it worked fine a
couple of days ago, then there was a disk full, now it doesn't. Nothing
has changed in /etc for several months, and regular mail client works.
On 05/19/2013 10:45 PM, David Josephson wrote:
/logs/smtp-failure shows
"Low le
On 05/19/2013 10:45 PM, David Josephson wrote:
>
> /logs/smtp-failure shows
> "Low level smtp error: (-2, 'Name or service not known'), msgid: ..."
> and then
This issue can have several different underlying causes including things
like permissions on /etc/hosts and /etc/resolv.conf. See the FAQ
On 05/20/2013 05:20 AM, Richard Shetron wrote:
I've noticed that if mailman is stopped/crashes/system reboot/etc. and
there is anything in mailman/qfiles/maildir/cur that stuff seems to just
hang in mailman until you stop mailman, clear this directory, and then
restart mailman. May not be your
On 05/20/2013 05:20 AM, Richard Shetron wrote:
> I've noticed that if mailman is stopped/crashes/system reboot/etc. and
> there is anything in mailman/qfiles/maildir/cur that stuff seems to just
> hang in mailman until you stop mailman, clear this directory, and then
> restart mailman. May not be
I've noticed that if mailman is stopped/crashes/system reboot/etc. and
there is anything in mailman/qfiles/maildir/cur that stuff seems to just
hang in mailman until you stop mailman, clear this directory, and then
restart mailman. May not be your problem but try checking it.
you might also w
A very old and well-used list has been fine for years on this box,
running Mailman 2.1.10 on Red Hat 7.2. The disk got full and everything
crashed. I was able to clear out a couple GB of space and get all
services running again, but now mailman will not send any messages,
either to the list adm
If that doesn't work (or you don't like the solution), change back to
using SMTPDirect and then try mucking about with some of the other SMTP
variables. In particular you might want to change:
SMTPHOST
On Tue, 2002-10-15 at 13:57, Jon Carnes wrote:
> Can you login to that server and:
> telnet
Can you login to that server and:
telnet 127.0.0.1 25
In other words is sendmail listing to all available ports on the server?
If so, what happens if you put the following in
~mailman/Mailman/mm_cfg.py:
DELIVERY_MODULE = 'Sendmail'
#DELIVERY_MODULE = 'SMTPDirect'
In other words, change
Hi,
and again my Problem with Mailman and SMTP, posting
is actually working, a posted message is even shown in the archive. Just
delivering to the members doesnt work, i get the following error message in the
/var/log/mail:
"Oct 15 16:33:18 p15093706 sendmail[28096]:
NOQUEUE: localhost.l
do with relaying and smtp auth... but i
> haven't found any posts or articles about that kind of failures
>
> thx
>
> Chris
> - Original Message -
> From: "Jon Carnes" <[EMAIL PROTECTED]>
> To: "Fuss, Christian" <[EMAIL PROTECT
If I read that warning correctly, it is simply telling you that the
email address [EMAIL PROTECTED] is bouncing.
What happens when you send an email to "[EMAIL PROTECTED]"? Does
it bounce? Are only Mailman messages bouncing to that address?
On Wed, 2002-01-02 at 07:06, Fuss, Christian wrote:
>
Hi,
i do have a really urgent Problem with my Mailman.
Actually everythings working fine except of sending the mails to the
list-members.
I get following failure in the smtp-failures
log:
Oct 12 19:49:11 2002 (2292) delivery to [EMAIL PROTECTED] failed with
code 553: 5.3.0 <[EMAIL PROTE
Hi all,
i've a problem with Mailman 2.0.9 and previous releases. When i post to a
list X and i Approve the message, message will not be sent with a lot of
errors message in /logs/smtp_failure e /logs/smtp.
Il /logs/stmp i see:
Apr 17 17:03:56 2002 (13952) All recipients refused: Server not co
On Wed, 17 Apr 2002 18:37:36 +0200
o-zone <[EMAIL PROTECTED]> wrote:
> Apr 17 17:03:56 2002 (13952) All recipients refused: Server not
> connected Apr 17 17:03:56 2002 (13952) smtp for 312 recips, completed
> in 5152.687 seconds
Do you have an MTA running on localhost? Does it answer on port
Hi all,
i've a problem with Mailman 2.0.9 and previous releases. When i post to a
list X and i Approve the message, message will not be sent with a lot of
errors message in /logs/smtp_failure e /logs/smtp.
Il /logs/stmp i see:
Apr 17 17:03:56 2002 (13952) All recipients refused: Server not co
18 matches
Mail list logo
