On 6/17/08, Allan Odgaard wrote:
For the web page forms to accept non-ASCII I had to put this:
add_language('en', 'English', 'utf-8')
Into `/etc/mailman/mm_cfg.py`. I think utf-8 should be the default
because even on an English list, you can use non-ASCII punctuation,
glyphs, and many
On 6/17/08, Allan Odgaard wrote:
I transferred a lot of list members from a previous list. A dozen of these
has left errors like the following in `logs/smtp-failures`:
delivery to «address» failed with code 450:
4.1.2 «address»: Recipient address rejected:
Domain not found
You'r
On 6/17/08, Allan Odgaard wrote:
I copied a list's mbox to a new server and regenerated the archive.
Unfortunately threading is not rendered satisfyingly, here are the
two Mailman/pipermail versions:
Your threading got broken somehow, but I can't tell you how. This
would need further inv
On 6/17/08, Allan Odgaard wrote:
I followed the FAQ' and sent a `who «password»` to my old list (where I
am administrator). This scheme had the following problems:
1. All user settings are lost (digest, no email, etc.).
2. It does not return subscribers with concealed identity (hide).
3. U
On 6/17/08, Allan Odgaard wrote:
When I look at the letters I receive from my list they do not have
my subscription address in the `Return-Path` header, so I suspect
VERP is disabled.
Correct.
I have placed the following in `/etc/mailman/mm_cfg:`
VERP_PERSONALIZED_DELIVERIES = Yes
When I look at the letters I receive from my list they do not have my
subscription address in the `Return-Path` header, so I suspect VERP is
disabled.
I have placed the following in `/etc/mailman/mm_cfg:`
VERP_PERSONALIZED_DELIVERIES = Yes
VERP_CONFIRMATIONS = Yes
But I also see opt
On a new list I had this set in `mm_cfg.py` at creation time:
OLD_STYLE_PREFIXING = No
This caused extra spaces between the tag inserted and the subject for
letters sent to the list.
I suspected that this option was the problem, but I was unable to
disable it again (seems to be another
I transferred a lot of list members from a previous list. A dozen of
these has left errors like the following in `logs/smtp-failures`:
delivery to «address» failed with code 450:
4.1.2 «address»: Recipient address rejected:
Domain not found
This is interpreted as a temporary failur
Some of my subscribers have accents and similar in their name and I
had to do the following post install to have Mailman properly work
with these:
## CLI
In order to get `list_members -f «list»` to properly output non-ASCII
user names I had to put the following:
import sys
sys.se
I copied a list’s mbox to a new server and regenerated the archive.
Unfortunately threading is not rendered satisfyingly, here are the two
Mailman/pipermail versions:
Old: http://lists.textdrive.com/pipermail/textmate/2008-January/thread.html
New: http://lists.macromates.com/textmate/
I followed the FAQ¹ and sent a `who «password»` to my old list (where
I am administrator). This scheme had the following problems:
1. All user settings are lost (digest, no email, etc.).
2. It does not return subscribers with concealed identity (hide).
3. User names with accents came through
Dony Tata wrote:
>
>- Pesan Asli
>Dari: Mark Sapiro <[EMAIL PROTECTED]>
>Kepada: Dony Tata <[EMAIL PROTECTED]>; mailman-users@python.org
>Terkirim: Senin, 16 Juni, 2008 03:16:01
>Topik: Re: [Mailman-Users] mailman patch + postfix true virtual hosting
>
>Dony Tata wrote:
>
>>i use postfix +
Carlos Williams wrote:
>I am migrating mailman from server_old (RHEL 4) to server_new (RHEL
>5). Its basically in all sense the same machine / arch / domain / blah
>blah blah.
>
>I am using this archive as a guide:
>
>http://mail.python.org/pipermail/mailman-users/2007-January/055208.html
>
>I cop
I am migrating mailman from server_old (RHEL 4) to server_new (RHEL
5). Its basically in all sense the same machine / arch / domain / blah
blah blah.
I am using this archive as a guide:
http://mail.python.org/pipermail/mailman-users/2007-January/055208.html
I copies everything over from my old s
14 matches
Mail list logo
