On Thu, Mar 13, 2008 at 10:26 PM, Mark Sapiro [EMAIL PROTECTED] wrote:
I am happy to announce the next beta release of Mailman 2.1.10.
This is a security and bug fix release and it is highly recommended
that all sites upgrade to this version.
Everyone? Or just 2.1.10 beta testers?
Are
Hi,
I am having an issue with the list_lists command, as well as the
listinfo CGI.
Also, when running the check_db script, it starts to go through the
lists, then stops with the same error below after about 6 lists. My
question is that something seems to be wrong with a list database
Hi,
I think mailman discards messages if i send a
text/html message, So how to enable that?
--
regards,
Prashanth
http://munichlinux.blogspot.com
--
Mailman-Users mailing list
Mailman-Users@python.org
Jim Popovitch wrote:
On Thu, Mar 13, 2008 at 10:26 PM, Mark Sapiro [EMAIL PROTECTED] wrote:
I am happy to announce the next beta release of Mailman 2.1.10.
This is a security and bug fix release and it is highly recommended
that all sites upgrade to this version.
Everyone? Or just 2.1.10
Prashanth wrote:
I think mailman discards messages if i send a
text/html message, So how to enable that?
In Content filtering, set filter_content to No or add text/html to
pass_mime_types.
However, your Subject: mentions Topics, so if you are asking about
Keywords: lines in
I've looked in the FAQ section and don't see anything regarding this.
All of a sudden, as of yesterday, I'm not receiving the requires approval
notices. I am not
knowledgeable with the technical stuff at all, but the settings say yes to
receive these notices immediately. While the listkeeper on
AJ wrote:
I am having an issue with the list_lists command, as well as the
listinfo CGI.
Also, when running the check_db script, it starts to go through the
lists, then stops with the same error below after about 6 lists. My
question is that something seems to be wrong with a list
Bonnie M wrote:
All of a sudden, as of yesterday, I'm not receiving the requires approval
notices. I am not
knowledgeable with the technical stuff at all, but the settings say yes to
receive these notices immediately. While the listkeeper on my list feels is
not a big deal, as we go and check
I am almost hesitant to post this email at all, because I am so amazingly
confused at what is going on I half-think I'm imagining it.
I have a Mailman 2.0.12 instance (not 2.0.5 as I previously thought, sorry
Mark) running on a Solaris 8 SPARC server, which I'd planned to move onto a
Linux
Christopher Waltham wrote:
process snipped, but it looks OK
The problem is when I run bin/list_members on a list of whose membership I
know well. Amazingly, when I run that command, I see list members from around
2-3 years ago; I do not see list members whom I absolutely know are on that
Again, apologies for the way Exchange Webmail quotes messages.
-Original Message-
From: Mark Sapiro [mailto:[EMAIL PROTECTED]
Sent: Fri 3/14/2008 1:37 PM
To: Christopher Waltham; mailman-users@python.org
Subject: Re: [Mailman-Users] What is really required to go from 2.0.x to 2.1.y?
The
We have an automated system that programmatically adds users to lists using the
email command functionality (subscribe nodigest address=$theemailaddress).
Though, some of the lists are large and occasionally we get the returned email
response:
We have received a message from your address
Hello,
I had the Mailman lists working but needed to update the URL's in the
mm-cfg.py file to change the name. I now cannot send mail to the lists when
using procmail to force it through SpamAssassin.
I get the following errors in my maillog:
Mar 7 12:37:15 xaanm10anp sendmail[17241]:
Christopher Waltham quoted me and wrote:
A possibly viable alternative is to look at your 2.1.9
installation and just remove the config.pck and config.pck.last
files from any lists/listname/ directory that has a config.db.
Mailman will then convert the config.db the first time the list
is
A mailman archive was inadvertently made public for a list I own (!) and
I'm trying to clean up any pages that were cached by search engines.
The way to flush the cache created by search engines is easy - just add an
html tag in the header section of the webpage pages. But I can't figure
out
Robin Lougee-Heimer wrote:
A mailman archive was inadvertently made public for a list I own (!) and
I'm trying to clean up any pages that were cached by search engines.
The way to flush the cache created by search engines is easy - just add an
html tag in the header section of the webpage
Brian Herold wrote:
We have an automated system that programmatically adds users to lists using
the email command functionality (subscribe nodigest address=$theemailaddress).
Though, some of the lists are large and occasionally we get the returned
email response:
We have received a message
liste yoneticisi wrote:
Actually I just want a vissible message for deleted/filtered attachments.
Actually, given the current architecture of content filtering, this
turns out to be not at all easy to do in any reasonable way. About the
best that could be done without too much difficulty is
On 3/14/08, Jones, Stephen \(SJONES\) wrote:
I had the Mailman lists working but needed to update the URL's in the
mm-cfg.py file to change the name. I now cannot send mail to the lists when
using procmail to force it through SpamAssassin.
First off, you don't want to use procmail to
19 matches
Mail list logo
