For users who have their mail go through procmail the problem can be
fixed by a rule like the following. But in light of Brads letter, I
feel it is necessary to add a disclaimer saying that if this setting
gets you killed or fired, I cannot be held responsible! :p
:0 fw
* [EMAIL
On 19 Jun 2008, at 08:38, adsarebad-at-. wrote:
[...]
Also it seems clicking reply on a msg here does a off list reply. So
all my previous reply`s were done off list.
It is the default for new Mailman installs and the admin UI even has:
Where are replies to list messages
On 19 Jun 2008, at 15:53, Mark Sapiro wrote:
[...] You have said in another thread that these links contribute to
excessive verbosity of the labels, but they often link to useful
supplemental information.
I don’t dispute that. I am sure there are lots of useful info there,
but it drowns
On 18 Jun 2008, at 20:32, Terri Oda wrote:
[...]
I've opened up a new page on the wiki to get more of a process going:
http://wiki.list.org/display/DEV/Web+Interface
This is great, but how should we use it? :)
I think the easiest is simply to go through all settings, decide what
is
On 17 Jun 2008, at 18:47, Mark Sapiro wrote:
[...]
If you want Mailman to VERP all deliveries, just set
VERP_DELIVERY_INTERVAL = 1 and don't worry about personalization.
Thanks, I ended up with just this one and it works.
--
Mailman-Users
On 17 Jun 2008, at 18:53, Mark Sapiro wrote:
Brad Knowles wrote:
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
On 17 Jun 2008, at 06:01, Brad Knowles wrote:
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
On 18 Jun 2008, at 10:04, adsarebad-at-. wrote:
I have searched all over for how to do true virtual list with
mailman and finely decided to run multiple mailman installs side by
side.
Have you seen http://www.gurulabs.com/downloads/postfix-to-mailman-2.1.py
?
It was included
On 18 Jun 2008, at 02:49, Mark Sapiro wrote:
[...]
Into `/etc/python2.5/sitecustomize.py`. This is despite proper setup
of `LC_CTYPE` on the system. Seems to me Mailman should use the
encoding of the current locale, not this site-wide Python default
encoding (settable by root only).
I am aware
On 18 Jun 2008, at 17:51, Brad Knowles wrote:
Allan Odgaard wrote:
I don’t think it will verify that the domain is the proper one (for
mails sent to each list), but it should be simple to duplicate the
service as mailman-list-a, b, c and setup the different ones to be
used as transport
On 18 Jun 2008, at 17:45, Mark Sapiro wrote:
Allan Odgaard wrote:
Raw mbox file.
And new letters sent to the list also show up with wrong indent in
the
web archive.
I'm only guessing, but I think there must have been some issue with
the
mbox file that caused the archive database file
On 18 Jun 2008, at 17:49, Brad Knowles wrote:
[...]
It is not necessary to recommend to others that they disable this
feature on their copy of postfix. Instead, you should be
recommending to them exactly what I recommended to you, which was to
run a second copy of postfix with all checks
On 18 Jun 2008, at 16:09, Mark Sapiro wrote:
[...]
The process of adding the list header and/or footer to the message
attempts to add these to a text/plain body by coercing the body and
the header/footer to unicode, concatenating them and then coercing
back to the original body charset. If the
On 18 Jun 2008, at 17:41, Terri Oda wrote:
[...] the more user input we get, the better!
Another thread said that “the web UI is scheduled for overhaul”.
Is anyone assigned to this? Is it an open process? Can we follow it
somewhere?
I think the admin UI suffers from:
1. Too many
On 19 Jun 2008, at 01:33, Mark Sapiro wrote:
[...]
The problem that I had initially and that you are apparently having
now is that at some point, they accept your mail and then silently
discard it. That hasn't happened to me again since the mitigation
period, but I'm never relaxed about
On 19 Jun 2008, at 00:24, Mark Sapiro wrote:
So should I consider it a bug that setting list encoding to utf-8
will
(in my experience) _always_ produce (base 64 encoded) utf-8 letters,
when both header/footer and letter itself sent to list is ASCII?
You may consider it a bug if you wish. It
On 18 Jun 2008, at 20:59, adsarebad-at-. wrote:
Have you seen http://www.gurulabs.com/downloads/postfix-to-mailman-2.1.py
?
[...]
I think I may have ran into that file in my travels, can`t remember
for sure through because I ran into so many. Is that the one where
I need to have
On 18 Jun 2008, at 22:46, Mark Sapiro wrote:
[...]
I have never before seen a report like this. Since it occurs for a new
list, there is apparently something wrong with the Mailman
installation itself. If it were a problem with the Ubuntu package, I
think it would have been seen elsewhere, so I
On 19 Jun 2008, at 07:00, Allan Odgaard wrote:
On 18 Jun 2008, at 22:46, Mark Sapiro wrote:
[...]
I have never before seen a report like this. Since it occurs for a
new
list, there is apparently something wrong with the Mailman
installation itself. If it were a problem with the Ubuntu
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
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:
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
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
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
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
25 matches
Mail list logo
