If you have the ability to patch your Mailman installation, you could add a
new variable name (like mlist.fortune) to the ALLOWEDS array in
Mailman/Gui/Digest.py and then use the 'withlist' command to set this
variable to a new value every so often, and include it in the msg_footer
field in
--On Wednesday, January 29, 2003 3:47 PM -0800 Robin Rowe
[EMAIL PROTECTED] wrote:
Can anyone answer my question as asked? Is it possible to use the mailman
spam filtering capabilities on message bodies as well as headers?
At the risk of garnering another that's not exactly what I asked, a 2.1
There seem to be some other threads capturing people's attention, but Barry
has logged in and sent mail a couple of times :), so I'm assuming this fell
through the cracks.
I have some lists on a host running MM1.1, and a new host running MM2.1. I
need to move the 1.1 lists over to the new
--On Tuesday, January 28, 2003 5:44 PM -0500 Matthew Davis
[EMAIL PROTECTED] wrote:
-[ From mailman-2.1/UPGRADING ]-
UPGRADING FROM 1.x to 2.x [...]
Yes, I read that document (and I've used its advice in the past),
unfortunately it doesn't cover my present situation because I'm not really
I looked through all the docs and list archives for an answer to this, but
didn't find one, so here goes.
I have several large active lists on Host A that's running Mailman 1.1.
I have a new server, Host B, that's more powerful and the new home, etc,
etc, and already has a few active lists
As Mike says, look at the Privacy options. SquirrelMail is exceptionally
well-behaved (I use it myself and recommend it) so I am surprised to see
its mails rejected. However, because it is web based and (in the default
configuration) runs sendmail to send messages, there is one header you
I am seeing what appears to be a series of one-sided answer posts from
[EMAIL PROTECTED]
quoting messages that have not previously appeared on the mailman-users
list. If this person is redirecting private responses to the list without
the correspondent's permission, that's considered rude
.
--On Monday, April 15, 2002 2:09 PM -0700 Marc MERLIN
[EMAIL PROTECTED] wrote:
On Mon, Apr 15, 2002 at 07:55:01AM -0400, Tom Neff wrote:
Billie R. McNamara [EMAIL PROTECTED] wrote:
We are using version 2.0.8 for a moderated list. But, we aren't able
to edit messages before approving them
It's difficult to edit message bodies with encoded MIME parts, although one
can still edit the headers. For plain text messages, I have found the
2.0.8 patch (which simply places headers and body in separate editable
textareas) to be usable. It sure would be nice if someone would make a
Billie R. McNamara [EMAIL PROTECTED] wrote:
We are using version 2.0.8 for a moderated list. But, we aren't able to
edit messages before approving them (for example, to delete just one
inappropriate word).
How can we do this?
There is a FAQ entry that wants you to hand edit various spool
David [EMAIL PROTECTED] wrote:
Actually itis the only product that my host offers for mailing lists.
It is a damn good program in all respects other than the programmers
decision to force this on us and wrongfully cite it as following the
standards. The standards make it optional not forced.
--On Friday, March 29, 2002 9:30 PM -0500 Ron Jarrell [EMAIL PROTECTED]
wrote:
In 2.1 you can go into mm_cfg.py and break RFC2369 compliance by setting
ALLOW_RFC2369_OVERRIDES to 1. That'll enable a policy at your site that
list owners can turn it off, which will cause the cgi scripts to
Dan Wilder [EMAIL PROTECTED] wrote:
Be aware that not having [Received:] headers will make troubleshooting
certain kinds of subscriber problems more difficult. Not an
issue for announce-only lists, and maybe not so much an issue
for moderated lists, but for others, keep a copy.
The simplest
Dmitry Barabanov [EMAIL PROTECTED] wrote:
is there any easy way to strip Received: headers from messages that
mailman sends to subscribers?
There are utilities that are distributed with 'procmail' and/or 'maildrop'
that are very useful for this sort of thing, in particular 'formail' and
14 matches
Mail list logo
