[Mailman-Users] Failure of rmlist command
Hello, Just getting started with Mailman and I can't get the rmlist command to work, although it does seem to be there in the bin directory as promised. I'm in the bin directory and I type python -S rmlist which returned Traceback (most recent call last): File rmlist, line 44, in ? from Mailman import mm_cfg ImportError: No module named Mailman What am I missing here? Much appreciated. Paul Flint -- Acting JAT Web Mail List Manager and Japanese to English Translation Kawasaki Japan -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] Failure of rmlist command
I'm in the bin directory and I type python -S rmlist which returned Traceback (most recent call last): File rmlist, line 44, in ? from Mailman import mm_cfg ImportError: No module named Mailman What am I missing here? run it from ~mailman -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] allowing postings from anything
[matthew zeier] I'm trying to use mailman to replace the sysadm mailing list. I have a lot of machines that send automated emails to that address. However, all are getting rejected with: Message has implicit destination [Jon Carnes replies] Web over to the Admin pages and go to the Privacy Options page, field: Alias names (regexps) which qualify as explicit to or cc destination names for this list. and put in the full name of list you are using. I don't *think* that's the right answer. It sounds like the problem is that these automated emails don't have a To or Cc header at all, in which case adding more addresses that are accepted as meaning this list in To/Cc won't make a bit of difference. I think Matthew wants the option immediately before this one: Must posts have list named in destination (to, cc) field. Set it to No. Don't do this on a public list, of course, as you'll get lots more spam this way. You should probably restrict the list of allowed posters. Greg -- Greg Ward - software developer[EMAIL PROTECTED] MEMS Exchangehttp://www.mems-exchange.org -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] Failure of rmlist command
The files in ~mailman/bin are standalone scripts. To run rmlist simply type: ~mailman/bin/rmlist Do not pipe it as a script into python. Jon Carnes === On Thursday 18 October 2001 08:33, Paul Flint wrote: Me: I'm in the bin directory and I type python -S rmlist which returned Traceback (most recent call last): File rmlist, line 44, in ? from Mailman import mm_cfg ImportError: No module named Mailman What am I missing here? Dan Mick [EMAIL PROTECTED] wrote: run it from ~mailman From usr/local/mailman I enter python -S rmlist and it responds with python: can't open file rmlist So, I tried python -S bin/rmlist and got the earlier message: Traceback (most recent call last): File rmlist, line 44, in ? from Mailman import mm_cfg ImportError: No module named Mailman What should I try now? Paul Flint Japanese to English Translation Kawasaki Japan -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] allowing postings from anything
[Jon Carnes replies] Web over to the Admin pages and go to the Privacy Options page, field: Alias names (regexps) which qualify as explicit to or cc destination names for this list. and put in the full name of list you are using. I don't *think* that's the right answer. It sounds like the problem is that these automated emails don't have a To or Cc header at all, in which case adding more addresses that are accepted as meaning this list in To/Cc won't make a bit of difference. I think Matthew wants the option immediately before this one: Must posts have list named in destination (to, cc) field. Set it to No. Don't do this on a public list, of course, as you'll get lots more spam this way. You should probably restrict the list of allowed posters. Greg [Jon Carnes replies again...] I agree that it sounds weird, but I'm not asking them to put in another username, I am asking them to put in a Listname that is equal to what they percieve their list to be named. This has worked quite well in the past. It seems that folks with multiple domain names for their server have a problem unless they use the default domain name with their lists. Adding the full list name (with the @domain.com) solves the problem. It worked for two folks last week - both whom had identical sypmtoms as Matthew. Jon Carnes -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] Mailman + Postfix
On 18 October 2001, Alessandro Luiz Petrocino said: When a mail message is sent to the list address, my antivirus program scan the mail, searching for virus attached. The normal process shoud be: - the antivirus program scan only the original message, before send this to the list. But, this doesn't hapen ! The antivirus program scan each mail before send to the user in the list ... with this, my server is high-loaded ... Ouch! I bet what's *really* happening is that incoming message are being scanned not N times, but N+1 times: 1 when the message is received by Postfix (before being passed to Mailman), and then once for each recipient. (Err, maybe not: if your Mailman is setup in the default way, then your outgoing message will be sent 34 times -- once for each block of 500 subscribers. Thus, the scanner should run 35 times. This is still a lot worse than running once, but a lot better than running 16600 times (or whatever your N is). How the mailman wrapper communicates with the smtp server ?? Assuming you have DELIVERY_MODULE set to SMTPDirect (which you should, as it's the default), Mailman will: * open an SMTP connection to port 25 on localhost * send MAIL FROM:[EMAIL PROTECTED] * send RCPT TO:... 500 times (for the first 500 recipients) * send DATA and the message body That number 500 is configurable -- see SMTP_MAX_RCPTS in Defaults.py. If your virus scanner is running 16,600+ times, then there's something seriously wrong either with the scanner or your Postfix configuration. If your virus scanner is running 35 times (1 + (16,600 / 500)), then that is completely understandable. I can see how you might want to reduce it, though, as 34 of those runs are unnecessary. However, that's not a Mailman question -- you'll have to consult the docs for your virus scanner. Probably you want to skip scanning on messages with the SMTP sender set to your list admin address. Or something like that. Greg -- Greg Ward - software developer[EMAIL PROTECTED] MEMS Exchangehttp://www.mems-exchange.org -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] Dummyfunction Newsletter
Hi, i try to setup a Newsletter for a customer. 1) Is it possible to change the Sender-Header from Sender: newsletter@domain to Sender: Newsletter Service newsletter@domain so that in most Mail Programs the Newsletter Service appear? 2) Is it possible to hide the List-Header (i.e. List-Subscribe)? Reason is that the Mailman installation is in our Intranet, and i don´t want to give out this informations. All Functions will be only availbable with the Mail command function. Thank you Bart Frackiewicz -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] Messages stuck in queue
Hi, I've search the FAQ and online documenation without any success. Basically, I have postfix with virtual domains set up. In the postfix main.cf file I have a line alias_database = hash:/etc/aliases and these aliases all seem to work, including the mailman wrapper lines I put in for my test mailing list. However, when I send to the test list, the message just ends up in the queue. Here's what the log says: Oct 18 17:25:52 nippleclamp postfix/smtpd[1060]: connect from lateral[195.224.94.178] Oct 18 17:25:52 nippleclamp postfix/smtpd[1060]: 6E8C66703B: client=lateral[195.224.94.178] Oct 18 17:25:52 nippleclamp postfix/cleanup[1061]: 6E8C66703B: message-id=[EMAIL PROTECTED] Oct 18 17:25:52 nippleclamp postfix/smtpd[1060]: disconnect from lateral[195.224.94.178] Oct 18 17:25:52 nippleclamp postfix/qmgr[898]: 6E8C66703B: from=[EMAIL PROTECTED], size=773, nrcpt=1 (queue active) Oct 18 17:25:52 nippleclamp postfix/local[1063]: 6E8C66703B: to=[EMAIL PROTECTED], relay=local, delay=0, status=sent (|/usr/local/mailman/mail/wrapper mailcmd test) And in /usr/local/mailman/qfiles/ there are two files: -rw-rw-r--1 mailman mailman 880 Oct 18 17:25 8d2eeefe7c1f90a60c2ccfb1f2a315a0a3d91f59.msg -rw-rw-r--1 mailman mailman 118 Oct 18 17:25 8d2eeefe7c1f90a60c2ccfb1f2a315a0a3d91f59.db Can anyone suggest what to do? If you need any more details, let me know and I can post them. Mailman v.2.0.6 Postfix v.20010228-pl05 # uname -a Linux mail.colateral.net 2.2.19pre17 #1 Tue Mar 13 22:37:59 EST 2001 i686 unknown Also, would I be better off using qmail, exim or another MTA? Thanks Fred -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] Logging and diagnostics for problem resolution?
I have a problem I can't resolve because I can't find any information in the logs. Situation: a cgi script generates a mail for the users wishing to subscibe. Because it's a script we know that it's of the correct format etc. In the mail logs we can follow the mail from cgi server, relay server and to the mailman server up to the point where the mail is delievered to listname-request and that piped to the wrapper mailcmd subscribe... So far so good. The majority of subscribe and unsubscribe request are honoured. However we regularly get a number of users who are not subscribed despite the fact that we can follow the subscription request all the was to the wrapper it has not been honoured. At that point I'm stumped because there is no trace in any of the logs: no bounce, no error and naturally nothing is subscribe. Is there a means by which some logging level can be turned up, or some additional actions logged that might permit me to see what is going wrong? Matthew -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] Mailman + Postfix
Hi Alessandro, Don't worry. Your command of English is far better than that of a few other posters for whom English is their primary (or only) language. :-) =) Amanda Alessandro Luiz Petrocino wrote: Hello, everybody ! I'm a brazilian administrator, and a new user in this list! So, sorry, for my bad english ... -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] Failure of rmlist command
On Thursday 18 October 2001 08:33 am, Paul Flint wrote: What should I try now? I don't have to run the commands in bin through the interpreter with Mandrake 8. Tried just doing ./rmmlist? If not, maybe I could try sending you my file. Ken -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] We're sorry, we hit a bug!
Hello, I setup mailman 2.0.2 and had it running for a long while. Last night for no obvious reason, it started giving this error when trying to get into admin: We're sorry, we hit a bug! Mailman experienced a very low level failure and could not even generate a useful traceback for you. Please report this to the Mailman administrator at this site. I checked the error log and it said nothing. So I tried upgrading to 2.0.4, didn't help. I tried completely removing the old version, still no go. It is getting to the admin login page, it's when you login that it gives an error (when the wrong password is entered, it's okay, but doesn't help much :). Does anyone have ideas where I can start troubleshooting this stuff? I restarted apache, sendmail, etc. And started from a fresh installation, did check_db and check_perm scripts, still didn't work. Thanks for any help. -Aaron -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] umbrella_list?
On Wed, 17 Oct 2001, Jon Carnes wrote:
To stop folks from receiving multiple copies, you will have to make your
own mega-list by using a script and building the mega-list from each of the
sub lists.
Not to be outdone, I came up with a one-liner that will add all
subscribers of foo_* to the umbrella list foo_all:
list_lists | awk '{ print $1 }' | grep -i ^foo_ | grep -iv foo_all | \
xargs -rl list_members | sync_members -f - -w=no foo_all
One may involve files at any point during the transaction, of course
(e.g., after the xargs and before the sync_members, perhaps involving
sort and uniq as you did in your code).
No matter how you write it, though, this seems like a bit of a kludge,
insofar as the list admin has to maintain redundant data with cron jobs
and so forth. I still think it would be a nice feature to be able to have
Mailman do the work for me, not so much because I don't want to do the
work, but because it can probably do it better than I. :)
At any rate, thanks for the suggestion!
- Shane
--
Mailman-Users maillist - [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] list hosting
On Tue, Oct 16, 2001 at 09:56:24AM -0700, J. St. Clair wrote: Am thinking of using your software on my server ... I have a 5,000 subscriber list, does your softare handle that many subscribers? Yes, and many more It can start to get slow when you go beyond 50-100k users in one list. Marc -- Microsoft is to operating systems security what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger [EMAIL PROTECTED] for PGP key -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] umbrella_list?
On Wed, 17 Oct 2001, Jon Carnes wrote:
On Wednesday 17 October 2001 02:13, Shane Beasley wrote:
On Wed, 17 Oct 2001, Jon Carnes wrote:
To stop folks from receiving multiple copies, you will have to make
your own mega-list by using a script and building the mega-list from
each of the sub lists.
Not to be outdone, I came up with a one-liner that will add all
subscribers of foo_* to the umbrella list foo_all:
list_lists | awk '{ print $1 }' | grep -i ^foo_ | grep -iv foo_all | \
xargs -rl list_members | sync_members -f - -w=no foo_all
Humbly I must decree that *you* are the superior coder! I had not thought
to use awk! :-)
And xargs. And this is why I went to college. Hmm...
BTW: If anyone wants to rewrite that in python, then I'm sure we could
get the developers of Mailman to include a new option that uses an
autogenerated list (generated from your code). Feel like being
immortalized today?
As you mention this, I land upon a patch:
http://mail.python.org/pipermail/mailman-developers/2001-September/009527.html
snip
Provides functionality/behaviour similar to how sendmail treats its
aliases file. eg
alias1: alias2, alias3, alias4
alias2: a, b
alias3: b, c
alias4: c, d
would only deliver one message to the union of alias2, alias3 and alias4
which is a, b, c, d
/snip
Sounds like what we want, eh?
Two problems:
- it's a patch for 2.1a (yes, that's a as in alpha)
- I know jack about Python and couldn't possibly smash it into 2.0.6
without a *lot* of free time, not to mention that it is claimed to rely on
a class hierarchy (MemberAdaptor) that doesn't exist in 2.0
If anybody's up for *that*, it would probably be better than working from
scratch. Perhaps one day I'll get bored and learn Python or something.
However, by that time, 2.1 won't be alpha anymore, and we'll all go back
to reminiscing about the good old days, when you had to create your
umbrella lists yourself, in the snow, uphill both ways.
In any event, best of luck to ye.
- Shane
--
Mailman-Users maillist - [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] Pending subscriber.db with Apache UID
System conf: OS RH7.1 Mailman 2.0.6-1u70_1cl.i386.rpm Sendmail 8.11.2-14 Apache 1.3.19-5 Python 1.5.2-30 - From web page when I add a member to the list, a file get created in /mailman/data called pending.subscriber.db or something like that, UID is Apache and GID is mailman. But when the subscription e-mail goes out to the member, it contains few lines of error and at the end of the mail say something about the .db permission denied with flag w I assume it means write. debugging of this message tells me that the pending file with UID of Apache is not editable by the script, To prove that the message is telling me the truth I change the UID of the pending subscribers to mailman and let qrunner to do it's job again. This time subscription e-mail goes out to the member without any error. Do you know where is wrong? I run check_perms and tells me no problem. The obvious logic is that the pending subscriber file is created by Apache in the first place, when entering e-mail address and password and click on subscribe. But I can't understand why mailman is not taking back the ownership of the pending data file. Please let me know if there is anything else I should check. Thanks. Vania -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] We're sorry, we hit a bug!
Hello, I setup mailman 2.0.2 and had it running for a long while. Last night for no obvious reason, it started giving this error when trying to get into admin: "We're sorry, we hit a bug! Mailman experienced a very low level failure and could not even generate a useful traceback for you. Please report this to the Mailman administrator at this site." I checked the error log and it said nothing. So I tried upgrading to 2.0.4,didn't help. I tried completely removing the old version, still no go. It is getting to the admin login page, it's when you login that it gives an error (when the wrong password is entered, it's okay, but doesn't help much :). Does anyone have ideas where I can start troubleshooting this stuff? I restarted apache, sendmail, etc. And started from a fresh installation. Thanks for any help. -Aaron
[Mailman-Users] configuration question
I inherited an installation of Mailman, v. 1.1. I can set up a new list and subcribe. When I am asked for confirmation, I click on the link to reply and get the message: [EMAIL PROTECTED]: Command died with status 2: /usr/local/mailman/mail/wrapper mailcmd manouche So, I went in and ran configure again (without any switches) and got the same result. So, I checked my syslog and it gives this message: Mailman mail-wrapper: Failure to exec script. WANTED gid 12345, got gid 60001. (Reconfigure to take 60001?). So, I ran configure again with the switch: --with-mail-gid=12345. In my group file, the mailer (Postfix) is 12345 and nobody is 60001. The Docs say that the default for with-cgi-gid is nobody. So, what next? I see in the Docs that I don't have to be Root to install Mailman, only to set permissions. However, I have to log in as Root to run configure. Would this make a difference? -- Christopher Adams Oregon State Library 503-378-4246 [EMAIL PROTECTED] -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] Dummyfunction Newsletter
Subject: [Mailman-Users] Dummyfunction Newsletter Hi, i try to setup a Newsletter for a customer. 1) Is it possible to change the Sender-Header from Sender: newsletter@domain to Sender: Newsletter Service newsletter@domain so that in most Mail Programs the Newsletter Service appear? You can certainly send it directly from your workstation with the email defined as being whomever you desire. Mailman neither impedes nor assists you here. Feel free to spoof the From field - just make sure that that individual email can send to the list. 2) Is it possible to hide the List-Header (i.e. List-Subscribe)? Reason is that the Mailman installation is in our Intranet, and i don´t want to give out this informations. All Functions will be only availbable with the Mail command function. See an earlier message about this (from yesterday?). You will have to edit a file and then recompile in order to get rid of those lines. If you are not going to use the web-based functions of mailman, you may wish to move to a List-serve that is designed for just email access - something like Majordomo. Otherwise, you will have to do a lot of work to cover-up the Web-based features. Jon Carnes -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] Messages stuck in queue
Is your Cron running? What happens when you run the qrunner script (from the mailman cron) by hand? Jon Carnes - Original Message - From: fred backman [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, October 18, 2001 12:37 PM Subject: [Mailman-Users] Messages stuck in queue Hi, I've search the FAQ and online documenation without any success. Basically, I have postfix with virtual domains set up. In the postfix main.cf file I have a line alias_database = hash:/etc/aliases and these aliases all seem to work, including the mailman wrapper lines I put in for my test mailing list. However, when I send to the test list, the message just ends up in the queue. Here's what the log says: Oct 18 17:25:52 nippleclamp postfix/smtpd[1060]: connect from lateral[195.224.94.178] Oct 18 17:25:52 nippleclamp postfix/smtpd[1060]: 6E8C66703B: client=lateral[195.224.94.178] Oct 18 17:25:52 nippleclamp postfix/cleanup[1061]: 6E8C66703B: message-id=[EMAIL PROTECTED] Oct 18 17:25:52 nippleclamp postfix/smtpd[1060]: disconnect from lateral[195.224.94.178] Oct 18 17:25:52 nippleclamp postfix/qmgr[898]: 6E8C66703B: from=[EMAIL PROTECTED], size=773, nrcpt=1 (queue active) Oct 18 17:25:52 nippleclamp postfix/local[1063]: 6E8C66703B: to=[EMAIL PROTECTED], relay=local, delay=0, status=sent (|/usr/local/mailman/mail/wrapper mailcmd test) And in /usr/local/mailman/qfiles/ there are two files: -rw-rw-r--1 mailman mailman 880 Oct 18 17:25 8d2eeefe7c1f90a60c2ccfb1f2a315a0a3d91f59.msg -rw-rw-r--1 mailman mailman 118 Oct 18 17:25 8d2eeefe7c1f90a60c2ccfb1f2a315a0a3d91f59.db Can anyone suggest what to do? If you need any more details, let me know and I can post them. Mailman v.2.0.6 Postfix v.20010228-pl05 # uname -a Linux mail.colateral.net 2.2.19pre17 #1 Tue Mar 13 22:37:59 EST 2001 i686 unknown Also, would I be better off using qmail, exim or another MTA? Thanks Fred -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] We're sorry, we hit a bug!
Check the lock files in ~mailman/locks/ If there are any lock files check the processes and see if they are actually running. The process is part of the name of the lock file. Kill any processes that are frozen and then delete the lock files for them. Have you upgraded or changed your browser lately? This could cause problems when trying to access the Admin pages. Jon Carnes - Original Message - From: Ken [EMAIL PROTECTED] To: Aaron Nikula [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, October 18, 2001 5:44 PM Subject: Re: [Mailman-Users] We're sorry, we hit a bug! Have you just tried resetting the admin password? Ken On Wednesday 17 October 2001 11:33 pm, Aaron Nikula wrote: Hello, I setup mailman 2.0.2 and had it running for a long while. Last night for no obvious reason, it started giving this error when trying to get into admin: We're sorry, we hit a bug! Mailman experienced a very low level failure and could not even generate a useful traceback for you. Please report this to the Mailman administrator at this site. I checked the error log and it said nothing. So I tried upgrading to 2.0.4, didn't help. I tried completely removing the old version, still no go. It is getting to the admin login page, it's when you login that it gives an error (when the wrong password is entered, it's okay, but doesn't help much :). Does anyone have ideas where I can start troubleshooting this stuff? I restarted apache, sendmail, etc. And started from a fresh installation. Thanks for any help. -Aaron -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] Just drop it?
One of my moderators asked me for help. She runs a moderated list, and only wants her messages to go to the list. We've done that. What is bothering her now is she gets a note every time a spammer tries to hit this list. She doesn't want to know about it, and she doesn't want to have to manually discard every one of the spam attempts. She wants Mailman to just drop the message into a black hole, without telling anyone it happened. I don't see a way to do that am I overlooking something? Thanks, Mike-- Mike Avery [EMAIL PROTECTED] Voice: (970)-642-0282 (home) (970)-642-0244 (office) FAX: (970)-642-0282 ICQ: 16241692 AOL IM: MAvery81230 * Spam is for lusers who can't get business any other way * A Randomly Selected Thought For The Day: It's always someone else's problem anyway -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] Just drop it?
Hi Mike, I believe you can specify to *not* send mail to the moderator when receiving a message to the list that would require approval. That will at least help her mailbox... but it will still queue the messages in the admin interface. ::sigh:: As far as silently discarding the messages, well, that seems to be a very popular question. :-) I don't think Mailman itself has any way to deal with that... next solution I suppose would be something in the MTA or something between the MTA and mailman, which would bitbucket mail unless it came from the moderator's email address. ::shrug:: There are probably a number of ways to do it, but it's going to be a matter of how much effort you want to put into it. =) Amanda Mike Avery wrote: One of my moderators asked me for help. She runs a moderated list, and only wants her messages to go to the list. We've done that. What is bothering her now is she gets a note every time a spammer tries to hit this list. She doesn't want to know about it, and she doesn't want to have to manually discard every one of the spam attempts. She wants Mailman to just drop the message into a black hole, without telling anyone it happened. I don't see a way to do that am I overlooking something? Thanks, Mike-- Mike Avery [EMAIL PROTECTED] Voice: (970)-642-0282 (home) (970)-642-0244 (office) FAX: (970)-642-0282 ICQ: 16241692 AOL IM: MAvery81230 * Spam is for lusers who can't get business any other way * A Randomly Selected Thought For The Day: It's always someone else's problem anyway -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] Just drop it?
One can do a very small amount of hacking to Mailman/Handlers/SpamDetect.py and accomplish the drop without further notice action. It's been useful for spammers for me. Basically, you just add to the list in the file; the comments are pretty readable; take a look and see what you think. Hi Mike, I believe you can specify to *not* send mail to the moderator when receiving a message to the list that would require approval. That will at least help her mailbox... but it will still queue the messages in the admin interface. ::sigh:: As far as silently discarding the messages, well, that seems to be a very popular question. :-) I don't think Mailman itself has any way to deal with that... next solution I suppose would be something in the MTA or something between the MTA and mailman, which would bitbucket mail unless it came from the moderator's email address. ::shrug:: There are probably a number of ways to do it, but it's going to be a matter of how much effort you want to put into it. =) Amanda Mike Avery wrote: One of my moderators asked me for help. She runs a moderated list, and only wants her messages to go to the list. We've done that. What is bothering her now is she gets a note every time a spammer tries to hit this list. She doesn't want to know about it, and she doesn't want to have to manually discard every one of the spam attempts. She wants Mailman to just drop the message into a black hole, without telling anyone it happened. I don't see a way to do that am I overlooking something? Thanks, Mike-- Mike Avery [EMAIL PROTECTED] Voice: (970)-642-0282 (home) (970)-642-0244 (office) FAX: (970)-642-0282 ICQ: 16241692 AOL IM: MAvery81230 * Spam is for lusers who can't get business any other way * A Randomly Selected Thought For The Day: It's always someone else's problem anyway -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] We're sorry, we hit a bug!
I have a second email account that I use for outgoing, and it wants to wait for moderation (and I don't want to :). So sorry if this gets double posted. I checked all the processes and the only ones given to mailman is /usr/bin/python -S /home/mailman/cron/qrunner, so I cleared out the processes and still get the bug message. I've tried it on 3 different computers each with different browsers, but I tried it with netscape 4.7 and it still gives the bug message. And I checked the logs again, and there's nothing in error, but here's some stuff from the other log files: tail logs/smtp Oct 17 16:54:39 2001 (4334) All recipients refused: (111, 'Connection refused') Oct 17 16:54:39 2001 (4334) smtp for 1 recips, completed in 0.184 seconds tail logs/post Oct 17 16:54:39 2001 (4334) post to test from [EMAIL PROTECTED], size=1294, 1 failures tail logs/smtp-failure Oct 17 16:54:39 2001 (4334) -1 [EMAIL PROTECTED] (ignore)] Maybe that will help? -Aaron -- Original Message -- From: Jon Carnes [EMAIL PROTECTED] Reply-To: Jon Carnes [EMAIL PROTECTED] Date: Thu, 18 Oct 2001 18:46:53 -0400 Check the lock files in ~mailman/locks/ If there are any lock files check the processes and see if they are actually running. The process is part of the name of the lock file. Kill any processes that are frozen and then delete the lock files for them. Have you upgraded or changed your browser lately? This could cause problems when trying to access the Admin pages. Jon Carnes - Original Message - From: Ken [EMAIL PROTECTED] To: Aaron Nikula [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, October 18, 2001 5:44 PM Subject: Re: [Mailman-Users] We're sorry, we hit a bug! Have you just tried resetting the admin password? Ken On Wednesday 17 October 2001 11:33 pm, Aaron Nikula wrote: Hello, I setup mailman 2.0.2 and had it running for a long while. Last night for no obvious reason, it started giving this error when trying to get into admin: We're sorry, we hit a bug! Mailman experienced a very low level failure and could not even generate a useful traceback for you. Please report this to the Mailman administrator at this site. I checked the error log and it said nothing. So I tried upgrading to 2.0.4, didn't help. I tried completely removing the old version, still no go. It is getting to the admin login page, it's when you login that it gives an error (when the wrong password is entered, it's okay, but doesn't help much :). Does anyone have ideas where I can start troubleshooting this stuff? I restarted apache, sendmail, etc. And started from a fresh installation. Thanks for any help. -Aaron -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
