[Mailman-Users] messages won't go through
I am using mailman version 2.1.11.cp3 to handle 6 mailing lists for a small community organization and am having difficulty. Each list has approximately 200 members, subscribed through the mass subscription function on the list admin interface and everything seems to be working, but when I send a message to the list it doesn't seem to be going on to the addresses on the list. I know this because I have put several of my own and other member's of the teams addresses on the list and we haven't gotten anything either to spam or inbox. I have called people on the list and they haven't gotten anything either. The messages are stored in the list archives. I have tried a variety of options including sending them as moderated and non moderated, from the admin address, from a member address, from a non admin address. I have gotten two messages in return. One was a fatal bounce error from one of the member addresses and the other was an automatically generated reply from another list saying that I would have to belong to that list to post there. I have also created a small test list with just three addresses on it (my own) and the messages went through fine. I have compared options on both the real lists and the test list and have found no solution. Can anyone help me? cheers Alex Wisser __ Win 1 of 4 Sony home entertainment packs thanks to Yahoo!7. Enter now: http://au.docs.yahoo.com/homepageset/ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] messages won't go through
alex wisser wrote: I am using mailman version 2.1.11.cp3 to handle 6 mailing lists for a small community organization and am having difficulty. Each list has approximately 200 members, subscribed through the mass subscription function on the list admin interface and everything seems to be working, but when I send a message to the list it doesn't seem to be going on to the addresses on the list. Do you receive other messages from Mailman, e.g., subscription notifications? I know this because I have put several of my own and other member's of the teams addresses on the list and we haven't gotten anything either to spam or inbox. I have called people on the list and they haven't gotten anything either. The messages are stored in the list archives. I have tried a variety of options including sending them as moderated and non moderated, from the admin address, from a member address, from a non admin address. If the messages are in the archive, they have gotten past all tests of moderation, poster, etc., and they should be delivered to the list. I have gotten two messages in return. One was a fatal bounce error from one of the member addresses and the other was an automatically generated reply from another list saying that I would have to belong to that list to post there. These would seem to indicate that the list is sending something. I have also created a small test list with just three addresses on it (my own) and the messages went through fine. I have compared options on both the real lists and the test list and have found no solution. Can anyone help me? The general troubleshooting tips are at http://wiki.list.org/x/A4E9. Also see http://wiki.list.org/x/sYA9 for cPanel information. If this is your Mailman installation, the above will be useful. If it is hosted, and you don't have shell or command access to the server, you will probably need to contact the host. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] buildup of attachment files...
Thanks Mark, The list's Non-digest options - scrub-nondigest is No. In the Content Filtering -Details for pass_mime_types field I show the following: multipart/mixed multipart/alternative text/plain Would that be sufficient to do what you are suggesting if I turn Edit filter_content on? Could I then remove the attachments subdirectories? Regards, Troy on 11/16/2009 07:23 PM Mark Sapiro said the following: Troy Campbell wrote: On one mailing list I'm seeing alot of attachment files building up in the archive directory: [...] Basically there are many directories in the attachments directory that go from 20070808 to 20091116. I'm running 2.1.9. I just need to know how to cleanup and turnoff if possible. It is Scrubber.py that saves these. Depending on settings, you may get one or two copies of each attachment which is either not text/plain or text/plain with an unknown character set. If the list's Non-digest options - scrub-nondigest is Yes, you will get one saved attachment when the attachment is removed from the message and replaced by a link to the saved attachment. Otherwise, you get two. One when the attachment is scrubbed for the archive and one when the attachment is scrubbed from the plain format digest. You can avoid almost all of this by removing all non-plain text with content filtering. If you don't remove them with content filtering, you can avoid the 'digest copies' by setting Digest options - digestable to No. You can avoid the 'archive copies' by turning off archiving for the list. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] buildup of attachment files...
Troy Campbell wrote: In the Content Filtering -Details for pass_mime_types field I show the following: multipart/mixed multipart/alternative text/plain Would that be sufficient to do what you are suggesting if I turn Edit filter_content on? I suggest the following in pass_mime_types multipart message/rfc822 text/html text/plain plus collapse_alternatives and convert_html_to_plaintext = Yes This will allow the sub-parts of any multipart message including multipart/related and multipart/signed to be examined. It will also allow plain text (and HTML) from attached messages and will ultimately discard all but the first alternative from multipart/alternative and convert any remaining HTML to plain text. This will allow very little that will ultimately be scrubbed. Only text/plain attachments with unspecified character sets. Could I then remove the attachments subdirectories? You can remove the attachments directories anyway. They will be recreated if needed. The problem with removal is there are messages in the HTML archive with links to scrubbed attachments and if you remove the directory or files, you break the links. Whether or not this is important is up to you. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Held messages not appearing on administrative web page
I have a number (about 500) of old held messages in /var/lib/mailman/data that should show up on the administrative interface of the list's website, but don't. 2 questions: 1) what determines if a file in /var/lib/mailman/data shows up in the web interface? 2) How can one reindex or rebuild the contents of /var/lib/mailman/data so the missing data shows up? We are running Mailman 2.1.9 on Linux SLES 10.2. Thanks! Anne -- Anne Anderson Web Application Developer / Database Manager Information Technology Westmont College -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Access
Please help me to access my admin. account I can't get in. Also is there an info page for me to learn just how to use mailman? I'm new and dumb to this and really need some help. I use supergreen hosting and mailman came as an option. I applied with my email jsdit...@msn.commailto:jsdit...@msn.com but my password didn't work. But still not sure how to utilize your program to my needs. Which is automated mailing list to send as I develope campaigns for products or services. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Access
On Tue, 17 Nov 2009, John Ditzel wrote: Please help me to access my admin. account I can't get in. You need to contact Supergreen Hosting about this, we can't help you with this. Also is there an info page for me to learn just how to use mailman? Try http://list.org/./admins.html Geoff. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Held messages not appearing on administrative webpage
Anne Anderson wrote: I have a number (about 500) of old held messages in /var/lib/mailman/data that should show up on the administrative interface of the list's website, but don't. 2 questions: 1) what determines if a file in /var/lib/mailman/data shows up in the web interface? The presence of an entry in lists/LISTNAME/request.pck pointing to the held message in data/ and containing other info about the message. 2) How can one reindex or rebuild the contents of /var/lib/mailman/data so the missing data shows up? You can't easily. There was information in the request.pck entry that is lost. The most important part is the metadata of the held message. You could probably fake it, but you would need to create a python script to do it. It would probably be easier to create a script to unpickle the heldmsg file, remove it and requeue it in the in queue as a new message to the list. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mailman - a few questions
At 12:21 PM -0500 on 8/15/09, Shop at \ Just Brits \ wrote: So IMHO Bill needs to tell The List not only the version of MM BUT the source of install so that everybody is playing with a FULL deck of cards. Right-:) ??? I don't remember if I answered this question before or not, but just to cover all the bases: lists.sonic.net is running Mailman v2.1.11 An overview of Mailman on this server can be found at: http://lists.sonic.net/mailman/listinfo I'm also posting a note to mail...@lists.sonic.net to find out about the source. Bill -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Revisit to moderator aliases
Hi Steve, et al, Awhile back I asked some questions about managing my Mailman list such that it worked like it did back on Autoshare (an old Mac OS 9 listserver). I received some good advice, and have made some great progress in attaining most of my goals. There were still some unresolved issues, but I took a break to let others on the list tackle their problems, and also to let myself digest (no pun intended) the situation for awhile. To recap, I have a mailing list of about 300 members. The reply-to is currently customized to go to one of my personal email addresses (versus the mailmon default address of foo-l...@lists.sonic.net). When I receive the posts, I determine whether the post is appropriate for the list, and if needed, edit out extraneous text (such as excessive quoted material and/or excessive signature lines) as well as profanity or classified information that doesn't belong on the list. I then use Eudora's redirect function (keeps headers in tact) to redirect the moderated post to foo-l...@lists.sonic.net. The two outstanding issues are: 1. After I do the redirect to foo-l...@lists.sonic.net, the listserver still sends the moderation email back to me, requiring me to approve of the post (despite the fact that the envelope sender is from the list owner/moderator). When the list traffic is slow, this isn't a big issue, but when topics get hot, this becomes a major headache (receive, read, modify, send, receive again, approve). 2. Replies to digest still automatically go to foo-l...@lists.sonic.net instead of to the customized reply-to address (and there does not appear to be any way to change that). This becomes a mess because now I have a mix of non-moderated posts and moderated posts in the same place, so I have to be careful about which ones I approve. DREAM SOLUTION: I'm looking for a solution that would resolve both these issues. I imagine a solution where I set the reply-to address to foo-l...@lists.sonic.net, but somehow get the list to send those posts to me intact unmodified (versus getting the Mailman generated moderator emails with all the extraneous stuff and extra headers). Then I perform any necessary modifications, and redirect to the list, with the original heads intact, but have the list recognize the envelope sender and therefore post to the list (rather than bounce back to the moderator). I don't know if the first part of this solution is possible. However, I believe I've already received information that tells me that the 2nd part is not possible because Mailman does not have a check the envelope sender first option. Experimentation has shown me that if I send a post to the list, and the FROM sender is not a member, but the envelope sender the moderator (aka, me), it passes it through to the list. However, if the FROM sender is a member (but mod flag turned on), then Mailman holds the post for moderator approval regardless of what the envelope sender is. The FROM sender will always be a member of the list, and I want to keep the FROM sender intact; hence, unless I'm the member posting, it will always be held for moderation. In one of the earlier replies, Steve suggested the following aliases: foo-list: modera...@example.com foo-list-moderated: | mailman post foo-list This suggestion sounds a bit like the first part of my dream solution above, where I let people post to the list address (instead of the customized reply-to address). The alias would then route the post directly to me rather than to Mailman. Putting aside, for now, how I get this alias set up, I'm still stuck on how I would then get the email posted to the mailing list (since if I send it to the list address, it will just come back to me again). Perhaps that is where the foo-list-moderated alias comes into play? Taking a stab at it, I should ask my ISP to do the following: 1. Set an alias for foo-l...@lists.sonic.net to go to modera...@example.com (my email). 2. Set an alias for foo-list-modera...@lists.sonic.net to go to | mailman post foo-list. Then my steps for moderating the list would be: Receive email at modera...@example.com (originally posted to foo-l...@lists.sonic.net), perform edits as necessary, then redirect the post to foo-list-modera...@lists.sonic.net (6 steps down to 3 steps). I did a test email to foo-list-modera...@lists.sonic.net, and it was returned as no such user, so I'm guessing that I'm actually creating a new email alias as part of this solution. Does it sound like I understand the suggestion correctly? And if so, is it the solution that you think I am after? I just want to make sure I'm on the right track before I start poking my ISP for help. THANKS!! Bill -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy:
Re: [Mailman-Users] Mailman - a few questions
Bill Catambay wrote: At 6:54 AM -0700 on 8/14/09, Mark Sapiro wrote: You can do this but it will require the cooperation of the Mailman host. The cooperation part is to set SENDER_HEADERS = (None, 'from', 'reply-to', 'sender') in mm_cfg.py. Putting None first will check the envelope sender before the From: header. [...] Just for clarity, who exactly would perform the above change? My ISP who hosts Mailman? Can you give me the technically correct language I could use to suggest it to them? (i.e., so that they know exactly what to do) This needs to be done by someone at the ISP who has the ability to write to the mailman configuration file which by default is at /usr/local/mailman/Mailman/mm_cfg.py, but may be elsewhere in their installation. They would just add the one line SENDER_HEADERS = (None, 'from', 'reply-to', 'sender') to the end of the file. This will change the order of membership tests. Instead of checking for membership and moderated in the default From:, (envelope sender), Reply-To:, Sender: order, it will check in the order (envelope sender), From:, Reply-To:, Sender:. From the host's point of view, this is a global change that affects every list, so they may be understandably reluctant to do it. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mailman - a few questions
Mark Sapiro writes: They would just add the one line SENDER_HEADERS = (None, 'from', 'reply-to', 'sender') An alternative to this would be a custom pipeline with the places that checks SENDER_HEADERS altered to use that. You might also want to grep for some appropriate host's trace headers to avoid replay attacks. Sorry, I don't have time to go into detail, but I think that in combination with changing the list-post address to go directly to the moderator should do what Bill wants to happen. It has the big advantage from the host's point of view that it only affects Bill's list; the small disadvantage is a small amount of work installing the change. It's not a ton of work though; the first time I did this it took 45 minutes from deciding to do it to a working installation. I think the host should be able to do this in less than 10 minutes, as long as Bill is willing to accept the slight risk that the ML might go down until the host has time to look at it again. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Revisit to moderator aliases
Bill Catambay wrote:
The two outstanding issues are:
1. After I do the redirect to foo-l...@lists.sonic.net, the
listserver still sends the moderation email back to me, requiring me
to approve of the post (despite the fact that the envelope sender is
from the list owner/moderator). When the list traffic is slow, this
isn't a big issue, but when topics get hot, this becomes a major
headache (receive, read, modify, send, receive again, approve).
2. Replies to digest still automatically go to
foo-l...@lists.sonic.net instead of to the customized reply-to
address (and there does not appear to be any way to change that).
This becomes a mess because now I have a mix of non-moderated posts
and moderated posts in the same place, so I have to be careful about
which ones I approve.
DREAM SOLUTION:
I'm looking for a solution that would resolve both these issues. I
imagine a solution where I set the reply-to address to
foo-l...@lists.sonic.net, but somehow get the list to send those
posts to me intact unmodified (versus getting the Mailman generated
moderator emails with all the extraneous stuff and extra headers).
Then I perform any necessary modifications, and redirect to the list,
with the original heads intact, but have the list recognize the
envelope sender and therefore post to the list (rather than bounce
back to the moderator).
I don't know if the first part of this solution is possible.
However, I believe I've already received information that tells me
that the 2nd part is not possible because Mailman does not have a
check the envelope sender first option. Experimentation has shown
me that if I send a post to the list, and the FROM sender is not a
member, but the envelope sender the moderator (aka, me), it passes it
through to the list. However, if the FROM sender is a member (but
mod flag turned on), then Mailman holds the post for moderator
approval regardless of what the envelope sender is.
The FROM sender will always be a member of the list, and I want to
keep the FROM sender intact; hence, unless I'm the member posting, it
will always be held for moderation.
Your posts arrived out of sequence due to greylisting at python.org, so
I've responded to this, and Stephen, as is often the case, has an even
better idea.
I don't recall if we covered custom handlers in the earlier thread, but
there is a FAQ at http://wiki.list.org/x/l4A9 that talks about
installing a custom handler for a single list. That FAQ talks about
adding a handler to the pipeline, but what you would want is to
replace the Moderate handler with your own version. Yours would differ
from the base by changing the initial part of process() from
def process(mlist, msg, msgdata):
if msgdata.get('approved') or msgdata.get('fromusenet'):
return
# First of all, is the poster a member or not?
for sender in msg.get_senders():
if mlist.isMember(sender):
break
else:
sender = None
to
def process(mlist, msg, msgdata):
if msgdata.get('approved') or msgdata.get('fromusenet'):
return
# First of all, is the poster a member or not?
for sender in msg.get_senders(headers=(None,
'from',
'reply-to',
'sender')):
if mlist.isMember(sender):
break
else:
sender = None
Actually, you could use any sequence of headers (and None for envelope
sender) you want, You could check just the envelope sender with
for sender in msg.get_senders(headers=(None,))
Then you (the host actually) would replace Moderate with this handler
in a custom pipeline for this list only.
In one of the earlier replies, Steve suggested the following aliases:
foo-list: modera...@example.com
foo-list-moderated: | mailman post foo-list
This suggestion sounds a bit like the first part of my dream
solution above, where I let people post to the list address (instead
of the customized reply-to address). The alias would then route the
post directly to me rather than to Mailman. Putting aside, for now,
how I get this alias set up, I'm still stuck on how I would then get
the email posted to the mailing list (since if I send it to the list
address, it will just come back to me again). Perhaps that is where
the foo-list-moderated alias comes into play?
Exactly. foo-list: becomes an alias for you and foo-list-moderated:
becomes the actual list posting address. Or, you (read the host) could
make the foo-list: alias like
foo-list: |/path/to/mailman/mail/mailman owner foo-list
so it would be a synonym for foo-list-owner and you wouldn't have to
bug the host if you wanted to change the address (note Stephen's
foo-list-moderated: is abbreviated and really should look more like
this one but with the 'post' argument he has).
Taking a stab at it, I should ask my ISP to do the following:
1. Set an alias for
