Le 21/02/2012 18:35, Mark Sapiro a écrit :
jdd wrote:
got it...
for some obscure reason, the openSUSE config utility did *not* update
the mm_cfg.py config file (and copied the good one next with an extension)
A Mailman install/upgrade should never replace an existing mm_cfg.py as
that is whe
jdd wrote:
>got it...
>for some obscure reason, the openSUSE config utility did *not* update
>the mm_cfg.py config file (and copied the good one next with an extension)
A Mailman install/upgrade should never replace an existing mm_cfg.py as
that is where you put your site customization of Mailm
jdd wrote:
>
>I can understand the content but it's only 2.8k, so I join it to this
>post, may be it will give clues
You can examine Mailman's saved Python pickle (.pck) files with
Mailman's bin/dumpdb.
--
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiab
got it...
for some obscure reason, the openSUSE config utility did *not* update
the mm_cfg.py config file (and copied the good one next with an extension)
using this config file solved the problem.
the local config (good) is:
DEFAULT_URL_PATTERN = 'http://%s/mailman/'
DEFAULT_NNTP_HOST = 'sav
Le 21/02/2012 11:19, jdd a écrit :
I can understand the content but it's only 2.8k, so I join it to this
post, may be it will give clues
do not pass the list. It's here:
http://dodin.org/temp/mailproblem.pck
thanks
jdd
--
Jean-Daniel Dodin
thanks to your answers, but none give result. I was even obliged to
revert to a previous (virtualbox) snapshot because after reboot I
couldn't configure the network :-)
that said, trying as many things, I finally got a cleaner mailman
folder. Clean logs, shunts, helds...
Now, sending a coupl
On 2/20/2012 10:55 AM, jdd wrote:
>
> I posted a couple of messages on the list, no return
>
> I have
> Feb 20 19:42:00 2012 (28177) post to linux-31 from jdani...@free.fr,
> size=1607, message-id=<4f4293f1.4090...@free.fr>, 2 failures
>
> in post log file
>
> Feb 20 19:42:00 2012 (28177) deliv
Le 20/02/2012 16:55, Mark Sapiro a écrit :
Remove the line
DELIVERY_MODULE = 'Sendmail'
from mm_cfg.py.
done (commented out)
even after rstarting mailman, this do not change the result (no delivery)
but I still have
Feb 20 19:38:44 2012 (10832) Uncaught runner exception: Use of the
Sendma
jdd wrote:
>
>I send a message to the linux-31 mailing list, I got this error message:
>
>Feb 20 10:27:58 2012 (10832) Uncaught runner exception: Use of the
>Sendmail.py delivery module is highly discouraged
>Feb 20 10:27:58 2012 (10832) Traceback (most recent call last):
> File "/usr/lib/mailma
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
> - I have try it to install mailman with the RPM mailman-2.0.13-3.i386.rpm
> - My system ist RedHat 8.0 whit sendmail
>
> My problem is:
> The installation was succsesfully.
> /var/mailman/bin/check_perms was succsesfully
ther missing aliases.
-Original Message-
From: Jon Carnes [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 18, 2003 10:12 PM
To: Frank L. Parks
Cc: [EMAIL PROTECTED]
Subject: Re: [Mailman-Users] No mail going out to lists members
Wow! I think that is the best problem ticket I&#x
Wow! I think that is the best problem ticket I've ever seen for
mailman.
You checked cron, so you are not running qrunner out of cron. You *are*
running Mailmanctl which starts up the qrunners.
The aliases should be taking the incoming mail and handing them off to
cgi's that either handle the in
12 matches
Mail list logo
