Hi,
I am using mailman 2.1.29, pipermail 0.09 , I am facing a problem with the
archives attachment. The HTML attachments are scrubbed in the url like
"mailman/private/announce/attachments/20191231/1ef651ee/*attachment.htm*" ,
when we open that url it shows as a html source code. can anyone
Mark Sapiro wrote:
Then the recent posts are probably not in the
archives/private/LISTNAME.mbox/LISTNAME.mbox file, perhaps because of
some permissions error. If that is the reason, they are probably all
shunted and in the shunt queue. If so, you will find error messages
and tracebacks in
LexIcon wrote:
[...]
... so no March errors, and I'm still not getting anywhere.
That appears to be almost an exact repost of
http://mail.python.org/pipermail/mailman-users/2010-March/069102.html
which was answered at
http://mail.python.org/pipermail/mailman-users/2010-March/069103.html.
Did
In regards to previous list message
http://mail.python.org/pipermail/mailman-users/2008-February/060593.html ...
I am entering arch in the /bin directory (/usr/lib/mailman/bin on a
CentOS server), but the archive does not rebuild, and I only get the
message i686 back.
I tried using
LexIcon wrote:
I am entering arch in the /bin directory (/usr/lib/mailman/bin on a
CentOS server), but the archive does not rebuild, and I only get the
message i686 back.
I tried using cleanarch but I get the error message bash: cleanarch:
command not found
I also get bash: mailmanctl:
You're using the wrong arch; there's an arch command that tells you your
machine's architecture (i.e. i686).
What you'll want to do is go into /usr/lib/mailman/bin and execute
./arch
and similarly for cleanarch
./cleanarch
from there to make sure that you're executing the right thing. Or
Mark Sapiro wrote:
LexIcon wrote:
I am entering arch in the /bin directory (/usr/lib/mailman/bin on a
CentOS server), but the archive does not rebuild, and I only get the
message i686 back.
I tried using cleanarch but I get the error message bash: cleanarch:
command not found
I also
LexIcon wrote:
Ok, so I ran...
//usr/lib/mailman/bin///checkperms -f/
... and it fixed a bunch of issues... the current result is No problems
found ... and now and I'm running...
//usr/lib/mailman/bin/arch listname//
/
... which processes a bunch of stuff, but the archive still does not
Mark Sapiro wrote:
Then the recent posts are probably not in the
archives/private/LISTNAME.mbox/LISTNAME.mbox file, perhaps because of
some permissions error. If that is the reason, they are probably all
shunted and in the shunt queue. If so, you will find error messages
and tracebacks in
LexIcon wrote:
Ok, so I ran...
chown -hR mailman private/
... and changed the owner of everything in there to the mailman user. I
then ran...
What you really want is
chgrp -R mailman private/
./unshunt
... which took a long time to process, and then I ran...
./arch listname
... which
When messages are archived in mailman, they are losing their original format.
Tables appear as text and are not readable. I would like to retain the original
format as is.
Please suggest.
Regards,
Krishna
--
Mailman-Users mailing list
Krishnadas Kossery wrote:
When messages are archived in mailman, they are losing their original format.
Tables appear as text and are not readable. I would like to retain the
original format as is.
What is the original format.
Please be more specific as to what is sent to the list, what is
Thank you Mark. We found a work around by providing a link in the footer as an
attachment.
Krishna
-Original Message-
From: Mark Sapiro [mailto:m...@msapiro.net]
Sent: Wednesday, October 21, 2009 7:39 AM
To: Krishnadas Kossery; mailman-users@python.org
Subject: Re: [Mailman-Users
Hello
I'm relatively new to mailman. I've searched the mailman lists and tried to
find a solution to my issue
but nothing.
Has anyone encountered the below issue and could offer some help.
I recently moved mailman from one server to another.I tarred up the old
archives and moved
them to the
Anthony Human wrote:
I recently moved mailman from one server to another.I tarred up the old
archives and moved
them to the new server, and simply untarred them into:
/usr/local/mailman/archives/public/[list-name]
That's your first problem. The archives are always in the
archives/private/
I found out the path to my mailing list archives. I first checked the link
on the admin page -go to list archives - 2006-June.txt.gz File name. I
then did a find on this file on our server. I found out that my archives
were in /var/lib/mailman/archives/public/newlist directory. I think by
Uthra Rao wrote:
I found out the path to my mailing list archives. I first checked the link
on the admin page -go to list archives - 2006-June.txt.gz File name. I
then did a find on this file on our server. I found out that my archives
were in /var/lib/mailman/archives/public/newlist
I added the correct path to the pipermail alias in the httpd.conf file and
restarted apache. I can now access the archive by typing
http://hostname/pipermail/newlist.
Thank you very much for your help.
UR.
At 12:35 PM 6/22/2006, you wrote:
Uthra Rao wrote:
I found out the path to my
For my mailing list the archiving options are as follows:
Archive message - YES
Is archive file source for Public or Private - PUBLIC
How often should a new archive volume be started - MONTHLY
This is the default setting and I did not change it. When I post a message
to the mailing list
On 6/20/06, Uthra Rao [EMAIL PROTECTED] wrote:
For my mailing list the archiving options are as follows:
snip
I created the archives/public directory and its owner/group is mailman. I
am not sure why my message is not getting archived. Could someone please
guide me on this?
Are the files
On 6/20/06, Uthra Rao [EMAIL PROTECTED] wrote:
I only created /usr/lib/mailman/archives/public directory and that is
empty. I don't have a /usr/lib/mailman/archives/private/list.mbox/list.mbox
Is Mailman install set to archive?
('DEFAULT_ARCHIVE' -- This is 'On' in Defaults.py, but it might be
At 03:33 PM 6/20/2006, you wrote:
On 6/20/06, Uthra Rao [EMAIL PROTECTED] wrote:
I only created /usr/lib/mailman/archives/public directory and that is
empty. I don't have a /usr/lib/mailman/archives/private/list.mbox/list.mbox
Is Mailman install set to archive?
('DEFAULT_ARCHIVE' -- This is 'On'
On 6/20/06, Uthra Rao [EMAIL PROTECTED] wrote:
Yes these links go to the messages that were posted in this
mailing list.
So, what's the problem? Or am I missing something?
It seems like your archiving is working as it's supposed to, yes?
The only issue I see here is that the archives
From the admin web page of the list I am able to see the archives but if I
login to the system and cd to /usr/lib/mailman/archives/public I don't see
anything. I would like to know in which directory it is archiving the
messages?
Thank You.
Uthra
At 04:43 PM 6/20/2006, you wrote:
On
On 6/20/06, Uthra Rao [EMAIL PROTECTED] wrote:
From the admin web page of the list I am able to see the archives but if I
login to the system and cd to /usr/lib/mailman/archives/public I don't see
anything. I would like to know in which directory it is archiving the
messages?
Check your
Uthra Rao wrote:
From the admin web page of the list I am able to see the archives but if I
login to the system and cd to /usr/lib/mailman/archives/public I don't see
anything. I would like to know in which directory it is archiving the
messages?
All archives are created and maintained in
Chris Rammos wrote:
First of all i would like to give you a sample of what i want to do ...
In my mailman archives i have a post like ...
FW: [SECURITY] [DSA 669-1] New php3 packages fix several vulnerabilities
*First_Name Last_Name * username_at_domain.com
/Tue Feb 8 10:31:32 EET 2005/
Hello to all,
i am a new member in this list and i hope that we'll have a great
cooperation.
First of all i would like to give you a sample of what i want to do ...
In my mailman archives i have a post like ...
FW: [SECURITY] [DSA 669-1] New php3 packages fix several vulnerabilities
*First_Name
Hi Brad,
I'm using MailMan 2.0.11 as default for Debian Woody.
When I now try to access the archive, it ask email and password as it
should be, and after a succesful login, I can select the messages I
would like to see. When I then select a thread, it asks me again to
login.
At 6:22 PM +0200 2004-08-04, Wolfgang Riedmann wrote:
I have now looked at www.backports.org, and there is a newer version
available: 2.1.4. Should this cure my problems?
It's hard to say. There are a lot of issues in making an upgrade
of this scale, and making this big a leap may cause more
Hi,
I have a mailman installation on a Debian 3 Woody server.
For a list I have configured the archive option o be active only for
subscribed users.
When I now try to access the archive, it ask email and password as it
should be, and after a succesful login, I can select the messages I
would
hello,
i'm new to mailman(2.1.2) and i have a question, which might seem simple to
you ...
the question is:
how to change default charset in archives (created by pipermail) from
iso-8859-1 to iso-8859-2, so IE 6.0 or any other browser could pick up the
right charset?
i've tried to change the
It doesn't do a complete job of obscuring email addresses in archived email.
1. Some email clients use the users' email address as the base of the
message-id.
2. Mailmain doesn't obscure email addresses in the body, so if this message
were archived, then [EMAIL PROTECTED] would
appear in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday, November 30, 2002, at 06:30 PM, John Summerfield wrote:
It doesn't do a complete job of obscuring email addresses in archived
email.
[snip]
2. Mailmain doesn't obscure email addresses in the body, so if this
message
were archived,
-Original Message-
From: Chris Hedemark [EMAIL PROTECTED]
Sent: Sunday, December 01, 2002 3:11 PM
It is easy for a user to render their email address relatively
unrecognizable to harvesters if they so desire (indeed, this
has been a common practice for years).
That is false.
35 matches
Mail list logo
