[Mailman-Users] bounce problem
Hallo, we are runnung mailman on two different servers under Debian Linux, one server is for the world, the mailman version is 2.1.4, and the other server is located in our LAN reachable only for users working inside our research institute, the mailman version is 2.1.5. The mail program on both servers is postfix, version 1.1.11 but they only pass all mails to or get the mails from our central mail server under SuSE Linux with postfix version 2.1.1 The bounce facility in mailman version 2.1.4 runs perfectly on the server in the world, the list-owner gets the information when an list member is disabled or deleted when a member has reached the given bounce score and the member itself is deleted from the list. This bounce facility does not work on the server with mailman version 2.1.5, in the bounce logfile I can find sending rzforum list probe to [EMAIL PROTECTED] ... after the maximum bounce score has been reached, but nothing happens - no disabling of the member, no information to the list-owner. I know that you have changed the bounce algorithm in version 2.1.5 and that the problem might be in the postfix program or in our difficult server constellation, but I do not understand why and I have no idea on how to configure my programs properly. What I do until now is to look in the bounce logfile and delete the list members that have bounce scores manually. A running bounce facility would be a great help. Maybe it would be a help when I understand what happens or should happen when a list probe is send to a member and when this probe bounces. Birgit Fenzke Monika Haberland Birgit Fenzke MPI für Biochemie - Rechenzentrum Am Klopferspitz 18 82152 Martinsried Tel.: (089) 8578 2725; Fax (089) 8578 2479 email: [EMAIL PROTECTED] -- 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] lists/create screen
I set VIRTUAL_HOST_OVERVIEW = Off and that seems to have resolved the problem I outlined below. I know nothing about Python at the moment, so hacking the *.py files for customized functionality (by me) is probably not happening anytime soon, not without a mess ;-) Thank you. Mark Sapiro wrote: Forrest Aldrich wrote: I have a new mailman instance set up - via a proxied connection. I've since found that doing it this way is more complex (but not my choice). Several items need to be addressed. Another one I found was this on the screen for lists/create: our.internal.host.net:1 mailing lists - Admin Links Welcome! There currently are no publicly-advertised Mailman http://www.gnu.org/software/mailman/index.html mailing lists on our.internal.host.net:1.To visit the administrators configuration page for an unadvertised list, open a URL similar to this one, but with a '/' and the list name appended. If you have the proper authority, you can also create a new mailing list http://gr1.sca.manyone.net:10016/lists/create. General list information can be found at the mailing list overview page http://gr1.sca.manyone.net:10016/lists/listinfo. (Send questions and comments to [EMAIL PROTECTED]:1 mailto:[EMAIL PROTECTED]:10016.) I'm not sure if this is a simple template that needs to be edited or if there's a more eloquent way to get these links to reflect the proper external links/hosts we want people to see. I think you have a real problem here. I hope you are not trying to use virtual hosts too as that will really complicate things. Assuming not, set VIRTUAL_HOST_OVERVIEW = Off in mm_cfg.py. This will allow all public lists to at least appear on the listinfo and admin overview pages. As far as the host names our.internal.host.net:1 and gr1.sca.manyone.net:10016 in the above are concerned, I'm confused. These should not be different (unless you've changed DEFAULT_URL_PATTERN replacing %s with gr1.sca.manyone.net:10016) as they both are obtained from Utils.get_domain(). Anyway, these come from the environment variables HTTP_HOST or SERVER_NAME and are the actual host name which would be the real host, not the proxy. To make these be the proxy, I think you'd have to hack Mailman/Cgi/admin.py where this page is built on the fly (not from template) or better, change Mailman/Utils.py to always return the name of the proxy - you could at least make it an mm_cfg.py variable. -- 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] cgi add seems not to work any more
Hello, I'm sorry to try again here but my previous post has been moderated. Sorry for my poor English. First, I am Olivier Duquesne, an adminsitrator of L'Autre Net web hosting service. We are using mailman (2.1.5-5.backport) on Debian Woody. I'm sorry to post here but I did not find any answer in the faq neither at http://www.mail-archive.com/mailman-users@python.org/ . As we encountered lots of problems with our loadbalanced architecture and mailman, we have now a proxypass from emma to elsa. emma and elsa are the pretty name of our servers :-) Now, the last issue is very blocking, we can not add members from the cgi manually. Some tests with my account (it's general to the site server) : when adding from * http://daffyduke.lautre.net/cgi-bin/mailman/admin/ag-staff/members/add?adminpw=XXsubscribees=daffyduke%40altern.org = OK * ./add_members -r /tmp/daffy ag-staff = OK * from http://daffyduke.lautre.net/cgi-bin/mailman/listinfo/ag-staff = OK * from http://daffyduke.lautre.net/cgi-bin/mailman/admin/ag-staff/members/add = KO with this error from the user : Bug in Mailman version 2.1.5 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. Nota : subscribing email are going well to the subscriber, but he is not a list member . Here is our trackback : admin(21183): [- Python Information -] admin(21183): sys.version = 2.2.1 (#1, Feb 3 2005, 06:16:31) [GCC 2.95.4 20011002 (Debian prerelease)] admin(21183): sys.executable = /usr/bin/python2.2 admin(21183): sys.prefix = /usr admin(21183): sys.exec_prefix = /usr admin(21183): sys.path= /usr admin(21183): sys.platform= linux2 admin(21183): [- Environment Variables -] admin(21183): HTTP_ACCEPT: text/xml,application/xml,application/xhtml +xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 admin(21183): HTTP_X_FORWARDED_SERVER: emma.lautre.net = emma is the http primary host , it ProxyPass to elsa. admin(21183): HTTP_REFERER: http://daffyduke.lautre.net/cgi-bin/mailman/admin/ag-staff/members/add admin(21183): HTTP_ACCEPT_LANGUAGE: fr,fr-fr;q=0.8,en-us;q=0.5,en;q=0.3 admin(21183): PYTHONPATH: /var/lib/mailman admin(21183): SCRIPT_FILENAME: /var/alternc/cgi-bin/mailman/admin admin(21183): SERVER_ADMIN: [EMAIL PROTECTED] = ok, elsa is working admin(21183): SCRIPT_NAME: /cgi-bin/mailman/admin admin(21183): SERVER_SIGNATURE: admin(21183): REQUEST_METHOD: POST admin(21183): HTTP_HOST: elsa.lautre.net admin(21183): PATH_INFO: /ag-staff/members/add admin(21183): SERVER_PROTOCOL: HTTP/1.1 admin(21183): QUERY_STRING: admin(21183): PATH_TRANSLATED: /var/alternc/dns/l/elsa.lautre.net/ag-staff/members/add = Ugh ? Is it used by the cgi, it can not exist ! admin(21183): SERVER_SOFTWARE: Apache admin(21183): REQUEST_URI: /cgi-bin/mailman/admin/ag-staff/members/add admin(21183): CONTENT_LENGTH: 1037 admin(21183): HTTP_ACCEPT_CHARSET: ISO-8859-1,utf-8;q=0.7,*;q=0.7 admin(21183): HTTP_USER_AGENT: Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.7.9) Gecko/20050716 Firefox/1.0.5 (Debian package 1.0.5-1) admin(21183): HTTP_CONNECTION: close admin(21183): HTTP_COOKIE: ag-staff +admin=28020069cacadc427328006238336531333064363464356162646631306661613639346635386134356265343564316335 admin(21183): SERVER_NAME: elsa.lautre.net admin(21183): REMOTE_ADDR: 80.67.160.69 = are this variables checked ? IP is emma, not elsa ! admin(21183): HTTP_X_FORWARDED_FOR: 85.69.41.71 = my IP, for test admin(21183): REMOTE_PORT: 35489 admin(21183): HTTP_X_FORWARDED_HOST: daffyduke.lautre.net admin(21183): SERVER_PORT: 80 admin(21183): UNIQUE_ID: QtzYeVBDoEMAAFKDAIw admin(21183): CONTENT_TYPE: multipart/form-data; boundary=---15738030772474278601055633327 admin(21183): GATEWAY_INTERFACE: CGI/1.1 admin(21183): REMOTE_HOST: emma.lautre.net admin(21183): HTTP_ACCEPT_ENCODING: gzip,deflate admin(21183): SERVER_ADDR: 80.67.160.67 admin(21183): DOCUMENT_ROOT: /var/alternc/bureau It's fun, but removal from the same interface is working. No problem with configuration modification, archiving, or any. -- DaffyDuke/Home [ jabber: [EMAIL PROTECTED] | iCQ: 7504537 ] C.L.X. : http://clx.anet.fr/ | L'Autre Net : http://lautre.net/ La Passerelle : http://www.legrandmix.com/ signature.asc Description: This is a digitally signed message part -- 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:
Re: [Mailman-Users] cgi add seems not to work any more
DaffyDuke wrote: * from http://daffyduke.lautre.net/cgi-bin/mailman/admin/ag-staff/members/add = KO with this error from the user : Bug in Mailman version 2.1.5 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. Nota : subscribing email are going well to the subscriber, but he is not a list member . Here is our trackback : admin(21183): [- Python Information -] snip There should be a stack trace immediately preceding this in the error log. Without that information, it is very difficult to know what's happening. If you have the stack trace, please provide it. If it isn't there, then there is some issue with the Debian package. -- 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] bounce problem
Birgit Fenzke wrote: The bounce facility in mailman version 2.1.4 runs perfectly on the server in the world, the list-owner gets the information when an list member is disabled or deleted when a member has reached the given bounce score and the member itself is deleted from the list. This bounce facility does not work on the server with mailman version 2.1.5, in the bounce logfile I can find sending rzforum list probe to [EMAIL PROTECTED] ... after the maximum bounce score has been reached, but nothing happens - no disabling of the member, no information to the list-owner. This is because the probe didn't bounce - actually it probably was lost because it is VERP like and something isn't handling it properly. I know that you have changed the bounce algorithm in version 2.1.5 and that the problem might be in the postfix program or in our difficult server constellation, but I do not understand why and I have no idea on how to configure my programs properly. What I do until now is to look in the bounce logfile and delete the list members that have bounce scores manually. A running bounce facility would be a great help. Maybe it would be a help when I understand what happens or should happen when a list probe is send to a member and when this probe bounces. From the NEWS file for 2.1.5 The bounce processor has been redesigned so that now when an address's bounce score reaches the threshold, that address will be sent a probe message. Only if the probe bounces will the address be disabled. The score is reset to zero when the probe is sent. The probe is VERP like, i.e. it has an envelope sender of [EMAIL PROTECTED] If the probe bounces, the bounce needs to be returned to the envelope sender and actually delivered as if addressed to [EMAIL PROTECTED] Because of problems with VERP for some installations, 2.1.6 has VERP probes configurable and disabled by default. In 2.1.5, you need to make your postfix(es) handle the VERPed addresses as intended. -- 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] got_owner_email, got_moderator_email?
Is there a list of the codes/values that can be used in postheld.txt? What is the code that can add 1) owner's and 2) moderator's real email address in postheld.txt? These values are not in the dictionary of replacements passed to the Utils.maketext() method by the hold_for_approval() method in Mailman/Handlers/Hold.py. You would have to add them to the dictionary. -- 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 in start up scripts?
On Wed, Jul 20, 2005 at 08:10:40AM -0700, James wrote: When I restart the server I have to manually start Mailman and Mailman's master qrunner. Is it possible to have these two added in startup scripts? Mailman 2.1.5 Postfix 2.1.5 GNU/Debian Linux Debian pachage already have init script, verify your installation -- Sythos - http://www.sythos.net () ASCII Ribbon Campaign - against html/rtf/vCard in mail /\- against M$ attachments -- 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 in start up scripts?
I don't know what to verify. Mailman works fine when I start these two: /etc/init.d/mailman start /usr/lib/mailman/bin/mailmanctl restart I have to do it manualy though. When I restart the server I have to manually start Mailman and Mailman's master qrunner. Is it possible to have these two added in startup scripts? Mailman 2.1.5 Postfix 2.1.5 GNU/Debian Linux Debian pachage already have init script, verify your installation -- 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] got_owner_email, got_moderator_email?
James wrote:
Is there a list of the codes/values that can be used in postheld.txt?
From Hold.hold_for_approval()
d = {'listname' : listname,
'hostname' : mlist.host_name,
'reason' : _(reason),
'sender' : sender,
'subject': usersubject,
'admindb_url': mlist.GetScriptURL('admindb', absolute=1),
}
and
d['confirmurl'] = '%s/%s' % (mlist.GetScriptURL('confirm',
absolute=1),
cookie)
I.e. the replacements you can use are listname, hostname, reason,
sender, subject, admindb_url and confirmurl. Sone of these are
intended to be used in the notice to the admin (postauth.txt) and
aren't to meaningful in the notice to the user, e.g., admindb_url.
--
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] Mailman in start up scripts?
Quoting James [EMAIL PROTECTED]: I don't know what to verify. Mailman works fine when I start these two: /etc/init.d/mailman start /usr/lib/mailman/bin/mailmanctl restart I have to do it manualy though. Did you do this: update-rc.d mailman defaults That should install the necessary rc links for auto start. Susan When I restart the server I have to manually start Mailman and Mailman's master qrunner. Is it possible to have these two added in startup scripts? Mailman 2.1.5 Postfix 2.1.5 GNU/Debian Linux Debian pachage already have init script, verify your installation -- 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/sfeng%40stanford.edu 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
[Mailman-Users] No such list mailman after creating list
Greetings, Installed 2.1.5 today and have been tinkering. I followed the installation document and everything went fine, except this one problem. I can create lists (such as the mailman list) and mailman emails the given user to let them know about the new list. I can create new lists from the command line, no errors, email sent out. When I execute list_lists all the lists I have created are displayed as expected. However, if I go to http://mydomain.com/mailman/admin/mailman at the top of the mailman page it says No such list mailman same goes for other lists I have created (No such list anotherlistname). If I view the error log, it says admin.py access for non-existent list: mailman. So apparently something is not seeing the list as existing. Another interesting thing is when I try to create a list using the web interface, it tells me Error: You are not authorized to create new mailing lists. I have tried both the site admin and list creator passwords, I have tried resetting them to new passwords, nothing works. Can someone point me in the direction I should look to resolve this? Many Thanks, Josh Simoneau -- 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] nested lists?
Duane Winner wrote: Hello, I have created an announcment mailing list so I can send announcements to all of my clients member's emails (several dozen). I already have 12 unique mailing lists created for each organization of which these clients are members. These are discussion mailing lists. Is there a way I can incorporate the existing discussion mailing list memberships into my new announce list, so that I don't have to replicate adding the members, and also so I don't have to remember in the future to add a new member to both their respective discussion list as well as the announcement list? Yes, it's called an umbrella list. See: http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.005.htp for several different ways to implement this. jc -- 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 in start up scripts?
This is very strange. In Debian (Woody stable) when you apt-get Mailman it uncorrectly installs the init script that looks like this: mail:/etc/rc2.d# ls -la mailman lrwxr-xr-x 1 root root 19 May 8 07:40 mailman - /etc/init.d/mailman I made a change like this: mail:/etc/rc2.d# ln -s /etc/init.d/mailman S12mailman I guess this would fix it, no? -- 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] Attachments in digest mode
Greetings, I'm quite new to mailman (having just implemented it) and have run into the following problem: when e-mail containing an attachment is sent to my test list, those users not in digest mode receive it, but it is scrubbed for those users in digest mode (non-text attachment has been scrubbed . . .). No combination of digest properties that I can find seem to have any effect on this behavior. Is this the way mailman's digests are supposed to operate? Or is this a well-known problem for green implementors? Any suggestions? Thanks in advance, H. D. Wiebe [EMAIL PROTECTED] -- 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] Mailman OutgoingRunner issue?
Mailman, Ok, I had this problem below. But what makes this interesting there were some queued messages in the out (bound) queue directory. Which one of these where not delivered. However, the queued file was further removed but did not deliver the message to the list. The message did get into the archive which I thought was interesting. My customer had to resent the message to list which this worked without a flaw. Basically my question is this. When the OutgoingRunner has an error like this is it plausible for it empty the out queue before it has time to restart it. I am running sendmail 8.13.3+ with mm-handler. I do realize that mm-handler can cause some problems with incoming e-mail. That however was not the case here. Cause Mailman had gotten the mail which was in the 'out' queue. PROBLEM: log from the ERROR file Jul 19 17:32:05 2005 qrunner(7779): Traceback (most recent call last): Jul 19 17:32:05 2005 qrunner(7779): File /usr/local/libexec/mailman/bin/qrunner, line 270, in ? Jul 19 17:32:05 2005 qrunner(7779): main() Jul 19 17:32:05 2005 qrunner(7779): File /usr/local/libexec/mailman/bin/qrunner, line 230, in main Jul 19 17:32:05 2005 qrunner(7779): qrunner.run() Jul 19 17:32:05 2005 qrunner(7779): File /usr/local/RPM/USER/TMP/mailman-2.1.5-root/usr/local/libexec/mailman/Mailman/Queue/Runner.py, line 87, in run Jul 19 17:32:05 2005 qrunner(7779): File /usr/local/RPM/USER/TMP/mailman-2.1.5-root/usr/local/libexec/mailman/Mailman/Queue/OutgoingRunner.py, line 134, in _cleanup Jul 19 17:32:05 2005 qrunner(7779): File /usr/local/RPM/USER/TMP/mailman-2.1.5-root/usr/local/libexec/mailman/Mailman/Queue/BounceRunner.py, line 132, in _cleanup Jul 19 17:32:05 2005 qrunner(7779): File /usr/local/RPM/USER/TMP/mailman-2.1.5-root/usr/local/libexec/mailman/Mailman/Queue/BounceRunner.py, line 120, in _register_bounces Jul 19 17:32:05 2005 qrunner(7779): File /usr/local/RPM/USER/TMP/mailman-2.1.5-root/usr/local/libexec/mailman/Mailman/Bouncer.py, line 131, in registerBounce END Best Regards, Frank Torres -- 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] Attachments in digest mode
At 1:20 PM -0400 2005-07-20, [EMAIL PROTECTED] wrote: I'm quite new to mailman (having just implemented it) and have run into the following problem: when e-mail containing an attachment is sent to my test list, those users not in digest mode receive it, but it is scrubbed for those users in digest mode (non-text attachment has been scrubbed . . .). Correct. It is not possible for Mailman to detect which attachments should go where in which parts of the digest, so it strips all attachments and instead provides URLs to where they can be found. This behaviour within the digest system cannot be modified. If you want the same behaviour within the non-digest mailing list recipients, that's easy enough to turn on if you're using Mailman 2.1.6. -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See http://www.sage.org/ for more info. -- 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] Posting from Mailman-NNTP to a moderated newsgroup
How are people handling the case of posting/gatewaying messages to a moderated newsgroup via Mailman? Is there a way to automatically inject an Approved: header . Does Mailman look at the Sender: or the From: envelope. Thanks. -- 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 2.1.6 slowness...?
On Jul 16, 2005, at 11:16 AM, Jeff Squyres wrote:
Short version -- all good tips; many thanks. We're investigating them
all, but as you suggested, we're changing one thing at a time.
Checking them thoroughly takes a little while, so I probably won't be
able to report anything intelligent back on our results for a week or
so (gotta wait for peak usage, for one thing).
Thanks again for all the tips.
To make a long story short, we dived into all the configurations on our
server (anti-spam, anti-virus, sendmail, mailman, DNS, etc.). There
were several culprits, but most of the issues revolved around sendmail
-- changes from the anti-* guys increased timeouts, more rigorious
checks of various things (that turned out to be redundant for mailman
posts), etc. So we solved the vast majority of our issues by tweaking
sendmail and other configs -- not so much in mailman.
The key insights offered here were the fact that mailman serializes its
connections to the MTA -- once we understood that, that really narrowed
down the possibilities about where the true bottlenecks were.
Thanks all!
--
{+} Jeff Squyres
{+} [EMAIL PROTECTED]
{+} Post Doctoral Research Associate, Open Systems Lab, Indiana
University
{+} http://www.osl.iu.edu/
--
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] Mailman 2.1.5 - FQDN Question
Hello, and Greetings from Japan - I'm new to the list and to Mailman, but I
hope someone more experienced will be able to give me some pointers since I
have not been able to get specific info from google or the manual on this
problem. Please allow me to explain a little:
After installing 2.1.5 from RPM on Fedora Core 4, I tried to set up
mm_cfg.py with FQDN values, but was only able to get Mailman to start
(service mailman start) if I only enter the virtual host section, like so,
with all my other failed attempts remmed out with a #:
=8=
...
# DEFAULT_URL_HOST = fqdn
# DEFAULT_EMAIL_HOST = fqdn
# DEFAULT_URL_HOST = www.domainofmine.net
# DEFAULT_EMAIL_HOST = domainofmine.net
# DEFAULT_URL_HOST = rcogley.user.myisp.com
# DEFAULT_EMAIL_HOST = rcogley.user.myisp.com
# Because we've overriden the virtual hosts above add_virtualhost
# MUST be called after they have been defined.
# NOTE: bug with quotes
# add_virtualhost('DEFAULT_URL_HOST', 'DEFAULT_EMAIL_HOST')
add_virtualhost('www.domainofmine.net', 'domainofmine.net')
...
8=
I was not able to get Mailman to start if I set DEFAULT_URL_HOST in the
lines above the add_virtualhost line. It complains about not being able to
find the hostname www. (I do have www defined in the DNS zone for
domainofmine.net). Anyway, even with just the add_virtualhost line only, I
am able to add lists from the web interface without trouble, and the lists
that get created work correctly. It is when I try adding and configuring
lists from the command line that I run into trouble.
Here's the essence of the shell script I cobbled together from a couple of
sources including the archives of this list. It's not sophisticated with
for/do loops or anything but it seems to get the job done. I am using it to
quickly create a few lists for a single company, and hope to increase
efficiency in doing so. If we have the customer Acme, then this asks for the
short name for the company at the prompt, and then proceeds to make 4
lists - acme-support@, acme-911@, acme-memo@, [EMAIL PROTECTED]
8
#!/bin/sh
# --
# mm-multi.sh - a script for creating Mailman lists.
...
echo mm-multi.sh - \$Revision: 0.1 $
# set global variables
...
MMLISTLANG=en
[EMAIL PROTECTED]
...
echo
echo Creating lists based on a structure...
while [ $x != y ]; do
echo
echo Enter a short name for the client, no spaces, lowercase:
read CSHORTNAME
echo
echo == SCRIPT PRESETS ==
echo Location of Mailman scripts: $MMBIN
echo Location of Mailman aliases: $MMALIASES
echo List language: $MMLISTLANG
echo List Owner Email: $MMOWNEREMAIL
echo List Admin Password: $MMADMINPASS
echo
echo == USER ==
echo Client Short Name: $CSHORTNAME
echo
echo Is this correct? (y/n)
read x
done
...
/path/to/newlist -l en -q $CSHORTNAME-sales [EMAIL PROTECTED] s0m3pass
/path/to/genaliases
/path/to/add_members -r memberlistfile -w n -a y $CSHORTNAME-sales
echo description = '$CSHORTNAME-sales'
/tmp/mm-multi-$CSHORTNAME-sales-tmp
echo available_languages = ['en', 'ja']
/tmp/mm-multi-$CSHORTNAME-sales-tmp
echo accept_these_nonmembers =
['[EMAIL PROTECTED]@(.+\\\.|)domainofmine\\\.co\\\.jp$',
'[EMAIL PROTECTED]@(.+\\\.|)domainofmine\\\.net$',
'[EMAIL PROTECTED]@(.+\\\.|)domainofmine\\\.org$',
'[EMAIL PROTECTED]@(.+\\\.|)domainofmine\\\.com$', '[EMAIL
PROTECTED]@(.+\\\.|)gmail\\\.com$']
/tmp/mm-multi-$CSHORTNAME-sales-tmp
/path/to/config_list -i /tmp/mm-multi-$CSHORTNAME-sales-tmp
$CSHORTNAME-sales
[[repeat newlist through config_list for three more default list
names...]]
echo Lists Just Created:
echo
/path/to/list_lists |grep $CSHORTNAME
# cleanup
rm -f /tmp/mm-multi*
exit 0
==8
A couple of observations:
* After I used this script to create a set of test lists, it sent mail to
the owner (my account) FROM: [EMAIL PROTECTED] That indicates
to me something is wrong with a config file somewhere. The web
interface-created lists do NOT have this problem. They come in FROM:
[EMAIL PROTECTED]
* Although Advertise this list when people ask what lists are on this
machine? is set to YES for these lists, all four that were autocreated by
the script are all not visible in the web list at
http://www.domainofmine.net/mailman/listinfo/. I can access them by typing
in the expected URL in the browser address bar:
http://www.domainofmine.net/mailman/admin/xyz-support/
* Even though I can bring up the admin area for the new lists by typing
their URLs in manually (the links are not visible) the links all have
localhost.localdomain in them, and so do not work.
So my questions are: what do I set or focus on to make this
localhost.localdomain anomaly go away? Also, those regexps in
accept_these_nonmembers seem to overlap - does anyone know if there is a way
to set the regexp so that all mail from any domain with a certain string is
accepted?
Any advice appreciated! THanks very much in advance...
Sincerely,
Rick Cogley
Tokyo
Re: [Mailman-Users] Mailman 2.1.5 - FQDN Question
Hope this formats ok this time. The relevant bit of the config file should
look like:
...
# NOTE: bug with quotes
# add_virtualhost('DEFAULT_URL_HOST', 'DEFAULT_EMAIL_HOST')
add_virtualhost('www.domainofmine.net', 'domainofmine.net')
...
8=
This is what is working for me.
Best Regards,
Rick
--
Rick Cogley (mailto:[EMAIL PROTECTED])
Tel: 03-5940-6880 || Fax: 03-5940-6881 || Cell: 090-4423-5475
(Outside Japan, remove leading zero -- +81-3-5940-6880)
English: http://www.esolia.com || Japanese: http://www.esolia.co.jp
Bilingual IT solutions and management firm -- eSolia.
--
-Original Message-
From: Cogley, Rick
Sent: Thursday, July 21, 2005 12:55 PM
To: 'mailman-users@python.org'
Cc: Cogley, Rick
Subject: Mailman 2.1.5 - FQDN Question
Hello, and Greetings from Japan - I'm new to the list and to Mailman, but I
hope someone more experienced will be able to give me some pointers since I
have not been able to get specific info from google or the manual on this
problem. Please allow me to explain a little:
After installing 2.1.5 from RPM on Fedora Core 4, I tried to set up
mm_cfg.py with FQDN values, but was only able to get Mailman to start
(service mailman start) if I only enter the virtual host section, like so,
with all my other failed attempts remmed out with a #:
=8=
...
# DEFAULT_URL_HOST = fqdn
# DEFAULT_EMAIL_HOST = fqdn
# DEFAULT_URL_HOST = www.domainofmine.net
# DEFAULT_EMAIL_HOST = domainofmine.net
# DEFAULT_URL_HOST = rcogley.user.myisp.com
# DEFAULT_EMAIL_HOST = rcogley.user.myisp.com
# Because we've overriden the virtual hosts above add_virtualhost # MUST be
called after they have been defined.
# NOTE: bug with quotes
# add_virtualhost('DEFAULT_URL_HOST', 'DEFAULT_EMAIL_HOST')
add_virtualhost('www.domainofmine.net', 'domainofmine.net') ...
8=
I was not able to get Mailman to start if I set DEFAULT_URL_HOST in the
lines above the add_virtualhost line. It complains about not being able to
find the hostname www. (I do have www defined in the DNS zone for
domainofmine.net). Anyway, even with just the add_virtualhost line only, I
am able to add lists from the web interface without trouble, and the lists
that get created work correctly. It is when I try adding and configuring
lists from the command line that I run into trouble.
Here's the essence of the shell script I cobbled together from a couple of
sources including the archives of this list. It's not sophisticated with
for/do loops or anything but it seems to get the job done. I am using it to
quickly create a few lists for a single company, and hope to increase
efficiency in doing so. If we have the customer Acme, then this asks for the
short name for the company at the prompt, and then proceeds to make 4
lists - acme-support@, acme-911@, acme-memo@, [EMAIL PROTECTED]
8
#!/bin/sh
# --
# mm-multi.sh - a script for creating Mailman lists.
...
echo mm-multi.sh - \$Revision: 0.1 $
# set global variables
...
MMLISTLANG=en
[EMAIL PROTECTED]
...
echo
echo Creating lists based on a structure...
while [ $x != y ]; do
echo
echo Enter a short name for the client, no spaces, lowercase:
read CSHORTNAME
echo
echo == SCRIPT PRESETS ==
echo Location of Mailman scripts: $MMBIN
echo Location of Mailman aliases: $MMALIASES
echo List language: $MMLISTLANG
echo List Owner Email: $MMOWNEREMAIL
echo List Admin Password: $MMADMINPASS
echo
echo == USER ==
echo Client Short Name: $CSHORTNAME
echo
echo Is this correct? (y/n)
read x
done
...
/path/to/newlist -l en -q $CSHORTNAME-sales [EMAIL PROTECTED] s0m3pass
/path/to/genaliases /path/to/add_members -r memberlistfile -w n -a y
$CSHORTNAME-sales echo description = '$CSHORTNAME-sales'
/tmp/mm-multi-$CSHORTNAME-sales-tmp
echo available_languages = ['en', 'ja']
/tmp/mm-multi-$CSHORTNAME-sales-tmp
echo accept_these_nonmembers =
['[EMAIL PROTECTED]@(.+\\\.|)domainofmine\\\.co\\\.jp$',
'[EMAIL PROTECTED]@(.+\\\.|)domainofmine\\\.net$',
'[EMAIL PROTECTED]@(.+\\\.|)domainofmine\\\.org$',
'[EMAIL PROTECTED]@(.+\\\.|)domainofmine\\\.com$', '[EMAIL
PROTECTED]@(.+\\\.|)gmail\\\.com$']
/tmp/mm-multi-$CSHORTNAME-sales-tmp
/path/to/config_list -i /tmp/mm-multi-$CSHORTNAME-sales-tmp
$CSHORTNAME-sales
[[repeat newlist through config_list for three more default list
names...]]
echo Lists Just Created:
echo
/path/to/list_lists |grep $CSHORTNAME
# cleanup
rm -f /tmp/mm-multi*
exit 0
==8
A couple of observations:
* After I used this script to create a set of test lists, it sent mail to
the owner (my account) FROM: [EMAIL PROTECTED] That indicates
to me something is wrong with a config file somewhere. The web
interface-created lists do NOT have this problem. They come in FROM:
[EMAIL PROTECTED]
* Although Advertise this list when people ask what lists are on this
machine? is set to
Re: [Mailman-Users] Mailman 2.1.5 - FQDN Question
Apologies - it formatted wrong again, stringing the most relevant line
together making it looked remarked out. Once more, it is probably obvious to
you, this is the relevant line in the config:
add_virtualhost('www.domainofmine.net', 'domainofmine.net')
This is what works, as opposed to using the DEFAULT_URL_HOST etc above it.
Thanks
Rick
-Original Message-
From: Cogley, Rick
Sent: Thursday, July 21, 2005 12:55 PM
To: 'mailman-users@python.org'
Cc: Cogley, Rick
Subject: Mailman 2.1.5 - FQDN Question
Hello, and Greetings from Japan - I'm new to the list and to Mailman, but I
hope someone more experienced will be able to give me some pointers since I
have not been able to get specific info from google or the manual on this
problem. Please allow me to explain a little:
After installing 2.1.5 from RPM on Fedora Core 4, I tried to set up
mm_cfg.py with FQDN values, but was only able to get Mailman to start
(service mailman start) if I only enter the virtual host section, like so,
with all my other failed attempts remmed out with a #:
=8=
...
# DEFAULT_URL_HOST = fqdn
# DEFAULT_EMAIL_HOST = fqdn
# DEFAULT_URL_HOST = www.domainofmine.net
# DEFAULT_EMAIL_HOST = domainofmine.net
# DEFAULT_URL_HOST = rcogley.user.myisp.com
# DEFAULT_EMAIL_HOST = rcogley.user.myisp.com
# Because we've overriden the virtual hosts above add_virtualhost # MUST be
called after they have been defined.
# NOTE: bug with quotes
# add_virtualhost('DEFAULT_URL_HOST', 'DEFAULT_EMAIL_HOST')
add_virtualhost('www.domainofmine.net', 'domainofmine.net') ...
8=
I was not able to get Mailman to start if I set DEFAULT_URL_HOST in the
lines above the add_virtualhost line. It complains about not being able to
find the hostname www. (I do have www defined in the DNS zone for
domainofmine.net). Anyway, even with just the add_virtualhost line only, I
am able to add lists from the web interface without trouble, and the lists
that get created work correctly. It is when I try adding and configuring
lists from the command line that I run into trouble.
Here's the essence of the shell script I cobbled together from a couple of
sources including the archives of this list. It's not sophisticated with
for/do loops or anything but it seems to get the job done. I am using it to
quickly create a few lists for a single company, and hope to increase
efficiency in doing so. If we have the customer Acme, then this asks for the
short name for the company at the prompt, and then proceeds to make 4
lists - acme-support@, acme-911@, acme-memo@, [EMAIL PROTECTED]
8
#!/bin/sh
# --
# mm-multi.sh - a script for creating Mailman lists.
...
echo mm-multi.sh - \$Revision: 0.1 $
# set global variables
...
MMLISTLANG=en
[EMAIL PROTECTED]
...
echo
echo Creating lists based on a structure...
while [ $x != y ]; do
echo
echo Enter a short name for the client, no spaces, lowercase:
read CSHORTNAME
echo
echo == SCRIPT PRESETS ==
echo Location of Mailman scripts: $MMBIN
echo Location of Mailman aliases: $MMALIASES
echo List language: $MMLISTLANG
echo List Owner Email: $MMOWNEREMAIL
echo List Admin Password: $MMADMINPASS
echo
echo == USER ==
echo Client Short Name: $CSHORTNAME
echo
echo Is this correct? (y/n)
read x
done
...
/path/to/newlist -l en -q $CSHORTNAME-sales [EMAIL PROTECTED] s0m3pass
/path/to/genaliases /path/to/add_members -r memberlistfile -w n -a y
$CSHORTNAME-sales echo description = '$CSHORTNAME-sales'
/tmp/mm-multi-$CSHORTNAME-sales-tmp
echo available_languages = ['en', 'ja']
/tmp/mm-multi-$CSHORTNAME-sales-tmp
echo accept_these_nonmembers =
['[EMAIL PROTECTED]@(.+\\\.|)domainofmine\\\.co\\\.jp$',
'[EMAIL PROTECTED]@(.+\\\.|)domainofmine\\\.net$',
'[EMAIL PROTECTED]@(.+\\\.|)domainofmine\\\.org$',
'[EMAIL PROTECTED]@(.+\\\.|)domainofmine\\\.com$', '[EMAIL
PROTECTED]@(.+\\\.|)gmail\\\.com$']
/tmp/mm-multi-$CSHORTNAME-sales-tmp
/path/to/config_list -i /tmp/mm-multi-$CSHORTNAME-sales-tmp
$CSHORTNAME-sales
[[repeat newlist through config_list for three more default list
names...]]
echo Lists Just Created:
echo
/path/to/list_lists |grep $CSHORTNAME
# cleanup
rm -f /tmp/mm-multi*
exit 0
==8
A couple of observations:
* After I used this script to create a set of test lists, it sent mail to
the owner (my account) FROM: [EMAIL PROTECTED] That indicates
to me something is wrong with a config file somewhere. The web
interface-created lists do NOT have this problem. They come in FROM:
[EMAIL PROTECTED]
* Although Advertise this list when people ask what lists are on this
machine? is set to YES for these lists, all four that were autocreated by
the script are all not visible in the web list at
http://www.domainofmine.net/mailman/listinfo/. I can access them by typing
in the expected URL in the browser address bar:
http://www.domainofmine.net/mailman/admin/xyz-support/
* Even though I can bring up the admin area
