Stephen J. Turnbull wrote:
John Fitzsimons writes:
This message was delivered by email from Gmane to mailman. It was
apperently posted via NNTP to Gmane by the poster and then mailed by
Gmane to the list.
Hopefully Gmane waits for the reply to the list email before it
accepts the
Stephen J. Turnbull wrote:
Mark Sapiro writes:
This is all irrelevant. Since the posts from Gmane are arriving via the
NNTP gateway, no membership tests whatsoever are applied to the post -
no list member, no moderation, no *_these_nonmembers.
Are you sure? The way I read
Received:
Mark Sapiro writes:
Hopefully Gmane waits for the reply to the list email before it
accepts the post.
I'm not sure what you're asking,
I think what John wants to happen is the following. Whether it actually
works this way or not, I don't know, but I think it might.
- User
There's a lot in there so I attached it. Not sure if this list allows
attachments but I'll try here anyways.
-Original Message-
From: Mark Sapiro [mailto:m...@msapiro.net]
Sent: Thursday, January 21, 2010 10:04 AM
To: Young, Darren; mailman-users@python.org
Subject: RE:
Young, Darren wrote:
There's a lot in there so I attached it. Not sure if this list allows
attachments but I'll try here anyways.
The text/plain attachment was allowed, but the message was too big. I
trimmed the attachment leaving only a few relevant parts. See my
comments inline and at the
The text/plain attachment was allowed, but the message was too big. I
trimmed the attachment leaving only a few relevant parts. See my
comments inline and at the end.
I had a feeling it would be one or the other.
[...]
drwxrwsr-x 2 rootmailman 4096 Jan 20 12:26 perl-ad-manager-users
Young, Darren wrote:
Issue #2 is once again an obvious thing to have checked, but I think
archiving must be disabled in mm_cfg.py with
ARCHIVE_TO_MBOX = -1
Nothing set in mm_cfg.py for that but it is set to -1 in Defaults.py. I
just set it to 0, didn't even think about looking in there for
Issue #2 is once again an obvious thing to have checked, but I
think
archiving must be disabled in mm_cfg.py with
ARCHIVE_TO_MBOX = -1
Nothing set in mm_cfg.py for that but it is set to -1 in Defaults.py.
I
just set it to 0, didn't even think about looking in there for it,
sorry,
On Fri, 22 Jan 2010, John Fitzsimons wrote:
I would like to know how to access the archive file so that I can
delete it by FTP. I cannot however find it ! Maybe my web hoster
has somehow made the directory invisible ?
Mailman files are usually put somewhere other than in your hosting area.
Geoff Shang wrote:
On Fri, 22 Jan 2010, John Fitzsimons wrote:
I would like to know how to access the archive file so that I can
delete it by FTP. I cannot however find it ! Maybe my web hoster
has somehow made the directory invisible ?
Mailman files are usually put somewhere other than in
On Fri, 22 Jan 2010, Mark Sapiro wrote:
On Fri, 22 Jan 2010, John Fitzsimons wrote:
I would like to know how to access the archive file so that I can
delete it by FTP. I cannot however find it ! Maybe my web hoster
has somehow made the directory invisible ?
Sorry. I missed the above query.
Geoff Shang wrote:
On Fri, 22 Jan 2010, Mark Sapiro wrote:
If your FTP session is not chrooted to your own home directory or some
other limitation, you chould be able to find them.
But presumably not delete them.
Presumably not, but it wouldn't be the first time that people had
permission
On Sat, 23 Jan 2010 00:42:25 +0900, Stephen J. Turnbull wrote:
Mark Sapiro writes:
snip
Eventually, we'll find out if it works. I suspect it does,
Preliminary testing suggests that it IS working.
I do too, because larsi is not an idiot. I have to imagine that like
99% of messages that
On Fri, 22 Jan 2010 12:59:20 -0800, Mark Sapiro wrote:
Geoff Shang wrote:
On Fri, 22 Jan 2010, Mark Sapiro wrote:
If your FTP session is not chrooted to your own home directory or some
other limitation, you chould be able to find them.
But presumably not delete them.
Presumably not, but it
John Fitzsimons wrote:
But this does lead me to think of a few more questions. If I closed
my mailing list then wouldn't all the Mailman archive files be
deleted ?
That's a cPanel question. In standard Mailman, whether you remove a
list from the command line with bin/rmlist or via the rmlist
On Fri, 22 Jan 2010 15:12:46 -0800, Mark Sapiro wrote:
John Fitzsimons wrote:
snip
If I did that then I could presumably start the list again. Identical
to the previous list. But with archiving turned off from the
beginning ?
The drawback is all user options/passwords/etc. get lost.
Yes,
John Fitzsimons wrote:
Yes, the loss of user options I can live with BUT the loss of
passwords would be a concern. In this case the Gmane subscription.
I don't think the password of the Gmane subscription to the Mailman
list is important.
If I un subscribed them, then re-subscribed them,
On Fri, 22 Jan 2010 16:33:07 -0800, Mark Sapiro wrote:
John Fitzsimons wrote:
Yes, the loss of user options I can live with BUT the loss of
passwords would be a concern. In this case the Gmane subscription.
I don't think the password of the Gmane subscription to the Mailman
list is important.
John Fitzsimons wrote:
On Fri, 22 Jan 2010 16:33:07 -0800, Mark Sapiro wrote:
The script is not a screen scraper in that sense. It accesses the
list's admin Membership Management... - Membership List pages and
parses them to get the data.
Via my browser, or via an FTP logon ? I am using a
19 matches
Mail list logo
