On 7 Sep 2008, at 23:14, [EMAIL PROTECTED] wrote:
Not sure what patches your are seeing, but right now there are zero
patches
on Launchpad and the are removed from Sourceforge.
Having two different Mailman listings on Launchpad does not help,
either.
Only one has the pogram - but neither
Richard Barrett writes:
I guess it is not intended that the old approach with sourceforge of
putting enhancements into the tracker with patch files attached,
should be followed with Launchpad. I expect someone is going to tell
me I should create my own branches of Mailman on
We have had a lot of spams sent directly to our list members (i.e. not sent
via mailman). All of them have subject headings taken from list emails
already sent out genuinely via mailman. Almost all have our specific list
prefix (but interesting not every one).
Has anyone else had this recently
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary=0-910632351-1220881949=:22767
--0-910632351-1220881949=:22767
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Hi Bill=0AI have explained already,=C2=A0I=C2=B4ve had=C2=A0a discussion li=
st for 5
Stephen J. Turnbull wrote:
Richard Barrett writes:
I guess it is not intended that the old approach with sourceforge of
putting enhancements into the tracker with patch files attached,
should be followed with Launchpad. I expect someone is going to tell
me I should create my own
Khalil Abbas wrote:
and please, leave the type of mailing aside, if you're a non believer
don't offend other people, I didn't try to shove my beliefs into your
faces and I was really offended with what you said about religion..
I've seen the same sort of thing, and it doesn't really matter
[EMAIL PROTECTED]:~# cat /etc/passwd | grep mailman
[EMAIL PROTECTED]:~#
I not have mailman user.
[EMAIL PROTECTED]:~# cat /etc/mailman/mm_cfg.py | grep MAILMAN
MAILMAN_UID = 'list'
MAILMAN_GID = 'daemon'
MAILMAN_SITE_LIST = 'mailman'
[EMAIL PROTECTED]:~#
I try to run mailman with postfix owned
[EMAIL PROTECTED] wrote:
[EMAIL PROTECTED]:~# cat /etc/passwd | grep mailman
[EMAIL PROTECTED]:~#
I not have mailman user.
[EMAIL PROTECTED]:~# cat /etc/mailman/mm_cfg.py | grep MAILMAN
MAILMAN_UID = 'list'
MAILMAN_GID = 'daemon'
MAILMAN_SITE_LIST = 'mailman'
[EMAIL PROTECTED]:~#
I try to run
David Beaumont wrote:
We have had a lot of spams sent directly to our list members (i.e. not sent
via mailman). All of them have subject headings taken from list emails
already sent out genuinely via mailman. Almost all have our specific list
prefix (but interesting not every one).
Has anyone
I notice this list's archives are not standard
mailman format!
I assume by 'this list' you mean [EMAIL PROTECTED] In what way
are the archives not standard?
Thanks I mean the archives at
http://www.mail-archive.com/mailman-users%40python.org/
Ours are at
David Beaumont wrote:
I notice this list's archives are not standard
mailman format!
I assume by 'this list' you mean [EMAIL PROTECTED] In what way
are the archives not standard?
Thanks I mean the archives at
http://www.mail-archive.com/mailman-users%40python.org/
We don't run those.
David Beaumont wrote:
I notice this list's archives are not standard
mailman format!
I assume by 'this list' you mean [EMAIL PROTECTED] In what way
are the archives not standard?
Thanks I mean the archives at
http://www.mail-archive.com/mailman-users%40python.org/
Ours are at
Hi,
I have googled this with little luck... :-(
Is there anyone who attempted an archive import of listserv archives
into mailman ?
I am looking for any kind of pointers/hints/suggestions/successes/failures.
How you did it, was it successful, any gotcha' to be aware of ...
Thanks in
Hi,
I have googled this with little luck... :-(
Is there anyone who attempted an archive import of listserv archives
into mailman ?
I am looking for any kind of pointers/hints/suggestions/successes/failures.
How you did it, was it successful, any gotcha' to be aware of ...
Thanks in
Wondering whether anyone has suggestions for dealing with this situation.
I run two mailing lists for coachess (577 members) and referees
(377 members) in a local volunteer youth sports group. Not exactly
large lists, and typically low traffic - 3 or 4 messages on a busy
day, none at all most
-Original Message-
From: [EMAIL PROTECTED] [mailto:mailman-
[EMAIL PROTECTED] On Behalf Of Beau James
Sent: Monday, September 08, 2008 2:42 PM
To: mailman-users@python.org
Subject: [Mailman-Users] Dealing with ISPs that blacklist by message
volune?
Wondering whether anyone has
At 6:13 PM +0100 9/8/08, David Beaumont wrote:
I notice this list's archives are not standard
mailman format!
I assume by 'this list' you mean [EMAIL PROTECTED] In what way
are the archives not standard?
Thanks I mean the archives at
Thanks is this still the case at http://lists.shire.net/pipermail/dbamain/
? We have just put a password on so I am hoping that will stop robots too.
David
-Original Message-
From: Paul [mailto:[EMAIL PROTECTED]
Sent: 08 September 2008 20:00
To: David Beaumont
Cc:
It helps to disallow but the site is allowing. So possible some engines
will bot the whole site:
http://www.mail-archive.com/robots.txt
On Mon, September 8, 2008 8:25 am, David Beaumont wrote:
We have had a lot of spams sent directly to our list members (i.e. not
sent
via mailman). All of
Bill Christensen wrote:
It appears that the code which does the obfuscation is in
($prefix)/Mailman/Mailman/Archiver/HyperArch.py between lines 280 and
290 in 2.1.11. (I'm sure someone will correct me if that's wrong info)
That's one place. There are several others for addresses in the
I've just checked myself and the HTML source still seems to allow robots:
META NAME=robots CONTENT=index,nofollow on each message and META
NAME=robots CONTENT=noindex,follow on the index page. I would want
noindex and nofollow on both pages.
Changing to private archives doesn't seem to make
Karen,
Thanks for you email.
Are you sure that this was a listserv migration ?
Looks more like a Majordomo migration. In fact, I cannot match my
directory hierarchy to yours.
Thanks anyway...
Max
Karen R McArthur wrote:
**Information listed in here is not guaranteed - it worked for us**
David Beaumont wrote:
I've just checked myself and the HTML source still seems to allow robots:
META NAME=robots CONTENT=index,nofollow on each message and META
NAME=robots CONTENT=noindex,follow on the index page. I would want
noindex and nofollow on both pages.
The META tags say don't
Max,
You may get some response from this list from someone who's done this
migration, but basically, you have to pursue this from the Listserv(r)
side.
Mailman can only import archives which are in *nix mbox format. The
tools to do this are
bin/cleanarch - to check for/fix unescaped From lines
-Original Message-
From: Mark Sapiro [mailto:[EMAIL PROTECTED]
The META tags say don't 'index' the index pages themselves, but follow
the links to the messages, and on the message pages 'index' the
contents, but don't follow links.
This is appropriate for a public archive.
Beau James wrote:
The trigger seems to be that some of our subscriber's ISP domans don't
like too many incoming messages per hour from one originating domain.
Worse, some of these ISPs apparently report the domain and the IP address
of the originating MTA to some of the blacklist siets. In
Brad Knowles writes:
Khalil Abbas wrote:
and please, leave the type of mailing aside, if you're a non believer
don't offend other people, I didn't try to shove my beliefs into your
faces and I was really offended with what you said about religion..
I've seen the same sort of
27 matches
Mail list logo
