21 September 2007
I am trying to set up my mailman this after my host changed my plans and
moved my data.
Previously all was functioning.
However now I am having a problem sending the mail.
I cannot figure out what to check to find out what is preventing the mail
from sending
When I address an
Mark Sapiro wrote:
Find the lines (watch for wrapping)
def prefix_subject(mlist, msg, msgdata):
# Add the subject prefix unless the message is a digest or is being
fast
# tracked (e.g. internally crafted, delivered to a single user such
as the
# list admin).
prefix =
On 9/19/07, Mark Sapiro [EMAIL PROTECTED] wrote:
Can Cizer wrote:
The problem has changed a little bit :). Now, the mailman can send the
messages inside the domain server,but it cannot send any messages to
outside
like gmail,hotmail or yahoo.I checked the smtp-failure log and it is
Mike Peachey wrote:
Mark Sapiro wrote:
and add two lines after the comment so it becomes
def prefix_subject(mlist, msg, msgdata):
# Add the subject prefix unless the message is a digest or is being
fast
# tracked (e.g. internally crafted, delivered to a single user such
as the
Mark Sapiro wrote:
Mike Peachey wrote:
Mark Sapiro wrote:
and add two lines after the comment so it becomes
def prefix_subject(mlist, msg, msgdata):
# Add the subject prefix unless the message is a digest or is being
fast
# tracked (e.g. internally crafted, delivered to a single
Mervyn Kahn wrote:
I am trying to set up my mailman this after my host changed my plans and
moved my data.
Previously all was functioning.
However now I am having a problem sending the mail.
I cannot figure out what to check to find out what is preventing the mail
from sending
When I address
Mike Peachey wrote:
I'm using this anyway :-)
if msg.has_key('x-no-subject-prefix') and msg.get('x-no-subject-prefix',
'').lower() == 'yes':
You don't need to test separately for the presence of the header.
That's what the second argument to msg.get() is for. It is returned
when the header
Can Cizer wrote:
Thank you, this may be the problem,but i don't know how to tell qmail
that it is allowed to relay mail from Mailman. May you help me?
No, I can't help you. I don't know a thing about configuring qmail, and
I don't know if anyone else on this list does either.
Note that this
On 9/21/07, Mark Sapiro [EMAIL PROTECTED] wrote:
Can Cizer wrote:
Thank you, this may be the problem,but i don't know how to tell qmail
that it is allowed to relay mail from Mailman. May you help me?
No, I can't help you. I don't know a thing about configuring qmail, and
I don't know
Mark Sapiro wrote:
Mike Peachey wrote:
I'm using this anyway :-)
if msg.has_key('x-no-subject-prefix') and msg.get('x-no-subject-prefix',
'').lower() == 'yes':
You don't need to test separately for the presence of the header.
That's what the second argument to msg.get() is for. It is
I am seeing Uncaught bounce notification e-mail from my Mailman 2.1.9.
The unhandled message looks like a return-receipt for a read of an orginal
e-mail sent thru a list managed by Mailman.
I have looked at the header of the e-mail that the reader is sending the
receipt too. There is no
Kevin J Dunlap wrote:
I am seeing Uncaught bounce notification e-mail from my Mailman 2.1.9.
The unhandled message looks like a return-receipt for a read of an orginal
e-mail sent thru a list managed by Mailman.
I have looked at the header of the e-mail that the reader is sending the
receipt
Ashley M. Kirchner wrote:
Mark Sapiro wrote:
It looks like the
#include Python.h
near the beginning of _koco.c is failing. Is there a python2.4 directory
in /usr/include?
That was it. python-devel was not installed on this machine. Would
be nice if the configure script checked
13 matches
Mail list logo
