Re: [Mailman-Users] Mailman would not start after upgrade to 2.1.26
Hi All, I would like to report that I have resolved the problem. It was a problem I introduced, not the ports package, showing what unintended side effects some server changes cause. I had introduced a new log rotation scheme using newsyslog in FreeBSD at around the same time I did the upgrade. This included, as an example, the following lines: # logfilename [owner:group] mode count size when flags [/pid_file] [sig_num] /usr/local/mailman/logs/bounce mailman:mailman 400 5 * $W2D1 X /usr/local/mailman/data/master-qrunner.pid /usr/local/mailman/logs/error mailman:mailman 400 5 * $W1D1 X /usr/local/mailman/data/master-qrunner.pid /usr/local/mailman/logs/locks mailman:mailman 400 5 * $W1D1 X /usr/local/mailman/data/master-qrunner.pid [..] The mode 400, applied on the first Tuesday morning to all mailman logs, also made all the log files unwritable for mailman. Mailman stopped, probably with the next attempt to write a log, and would not start again. I have now changed the mode to 660, which has fixed the problem. A manual chmod for all log files was the immediate fix. Amardeo -- Amardeo Sarma @amardeo sa...@gwup.org -Original Message- From: Mailman-Users [mailto:mailman-users-bounces+sarma=gwup@python.org] On Behalf Of Mark Sapiro Sent: Tuesday, February 13, 2018 7:25 PM To: mailman-users@python.org Subject: Re: [Mailman-Users] Mailman would not start after upgrade to 2.1.26 On 02/12/2018 12:34 PM, Amardeo Sarma wrote: > > Does anyone have an idea what could have changed the write permissions for > the logs during an upgrade? I use portmaster under FreeBSD. This would seem to be an issue with FreeBSD ports. You should report this to whoever is responsible for that. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/sarma%40gwup.org -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Mailman would not start after upgrade to 2.1.26
Hi, After upgrading to Mailman 2.1.26 via ports in FreeBSD 11.1 and a reboot of the server, I just could not start Mailman at all. It would not indicate any error. The Mailman logs here: /usr/local/mailman/logs did not record anything. On second looks, I found that, after the upgrade, the write permissions for all logs under /usr/local/mailman/ logs had been removed. All log files had only read permissions for user and group. After adding write permissions (chmod 660 *) to all log files, I could restart Mailman again, and everything works again. I am not sure this has happened before but just wanted to send this note to the list for the record just in case it is a problem no one had before. And I am sorry if I am reporting a solution to a well-known problem. Does anyone have an idea what could have changed the write permissions for the logs during an upgrade? I use portmaster under FreeBSD. Cheers, Amardeo P.S.: I was subscribed before and have resubscribed now. -- Amardeo Sarma sa...@gwup.org @amardeo -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Mailman Installation with Multiple IP Addresses
For many years I have been running Mailman with several mailman lists using multiple domains (virtual hosts) on a single server without major issues (Thanks btw for this great and reliable software - hard to imagine living without it). Now I have a problem with a server with multiple IP addresses (FreeBSD 6.3, Mailman 2.1.12, Apache 2.2, Sendmail). When virtual hosts are assigned to *different* IP Addresses, the Mailman Web Interface does not work for any but the virtual hosts assigned to the main IP Address, though mail delivery is not a problem. With https://lists.mydomain.org/mailman/admin/listname and lists.mydomain.org assigned to a non-main IP address I get an error with: "Premature end of script headers: admin" I temporarily reassigned lists.mydomain.org to the main IP address on the server and things work fine, but if this can be configured for Mailman I would like to change it back. I tried adding the same lines: ScriptAlias /mailman/ /usr/local/mailman/cgi-bin/ AllowOverride None Options ExecCGI Order allow,deny Allow from all Alias /pipermail/ /usr/local/mailman/archives/public/ AddDefaultCharset Off inside the specific virtual host in httpd.conf, of course restarted apache, but that did not work either. The temporary solution works fine for the moment, but does anyone have a suggestion how this can be fixed? Are there Apache configuration examples for this (possibly) exotic case? -- Amardeo Sarma sa...@gwup.org -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
[Mailman-Users] Limiting the number of Mailman processes
Hi, with some UNIX FreeBSD VPS versions, I have had problems with mail delivery for moderately large lists (~300). Apparently the problem is that the maximum number of processes for some systems are limited (e.g. to 75). Is there any Mailman setting that can limit the maximum number of processes that Mailman can spawn in parallel to allow large lists to be used on systems with a limited maximum number of processes? I am using Mailman 2.1.5. Amardeo -- Amardeo Sarma [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=show&file=faq01.027.htp
Re: [Mailman-Users] Mail not delivered to one of many lists
Once again regarding mail that is not delivered to a single list (shunted to ~/mailman/qfiles/shunt, Mailman 2.1.1), while all others continue to work: Perhaps the following info from logs/error are useful: May 03 17:58:56 2005 (76344) Uncaught runner exception: Incorrect padding May 03 17:58:56 2005 (76344) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 82, in process send_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 123, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_digests print >> plainmsg, msg.get_payload(decode=1) File "/usr/local/mailman/pythonlib/email/Message.py", line 189, in get_payload return Utils._bdecode(payload) File "/usr/local/mailman/pythonlib/email/Utils.py", line 75, in _bdecode value = base64.decodestring(s) File "/usr/local/lib/python2.2/base64.py", line 44, in decodestring return binascii.a2b_base64(s) Error: Incorrect padding May 03 17:58:56 2005 (76344) SHUNTING: 1115143135.20801+9f18b7d05a7ab6c533bb9ac0c367f3bbdbbe2660 Any help would be sincerely appreciated. Amardeo Amardeo Sarma wrote: > Hi, > > there is a problem that never happened on our lists so far. Mails to a > particular list are not delivered and seem to be queued under: > > ~/mailman/qfiles/shunt > > Just one list is affected, all others are not. I moved all files under > ~/mailman/qfiles/shunt to a temporary directory, but that did not help. > New test messages to the list again get stuck in that (same) directory. > Mails to other lists do not appear there. > > I am running 2.1.1 using FreeBSD 4.7 with Mailman installed as a port, > and sendmail. > > Is there a way to remove the block that apparently is blocking one of > many lists only? > > Amardeo Sarma -- Amardeo Sarma [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=show&file=faq01.027.htp
Re: [Mailman-Users] Mail not delivered to one of many lists
Addendum: Mails to all other lists are delivered, but mails to this particular list get stranded in ~/mailman/qfiles/shunt Anyone have an idea what to do? Amardeo Sarma Amardeo Sarma wrote: > Hi, > > there is a problem that never happened on our lists so far. Mails to a > particular list are not delivered and seem to be queued under: > > ~/mailman/qfiles/shunt > > Just one list is affected, all others are not. I moved all files under > ~/mailman/qfiles/shunt to a temporary directory, but that did not help. > New test messages to the list again get stuck in that (same) directory. > Mails to other lists do not appear there. > > I am running 2.1.1 using FreeBSD 4.7 with Mailman installed as a port, > and sendmail. > > Is there a way to remove the block that apparently is blocking one of > many lists only? > > Amardeo Sarma -- Amardeo Sarma [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=show&file=faq01.027.htp
[Mailman-Users] Mail not delivered to one of many lists
Hi, there is a problem that never happened on our lists so far. Mails to a particular list are not delivered and seem to be queued under: ~/mailman/qfiles/shunt Just one list is affected, all others are not. I moved all files under ~/mailman/qfiles/shunt to a temporary directory, but that did not help. New test messages to the list again get stuck in that (same) directory. Mails to other lists do not appear there. I am running 2.1.1 using FreeBSD 4.7 with Mailman installed as a port, and sendmail. Is there a way to remove the block that apparently is blocking one of many lists only? Amardeo Sarma -- Amardeo Sarma [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=show&file=faq01.027.htp
Re: [Mailman-Users] Importing subscribers
--On Donnerstag, 7. August 2003 11:59 -0400 John DeCarlo <[EMAIL PROTECTED]> wrote: Hindy, You certainly can. Either via the web or via the command line. Mailman will accept various formats, too. I just use the format: Joe Smith <[EMAIL PROTECTED]> Which works fine via the web or the command line. Chinn, Hindy wrote: Can one subscribe a list of email addresses with their corresponding names (one email + name per line)? I imported a text filewith one email address per line (almost 400 addresses / lines) via the web interface (mass subscription under membership management) without any major problems (except many bounces because some email addresses were not reachable). Amardeo. -- Amardeo Sarma [EMAIL PROTECTED] -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Keeping process count low
In the meanwhile, I am getting around 200 error messages a day complaining about "cannot fork". I have tried various settings of SMTP_MAX_SESSIONS_PER_CONNECTION and MAX_DELIVERY_THREADS, but that does not seem to help. Does anyone know what the problem could be? Amardeo. --On Dienstag, 5. August 2003 19:52 +0200 Amardeo Sarma <[EMAIL PROTECTED]> wrote: Hi, since a larger number of lists are hosted on our server, I am running into a problem with the number of processes on the server, which is limited. Is it a way out to set some limit on: SMTP_MAX_SESSIONS_PER_CONNECTION or MAX_DELIVERY_THREADS Any other suggestions to keep the number of concurrent processes down, even if delivery takes a bit longer? Typical errors I get are: - The following addresses had permanent fatal errors - "|/usr/local/mailman/mail/mailman bounces abc" (reason: 2) (expanded from: <[EMAIL PROTECTED]>) - Transcript of session follows - Cannot fork: Resource temporarily unavailable 554 5.3.0 unknown mailer error 2 It seems to me that this indicates that the maximum number of allowed processes has been exceeded. Amardeo. -- Amardeo Sarma [EMAIL PROTECTED] -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Keeping process count low
Hi, since a larger number of lists are hosted on our server, I am running into a problem with the number of processes on the server, which is limited. I get a number Is it a way out to set some limit on: SMTP_MAX_SESSIONS_PER_CONNECTION or MAX_DELIVERY_THREADS Any other suggestions to keep the number of concurrent processes down, even if delivery takes a bit longer? Typical errors I get are: - The following addresses had permanent fatal errors - "|/usr/local/mailman/mail/mailman bounces abc" (reason: 2) (expanded from: <[EMAIL PROTECTED]>) - Transcript of session follows - Cannot fork: Resource temporarily unavailable 554 5.3.0 unknown mailer error 2 It seems to me that this indicates that the maximum number of allowed processes has been exceeded. Amardeo. -- Amardeo Sarma [EMAIL PROTECTED] -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Customising Languages per Virtual Host
Maybe someone knows the solution to this one: I would like to customise different virtual hosts to use different languages when showing the lists available for the virtual host, e.g.: https://lists.engdom.org/mailman/listinfo to show the general text in English, and https://lists.gerdom.org/mailman/ to show the general text in German. Customising each individual list is no problem, nor is the default language. But how does one customise the language of the welcome texts that show the lists available for the virtual host? Amardeo. -- Amardeo Sarma [EMAIL PROTECTED] -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Starting qrunner for FreeBSD
On 24 Jun 2003 at 21:57, John Michael Mars wrote: > There is not BSD specific documentation in there. I was thinking about > submitting a patch for anyone who wants it... > > Basically, (I use OpenBSD), you need to set this stuff in /etc/rc.local > and /etc/rc.shutdown instead of /etc/rc.d/init.d. BSDs are BSDish. Linux > is SysVish. The layout of some of the file system (including config files) > is a bit different. Linux, being the most popular, is the one that > typically gets documented and BSDers just have to get to it themselves. > Anyone have an idea why on running "bin/mailmanctl start" from the $prefix directory (again FreeBSD) I get the error message: Site list is missing: mailman ? Amardeo. > - JMM > > On Wed, 25 Jun 2003, Amardeo Sarma wrote: > > > Hi, > > > > I am a newbie and running Mailman 2.1.1 on FreeBSD 4.7 / VPSv2, which works > > with the old technique of running qrunner every minute from cron. The INSTALL > > instructions give some hints on how to start the qrunner daemon at startup time > > (apparently the preferred mode for 2.1.x), but this seems geared to Linux. I > > would appreciate any hints on what the best solution for FreeBSD systems is. > > > > Amardeo. > > > > -- > > Amardeo Sarma > > [EMAIL PROTECTED] > > > > > > -- > > Mailman-Users mailing list > > [EMAIL PROTECTED] > > 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/ > > > > This message was sent to: [EMAIL PROTECTED] > > Unsubscribe or change your options at > > http://mail.python.org/mailman/options/mailman-users/michael%40firewing.org > > > > -- Amardeo Sarma [EMAIL PROTECTED] -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Starting qrunner for FreeBSD
Hi, I am a newbie and running Mailman 2.1.1 on FreeBSD 4.7 / VPSv2, which works with the old technique of running qrunner every minute from cron. The INSTALL instructions give some hints on how to start the qrunner daemon at startup time (apparently the preferred mode for 2.1.x), but this seems geared to Linux. I would appreciate any hints on what the best solution for FreeBSD systems is. Amardeo. -- Amardeo Sarma [EMAIL PROTECTED] -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
