Re: [Mailman-Users] Confirmation problems
-Alkuperäinen viesti-
Lähettäjä: Mark Sapiro [mailto:[EMAIL PROTECTED]
Lähetetty: 27. tammikuuta 2006 23:30
Vastaanottaja: Niemi Hannu; mailman-users@python.org
Aihe: Re: [Mailman-Users] Confirmation problems
Niemi Hannu wrote:
Is it only this list that fails? It is not likely a virtual host
problem as host really isn't involved in processing confirmations.
I had to test the others. To be honest I haven't earlier
used this kind
of user-driven subscription in any of the lists on that
server, but have been adding the users on the web form instead.
Check mailman's 'error' log and also permissions on the
list's pending.pck file.
Hello
I was away for some time (hey, even I have vacation somedays ;)) and have now
come back.
If you have forgotten what the problem is:
e-mail conformation isn't working for a list (though for others it does).
After evaluating the problem again it seems that my first impression was a bit
erroneous (read I didn't debug efficiently enough):
It seems that confirming via web page works, but only if one hasn't tried to do
it by mail. It seems that the mail removes the confirmation from the pending
confirmations, but doesn't do the trick. And after that the web page
confirmation doesn't really have anything to confirm against.
The error log gives the following information:
-8--8-
Feb 08 21:26:11 2006 (29601) Uncaught runner exception: [Errno 9] Bad file
descriptor
Feb 08 21:26:11 2006 (29601) Traceback (most recent call last):
File /usr/lib/mailman/Mailman/Queue/Runner.py, line 110, in _oneloop
self._onefile(msg, msgdata)
File /usr/lib/mailman/Mailman/Queue/Runner.py, line 160, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File /usr/lib/mailman/Mailman/Queue/OutgoingRunner.py, line 74, in _dispose
self._func(mlist, msg, msgdata)
File /usr/lib/mailman/Mailman/Handlers/SMTPDirect.py, line 180, in process
mm_cfg.SMTP_LOG_EVERY_MESSAGE[1], kws=d)
File /usr/lib/mailman/Mailman/Logging/Syslog.py, line 49, in write_ex
logf = self._logfiles[kind] = StampedLogger(kind)
File /usr/lib/mailman/Mailman/Logging/StampedLogger.py, line 52, in __init__
Logger.__init__(self, category, nofail, immediate)
File /usr/lib/mailman/Mailman/Logging/Logger.py, line 49, in __init__
self.__get_f()
File /usr/lib/mailman/Mailman/Logging/Logger.py, line 75, in __get_f
_logexc(self, e)
File /usr/lib/mailman/Mailman/Logging/Utils.py, line 22, in _logexc
sys.__stderr__.write('Logging error: %s\n' % logger)
IOError: [Errno 9] Bad file descriptor
Feb 08 21:26:11 2006 (29601) SHUNTING:
1139426770.15838+256c6fef5c6868ee41812a6ec8d71a9d1da73730
-8--8-
Any suggestions based on this one?
Best regards
Hannu Niemi
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] sendmail and mm-handler woes
Hi, I am using Solaris 10 and installing mailman 2.1.7 I have followed the mailman instruction and mm-handler.readme and I can administer everything via web and receive confirmation emails, except I get User unknown when I try send to my testlist at mailman.symsoft.se. From reading the archives it suggests that sendmail is not recognising mm-handler as the recipient of mail to the mailman.symsoft.se domain. Here is my sendmail.mc: VERSIONID(`@(#)sendmail.mc 1.11 (Sun) 06/21/04') OSTYPE(solaris2)dnl DOMAIN(generic)dnl FEATURE(`use_cw_file')dnl FEATURE(`smrsh',`/usr/lib/smrsh')dnl FEATURE(`access_db',`hash -TTMPF /etc/mail/access.db')dnl FEATURE(`delay_checks')dnl FEATURE(`ratecontrol',`nodelay')dnl define(`PROCMAIL_MAILER_PATH', `/opt/sfw/bin/procmail')dnl FEATURE(`local_procmail')dnl FEATURE(`mailertable', `hash -o /etc/mail/mailertable')dnl FEATURE(`virtusertable', `hash -o /etc/mail/virtusertable')dnl VIRTUSER_DOMAIN(`mailman.symsoft.se')dnl define(`confDONT_PROBE_INTERFACES', `True')dnl FEATURE(`limited_masquerade')dnl MASQUERADE_AS(`mailman.symsoft.se')dnl FEATURE(`blacklist_recipients')dnl define(`confTO_IDENT', `0s')dnl define(`confMAX_MESSAGE_SIZE', `5000')dnl define(`confCONNECTION_RATE_THROTTLE', `1')dnl define(`confPRIVACY_FLAGS', `goaway')dnl define(`confMAX_DAEMON_CHILDREN', `60')dnl define(`confMAX_QUEUE_CHILDREN', `70')dnl define(`confDOUBLE_BOUNCE_ADDRESS', `nobody')dnl define(`confDELAY_LA', `8')dnl define(`confCONNECTION_RATE_WINDOW_SIZE', `60s')dnl MAILER(`local')dnl MAILER(`smtp')dnl MAILER(`procmail')dnl MAILER_DEFINITIONS ### New Mailer specifications ### ## Special flags! See ## http://www.sendmail.org/~ca/email/doc8.10/op-sh-5.html#sh-5.4 ## Note especially the absence of the m and n flags. THIS IS ## IMPORTANT: mm-handler assumes this behavior to avoid having to know ## too much about address parsing and other RFC-2822 mail details. Mmailman, P=/etc/mail/mm-handler, F=rDFMhlqSu, U=mailman:other, S=EnvFromL, R=EnvToL/HdrToL, A=mm-handler $h $u --- # cat mailertable mailman.symsoft.se mailman:mailman.symsoft.se Please help, Kevin -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Virtual Servers
Thanks for the help to date... still struggling with the virtual domains configuration with postfix/mailman, however. I did what was suggested below... Since you haven't had MTA = 'Postfix', you've been using the default MTA = 'Manual' which just tells you what the aliases are and asks you to manually install them. If you now run bin/genaliases, it should create the data/aliases and data/virtual-mailman files containing data for all your lists, and run the postalias and postmap commands to create the .db files. Then you can update your Postfix config to use these files and not have to do the aliases manually in the future. yet, mailman created data/aliases, but not data/virtual-mailman. I made a vain attempt with touch virtual-mailman, and then genalias. This produced a virtual-mailman.db, but throws up errors in the mail log because it is empty. Also, I assume I create a list on the virtual domain using newlist [EMAIL PROTECTED] ? Any futher thoughts? Thanks, Jon ___ To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Privacy Options Sender Filters non-memberfilters
Is it possible to reference a one-address-per-line text file for this filter? Not without modifying the source code. One way you could accomplish this is to get the patch at http://sourceforge.net/tracker/index.php?func=detailaid=1220144group_id=103atid=300103. Then you could either modify the patch to get its whitelist from a file instead of another list, or you could create a separate list which is essentially turned off except that its membership could be the whitelist for the other lists. Looks like this will work - thanks! But... I prefer to not apply custom patches if at all possible - is support for this planned for future releases? Seems like 'a good thing' to have, no? Thanks again for the pointer... -- Best regards, Charles -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Confirm setting not holding
Under Privacy Options/Subscription Rules (Mailman 2.1.4) are the settings for either Confirm, Approve, or Confirm and Approve. On half a dozen of my lists, even though they're set for Confirm, the setting won't hold -- it keeps changing to Confirm and Approve. Anyone have any idea why? Bob -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Virtual Servers
Jon Loose wrote: I did what was suggested below... ... If you now run bin/genaliases, it should create the data/aliases and data/virtual-mailman files containing data for all your lists, and run the postalias and postmap commands to create the .db files. ... yet, mailman created data/aliases, but not data/virtual-mailman. I made a vain attempt with touch virtual-mailman, and then genalias. This produced a virtual-mailman.db, but throws up errors in the mail log because it is empty. In order for virtual-mailman to be created/updated, you must have a list of virtual domains in mm_cfg.py like: POSTFIX_STYLE_VIRTUAL_DOMAINS = ['domain2', 'domain3'] (see http://www.list.org/mailman-install/postfix-virtual.html for what actually goes in this list - it could be just one domain or two as above or more), AND you must have one or more Mailman lists with host_name equal to one of the domains in POSTFIX_STYLE_VIRTUAL_DOMAINS. Apparently you don't have both of these conditions. Also, I assume I create a list on the virtual domain using newlist [EMAIL PROTECTED] ? Yes, but contrary to intuition, domain2 in this case must be the URL host of the list, not the email host unless they are the same. There are also options in later versions of newlist to specify this less counter-intuitively. See 'bin/newlist --help' -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] News - Mail issues.
Steven Haigh wrote: Just some more info to this - when looking at the news.notice file for innd, I can see that the gate_news process actually connect to the news server, and check for news in the groups specified - the problem is however, that if there is new stuff in the newsgroups, it never gets sent to one of the two mailing lists. Anyone know how I can do some more debugging on this? Check Mailman's error and fromusenet logs. If that doesn't show anything, 'cp cron/gate_news cron/my_gate_news' and add some debugging prints to my_gate_news and run it manually. -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Privacy Options Sender Filters non-memberfilters
Charles Marcus wrote: One way you could accomplish this is to get the patch at http://sourceforge.net/tracker/index.php?func=detailaid=1220144group_id=103atid=300103. Looks like this will work - thanks! But... I prefer to not apply custom patches if at all possible - is support for this planned for future releases? Seems like 'a good thing' to have, no? As it says in the patch comments, this is a candidate for Mailman 2.2 -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Confirmation problems
Niemi Hannu wrote:
After evaluating the problem again it seems that my first impression was a
bit erroneous (read I didn't debug efficiently enough):
It seems that confirming via web page works, but only if one hasn't tried to
do it by mail. It seems that the mail removes the confirmation from the
pending confirmations, but doesn't do the trick.
What are the subscription rules? is moderator approval also required?
Is this why the confirmation by email appears to not work?
And after that the web page confirmation doesn't really have anything to
confirm against.
The error log gives the following information:
-8--8-
Feb 08 21:26:11 2006 (29601) Uncaught runner exception: [Errno 9] Bad file =
descriptor
Feb 08 21:26:11 2006 (29601) Traceback (most recent call last):
File /usr/lib/mailman/Mailman/Queue/Runner.py, line 110, in _oneloop
self._onefile(msg, msgdata)
File /usr/lib/mailman/Mailman/Queue/Runner.py, line 160, in _onefile
keepqueued =3D self._dispose(mlist, msg, msgdata)
File /usr/lib/mailman/Mailman/Queue/OutgoingRunner.py, line 74, in _dis=
pose
self._func(mlist, msg, msgdata)
File /usr/lib/mailman/Mailman/Handlers/SMTPDirect.py, line 180, in proc=
ess
mm_cfg.SMTP_LOG_EVERY_MESSAGE[1], kws=3Dd)
File /usr/lib/mailman/Mailman/Logging/Syslog.py, line 49, in write_ex
logf =3D self._logfiles[kind] =3D StampedLogger(kind)
File /usr/lib/mailman/Mailman/Logging/StampedLogger.py, line 52, in __i=
nit__
Logger.__init__(self, category, nofail, immediate)
File /usr/lib/mailman/Mailman/Logging/Logger.py, line 49, in __init__
self.__get_f()
File /usr/lib/mailman/Mailman/Logging/Logger.py, line 75, in __get_f
_logexc(self, e)
File /usr/lib/mailman/Mailman/Logging/Utils.py, line 22, in _logexc
sys.__stderr__.write('Logging error: %s\n' % logger)
IOError: [Errno 9] Bad file descriptor
Feb 08 21:26:11 2006 (29601) SHUNTING:
1139426770.15838+256c6fef5c6868ee41812a6ec8d71a9d1da73730
Do (watch out for folding)
bin/show_qfiles
qfiles/shunt/1139426770.15838+256c6fef5c6868ee41812a6ec8d71a9d1da73730.pck
And see what's in the shunted message. Unless you have a large number
of these, I don't know what happened to cause this.
What the trace shows is the SMTP delivery handler successfully
delivered the message to the outgoing MTA and was trying to log that
fact in the 'smtp' log, but for some reason logging encountered an
exception (I think) and tried to write that to stderr which wasn't
available, so the error logged here is the inability to write to
stderr.
Also, the actual message in this case that was shunted, should have
been successfully delivered anyway, so this seems to have nothing to
do with the confirmation problem.
--
Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] (no subject)
unsubscribe -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] why is plain text option (removes MIME/HTML) only available
Thanks for the replies - a better yet subjsect may have been ' how do you apply content filtering on a per-user basis'. Basically we want to allow crusty old non-MIME or non-HTML browsers and clients to still view our nice fancy html emails instead of the mime and html source code. Sounds like two separate lists (a mime list and a plain-text list) is probably the way to go. -Tom -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] error log - Failed before cPickle:
Hi, I noticed the following messages in mailman error log every time when a list is accessed, for example: /usr/local/mailman/lists/email-team/config.pck.tmp.mailman.Stanford.EDU.13813 Feb 09 09:49:38 2006 (13810) Failed before cPickle: /usr/local/mailman/lists/email-team/config.pck.tmp.mailman.Stanford.EDU.13810 Feb 09 09:50:38 2006 (13813) Failed before cPickle: It doesn't seem to be harmful, because all operations seem normal. The permission for the list is: drwxrwsr-x 2 mailman mailman 4096 Feb 9 09:49 email-team/ and under email-team: -rw-rw-r-- 1 www-data mailman24 Jan 21 08:55 request.pck -rw-rw 1 mailman mailman 12595 Feb 9 09:49 digest.mbox -rw-rw 1 mailman mailman 6184 Feb 9 09:49 config.pck.last -rw-rw 1 mailman mailman 6184 Feb 9 09:49 config.pck What does the error mean? Should I worry? Thanks! Susan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Redirect all -bounce emails
Hello Folks, I recently setup a mailman server with ver 2.1.6, and I am liking it so far. Since I am not with the IT Team of my organization, I am working around some mailman problems and this is where I need some ideas. I setup a few mail lists (including default mailman list) in name.comdomain, and worked with my IT folks to redirect maillist@ name.com to my mail server mailist@mine.name.com I do get a few maillist-name[EMAIL PROTECTED] emails, and I would like to re-direct all these emails to [EMAIL PROTECTED] (or [EMAIL PROTECTED]) Does someone have ideas how to accomplish this? I do not administer the company's mail servers. Folks here are not open to the list.name.com domain idea, for legacy reasons. I have a bunch of /etc/aliases entries for each of my mail lists on mine.name.com server. Is there a way I can use these alaises to re-firect maillist-bounce@ name.com to [EMAIL PROTECTED] Any help / ideas are appreciated. Thanks! Tom -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Problems sending to list
I have a relatively small list (13 recipients, several of which are mm lists on the same box, but they work fine). I'm using sendmail, and /etc/aliases is configured to pass the email to procmail with a special file which matches the ^TO_ metatarget to dispatch the emails to the appropriate mailman command (mailman post list) after running some spam filtering and whitelisting stuff on them. Any time a message is sent to this list (the 'announce' list), mailman appears to receive it, because it generates 3 messages (ceil(13/5)=3; they are all at the same site). However, the messages are addressed to announce instead of being addressed to the recipients. Mailman correctly ignores the three duplicates. The problem here is that since the messages are addressed to announce instead of the correct users... nobody receives messages sent to the list. This happens even when /etc/aliases is changed to send directly to mailman again instead of using procmail. The only change since the last time this was working is a user was removed from the list (using the remove_members command). Any advice on where to start looking for the problem would be greatly appreciated. -- - Patrick Bogen -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] mailman + apache2
Am Dienstag, 7. Februar 2006 18:16 schrieben Sie: Stefan Fuhrmann wrote: Am Dienstag, 7. Februar 2006 02:45 schrieben Sie: BTW, I'm not sure why you have the 'cgi-bin/' in the above URL, Normally, if the ScriptAlias says '/mailman/' the URL uould just be http://domain.tld/mailman/create When I browse this then I get file not found dont know what to do here! In a prior post you said: I set in Vhosts_ispconfig.conf (where the virutual hosts are created) ScriptAlias /mailman/ /var/www/web1/cgi-bin/ If that directive actually applies to domain.tld, then (assuming that /var/www/web1/cgi-bin/ is the directory that contains Mailman's wrappers) the URL http://domain.tld/mailman/create should cause Apache to execute the create wrapper. Debian installs mailman to /usr/lib/cgi-bin/mailman. I linked it to /var/www/web1/cgi-bin/ ScriptAlias is set to ScripAlias /mailman/ /var/www/web1/cgi-bin/ this gives the aboves errors Now it is clear that you do get to Mailman when you go to http://domain.tld/cgi-bin/mailman/create so there is likely some other Alias or ScriptAlias that handles that URL. What is in Apache's error_log for the attempt to get http://domain.tld/mailman/create thats it what is created in apache2 error.log when I try to access the URL: [Fri Feb 10 00:13:00 2006] [notice] Apache/2.0.54 (Debian GNU/Linux) mod_python/3.1.3 Python/2.3.5 PHP/4.3.10-16 mod_ssl/2.0.54 OpenSSL/0.9.7e mod_perl/1.999.21 Perl/v5.8.4 configured -- resuming normal operations [Fri Feb 10 00:31:23 2006] [notice] caught SIGTERM, shutting down [Fri Feb 10 00:31:24 2006] [notice] suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec2) [Fri Feb 10 00:31:25 2006] [notice] mod_python: Creating 20 session mutexes based on 20 max processes and 0 max threads. [Fri Feb 10 00:31:31 2006] [notice] Apache/2.0.54 (Debian GNU/Linux) mod_python/3.1.3 Python/2.3.5 PHP/4.3.10-16 mod_ssl/2.0.54 OpenSSL/0.9.7e mod_perl/1.999.21 Perl/v5.8.4 configured -- resuming normal operations In any case, this is not the cause of the we hit a bug you get when you go to http://domain.tld/cgi-bin/mailman/create. That's a Mailman message and we need Mailman's error log for that. I had a look in /var/log/mailman/error - empty in /var/log/mailman/qrunner: eb 09 06:27:58 2006 (929) VirginRunner qrunner caught SIGHUP. Reopening logs. Feb 09 06:27:59 2006 (930) RetryRunner qrunner caught SIGHUP. Reopening logs. Feb 09 06:27:59 2006 (918) ArchRunner qrunner caught SIGHUP. Reopening logs. Feb 09 06:27:59 2006 (919) BounceRunner qrunner caught SIGHUP. Reopening logs. Feb 09 06:27:59 2006 (920) CommandRunner qrunner caught SIGHUP. Reopening logs. Feb 09 06:27:59 2006 (922) IncomingRunner qrunner caught SIGHUP. Reopening logs. Feb 09 06:27:59 2006 (924) OutgoingRunner qrunner caught SIGHUP. Reopening logs. Feb 09 06:27:59 2006 (923) NewsRunner qrunner caught SIGHUP. Reopening logs. Feb 09 06:28:00 2006 (917) Master watcher caught SIGHUP. Re-opening log files. but this is not the real log file, or? I looked also multiple times through the files you meant but was not able to find something what is discribing a path to a log file! So, where is it? tia stefan ~ -- pgpXbypCT1gD6.pgp Description: PGP signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Problems sending to list
Patrick Bogen wrote: I have a relatively small list (13 recipients, several of which are mm lists on the same box, but they work fine). I'm using sendmail, and /etc/aliases is configured to pass the email to procmail with a special file which matches the ^TO_ metatarget to dispatch the emails to the appropriate mailman command (mailman post list) after running some spam filtering and whitelisting stuff on them. What are you doing about the other list addresses like announce-bounces, announce-owner, etc. Are you piping them to 'mailman bounces list', 'mailman owner list', etc. Also, have you checked to see if the post is waiting moderator approval? -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Unknown password on new list...
I just set up a new list, and must have fat fingered the password. How can I change it since I cannot log into the GUI? I see 'mmsitepass', but it changes a master password for all lists. I don't want that. I only want to change for ONE specific list. Also, this seems kind of short-sighted that it takes only one password on the command line and hides the typing. Why doesn't mailman ask for a confirmation of the password, and keep re-prompting for a new one if they do not match? -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Unknown password on new list...
Just to clarify, I'm not completely retarded. Yes, an email is sent, however it says: Your mailing list password is: cand^H^H^H^H^H^H^Hvegas And obviously, when I try to type that into the GUI, it fails. I've also tried the following combinations with no luck: cand candvegas vegas -Original Message- From: Daevid Vincent [mailto:[EMAIL PROTECTED] Sent: Thursday, February 09, 2006 5:05 PM To: 'Mailman Users' Subject: Unknown password on new list... I just set up a new list, and must have fat fingered the password. How can I change it since I cannot log into the GUI? I see 'mmsitepass', but it changes a master password for all lists. I don't want that. I only want to change for ONE specific list. Also, this seems kind of short-sighted that it takes only one password on the command line and hides the typing. Why doesn't mailman ask for a confirmation of the password, and keep re-prompting for a new one if they do not match? -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Fw: (no subject)
This HAS to be my most FAVORITE rec'd mail in over a DECADE, folks!!! I do handle 5 Mailman Lists and am on anoth 8 or 9 or so INCLUDING this one. One of not only my pet peeves but mantra is: KEEP the instructions that come with!! Your know --:) But to see the below HERE, is UN-real!!! Yo Tony!! Go to the line just above (in the trailer) that says Security ??!!?? Thanks, folks!! /rant Ed - Original Message - From: Tony Sciortino [EMAIL PROTECTED] To: mailman-users@python.org Sent: Thursday, February 09, 2006 9:44 AM Subject: [Mailman-Users] (no subject) unsubscribe -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/justbrits%40comcast.net Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Unknown password on new list...
Daevid Vincent wrote: I just set up a new list, and must have fat fingered the password. How can I change it since I cannot log into the GUI? You can use the master site password to log in the admin page and change the list password. If you can not use GUI for any other reason, then use bin/withlist to change the password with a little trick like this: % bin/withlist test Loading list test (unlocked) The variable `m' is the mm-test MailList instance import sha p = 'newpass' cp = sha.new(p).hexdigest() m.Lock() m.password = cp m.Save() m.Unlock() Finalizing % I see 'mmsitepass', but it changes a master password for all lists. I don't want that. I only want to change for ONE specific list. Also, this seems kind of short-sighted that it takes only one password on the command line and hides the typing. Why doesn't mailman ask for a confirmation of the password, and keep re-prompting for a new one if they do not match? -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Problems sending to list
The aliases for the other addresses for announce are actually disabled (it worked that way before)- it's been thus since I've been handling this server (about a year and a half). If you think this might have something to do with the problem, I can re-enable them... Since this list exists primarily just to propagate messages to sub-lists, there's no membership or moderator issues to worry about. Non-member messages are allowed (and I have checked; the messages are not waiting for approval). On 2/9/06, Mark Sapiro [EMAIL PROTECTED] wrote: Patrick Bogen wrote: I have a relatively small list (13 recipients, several of which are mm lists on the same box, but they work fine). I'm using sendmail, and /etc/aliases is configured to pass the email to procmail with a special file which matches the ^TO_ metatarget to dispatch the emails to the appropriate mailman command (mailman post list) after running some spam filtering and whitelisting stuff on them. What are you doing about the other list addresses like announce-bounces, announce-owner, etc. Are you piping them to 'mailman bounces list', 'mailman owner list', etc. Also, have you checked to see if the post is waiting moderator approval? -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- - Patrick Bogen -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
