Hi all,
We have 870+ mailing lists and about 20 gigs worth of stuff in the
private/archives
directory. I thought I would do a little spring cleaning, such as
sending mail to list
owners to see if they still want their lists. But I would also like to
pare down the size
of the archives
Brad Knowles wrote:
Correct. The Mailman developers feel that forcing all
replies to go back to the list causes much more harm than
good.
For a real-world example: We run several thousand lists here
at our university (not all in Mailman) and we had a class list
set up with replies go to
I guess we might be considered a fascist regime, but mass-subscribe
is an invauable tool here at our university. Hardly any of our lists are
opt-in (what a nightmare that would be for us - we need our lists up
and populated on exact dates and ready to roll). We have class lists,
lab lists,
Brad Knowles wrote:
Mailing lists are useful for a wide variety of things, but
VT-type emergencies are not among them.
Well we definitely know that it isn't the *only* solution (there are
speakers and alarms and sirens and lights and cameras everywhere on
campus). But it is just one more
George Bannerman wrote:
I've got a tricky problem on my mailman server. Right now, I have
admin_immed_notify set to yes, but I'm not getting notifications when
there
are emails to approve. I'm also not getting the once-a-day # list
moderator request(s) waiting either. Forward messages
Jim Savoy wrote:
Reading this reminded me that I have a similar problem. All of our
lists
are set by default to be admin_immed_notify=yes, but the list owners
only
get a message when something new arrives (that is put on hold). They
never get a daily reminder about the queued-up stuff. Is
Jim Savoy wrote:
I am not all that familiar with cron. Is that crontab -u mailman
crontab.in something you need to run every time you reboot the system?
Or does it add something to /etc/cron.d or /etc/cron.daily or
/etc/crontab?
(I don't see anything new in those).
Jim Savoy answers himself:
I think I have my phantom requests (eg the -1 request(s) pending)
question
answered. Googling it I see that Mark provided a fix, but also said that
by
going to that admin page once should clear it. That may save me from
manually
having to fix hundreds of lists.
Jim Savoy wrote:
I am not all that familiar with cron. Is that crontab -u mailman
crontab.in something you need to run every time you reboot the
system?
Or does it add something to /etc/cron.d or /etc/cron.daily or
/etc/crontab?
(I don't see anything new in those).
Mark Sapiro wrote:
As you
Jim Savoy wrote:
I will probably leave the gateway news stuff out forever. And also the
password reminder thing, as we don't want to bombard our students with
more info...
Mark Sapiro wrote:
Fair enough, although the sending of reminders is a list option. You
can set
DEFAULT_SEND_REMINDERS =
Hi all,
I started a new thread for this as it no longer applies to cron, but
rather digests.
I just ran the senddigests cron option (again, for the first time ever)
but it didn't seem to do anything. I can't really understand what it
does anyway
(from the description given). All of
Mark Sapiro wrote:
The digest messages are accumulated for a list in a mbox format file
lists/LISTNAME/digest.mbox. When a new message arrives and is added to
digest.mbox and the size of digest.mbox is now greater than the list's
digest_size_threshold, a digest is sent at that time for that
Mark Sapiro wrote:
The digest messages are accumulated for a list in a mbox format file
lists/LISTNAME/digest.mbox. When a new message arrives and is added to
digest.mbox and the size of digest.mbox is now greater than the list's
digest_size_threshold, a digest is sent at that time for that
Mark Sapiro wrote:
You need the cron job because nothing else in Mailman sends digests
periodically. The only other mechanism sends a digest when the list's
digest.mbox exceeds a certain size, which may not happen for weeks on
a low traffic list.
Ok I understand 100% now. The only reason I
Jim Savoy wrote:
I did check out a couple of the lists that had outstanding
digest.mboxes and found that they didn't have any subscribers with the
digest option checked.
Mark Sapiro wrote:
But, assuming this is a more or less standard Mailman (2.1.5), even if
no one is subscribed to the
Mark Sapiro wrote:
Thanks for the MAILTO info.
Try
su mailman
cron/senddigests
Boom. That worked. All (but 3) of the 501 digest.mboxes are gone
now and I got a delivery from the list I am a digest member of.
It ran rather quickly too (1 minute flat).
If/when we resolve this, I guess I'll
Mark Sapiro wrote:
Try
su mailman
cron/senddigests
Since we are trying to troubleshoot a very mysterious problem, I should
include all of the information I have. When I ran senddigest by hand (as
user mailman), I did get a warning:
[mailman cron]$ ./senddigests
Jim Savoy wrote:
So obviously, this has something to do with this being run from cron.
You would think all of it would fail though (the checkdbs stuff runs
fine from cron).
Hmmm - the above may not be true. Checkdbs did not run this morning.
Mark Sapiro wrote:
What does crontab -u mailman -l
Savoy, Jim wrote:
If/when we resolve this, I guess I'll have to start a new thread on
why those 3 didn't go away. :-)
Mark Sapiro wrote:
Are they for lists that had a post arrive during or immediately after
the time the digest was sent? In other words do they just contain
messages waiting
Savoy, Jim wrote:
Two of them yes, but the other two no.
Mark Sapiro wrote:
For the two old ones, be sure to check the list's digest_send_periodic
setting.
Right. That was the difference. They are the only two that say NO to
this query.
Thanks for everything, Mark
Sorry to break the thread on this (my previous message didn't go
through, so I guess this
list is being moderated now).
Anyway, just wanted to say that I fixed my regexp problem. I am running
an older version
of Mailman, so tried this instead:
\nfrom:.*unique.name
and it worked!
Hi all - I am trying to have all of the mail sent to a certain email
account automatically forwarded
to a moderated mailing list (moderated to everyone accept the mail from
this particular email
account). So I created the account (we'll call it
unique.n...@some.domain) and set up the mailing
I wrote:
Anyway, just wanted to say that I fixed my regexp problem. I am running
an older version of Mailman, so tried this instead:
\nfrom:.*unique.name
and it worked!
Looks like I spoke to soon. It actually did not work. I have also tried
\n.*unique.name and that failed as well (I assumed
Jim, try
from: .*@(?!.*uleth.ca)
The 'anything before the @ sign' is obvious, but the '?!.*' is to test
for possible machine names, in case they're there.
Nope. That failed. I added a \n to the front of this and that failed
as well. I didn't think I would have to make any accommodations for the
George Booth wrote:
Why don't you just add the email account to the list, set it for no
mail,
and set it so it's unmoderated?
Well that was the first thing I did, but that didn't work because the
mail
is not technically coming from that account. It's coming from whoever
originally
sent it (the
I looked at one of the actual headers (I am not posting the actual name
I am using as we don't want anyone to mail to it just yet!) but it
looked
like this:
To: Name, Unique unique.n...@uleth.ca
Since there is a dot in the username, I thought maybe that was fouling
up
the regular expression, so
CNulk writes:
Hi Jim,
I may be completely wrong (heck, wouldn't be the first time), but why
not have your unique.name address be an alias to a simple
bash/perl/etc. script which simply accepts the email message, rewrites
the message to be from the unique.name address, and sends it on to the
Mark Sapiro wrote:
What you need is a custom handler. See the FAQ at
http://wiki.list.org/x/l4A9 for how to install one.
Thank you. Done.
In your case, the handler is very simple - just 9 lines.
import re
cre = re.compile('unique\.name', re.IGNORECASE)
def process(mlist, msg, msgdata):
if
I also just noticed that the shunt queue started to fill up with
messages
for other lists as well, so I quickly removed the line I had inserted
into
Defaults.py, stopped/started the Mailman processes, and successfully
unshunted
everything. I was hoping the code would only affect the one list I am
I also just noticed that all of the other handlers have an accompanying
.pyc file, but my Foo.py does not. Perhaps that 'c' stands for
compiled
and I was supposed to compile the code first? (probably seems obvious to
someone familiar with Mailman/Python).
Mark Sapiro wrote:
You used some kind of word processor to create foo.py that concatenated
lines 2 and 3 into a single line. Your Foo.py file must be just like
my original example with lines 1, 2 and 3 at the left margin, lines 4
and 6 indented 4 spaces and lines 5, 7, 8 and 9 indented 8 spaces.
Depending on the options set in vi, it can do horrible things to
indentation when you paste things in :(
I just looked at your original posting (using Outlook) and line 3 is
not indented, but rather continuous from line 2, and the other indents
are in columns 5 and 9 (not 4 and 8). I shall try
Mark Sapiro wrote:
Did you put 'Foo' back in the GLOBAL_PIPELINE prior to 'Moderate' and
restart Mailman?
I did.
What happens when you mail to test.account? Is the mail rejected by
Mailman? Does the To: header in the mail in the reject notice contain
'test.account'?
Yes, it is rejected. And
Hi Mark,
I got it to compile properly, but it is still not working.
I made the following changes in Foo.py:
import re
cre = re.compile('test.account', re.IGNORECASE)
def process(mlist, msg, msgdata):
if mlist.internal_name 'abc-l':
return
if cre.search(msg.get('to', '')):
Mark Sapiro wrote:
That would be the To: header of the reject notice.
Yes. That is the message I am analyzing.
Mailman sends a multipart/mixed message with two parts - a text/plain
part containing the reject reason and a message/rfc822 part containing
the post as received by Mailman. It is the
Hi all - I am running Mailman 2.1.5 (still!).
I was wondering what it is that determines if a message has scrubbed
attachments. For instance, a couple of days ago, I sent a simple message to
one of my lists - just a sentence or two of text, and it created a directory
under
to NO on all lists, I don't imagine we're doing any filtering anyway.
As for the listname.mbox file, there isn't one. That directory has always
been empty.
The attachments dfirectory is very large though.
- jim -
On Wed, May 5, 2010 at 7:44 PM, Stephen J. Turnbull step...@xemacs.orgwrote:
Savoy, Jim
37 matches
Mail list logo
