[EMAIL PROTECTED] wrote:
>When I create a new list and put my email address, I do receive a
>confirmation. I can deliver mail as root also from my server. Once I
>try and post to the list is when nothing happens, just a bounce back
>saying the "Connection is refused." The only clue I can see if
Josh Clark wrote:
>
>Also, I should have noted in my original messge that this installation
>was recently moved from another server, and I believe that my failed
>attempt is actually the first message that's being sent to the list
>through the new setup (it's used as a broadcast newsletter li
When I create a new list and put my email address, I do receive a
confirmation. I can deliver mail as root also from my server. Once I
try and post to the list is when nothing happens, just a bounce back
saying the "Connection is refused." The only clue I can see if the
following in my maillog:
Mark Sapiro wrote:
>Bill Moseley wrote:
>
>>My question is why is mail to mailmain@ seemingly getting delivered to
>>[EMAIL PROTECTED]
>
>
>My first guess, assuming you've verified the above by actually sending
>your own message to [EMAIL PROTECTED], is that your MTA aliases or whatever
>are pipin
Bill Moseley wrote:
>Mailman version 2.1.8
>
>I administer mailman on a few domains, and on one I receive a lot of
>spam seemingly sent to the mailman@ list. I can work on my spam
>filters, but I'm trying to understand the path the mail is taking
>through mailman.
>
>The mailman@ list has only me
Hi Mark,
Many thanks for your help.
Is your Mailman/Handlers/Decorate.py unmodified?
This is an unmodified installation.
What do you see as the value of msg_footer from the output of
bin/config_list -o - listname | grep -A10 msg_footer
Here's what I get:
$ bin/config_list -o - moxiema
Josh Clark wrote:
>
>I'm having trouble sending a message from one of my lists using
>Mailman 2.1.11. The message itself is entirely ascii and sent with the
>US-ASCII charset, but it's failing with a "unicode is not supported"
>error. My (extremely unsophisticated) reading of the error log le
Daniel Novotny wrote:
>
>we have stumbled upon a problem, that in msg_footer,
>Mailman discards the space at the end of the signature delimiter "-- ",
>which should be two dashes and space,
>according to http://www.guckes.net/mail/sig.etiquette.html#sigdashes
>
>the code (Mailman/Handlers/Decorat
Mailman version 2.1.8
I administer mailman on a few domains, and on one I receive a lot of
spam seemingly sent to the mailman@ list. I can work on my spam
filters, but I'm trying to understand the path the mail is taking
through mailman.
The mailman@ list has only me as the admin and NO members.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi list,
i'm searching for a way (script, software, ...) to import a
pipermail-archive (formated like the archives of this list) into a
relational SQL-database (MySQL or PostgreSQL) incl. the thread- and
date-based structure.
For my PhD I want to analy
Hi,
I'm having trouble sending a message from one of my lists using
Mailman 2.1.11. The message itself is entirely ascii and sent with the
US-ASCII charset, but it's failing with a "unicode is not supported"
error. My (extremely unsophisticated) reading of the error log leads
me to believ
hello,
we have stumbled upon a problem, that in msg_footer,
Mailman discards the space at the end of the signature delimiter "-- ",
which should be two dashes and space,
according to http://www.guckes.net/mail/sig.etiquette.html#sigdashes
the code (Mailman/Handlers/Decorate.py) says
text = re.
Andre Tann, Montag, 27. Oktober 2008 11:14:
> Can anybody tell me what's going on here? Where can I start my
> search?
OK... Postfix did not listen to localhost, where Mailman tried to
deliver the mails to...
--
Andre Tann
--
Mailman-Users
Hello everyone,
there is a mailman problem on my machine which i cannot really
locate. I can send a mail to one of the lists. The mail is
delivered to mailman. But then as I see in the postfix logs, the
mail never returns back to the postfix system.
Instead, mailman produces errors like these:
14 matches
Mail list logo