Re: [Mailman-Users] Digests not being sent, accumulating instead
Thank you for your suggestion. I ran the 'senddigests' command on the list and the digest was delivered successfully. No errors. On Thu, Jul 20, 2017 at 9:38 AM, Mark Sapiro <m...@msapiro.net> wrote: > On 07/20/2017 09:16 AM, Christopher Adams wrote: > > > > I noticed that a list digest is not being sent. The list is set to send a > > daily digest regardless if the quota has been reached. > > > > I verified that the cron is running: > > > > Jul 16 12:00:01 swiki CROND[44968]: (mailman) CMD (/usr/bin/python -S > > /usr/local/mailman/cron/senddigests) > > > > The digest.mbox has accumulated since 7/16 til the present. > > > There is probably some defective message in the digest.mbox which is > causing some exception to be thrown in processing the digest. > > Part of the issue is you probably never see the output from Mailman's > crons when they encounter errors. See <https://wiki.list.org/x/10715167>. > > You can run > > cron/senddigests > > or > > cron/senddigests -l > > as the mailman user manually from the command line to get more > information on the error. > > The ultimate solution will be to remove the problem message from the > digest.mbox or fix it. > > -- > Mark Sapiro <m...@msapiro.net>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/ > adamsca%40gmail.com > -- Christopher Adams adam...@gmail.com -- 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] Digests not being sent, accumulating instead
Hello, I noticed that a list digest is not being sent. The list is set to send a daily digest regardless if the quota has been reached. I verified that the cron is running: Jul 16 12:00:01 swiki CROND[44968]: (mailman) CMD (/usr/bin/python -S /usr/local/mailman/cron/senddigests) The digest.mbox has accumulated since 7/16 til the present. I would appreciate any ideas about what might be happening and how to resolve it. Many thanks, Christopher Adams -- 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
Re: [Mailman-Users] attachements scrubbed, but list doesn't use Content Filtering
Sorry, I was a bit premature in my question. Apparently, an admin with little knowledge of the settings had toggled the non_digest settings to scrub everything. I missed that setting after going through it several times. On Tue, Jul 18, 2017 at 1:42 PM, Christopher Adams <adam...@gmail.com> wrote: > Hello all, > > A list administrator reports that all attachments are being scrubbed, in > the sent messages and in the archives. The site default is to not use > Content Filtering and this list uses that default. Also, there are many > other lists with the same default settings and I am not hearing of this > behavior. > > What am I missing here ? > > Many thanks, > > Christopher Adams > -- Christopher Adams adam...@gmail.com -- 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] attachements scrubbed, but list doesn't use Content Filtering
Hello all, A list administrator reports that all attachments are being scrubbed, in the sent messages and in the archives. The site default is to not use Content Filtering and this list uses that default. Also, there are many other lists with the same default settings and I am not hearing of this behavior. What am I missing here ? Many thanks, Christopher Adams -- 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
Re: [Mailman-Users] Remove pending requests from one address for all lists
Thank you, Mark. This is very helpful. On Feb 15, 2017 2:45 PM, "Mark Sapiro" <m...@msapiro.net> wrote: > On 02/15/2017 12:03 PM, Christopher Adams wrote: > > > > Is there a way to remove pending requests from a specific address for all > > lists ? Our system periodically is flooded by requests like this. The > > result is dependent on how the individual list is set up. There are over > > 1000 lists on our server. The 'discard' command can remove all pending > > requests to one specific list. > > > See <https://www.msapiro.net/scripts/erase>, mirrored at > <https://fog.ccsf.edu/~msapiro/scripts/erase>, described as: > > erase > Remove an address or all addresses matching a regexp from the > installation. I.e. for every list, if the address is a member, it is > removed. If there are any held posts or (un)subscription requests from > the address, they are removed too. Optionally, any subscription requests > from the address waiting user confirmation are also removed. > > -- > Mark Sapiro <m...@msapiro.net>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/ > adamsca%40gmail.com > -- 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] Remove pending requests from one address for all lists
Hell9o all, Is there a way to remove pending requests from a specific address for all lists ? Our system periodically is flooded by requests like this. The result is dependent on how the individual list is set up. There are over 1000 lists on our server. The 'discard' command can remove all pending requests to one specific list. Is there a command line utility or script that can do this ? Many thanks. -- Christopher Adams adam...@gmail.com -- 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
Re: [Mailman-Users] subscribers being unsubscribed at wrong time based on bounce settings.
Sorry if my reply doesn't follow the standards for reply, but gmail is not quoting messages as it usually does. --- I tracked one of the disabled addresses that was unsubscribed. It is the same for all that were unsubscribed. bounce.log-20161101:Oct 31 16:16:36 2016 (32252) oebbmembers: recipi...@wherever.com current bounce score: 2.0 bounce.log-20161107:Nov 06 15:21:38 2016 (24109) oebbmembers: recipi...@wherever.com current bounce score: 3.0 bounce.log-20161107:Nov 06 15:21:38 2016 (24109) oebbmembers: recipi...@wherever.com disabling due to bounce score 3.0 >= 3.0 bounce.log-20161112:Nov 11 15:56:41 2016 (11544) oebbmembers: recipi...@wherever.com residual bounce received bounce.log-20161117:Nov 17 09:04:35 2016 (58403) Notifying disabled member recipi...@wherever.com for list: oebbmembers bounce.log-20161123:Nov 22 10:11:14 2016 (60465) oebbmembers: recipi...@wherever.com residual bounce received bounce.log-20161125:Nov 24 09:16:14 2016 (35874) Notifying disabled member recipi...@wherever.com for list: oebbmembers bounce.log-20161125:Nov 24 09:16:14 2016 (35874) oebbmembers: recipi...@wherever.com deleted after exhausting notices The cron/disabled ran every day during November at 9. I think all of the unsubscribes were because of being disabled due to bounce settings. The "valid" addresses were also disabled and unsubscribed, but that is aside from this and something that the customer needs to deal with. I learned something new - disabled and unsubscribed addresses receive a message regardless of the other list settings for receiving messages when unsubscribed. Thanks. I am not sure if the bounce settings for the list were changed after 11/1. I don't suppose that logs reflect this. I will take it up with the customer. This seems to be the lone remaining question. Thank you for the information, Mark. -- 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] subscribers being unsubscribed at wrong time based on bounce settings.
Hello, I have done some fairly extensive examination of logs and list settings for one of the lists hosted here, and I can't come up with a sensible explanation to tell a customer. The list is set to not send messages when a person unsubscribes. The bounce settings are set so that 2 warning messages are sent after the address is disabled and those messages should be 7 days apart. A message was sent to the list on 11/1. I see in the logs that a substantial number of addresses reached the bounce limit and were disabled. So, based on the bounce settings, many of these should have been unsubscribed 14 days later. They were not. However, on 11/24, there was a mass unsubscribe of addresses that had been disabled. Additionally, many (including some that turned out to have valid addresses) received unsubscribe notices. I tend to think that these are not related, but are two issues that I have not been able to explain. Many thanks, Christopher Adams -- 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
Re: [Mailman-Users] problems linking to successive chunks of addresses in admin user search
Sorry, lines were truncated. This is more accurate. -rw-r--r--. 1 mailman mailman 72139 Sep 28 16:19 /usr/local/mailman/Mailman/admin.py -rw-r--r--. 1 apache mailman 46447 Sep 28 16:20 /usr/local/mailman/Mailman/admin.pyc -rw-r--r--. 1 mailman mailman 71971 Sep 28 14:31 /usr/local/mailman/Mailman/admin.py.old -rw-r--r--. 1 mailman mailman 71971 Sep 28 16:18 /usr/local/mailman/Mailman/admin.py.orig On Thu, Sep 29, 2016 at 8:35 AM, Mark Sapiro <m...@msapiro.net> wrote: > On 09/29/2016 08:04 AM, Christopher Adams wrote: > > I cleared browser cache and reloaded. Same problem. Here are answers to > > your questions. > > > > ScriptAlias /mailman/ "/usr/local/mailman/cgi-bin/" > > > > strings /usr/local/mailman/cgi-bin/admin | grep scripts > > /usr/local/mailman/scripts/ > > > > prefix = '/usr/local/mailman' > > > OK. > > Send me (off list) a copy of /usr/local/mailman/Mailman/Cgi/admin.py > > Also, what does > > ls -l /usr/local/mailman/Mailman/Cgi/admin.py* > > show? > > -- > Mark Sapiro <m...@msapiro.net>The highway is for gamblers, > San Francisco Bay Area, Californiabetter use your sense - B. Dylan > -- Christopher Adams adam...@gmail.com -- 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
Re: [Mailman-Users] problems linking to successive chunks of addresses in admin user search
ls -l /usr/local/mailman/Mailman/Cgi/admin.py* -rw-r--r--. 1 mailman mailman 72139 Sep 28 16:19 /usr/local/mailman/Mailadmin.py -rw-r--r--. 1 apache mailman 46447 Sep 28 16:20 /usr/local/mailman/Mailadmin.pyc -rw-r--r--. 1 mailman mailman 71971 Sep 28 14:31 /usr/local/mailman/Mailadmin.py.old -rw-r--r--. 1 mailman mailman 71971 Sep 28 16:18 /usr/local/mailman/Mailadmin.py.orig I will send a copy of admin.py off list. Thanks. On Thu, Sep 29, 2016 at 8:35 AM, Mark Sapiro <m...@msapiro.net> wrote: > On 09/29/2016 08:04 AM, Christopher Adams wrote: > > I cleared browser cache and reloaded. Same problem. Here are answers to > > your questions. > > > > ScriptAlias /mailman/ "/usr/local/mailman/cgi-bin/" > > > > strings /usr/local/mailman/cgi-bin/admin | grep scripts > > /usr/local/mailman/scripts/ > > > > prefix = '/usr/local/mailman' > > > OK. > > Send me (off list) a copy of /usr/local/mailman/Mailman/Cgi/admin.py > > Also, what does > > ls -l /usr/local/mailman/Mailman/Cgi/admin.py* > > show? > > -- > Mark Sapiro <m...@msapiro.net>The highway is for gamblers, > San Francisco Bay Area, Californiabetter use your sense - B. Dylan > -- Christopher Adams adam...@gmail.com -- 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
Re: [Mailman-Users] problems linking to successive chunks of addresses in admin user search
I cleared browser cache and reloaded. Same problem. Here are answers to your questions. ScriptAlias /mailman/ "/usr/local/mailman/cgi-bin/" strings /usr/local/mailman/cgi-bin/admin | grep scripts /usr/local/mailman/scripts/ prefix = '/usr/local/mailman' On Wed, Sep 28, 2016 at 9:57 PM, Mark Sapiro <m...@msapiro.net> wrote: > On 09/28/2016 09:34 PM, Christopher Adams wrote: > > I did patch the installed instance of Mailman > > (/usr/local/mailman/Mailman/Cgi/admin.py). I can see the changes that > > it made, but the result is the same when looking at the subscriber list. > > > The patch converts a unicode URL to the character set of the list's > preferred language. The result should not be a u'http://... string. > > I can only guess that your web server is not executing the script you > think it is. Or possibly you are looking at an older, cached version of > the page. Have you tried reloading the page in your browser? > > What is the path in the web server's ScriptAlias (if it's apache or > whatever it is in your web server). Is it /usr/local/mailman/cgi-bin/ or > something else? > > If it is /usr/local/mailman/cgi-bin/, what does > > strings /usr/local/mailman/cgi-bin/admin | grep scripts > > show? and if you look in the paths.py file in that directory, what is > the value in the > > prefix = > > statement? > > -- > Mark Sapiro <m...@msapiro.net>The highway is for gamblers, > San Francisco Bay Area, Californiabetter use your sense - B. Dylan > -- Christopher Adams adam...@gmail.com -- 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
Re: [Mailman-Users] problems linking to successive chunks of addresses in admin user search
I did patch the installed instance of Mailman (/usr/local/mailman/Mailman/Cgi/admin.py). I can see the changes that it made, but the result is the same when looking at the subscriber list. On Sep 28, 2016 4:37 PM, "Mark Sapiro" <m...@msapiro.net> wrote: > On 09/28/2016 04:28 PM, Christopher Adams wrote: > > Thank you. I did patch the admin.py file and I can see the changes. > > However, if I go to the list subscribers, the link to the next group of > > addresses takes me back to the main admin page. > > > > I did notice that the URL includes < u'http:// > which I thought > > was the problem that this was supposed to remedy. I then restarted > > Mailman, but that made no difference. > > > It is exactly that issue that the patch fixes. What admin.py file did > you patch? You should be patching Mailman/Cgi/admin.py where the > 'Mailman' directory is the actual installed Mailman, maybe something > like /usr/local/mailman/Mailman, but this depends on how Mailman was > installed. > > -- > Mark Sapiro <m...@msapiro.net>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/archive%40jab.org
Re: [Mailman-Users] problems linking to successive chunks of addresses in admin user search
Thank you. I did patch the admin.py file and I can see the changes. However, if I go to the list subscribers, the link to the next group of addresses takes me back to the main admin page. I did notice that the URL includes < u'http:// > which I thought was the problem that this was supposed to remedy. I then restarted Mailman, but that made no difference. On Wed, Sep 28, 2016 at 4:12 PM, Mark Sapiro <m...@msapiro.net> wrote: > On 09/28/2016 11:04 AM, Christopher Adams wrote: > > > > Do I need to patch Mailman and then follow the process as I would for > > installing/upgrading Mailman ? > > > You could, but it isn't necessary. > > > > When I patch, should I be in the Mailman build/source directory and not > > in the current Mailman directory ? > > > The easiest thing is to just patch the active Mailman, not the > build/source. > > > > Would 'patch < admin.patch' work ? > > > It will if you are in the $prefix directory. > > Since this patch only affects the admin CGI which is not a persistent > process, it is only necessary to apply the patch to > $prefix/Mailman/Cgi/admin.py. It is not necessary to restart Mailman. > See <https://wiki.list.org/x/17891729>. > > -- > Mark Sapiro <m...@msapiro.net>The highway is for gamblers, > San Francisco Bay Area, Californiabetter use your sense - B. Dylan > -- Christopher Adams adam...@gmail.com -- 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
Re: [Mailman-Users] problems linking to successive chunks of addresses in admin user search
Thank you for the reply and the attached patch. Do I need to patch Mailman and then follow the process as I would for installing/upgrading Mailman ? When I patch, should I be in the Mailman build/source directory and not in the current Mailman directory ? Would 'patch < admin.patch' work ? Many thanks. On Tue, Sep 27, 2016 at 5:31 PM, Mark Sapiro <m...@msapiro.net> wrote: > On 09/27/2016 04:31 PM, Christopher Adams wrote: > > > > So, the first chunk is '0' and then the link goes to chunk '1', but it > > links back to the top-level admin page. > ... > > Is this a Feature or a Bug ? > > > It is this bug <https://bugs.launchpad.net/mailman/+bug/1604544> which > was fixed by the attached patch. > > -- > Mark Sapiro <m...@msapiro.net>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/ > adamsca%40gmail.com > -- Christopher Adams adam...@gmail.com -- 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] problems linking to successive chunks of addresses in admin user search
Hello, I have a list with nearly 45,000 subscribers. When a list owner searches for a subscriber through the admin interface, she gets a list of addresses, then a link to follow to get the next 'chunk'. The link leads to something like the following if I were searching for 'stephanie'. http://mydomain.com/mailman/admin/mylist/u'http:// mydomain.com/mailman/admin/mylist/members?letter=s= 1=stephanie So, the first chunk is '0' and then the link goes to chunk '1', but it links back to the top-level admin page. If you click the chunks of addresses by the alphabetical letters, it will successfully take you to each section. Is this a Feature or a Bug ? -- Christopher Adams adam...@gmail.com -- 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
Re: [Mailman-Users] Problems using Postfix with Mailman
Yes, you are so right. I did have an entry for 127.0.0.1 localhost in /etc/hosts, but also the entry for IPV6, which I didn't need and it apparently took preference. So, this did help and I thank you. Additionally, there was some configuration in the Postfix main.cf that needed updating due to a change in the version of Postfix. Many thanks, Mark. On May 3, 2016 5:56 PM, "Mark Sapiro" <m...@msapiro.net> wrote: > On 05/03/2016 04:50 PM, Christopher Adams wrote: > > > In the maillog file, I get NOQUEUE: reject RCPT from localhost [::1] 454 > > 4.71 <my.addr...@mydomain.com>: Relay access denied; from=< > > mylist-boun...@mymailmanserver.com> > > > > In the Mailman smtp-failure log file, I get: "Relay access denied" > > > >>From all that I have read, it must be a Postfix configuration problem, > but > > since I just moved the old main.cf to the new server, I am perplexed. > Posts > > to the Postfix-Users list has not been productive. > > > Right, and the problem is you didn't change the postfix main.cf to match > the RedHat/CentOS change in /etc/hosts. > > The issue is that mailman is sending to 'localhost', /etc/hosts is > defining localhost as the IPv6 address [::1], and this is not in > mynetworks in main.cf. There are various ways to fix this including > replacing the localhost entry in /etc/hosts - something like > > ::1 localhost > > with > > 127.0.0.1 localhost > > or adding [::1]/128 to mynetworks in main.cf. > > -- > Mark Sapiro <m...@msapiro.net>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/adamsca%40gmail.com > -- 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] Problems using Postfix with Mailman
Hello all, I previously posted a message about a server "migration" of Mailman to a new CentOS 7 server. It actually is a rebuild and I will be trying to restore list info from backup. Anyway, I have Mailman installed and can access web pages and create lists. I am using Postfix as the MTA and I restored the main.cf file from the old server. I have indicated MTA ="Postfix" in mm_cfg.py, which I also moved over frrom old server backup. I restarted Postfix and Mailman. Now, when I post to a list, I get a variety of errors. In my own mailbox, I get this: mymailmanserver.com #<mymailmanserver.com#5.1.1 SMTP; 550 5.1.1 < oslt...@mymailmanserver.com <oslt...@listsmart.osl.state.or.us>>: Recipient address rejected: User unknown in local recipient table> #SMTP# In the maillog file, I get NOQUEUE: reject RCPT from localhost [::1] 454 4.71 <my.addr...@mydomain.com>: Relay access denied; from=< mylist-boun...@mymailmanserver.com> In the Mailman smtp-failure log file, I get: "Relay access denied" >From all that I have read, it must be a Postfix configuration problem, but since I just moved the old main.cf to the new server, I am perplexed. Posts to the Postfix-Users list has not been productive. If anyone uses Mailman and Postfix, maybe you can share your experiences. Many thanks. -- Christopher Adams adam...@gmail.com -- 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
Re: [Mailman-Users] Problems with getting httpd to play well with new Mailman install
Yes, it is Apache 2.4 and I had already taken those measures. I don't know what was fouled up, but I rebooted the server and can now get to the web pages and create lists. However, I am still having problems, but will post that as s different issue. Thanks. On Mon, May 2, 2016 at 8:49 PM, Mark Sapiro <m...@msapiro.net> wrote: > On 05/02/2016 02:51 PM, Christopher Adams wrote: > > > > Looking in the httpd error log, I find this: "client denied by server > > configuration: /usr/local/mailman/cgi-bin/listinfo". > > > > I added a block in the httpd.conf file to allow access to the cgi-bin > > directory and restarted httpd. Still, I am being forbidden. Files and > > directories are owned by mailman.mailman and they seem like they have > > proper permissions. I am assuming that it is > > > > > > Order allow,deny > > Allow from all > > > > > If this is Apache 2.4, instead of > > Order allow,deny > Allow from all > > you need > > Require all granted > > See <http://httpd.apache.org/docs/2.4/upgrading.html>. > > > > I then commented out the directory block that limited access to the > entire > > file system. I restarted httpd. Now, I get this : > > Bug in Mailman version 2.1.22 We're sorry, we hit a bug! > > > And what's in Mailman's error log? We need this info to begin to > understand what the issue might be. > > -- > Mark Sapiro <m...@msapiro.net>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/adamsca%40gmail.com > -- Christopher Adams adam...@gmail.com -- 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] Problems with getting httpd to play well with new Mailman install
Hello all, I recently had a server fail and I am rebuilding a new server (CentOS 7 ) for Mailman. I have the server and OS working and Mailman installed. I have installed Mailman a number of times, so kind of know the routine. I have Apache running and verified that it is by browsing to the root of the web server. I created a new mailing list and then tried to navigate to the admin and listinfo page. The result was '403 Forbidden'. Looking in the httpd error log, I find this: "client denied by server configuration: /usr/local/mailman/cgi-bin/listinfo". I added a block in the httpd.conf file to allow access to the cgi-bin directory and restarted httpd. Still, I am being forbidden. Files and directories are owned by mailman.mailman and they seem like they have proper permissions. I am assuming that it is Order allow,deny Allow from all I then commented out the directory block that limited access to the entire file system. I restarted httpd. Now, I get this : Bug in Mailman version 2.1.22 We're sorry, we hit a bug! -- Christopher Adams adam...@gmail.com -- 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] config.pck files
Hello all, A list that is hosted here reported that the membership list and other settings had reverted to previous content. I took a look at the files and see this: -rw-rw 1 mailman mailman 14526 Oct 30 08:00 config.pck -rw-rw 1 mailman mailman 48950 Sep 29 13:15 config.pck.corrupt -rw-rw 1 mailman mailman 14526 Oct 30 08:00 config.pck.last -rw-rw 1 apache mailman 49499 Sep 29 16:38 config.pck.safety It looks like the config.pck file was corrupt. Just for clarification, what are the other config.pck* files ? Since teh config.pck.safety looks like it is much larger in size, and I ran ./dumpdb to read it and it appears to be more current data, I am thinking that I can use it to overwrite the config.pck, which apparently was used because the file was corrupt. Can someone explain how these files work when the file becomes corrupt? Can I just copy the config.pck.safety to config.pck ? Many thanks -- Christopher Adams adam...@gmail.com -- 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
Re: [Mailman-Users] subscribed address that forwards to secondary address can't be identified
Thank you all for your suggestions. I have set up VERP via Mailman in mm_cfg.py. I logged in to the list admin and followed guidelines about enabling Personalization. I referred to this: http://wiki.list.org/pages/viewpage.action?pageId=4030545 I may be missing something, but I don't see anything under 'Non-digest options' for enabling Personalization. Does it just refer to custom headers, footers, etc? It seems that you can do that anyways without the setting allowing Personalization in mm_cfg.py. Also, when enabling something in mm_cfg.py, the guidelines say to use 1=true/yes, but then I see it looking something like the following. Maybe this is part of the problem. I would appreciate some clarification. Thank you. VERP_PERSONALIZED_DELIVERIES = Yes OWNERS_CAN_ENABLE_PERSONALIZATION = Yes On Sat, Apr 5, 2014 at 9:48 AM, Lindsay Haisley fmo...@fmp.com wrote: VERP will nail the problem quickly. I have relatively small lists on my server and leave VERP turned on. This also helps eliminate complaining AOL subscribers since AOL often doesn't redact VERPed addresses in their TOS notifications. On Fri, 2014-04-04 at 14:44 -0700, Mark Sapiro wrote: If all else fails, and you have the ability, you can enable Mailman's VERP. Then each message from Mailman will have the envelope from and Sender: and Errors-To: headers with the address LISTNAME-bounces-user=example.com@your.domain where u...@example.com is the address sent to. -- Lindsay Haisley | Everything works if you let it FMP Computer Services | 512-259-1190 | --- The Roadie http://www.fmp.com| -- 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/adamsca%40gmail.com -- Christopher Adams adam...@gmail.com -- 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
Re: [Mailman-Users] subscribed address that forwards to secondary address can't be identified
Ok, I think I have what I need. I checked the mail logs and see that the header is showing the list name and the subscriber address. Now, I need to see what happens when I set a forward and send a message. On Mon, Apr 7, 2014 at 12:24 PM, Christopher Adams adam...@gmail.comwrote: Thank you all for your suggestions. I have set up VERP via Mailman in mm_cfg.py. I logged in to the list admin and followed guidelines about enabling Personalization. I referred to this: http://wiki.list.org/pages/viewpage.action?pageId=4030545 I may be missing something, but I don't see anything under 'Non-digest options' for enabling Personalization. Does it just refer to custom headers, footers, etc? It seems that you can do that anyways without the setting allowing Personalization in mm_cfg.py. Also, when enabling something in mm_cfg.py, the guidelines say to use 1=true/yes, but then I see it looking something like the following. Maybe this is part of the problem. I would appreciate some clarification. Thank you. VERP_PERSONALIZED_DELIVERIES = Yes OWNERS_CAN_ENABLE_PERSONALIZATION = Yes On Sat, Apr 5, 2014 at 9:48 AM, Lindsay Haisley fmo...@fmp.com wrote: VERP will nail the problem quickly. I have relatively small lists on my server and leave VERP turned on. This also helps eliminate complaining AOL subscribers since AOL often doesn't redact VERPed addresses in their TOS notifications. On Fri, 2014-04-04 at 14:44 -0700, Mark Sapiro wrote: If all else fails, and you have the ability, you can enable Mailman's VERP. Then each message from Mailman will have the envelope from and Sender: and Errors-To: headers with the address LISTNAME-bounces-user=example.com@your.domain where u...@example.com is the address sent to. -- Lindsay Haisley | Everything works if you let it FMP Computer Services | 512-259-1190 | --- The Roadie http://www.fmp.com| -- 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/adamsca%40gmail.com -- Christopher Adams adam...@gmail.com -- Christopher Adams adam...@gmail.com -- 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] subscribed address that forwards to secondary address can't be identified
Hello all, This is not necessarily a Mailman question, but I thought someone administering Mailman may have come across this before. A person is receiving mail through a list. The address that they are currently using (@gmail.com) is not subscribed to the list. I assume that means a subscribed address is forwarding to the gmail account. The gmail account people don't have any idea what they could have been subscribed as. I thought maybe the Mailman or MTA logs would show the susbscribed address forwarding to the gmail address. However, I can't find anything, so can't identify which address is the culprit. Does anyone have an idea how to get to the bottom of this? -- Christopher Adams adam...@gmail.com -- 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
Re: [Mailman-Users] smtp-failure.log / diagnosing delivery to only some subscribers
Thank you all for your replies. I queried my MTA log for the message ID and only came up with 8 out of 66 addresses. These were logged as sent. I assumed that the bounces/undeliverables would also show up with the same message ID. Am I mistaken? Am I not looking for the right info in the MTA log? On Thu, Dec 12, 2013 at 11:16 PM, Mark Sapiro m...@msapiro.net wrote: On 12/12/2013 06:41 PM, Stephen J. Turnbull wrote: Christopher Adams writes: So, I assumed that smtp-failure.log would show which addresses were not sent to. I don't think that is what it is for. No, it shows addresses that were sent to and rejected by the remote SMTP server. Actually, smtp-failure only logs addresses that were rejected by the local MTA. Addresses rejected by a remote MTA should be logged in the local MTA's logs and result in bounces to Mailman, but they won't be logged in smtp-failure. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org 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/adamsca%40gmail.com -- Christopher Adams adam...@gmail.com -- 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] smtp-failure.log / diagnosing delivery to only some subscribers
Based on the logs that I have seen, this log records messages sent to addresses with bad syntax. Is that all it does. I don't see many items in these, and with the volume of mail going through our system, I would expect to see more. failed with code 501: 5.1.3 Bad recipient address syntax A post to a list shows 1) it was posted to the list (post.log) 2) Mailman sent it to x number of recipients (smtp.log). When I look at the actual MTA log, I only see that message, based on the message ID, going to a portion of the x number of recipients. So, I assumed that smtp-failure.log would show which addresses were not sent to. I don't think that is what it is for. Any suggestions on how to troubleshoot why the message seems to be only sent to a portion of the subscribers, though Mailman tells me it was sent to all the subscribers? -- Christopher Adams adam...@gmail.com -- 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
Re: [Mailman-Users] problems with bounce processing
Mark, I had restarted Mailman several times and still, bounce processing was not taking place and the bounce log had not been written since 11/13. Before I left last night, I restarted it and then I noticed a flurry of activity, with queued bounces being processed. I hadn't looked in the /qfiles/bounces/ until this morning. Now I see that there is nothing queued. So, any idea of what might of happened to gum it up. Thanks for taking the time to address this issue. It seemingly has corrected itself. On Tue, Nov 19, 2013 at 4:22 PM, Mark Sapiro m...@msapiro.net wrote: On 11/19/2013 03:35 PM, Christopher Adams wrote: There is no bounce score entry in the bounce log. As it turns out, there has not been a bounce log generated since 11/13. Would BounceRunner show in a list of processes. If so, I don't see it. ps -fwC python or ps -fwu mailman should show all the qrunners with the commands that invoked them (including the runner name). e.g. $ ps -fwu mailman UIDPID PPID C STIME TTY TIME CMD mailman 21122 1 0 Nov18 ?00:00:00 /usr/bin/python2.7 /usr/local/mailman/bin/mailmanctl -s -q start mailman 21123 21122 0 Nov18 ?00:00:03 /usr/bin/python2.7 /usr/local/mailman/bin/qrunner --runner=ArchRunner:0:1 -s mailman 21124 21122 0 Nov18 ?00:00:00 /usr/bin/python2.7 /usr/local/mailman/bin/qrunner --runner=BounceRunner:0:1 -s mailman 21125 21122 0 Nov18 ?00:00:00 /usr/bin/python2.7 /usr/local/mailman/bin/qrunner --runner=CommandRunner:0:1 -s mailman 21126 21122 0 Nov18 ?00:00:00 /usr/bin/python2.7 /usr/local/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s mailman 21127 21122 0 Nov18 ?00:00:00 /usr/bin/python2.7 /usr/local/mailman/bin/qrunner --runner=NewsRunner:0:1 -s mailman 21128 21122 0 Nov18 ?00:00:08 /usr/bin/python2.7 /usr/local/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s mailman 21129 21122 0 Nov18 ?00:00:00 /usr/bin/python2.7 /usr/local/mailman/bin/qrunner --runner=VirginRunner:0:1 -s mailman 21130 21122 0 Nov18 ?00:00:00 /usr/bin/python2.7 /usr/local/mailman/bin/qrunner --runner=RetryRunner:0:1 -s If BounceRunner isn't running (since 11/13?) that would explain a lot. Here is an entry in the qrunner log related to BounceRunner: Nov 19 04:02:36 2012 (29791) Master qrunner detected subprocess exit (pid: 27168, sig: None, sts: 2, class: BounceRunner, slice: 1/1) [restarting] What happens daily at 04:02? Check your cron logs or /etc/cron.daily sts: 2 could be a missing file or directory, but there should be an entry in Mailman's error log from the same time. Are there queued bounces in the bounces queue (Mailman's qfiles/bounces/ or wherever your package puts it (e.g. /var/spool/mailman/bounces in the RedHat/CentOS package). -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Christopher Adams adam...@gmail.com -- 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] problems with bounce processing
Hello, I am having some problems with bounce processing working correctly. If I set a list so that a max bounce score 1 ( .1 in this case). So, the expectation is that the subscriber's account will immediately be tagged as 'No Mail by Bounce (B). That is not happening. In addition, the bounce logs are quite a bit leaner than I would expect and the bounces don't seem to be showing up there. Can someone point me in the right direction? I have checked the cron and list settings and can't seem to resolve this. Stale users are not being marked disabled and are not getting unsubscribed. -- Christopher Adams adam...@gmail.com -- 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
Re: [Mailman-Users] problems with bounce processing
Mark, Here is a log that shows a message sent to the 'test7' list. The list is set up for bounce processing and all notifications are set to 'yes'. This is happening with the entire system, not just individual lists. It doesn't seem to be processing bounces. The bounce.log,which rotated at 4 am this morning, is currently empty. The mailman.cron has an entry that sends messages to disabled subscribers at 9 am every day. Looking at some older bounce logs, it appears that a few entries for bounce score appear, but not as many as I would expect. Additionally, nobody is being tagged as (B) bounce in the membership list. Nov 19 11:58:26 swiki postfix/local[17412]: 270961998422: to= te...@mydomain.com, relay=local, delay=0.15, delays=0.05/0/0/0.1, dsn=2.0.0, status=sent (delivered to command: /usr/local/mailman/mail/mailman post test7) Nov 19 11:58:27 swiki postfix/qmgr[6381]: 824501998422: from= test7-boun...@mydomain.com, size=5830, nrcpt=1 (queue active) Nov 19 11:58:27 swiki postfix/qmgr[6381]: 852721998424: from= test7-boun...@mydomain.com, size=5798, nrcpt=3 (queue active) Nov 19 11:58:31 swiki postfix/local[17411]: 9E66A1998437: to= test7-boun...@mydomain.com, relay=local, delay=0.2, delays=0.02/0/0/0.18, dsn=2.0.0, status=sent (delivered to command: /usr/local/mailman/mail/mailman bounces test7) On Tue, Nov 19, 2013 at 12:20 PM, Mark Sapiro m...@msapiro.net wrote: On 11/19/2013 11:26 AM, Christopher Adams wrote: I am having some problems with bounce processing working correctly. If I set a list so that a max bounce score 1 ( .1 in this case). So, the expectation is that the subscriber's account will immediately be tagged as 'No Mail by Bounce (B). That is not happening. It should work. The first bounce should disable delivery by bounce. You can also set bounce_score_threshold to 0, but .1 should do the same thing. Is bounce_processing set to Yes for the list? Are all the notifications set to Yes? In addition, the bounce logs are quite a bit leaner than I would expect and the bounces don't seem to be showing up there. What do you see in the MTA logs for mail which bounces? Can someone point me in the right direction? I have checked the cron and list settings and can't seem to resolve this. Stale users are not being marked disabled and are not getting unsubscribed. Ultimate unsubscription, assuming bounce_you_are_disabled_warnings is greater than 0 depends on cron/disabled, but if delivery is not being disabled by bounce, then removal won't occur. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org 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/adamsca%40gmail.com -- Christopher Adams adam...@gmail.com -- 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
Re: [Mailman-Users] problems with bounce processing
There is no bounce score entry in the bounce log for that post, or for probably any posts. There is nothing in the error log about bounces. The only entry in the qrunner related to BounceRunner is at 4:02 am every day: Nov 19 04:02:36 2012 (29791) Master qrunner detected subprocess exit (pid: 27168, sig: None, sts: 2, class: BounceRunner, slice: 1/1) [restarting] On Tue, Nov 19, 2013 at 1:25 PM, Mark Sapiro m...@msapiro.net wrote: On 11/19/2013 12:59 PM, Christopher Adams wrote: Looking at some older bounce logs, it appears that a few entries for bounce score appear, but not as many as I would expect. Additionally, nobody is being tagged as (B) bounce in the membership list. If there is a bounce score entry in the bounce log and the score exceeds threshold, the member should be disabled. Nov 19 11:58:31 swiki postfix/local[17411]: 9E66A1998437: to=test7-boun...@mydomain.com mailto:test7-boun...@mydomain.com, relay=local, delay=0.2, delays=0.02/0/0/0.18, dsn=2.0.0, status=sent (delivered to command: /usr/local/mailman/mail/mailman bounces test7) This should result in a bounce log entry. Is BounceRunner running? Is there anything in Mailman's error log relating to bounces? What's in Mailman's qrunner log relating to BounceRunner? -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Christopher Adams adam...@gmail.com -- 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
Re: [Mailman-Users] problems with bounce processing
There is no bounce score entry in the bounce log. As it turns out, there has not been a bounce log generated since 11/13. Would BounceRunner show in a list of processes. If so, I don't see it. Here is an entry in the qrunner log related to BounceRunner: Nov 19 04:02:36 2012 (29791) Master qrunner detected subprocess exit (pid: 27168, sig: None, sts: 2, class: BounceRunner, slice: 1/1) [restarting] /Bounce 1973,40 4 On Tue, Nov 19, 2013 at 1:25 PM, Mark Sapiro m...@msapiro.net wrote: On 11/19/2013 12:59 PM, Christopher Adams wrote: Looking at some older bounce logs, it appears that a few entries for bounce score appear, but not as many as I would expect. Additionally, nobody is being tagged as (B) bounce in the membership list. If there is a bounce score entry in the bounce log and the score exceeds threshold, the member should be disabled. Nov 19 11:58:31 swiki postfix/local[17411]: 9E66A1998437: to=test7-boun...@mydomain.com mailto:test7-boun...@mydomain.com, relay=local, delay=0.2, delays=0.02/0/0/0.18, dsn=2.0.0, status=sent (delivered to command: /usr/local/mailman/mail/mailman bounces test7) This should result in a bounce log entry. Is BounceRunner running? Is there anything in Mailman's error log relating to bounces? What's in Mailman's qrunner log relating to BounceRunner? -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Christopher Adams adam...@gmail.com -- 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
Re: [Mailman-Users] (no subject)
Thank you for your reply. QRUNNER_SLEEP_TIME = seconds(1) in Defaults.py Mesages are being archived almost immediately. There is nothing in the in/ queue. There currently are about 954 files in the out/ queue and seemingly always growing. Is that significant? A message sent yesterday at 12:30 was received by Mailman within seconds. It delivered at 3:30. The smtp.log for that message shows: May 13 15:32:36 2013 (26531) 0b03fe68e0e760478d413f045b39a02838032...@oslexchange.my.mail.server.local smtp to test7 for 2 recips, completed in 0.020 seconds On Mon, May 13, 2013 at 9:03 PM, Mark Sapiro m...@msapiro.net wrote: On 05/13/2013 08:39 PM, Christopher Adams wrote: Postfix sends the list message it to the remote server, which shows that it was accepted by the Mailman server. We are not communicating here. The above makes no sense to me. I think the sequence is: - List mail arrives at the local Postfix. - Postfix delivers to the local Mailman. - Mailman delivers - here I don't know if to the local Postfix for relay to the remote server or directly to the remote server. The mm_cfg.py setting for SMTPHOST determines this. The Default is localhost meaning relay via the local Postfix. The Mailman server has logs that show that the message was directed to the command 'post' to list 'test7'. However, nothing happens after that for 2-7 hours. Once it actually sends to the list, there are smpt.log entries that show it going to 'x recipients' OK, so here you are saying that the delay is definitely in Mailman. I.e. Postfix delivers to the mailman mail wrapper which presumably immediately queues the message in Mailman's in/ queue, and it's a long time later that Mailman logs the delivery. What is the processing time in the smtp log entry. Is it a few seconds or less or hours? I'm guessing that during this time IncomingRunner or OutgoingRunner or both are asleep. Do you have a setting in mm_cfg.py for QRUNNER_SLEEP_TIME? The default in Defaults.py is (or should be) QRUNNER_SLEEP_TIME = seconds(1) If you have set this to a few hours, it would explain the behavior you are seeing. If not, when does the post get archived? Is that delayed too? Also, messages in the in/ queue are processed by IncomingRunner and then queued in the archive/ queue for ArchRunner and the out/ queue for OutgoingRunner. You could look and see if messages move from the in/ queue quickly or not. Note that if you have set QRUNNER_SLEEP_TIME to say 4 hours, messages can sit in the in/ queue for an average of 2 and up to 4 hours before moving to the out/ queue where they may wait up to an additional 4 hours before being sent. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Christopher Adams adam...@gmail.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] (no subject)
Mark, I was reading some previous posts about Mailman and qfiles. Late yesterday, I found a couple of *.bak files in the out/ queue, so I moved all the *.bak and *.pck files to another directory. I restarted Mailman. Mail was not still not being delivered in a timely way. Then, this morning, I read another post about dns lookups in Postfix main.cf. A poster said that he modifed his smtpd_recipient_restrictions and put permit_mynetworks at the top. So, I followed this and restarted Postfix. I immediately saw mail flowing and the out/q queue emptied and mail began to come in. I'm not sure exactly why it had that affect. So, I have a final question. Should I move the .pck and .bak (renamed to .pck) files back to the out/ queue. If so, should I stop mailman before doing this. BTW - The posts that I read above involved you. so thanks for the indirect assistance. On Tue, May 14, 2013 at 8:26 AM, Christopher Adams adam...@gmail.comwrote: Thank you for your reply. QRUNNER_SLEEP_TIME = seconds(1) in Defaults.py Mesages are being archived almost immediately. There is nothing in the in/ queue. There currently are about 954 files in the out/ queue and seemingly always growing. Is that significant? A message sent yesterday at 12:30 was received by Mailman within seconds. It delivered at 3:30. The smtp.log for that message shows: May 13 15:32:36 2013 (26531) 0b03fe68e0e760478d413f045b39a02838032...@oslexchange.my.mail.server.local smtp to test7 for 2 recips, completed in 0.020 seconds On Mon, May 13, 2013 at 9:03 PM, Mark Sapiro m...@msapiro.net wrote: On 05/13/2013 08:39 PM, Christopher Adams wrote: Postfix sends the list message it to the remote server, which shows that it was accepted by the Mailman server. We are not communicating here. The above makes no sense to me. I think the sequence is: - List mail arrives at the local Postfix. - Postfix delivers to the local Mailman. - Mailman delivers - here I don't know if to the local Postfix for relay to the remote server or directly to the remote server. The mm_cfg.py setting for SMTPHOST determines this. The Default is localhost meaning relay via the local Postfix. The Mailman server has logs that show that the message was directed to the command 'post' to list 'test7'. However, nothing happens after that for 2-7 hours. Once it actually sends to the list, there are smpt.log entries that show it going to 'x recipients' OK, so here you are saying that the delay is definitely in Mailman. I.e. Postfix delivers to the mailman mail wrapper which presumably immediately queues the message in Mailman's in/ queue, and it's a long time later that Mailman logs the delivery. What is the processing time in the smtp log entry. Is it a few seconds or less or hours? I'm guessing that during this time IncomingRunner or OutgoingRunner or both are asleep. Do you have a setting in mm_cfg.py for QRUNNER_SLEEP_TIME? The default in Defaults.py is (or should be) QRUNNER_SLEEP_TIME = seconds(1) If you have set this to a few hours, it would explain the behavior you are seeing. If not, when does the post get archived? Is that delayed too? Also, messages in the in/ queue are processed by IncomingRunner and then queued in the archive/ queue for ArchRunner and the out/ queue for OutgoingRunner. You could look and see if messages move from the in/ queue quickly or not. Note that if you have set QRUNNER_SLEEP_TIME to say 4 hours, messages can sit in the in/ queue for an average of 2 and up to 4 hours before moving to the out/ queue where they may wait up to an additional 4 hours before being sent. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Christopher Adams adam...@gmail.com -- Christopher Adams adam...@gmail.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] (no subject)
Thank you, Mark. SMTPHOST = 'localhost' in Defaults.py The out/ queue is now clear and processing mail. I'll see how it goes. Thanks, again. On another note, what are thoughts about utilizing SpamAssasin or other spam software with Postfix and Mailman. It seems that a lot of the traffic that is going through the Mailman server is spam, quite a bit which is flagged and blocked by using RBLS in postfix smptd_recipient_restrictions. I am seeing upwards to 8,000 messages blocked every day. Is there a more efficient way to manage this without making it a full time job? :) On Tue, May 14, 2013 at 9:43 AM, Mark Sapiro m...@msapiro.net wrote: On 05/14/2013 09:28 AM, Christopher Adams wrote: Then, this morning, I read another post about dns lookups in Postfix main.cf. A poster said that he modifed his smtpd_recipient_restrictions and put permit_mynetworks at the top. So, I followed this and restarted Postfix. I immediately saw mail flowing and the out/q queue emptied and mail began to come in. I'm not sure exactly why it had that affect. So, Mailman is delivering via the local Postfix and not directly to the remote server. Postfix was doing DNS lookups on the sending domain for all messages which slowed it way down. You avoided this by the change you made. So, I have a final question. Should I move the .pck and .bak (renamed to .pck) files back to the out/ queue. If so, should I stop mailman before doing this. You can move the .pck files back without stopping/starting Mailman. If you move the .bak files without renaming them, they won't be processed until you restart Mailman. If you rename them to .pck, they will be processed along with the others without a restart. BUT, the messages in the .bak files have been 'partially' processed and possibly delivered to some recipients. You can examine the .bak files with bin/dumpdb -p to see what they contain and decide if you want to reprocess them. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Christopher Adams adam...@gmail.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] (no subject)
Below is a log of a message sent from me. The remote server handles mail from my mail server. It is sent to the test7 mailing list address. From there, Mailman/Postfix handles the dissemination of mail. I can't figure out where it is getting hung up. Sometimes delivery takes 2-8 hours from the time it was posted. May 13 08:02:09 swiki postfix/smtpd[15145]: 692E8199849A: client=remote.mail.server[xxx.xxx.xxx.xx] May 13 08:02:09 swiki postfix/cleanup[15168]: 692E8199849A: message-id=0b03fe68e0e760478d413f045b39a02838032...@oslexchange.my.mail.server.local May 13 08:02:09 swiki postfix/qmgr[17481]: 692E8199849A: from=prvs=1845613428=my.addr...@my.mail.server, size=4112, nrcpt=1 (queue active) May 13 08:02:09 swiki postfix/local[15169]: 692E8199849A: to= te...@mailmanserver.com, relay=local, delay=0.13, delays=0.02/0/0/0.1, dsn=2.0.0, status=sent (delivered to command: /usr/local/mailman/mail/mailman post test7) May 13 08:02:09 swiki postfix/qmgr[17481]: 692E8199849A: removed On Thu, May 9, 2013 at 3:23 PM, Mark Sapiro m...@msapiro.net wrote: On 05/09/2013 01:30 PM, Christopher Adams wrote: At 12 noon, messages that had been sent but not delivered earlier today, suddenly were all sent. This sure seems like a cron (not a con) job, but I haven't a clue why. As far as I know the only Mailman cron job that runs at 12 noon is the digest generation. I am really puzzled here. This may be a Postfix/MTA issue, maybe a local server issue, but I am mainly curious about the batch send that occurred. Here is an entry from maillog. It shows a message being delivered to the alias, then removed from the queue. The message never gets to the person behind the alias. May 9 12:57:49 swiki postfix/smtpd[26679]: E774019985DC: client= nm2-vm0.bullet.mail.bf1.yahoo.com[98.139.213.127] [...] Does Mailman deliver directly to the remote server or via Postfix? If directly, what does Mailman's smtp log say about the posts that were delayed. I.e. a post to a list will have an entry like May 09 12:53:47 2013 (6114) 009b01ce4cee$e4c00540$ae400fc0$@x...@example.com smtp to LISTNAME for 237 recips, completed in 4.337 seconds which says the the message with message-id 009b01ce4cee$e4c00540$ae400fc0$@x...@example.com was delivered from the LISTNAME list to (in this case) 237 reqular subscribers and SMTP to the MTSA was completed at 12:53:47 (and started 4.337 seconds earlier). I suspect they were delivered to the remote server well before and not all at once at noon. If Mailman delivers via Postfix, what does the maillog say about those deliveries? -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Christopher Adams adam...@gmail.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] (no subject)
Postfix sends the list message it to the remote server, which shows that it was accepted by the Mailman server. The Mailman server has logs that show that the message was directed to the command 'post' to list 'test7'. However, nothing happens after that for 2-7 hours. Once it actually sends to the list, there are smpt.log entries that show it going to 'x recipients' The problem is not non-delivery but extremely slow delivery, anywhere from 2-8 hrs,even for a small list (2 subscribers) like the test7 list. The Mailman server has over 600 lists and 250,000 subscribers. Some of the lists have 40,000 subscribers. Additionally, there is quite a bit of spam being sent to the list owner addresses and other attempts at posts by spammers, many which are flagged and blocked. That is just to point out that there is a lot going on with the Mailman server. What would be some reasons for such long delays and why does it seem that they seem to be released all at the same time. If they have been handed off to Mailman,where are they held during this long delay? Are there some optimizations that could be made in mm_cfg.py and/or with Postfix? I saw some reference to some work that had already been done with this, but it appears to be from 2008. Thank for any suggestions that you might have. On Mon, May 13, 2013 at 3:57 PM, Mark Sapiro m...@msapiro.net wrote: On 05/13/2013 09:32 AM, Christopher Adams wrote: Below is a log of a message sent from me. The remote server handles mail from my mail server. It is sent to the test7 mailing list address. From there, Mailman/Postfix handles the dissemination of mail. Does Mailman send to your Postfix to relay to the remote server. If so, what are the Postfix log entries for the mail from Mailman through Postfix to the remote server? In any case, what is Mailman's smtp log entry for the post (the one for the message-id of the post)? The time stamp of the smtp log entry is the time that Mailman completed smtp delivery of the post to Postfix or the remote server as the case may be. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Christopher Adams adam...@gmail.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] (no subject)
Hello, I have posted here before about mail issues that may not be strictly a Mailman problem. However, this time there is something Mailman-related that I need to figure out. A week or so ago, a remote mail server that all of our list mail goes through used a spam vendor that had slapped a signature on our server address, so mail was being held there. i think that was resolved. After a week or so of mail successfully working, it has tailed off again. The remote mail server administrator can't identify that there is a spam problem, though Yahoo and Verizon have apparently temporaily blocked mail from our server due to the traffic. In tests, I send various mail (list traffic, subscription requests, mail directly to the listname-owner address, etc) and it reaches the server, but goes nowhere from there. At 12 noon, messages that had been sent but not delivered earlier today, suddenly were all sent. This sure seems like a cron (not a con) job, but I haven't a clue why. As far as I know the only Mailman cron job that runs at 12 noon is the digest generation. I am really puzzled here. This may be a Postfix/MTA issue, maybe a local server issue, but I am mainly curious about the batch send that occurred. Here is an entry from maillog. It shows a message being delivered to the alias, then removed from the queue. The message never gets to the person behind the alias. May 9 12:57:49 swiki postfix/smtpd[26679]: E774019985DC: client= nm2-vm0.bullet.mail.bf1.yahoo.com[98.139.213.127] May 9 12:57:50 swiki postfix/cleanup[26968]: E774019985DC: message-id= 1368129468.24511.yahoomail...@web164901.mail.bf1.yahoo.com May 9 12:57:50 swiki postfix/qmgr[23217]: E774019985DC: from=m...@yahoo.com, size=3404, nrcpt=1 (queue active) May 9 12:57:50 swiki postfix/local[27542]: E774019985DC: to= test7-ow...@mydomain.com, relay=local, delay=0.9, delays=0.74/0/0/0.16, dsn=2.0.0, status=sent (delivered to command: /usr/local/mailman/mail/mailman owner test7) May 9 12:57:50 swiki postfix/qmgr[23217]: E774019985DC: removed -- Christopher Adams adam...@gmail.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Withlist with python module to change all lists to non-advertised
I have been tasked to look into modifying all existing lists to be non-advertised. I have some knowledge of how withlist works with python. Has anyone created a module for use with python taht will accomplish this. I may have to get in and learn python again. Many thanks -- Christopher Adams adam...@gmail.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Withlist with python module to change all lists to non-advertised
Geez, that is even documented. http://wiki.list.org/pages/viewpage.action?pageId=4030597 Thanks, Mark for getting me on the right track. On Wed, May 8, 2013 at 12:57 PM, Mark Sapiro m...@msapiro.net wrote: On 5/8/2013 12:41 PM, Christopher Adams wrote: I have been tasked to look into modifying all existing lists to be non-advertised. I have some knowledge of how withlist works with python. Has anyone created a module for use with python taht will accomplish this. I may have to get in and learn python again. You don't need withlist for this, although you could do it with something as simple as def set_non_advertised(mlist): mlist.advertised = 0 All you need to do is create a one-line file containing advertised = 0 and run #! /bin/sh cd /path/to/mailman for list in `bin/list_lists --bare` ; do bin/config_list -i /path/to/file done -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/adamsca%40gmail.com -- Christopher Adams adam...@gmail.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Admin approval messages not being sent
Apparently, the central mail server does not filter spam by examining headers. It uses Fortiguard to look for identified spam and then flag IPs that send an inordinate amount of spam. Our system handles over 600 lists and 250,000 subscribers, so there is a lot of opportunities for spam to get through. The lists don't send spam, but the owner addresses are open for sending (weakness of Mailman) and for whatever reason, legitimate mail is being flagged with a hash by Fortiguard. All the Fortiguard problems aside, are there any suggested ways to harden Postfix for use withe Mailman at the volume we are using it. Maybe this is a question for the Postfix list. I have already implemented many of the configuration ideas to cut down on spam, though have not implemented an actual spam application like SpamAssassin. Many thanks, On Wed, Apr 24, 2013 at 3:42 PM, Christopher Adams adam...@gmail.comwrote: Thank you, Mark. It has been awhile, as I submitted a ticket to the provider of mail, but they have not been responding. I do thank you for the suggestion and am following up a second time with them and will post when I have a resolution. On Mon, Apr 1, 2013 at 2:40 PM, Mark Sapiro m...@msapiro.net wrote: Christopher Adams wrote: I can send mail outside of Mailman to the listname-owner address and it delivers correcty regardless of whether the list owners are inside the local subnet. The problem only seems to occur when sending through the Mailman server and Postfix. When you send mail originating outside Mailman to the listname-owner address it is ultimately delivered to Postfix from Mailman for the owner/moderator recipients in exactly the same way as a Mailman generated notice. There are a few differences in the headers of the message ultimately sent to the owner/moderator recipients and of course, the bodies are different (but you could test manually sending a copy of an actual notice). The major difference is the From: header which in the cast of the message you send has hour address and in the case of the notice has the listname-owner address. The notice also has headers like Precedence: bulk X-BeenThere: listn...@example.com X-Mailman-Version: ... List-Id: ... X-List-Administrivia: yes that probably aren't in the manually generated message. Perhaps the issue is that there is spam filtering in the local network that discards Precedence: bulk messages destined for local recipients. It is also possible that the central server that mail is routed through is not looking kindly on the admin notifications, so I will look in to that as well as problems with Postfix. Yes, particularly the Precedence: header. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Christopher Adams adam...@gmail.com -- Christopher Adams adam...@gmail.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Admin approval messages not being sent
Thank you, Mark. It has been awhile, as I submitted a ticket to the provider of mail, but they have not been responding. I do thank you for the suggestion and am following up a second time with them and will post when I have a resolution. On Mon, Apr 1, 2013 at 2:40 PM, Mark Sapiro m...@msapiro.net wrote: Christopher Adams wrote: I can send mail outside of Mailman to the listname-owner address and it delivers correcty regardless of whether the list owners are inside the local subnet. The problem only seems to occur when sending through the Mailman server and Postfix. When you send mail originating outside Mailman to the listname-owner address it is ultimately delivered to Postfix from Mailman for the owner/moderator recipients in exactly the same way as a Mailman generated notice. There are a few differences in the headers of the message ultimately sent to the owner/moderator recipients and of course, the bodies are different (but you could test manually sending a copy of an actual notice). The major difference is the From: header which in the cast of the message you send has hour address and in the case of the notice has the listname-owner address. The notice also has headers like Precedence: bulk X-BeenThere: listn...@example.com X-Mailman-Version: ... List-Id: ... X-List-Administrivia: yes that probably aren't in the manually generated message. Perhaps the issue is that there is spam filtering in the local network that discards Precedence: bulk messages destined for local recipients. It is also possible that the central server that mail is routed through is not looking kindly on the admin notifications, so I will look in to that as well as problems with Postfix. Yes, particularly the Precedence: header. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Christopher Adams adam...@gmail.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Admin approval messages not being sent
I see the message in the Mailman smtp log going to the list and the two list owners. I also see the message directed to the list owner address in the MTA logs. However, the message is not actually being delivered to the list owner via the alias. I have discovered that, using owner addresses outside of our subnet work for getting confirmation approvals. However, they don't for addresses inside our subnet. That is strange because the owner addresses are deliverable and receive mail through list traffic via Mailman. On Thu, Mar 28, 2013 at 5:25 PM, Mark Sapiro m...@msapiro.net wrote: Christopher Adams wrote: On Thu, Mar 28, 2013 at 1:10 PM, Mark Sapiro m...@msapiro.net wrote: Are you saying that you see a 'held subscription' message in Mailman's 'vette' log? Yes, it shows in the vette.log as being held. Do the held subscriptions appear in the web admindb interface? The list has the *admin_immed_notify* set to 'yes'. The cron /cron/checkdbs runs every morning at 8 am. Does the held subscription appear in the daily summary of moderator requests? Yes, it is sent successfully every morning at 8 am. Until I get this fixed, I have increased this to every 2 hrs. The notice to the owner(s)/moderator(s) is sent by the same process immediately following writing the vette log entry contingent only on admin_immed_notify being True. The message is sent From: and To: the listname-owner address with envelope from the listname-bounces address. Check Mailman's smtp log for entries with the same or perhaps + 1 or 2 seconds time stamp as the vette log entry. There should be a send for 1 recip for the list followed immediately by a send for a number of recips = to the number of owner(s)/moderator(s). Do you see these? How about in the MTA logs? -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Christopher Adams adam...@gmail.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Admin approval messages not being sent
I did not mean to imply that there was a connection between the owners and list posts, just that Mailman list traffic is flowing without problems. Your assumptions 1-3 are correct. As for #4, if I understand you correctly, I can send mail outside of Mailman to the listname-owner address and it delivers correcty regardless of whether the list owners are inside the local subnet. The problem only seems to occur when sending through the Mailman server and Postfix. I have been considering that Postfix is the possible problem, but since list traffic is working fine, I don't know exactly what to address with the MTA. The 'inside' addresses are fully qualified. It is also possible that the central server that mail is routed through is not looking kindly on the admin notifications, so I will look in to that as well as problems with Postfix. Thank you for taking time to reply. On Mon, Apr 1, 2013 at 9:58 AM, Mark Sapiro m...@msapiro.net wrote: On 4/1/2013 8:22 AM, Christopher Adams wrote: I see the message in the Mailman smtp log going to the list and the two list owners. I also see the message directed to the list owner address in the MTA logs. However, the message is not actually being delivered to the list owner via the alias. I have discovered that, using owner addresses outside of our subnet work for getting confirmation approvals. However, they don't for addresses inside our subnet. This is what I think I understand from the above. 1) The notice is sent as expected by Mailman to LISTNAME-owner@... 2) The message to LISTNAME-owner@... is received by Mailman and resent by Mailman to all the owner and moderator addresses. 3) Those owner and moderator addresses outside your local subnet receive the notice, but those inside your local subnet do not. 4) Presumably, the same is true for any mail sent to the LISTNAME-owner@... address, i.e., the non-delivery issue does not depend on the mail to LISTNAME-owner@... having been generated by Mailman itself. Is this understanding correct? Do the 'inside' owner/moderator addresses have a fully qualified domain name? That is strange because the owner addresses are deliverable and receive mail through list traffic via Mailman. Owners and moderators do not receive list posts. Only members receive list posts. There is no connection within Mailman between an owner/moderator address and a list member address which may be the same. See http://wiki.list.org/x/5YA9. In any case, if my understanding above is correct, and if the owner/moderator 'inside' addresses are fully qualified, this is an MTA issue, not a Mailman issue. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Christopher Adams adam...@gmail.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Admin approval messages not being sent
Hello, Confirmation messages sent to users are being sent successfully. Messages intended as approval for subscriptions and sent to the list administrators are not being sent. They appear as 'held subscription' in the mail logs. The list has the *admin_immed_notify* set to 'yes'. The cron /cron/checkdbs runs every morning at 8 am. I have read of possible Handler exceptions in Mailman, but the error logs don't show anything. What else could I look for to diagnose this problem? Thank you. -- Christopher Adams adam...@gmail.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Admin approval messages not being sent
On Thu, Mar 28, 2013 at 1:10 PM, Mark Sapiro m...@msapiro.net wrote: Christopher Adams wrote: Confirmation messages sent to users are being sent successfully. Messages intended as approval for subscriptions and sent to the list administrators are not being sent. They appear as 'held subscription' in the mail logs. Are you saying that you see a 'held subscription' message in Mailman's 'vette' log? Yes, it shows in the vette.log as being held. Do the held subscriptions appear in the web admindb interface? The list has the *admin_immed_notify* set to 'yes'. The cron /cron/checkdbs runs every morning at 8 am. Does the held subscription appear in the daily summary of moderator requests? Yes, it is sent successfully every morning at 8 am. Until I get this fixed, I have increased this to every 2 hrs. Is the listname-owner address deliverable? Is mail to that address delivered to the list's owner and moderator addresses? Yes, I can send directly to the list owner address and to the actual person's address. -- Christopher Adams adam...@gmail.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] upgrade path from 2.1.13 to 2.1.15
Hello, I am finally getting around to to upgrading Mailman 2.1.13. Should I upgrade to 2.1.14 and then upgrade to 2.1.15, or just go directly to 2.1.15? It sounds like 2.1.15 changes some files significantly, but the process remains the same. Basically, do as if installing mailman initially, using all parameters that were previously used. Am I correct in my assumptions and is there anything else that I should know. based on what others experiences when upgrading. Many thanks, -- Christopher Adams adam...@gmail.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] non-digest member received message in digest format
Hello all, This particular issue has me perplexed. I had a call from a user who is subscribed to a list in regular/non-digest mode. He received a message in digest mode, a day later than when it was sent, which is what should happen with digests. However, as I said, he is not on digest. I checked logs and his status hasn't changed in the last 30 days. Others on the list received it yesterday. What might be going on here? -- Christopher Adams adam...@gmail.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] question about harvesting of non-archived lists by archiveorange.com
Hello all, A list owner of one of our 500+ mailing lists notified me that postings from their non-archived list was being harvested by archiveorange.com and could be found via Google. I found that many of our lists are archived on this site, and this is not something that we really want. I am just querying the list to see if this has happened with others using Mailman. The website explains that archiveorange subscribes to lists and then harvests messages. It seems that the only way this could happen to a non-archived list is for the mailbox directories to readable to the outside. Is there something else that is going on here? Thanks for any information that anyone has to offer. -- Christopher Adams adam...@gmail.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Outlook and priority messages to Mailman
Hello, If an individual sends a priority message via Outlook to a Mailman list, does it assume that it is a bcc? I was able to verify that the person sent the message directly to the list, but the message was sent to the administrator with the implicit destination tag. I realize that I can control this behavior at the list or system level, but just looking for verification of this behavior. Thanks. -- Christopher Adams adam...@gmail.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] question about logging subscription changes
I think that the answer is 'no', but I thought I would check. Do any of the mailman log files show when a subscription is changed from a regular subscription to digest? I have parsed the logs and can't find evidence of this. -- Christopher Adams adam...@gmail.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] unsubscribing addresses from domain in one fellswoop?
Thanks, Mark. I was just starting to construct a script, but yours is much more streamlined and works just fine. Thanks. Anyone else dealing with zeusmail.org ? On Mon, Jan 4, 2010 at 5:25 PM, Mark Sapiro m...@msapiro.net wrote: Christopher Adams wrote: A spammer has subscribed completely unique addresses from the same domain to many of the mailing lists that we host. Is there a way to unsubscribe everything from this domain without writing a script that will do it? If you mean 'automatically' as opposed to just manually going through the lists and unsubscribing addresses, no. However, there are lots of very simple scripts. Consider #!/bin/sh for list in `bin/list_lists --bare`; do bin/list_members $list | grep example.com | \ bin/remove_members -f - -n -N $list done where example.com is the domain. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Christopher Adams adam...@gmail.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] unsubscribing addresses from domain in one fell swoop?
We host over 600 lists and have about 250,000 subscribers. List owners have been asking me about how particular subscribers were able to subscribe to their lists. Well, in some cases, the list had open subscription. However, in almost all cases, the subscribers were from zeusmail.org. I did a scan of the subscribe logs and found over 800 subscribed addresses using zeusmail.org domain. Interestingly, all subscriptions come from the same IP address. Looking at the addresses, it is obvious that they are bogus, though they are interesting and rather humorous names that when all are put together, show a pattern of automated subscriptions. I checked the post logs and found that none from that domain had posted. So, I have done a couple of things. 1) blocked the ip at the firewall, 2) created a Postfix filter to not allow that domain to be able to send through the mail server, 3) added a robots.txt file to specifically block that domain, and 4) unsubscribed all zeusmail.org subscribers using the script Mark provided. It seems that zeusmail.org is a legitimate and non-blacklisted domain, but it just reeks of spammers. If there is a problem with the few that may be legitimate, they can easily be reinstated. On Mon, Jan 4, 2010 at 4:34 PM, Christopher Adams adam...@gmail.com wrote: A spammer has subscribed completely unique addresses from the same domain to many of the mailing lists that we host. Is there a way to unsubscribe everything from this domain without writing a script that will do it? -- Christopher Adams adam...@gmail.com -- Christopher Adams adam...@gmail.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] unsubscribing addresses from domain in one fell swoop?
A spammer has subscribed completely unique addresses from the same domain to many of the mailing lists that we host. Is there a way to unsubscribe everything from this domain without writing a script that will do it? -- Christopher Adams adam...@gmail.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Mailman current version?
I have been using Mailman 2.1.12 for awhile now and am migrating to a different server. When I looked on the website, I found two sources for the Mailman package, Launchpad and Gnu. It says that Gnu tends to lag behind in versions available. In Launchpad, it says the current version is 3.0.0a3 and Gnu has 2.1.12. I am pretty sure that the latter is the most current stable version and I have not seen any posts about a new version, so? I just want to verify this before moving forward with the migration. -- Christopher Adams adam...@gmail.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] bug error when subscribing through web afterMailman 2.1.12 upgrade
Mark,
The modification to MailList.py is something that you suggested awhile
back and I had carried it through as Mailman was upgraded. Here is the
thread from 2005.
http://mail.python.org/pipermail/mailman-users/2005-January/042116.html
This time, it didn't seem to work and broke it.The problem was the
email sent to new list owners had the list address, but didn't
complete the actual address. Instead, it results in this:
Send list messages to:
%(emailaddr)s
What is the actual solutilon to the template being populated with the
actual list address. This seems like something that would be assumed
to exist in an out of the box installation.
Thanks again for your help. I have removed the modifications and it is
working correctly again.
Christopher Adams
On Wed, Jul 22, 2009 at 5:50 PM, Mark Sapirom...@msapiro.net wrote:
Christopher Adams wrote:
Since upgrading to version 2.1.12, I have experienced a number of
errors that have resulted in a You've Hit a Bug. So far, I have been
able to patch things up. The latest occurs when a user attempts to
subscribe from the web. Here is the error log information:
admin(9559): [- Mailman Version: 2.1.12 -]
admin(9559): [- Traceback --]
admin(9559): Traceback (most recent call last):
admin(9559): Â File /usr/local/mailman/scripts/driver, line 112, in run_main
admin(9559): Â Â main()
admin(9559): Â File /usr/local/mailman/Mailman/Cgi/subscribe.py,
line 97, in main
admin(9559): Â Â process_form(mlist, doc, cgidata, language)
admin(9559): Â File /usr/local/mailman/Mailman/Cgi/subscribe.py,
line 177, in process_form
admin(9559): Â Â mlist.AddMember(userdesc, remote)
Here in the traceback, the subscribe CGI is calling the list object's
AddMember method to add the member
admin(9559): Â File /usr/local/mailman/Mailman/MailList.py, line
894, in AddMember
admin(9559): Â Â listinfo_url = self.getScriptUrl('listinfo', absolute=1)
Then within the AddMember method in
/usr/local/mailman/Mailman/MailList.py, the above line calls the
list's getScriptUrl method which triggers the exception below saying
the list object has no getScriptUrl method.
There are two things seriously wrong here:
1) In the 2.1.12 released MailList.py, there is no line containing the
name 'listinfo_url' anywhere in the module
2) the 'getScriptUrl' list method doesn't exist, thus the exception.
The method's name is 'GetScriptURL'.
admin(9559): Â File /usr/local/mailman/Mailman/MailList.py, line
146, in __getattr__
admin(9559): Â Â raise AttributeError, name
admin(9559): AttributeError: getScriptUrl
So, the question here is where did this MailList.py module come from?
Is this a source install or a package? Did you modify it in any way?
It is clearly not an unmodified source distribution, and it is clearly
broken.
--
Mark Sapiro m...@msapiro.net     The highway is for gamblers,
San Francisco Bay Area, California   better use your sense - B. Dylan
--
Christopher Adams
adam...@gmail.com
--
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
Re: [Mailman-Users] bug error when subscribing through webafterMailman 2.1.12 upgrade
Mark,
Yes, you are correct. I realized that I was referring to the wrong fix
after sending my message. I certainly didn't want to insinuate that
you gave me bad information.
That aside, the question still stands. Why are these fixes needed to
force the templates to display as it seems they should be default?
What about a list adminstrator who doesn't have full run of the system
to make these fixes? An administrator who does have full run would
have to know some python and understand the way Mailman works on the
backend. I guess that is the hope for an adminstrator, isn't it?
On Thu, Jul 23, 2009 at 7:39 AM, Mark Sapirom...@msapiro.net wrote:
Christopher Adams wrote:
The modification to MailList.py is something that you suggested awhile
back and I had carried it through as Mailman was upgraded. Here is the
thread from 2005.
http://mail.python.org/pipermail/mailman-users/2005-January/042116.html
This time, it didn't seem to work and broke it.The problem was the
email sent to new list owners had the list address, but didn't
complete the actual address. Instead, it results in this:
Send list messages to:
 %(emailaddr)s
What is the actual solutilon to the template being populated with the
actual list address. This seems like something that would be assumed
to exist in an out of the box installation.
The problem with the modification is my fault. I said to add
     listinfo_url = self.getScriptUrl('listinfo', absolute=1)
but this is wrong. It needs to be
     listinfo_url = self.GetScriptURL('listinfo', absolute=1)
However, this has nothing to do with the mail sent to the owner of a
new list. This particular modification was to add a definition of
'listinfo_url' to the substitutions in the verify.txt template for the
confirmation message sent to someone subscribing when the policy
includes 'confirm'. The same modification is also required when the
verify.txt template is used for an address change confirmation.
Adding %(emailaddr)s to the newlist.txt template requires a different
modification to MailList.py.
--
Mark Sapiro m...@msapiro.net     The highway is for gamblers,
San Francisco Bay Area, California   better use your sense - B. Dylan
--
Christopher Adams
adam...@gmail.com
--
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] bug error when subscribing through web after Mailman 2.1.12 upgrade
Since upgrading to version 2.1.12, I have experienced a number of
errors that have resulted in a You've Hit a Bug. So far, I have been
able to patch things up. The latest occurs when a user attempts to
subscribe from the web. Here is the error log information:
admin(9559): [- Mailman Version: 2.1.12 -]
admin(9559): [- Traceback --]
admin(9559): Traceback (most recent call last):
admin(9559): File /usr/local/mailman/scripts/driver, line 112, in run_main
admin(9559): main()
admin(9559): File /usr/local/mailman/Mailman/Cgi/subscribe.py,
line 97, in main
admin(9559): process_form(mlist, doc, cgidata, language)
admin(9559): File /usr/local/mailman/Mailman/Cgi/subscribe.py,
line 177, in process_form
admin(9559): mlist.AddMember(userdesc, remote)
admin(9559): File /usr/local/mailman/Mailman/MailList.py, line
894, in AddMember
admin(9559): listinfo_url = self.getScriptUrl('listinfo', absolute=1)
admin(9559): File /usr/local/mailman/Mailman/MailList.py, line
146, in __getattr__
admin(9559): raise AttributeError, name
admin(9559): AttributeError: getScriptUrl
admin(9559): [- Python Information -]
admin(9559): sys.version = 2.5 (r25:51908, Jul 17 2007, 11:25:13)
[GCC 3.2.3 20030502 (Red Hat Linux 3.2.3-20)]
admin(9559): sys.executable = /usr/local/bin/python
admin(9559): sys.prefix = /usr/local
admin(9559): sys.exec_prefix = /usr/local
admin(9559): sys.path= /usr/local
admin(9559): sys.platform= linux2
admin(9559): [- Environment Variables -]
admin(9559):HTTP_COOKIE:
orcollabproj+admin=280200693832674a7328006539623134333835346134333539303563353163393335636564306366643338663533326234;
ei-news+admin=28020069243a674a7328006231373565303562646534656339393734613530616437643337656231663631393734306233;
ola2010+admin=28020069953a674a73280064373236653737626132383038653838313930646234616662643139343531383334653536353764;
orshots+admin=280200694e3c674a73280035383661646366366230653064346432666536643064353263386631366366336665666164613539;
test7+admin=28020069c83f674a73280037663466353036643030353334346437643332316233636430393266326534633038373935306661
admin(9559):SERVER_SOFTWARE: Apache/2.2.4 (Unix)
admin(9559):SCRIPT_NAME: /mailman/subscribe
admin(9559):SERVER_SIGNATURE:
admin(9559):REQUEST_METHOD: POST
admin(9559):HTTP_KEEP_ALIVE: 300
admin(9559):SERVER_PROTOCOL: HTTP/1.1
admin(9559):QUERY_STRING:
admin(9559):CONTENT_LENGTH: 101
admin(9559):HTTP_ACCEPT_CHARSET: ISO-8859-1,utf-8;q=0.7,*;q=0.7
admin(9559):HTTP_USER_AGENT: Mozilla/5.0 (Windows; U; Windows NT
5.1; en-US; rv:1.9.0.11) Gecko/2009060215 Firefox/3.0.11
admin(9559):HTTP_CONNECTION: keep-alive
admin(9559):HTTP_REFERER:
http://listsmart.osl.state.or.us/mailman/listinfo/test7
admin(9559):SERVER_NAME: listsmart.osl.state.or.us
admin(9559):REMOTE_ADDR: 159.121.122.135
admin(9559):PATH_TRANSLATED: /usr/local/apache2/htdocs/test7
admin(9559):SERVER_PORT: 80
admin(9559):SERVER_ADDR: 159.121.122.233
admin(9559):DOCUMENT_ROOT: /usr/local/apache2/htdocs
admin(9559):PYTHONPATH: /usr/local/mailman
admin(9559):SCRIPT_FILENAME: /usr/local/mailman/cgi-bin/subscribe
admin(9559):SERVER_ADMIN: r...@swiki.osl.state.or.us
admin(9559):HTTP_HOST: listsmart.osl.state.or.us
admin(9559):REQUEST_URI: /mailman/subscribe/test7
admin(9559):HTTP_ACCEPT:
text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
admin(9559):GATEWAY_INTERFACE: CGI/1.1
admin(9559):REMOTE_PORT: 1638
admin(9559):HTTP_ACCEPT_LANGUAGE: en-us,en;q=0.5
admin(9559):CONTENT_TYPE: application/x-www-form-urlencoded
admin(9559):HTTP_ACCEPT_ENCODING: gzip,deflate
admin(9559):PATH_INFO: /test7
--
Christopher Adams
adam...@gmail.com
--
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
Re: [Mailman-Users] digests/Python/2.1.12 upgrade
Mark, From crontab.in : # # Noon, mail digests for lists that do periodic as well as threshhold delivery. 0 12 * * * /usr/local/bin/python -S /usr/local/mailman/cron/senddigests # This invokes version 2.5. From senddigests: #! /usr/local/bin/python This invokes version 2.5 As for /usr/local/mailman/pythonlib/lib/python2.5, that does seem to be irrelevant to this. It points to some Japanese site-packages or something. I thought is was something else. On Sat, Jul 18, 2009 at 10:05 PM, Mark Sapirom...@msapiro.net wrote: Christopher Adams wrote: It says __version__ = '4.0.1' I guess my only alernative is to upgrade to 2.5.2, though I am not sure if the OS will support it. I don't know if that will help as it has the same version 4.0.1 email package. What are the python comands in Mailman's crontab and in the initial line of cron/senddigests, and what python do they invoke? You mentioned earlier I also have this in the mailman directory: /usr/local/mailman/pythonlib/lib/python2.5 That in itself is probably irrelevant, but what is that? Is it a symlink or the entire Python library or ? -- Mark Sapiro m...@msapiro.net     The highway is for gamblers, San Francisco Bay Area, California   better use your sense - B. Dylan -- Christopher Adams adam...@gmail.com -- 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] mailman-loop question
Since upgrading to Mailman 2.1.12, the system has been generating dozens of messages similar to the one below. Prior to the upgrade, I did not see these sent from mailman-loop. I checked the mailman aliases and see the entry for it: # The ultimate loop stopper address mailman-loop: /usr/local/mailman/data/owner-bounces.mbox An example of the messages: From: mailman-l...@mydomain.com; on behalf of; Mail Delivery System [mailer-dae...@mydomain.com] Subject: Staying healthy is easy Sent: 7/20/2009 10:08 AM The following recipient(s) could not be reached: joe.b...@wherever.com on 7/20/2009 10:08 AM Failed (host mail.system.com[xxx.xxx.xxx.xx] said: 550 5.1.1 joe.b...@wherever.com... User unknown (in reply to RCPT TO command)) What specifically is mailman-loop supposed to do and is this just a coincidence that I am getting them after the upgrade? I commented out the alias and restarted mailman, yet the message continue to be delivered. -- Christopher Adams adam...@gmail.com -- 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
Re: [Mailman-Users] digests/Python/2.1.12 upgrade
Mark,
Running crontab -u mailman -i just reads out crontab.in.
The edit to charset.py worked and the digests have been generated.
Thank you for your commitment to help. It really makes a big
difference to us adminstrators. I wonder why this particular
installation presented a unique problem.
Thanks again,
Christopher Adams
On Mon, Jul 20, 2009 at 6:08 PM, Mark Sapirom...@msapiro.net wrote:
Christopher Adams wrote:
From crontab.in :
What about from
crontab -u mailman -l
although it's popbably the same.
#
# Noon, mail digests for lists that do periodic as well as threshhold
delivery.
0 12 * * * /usr/local/bin/python -S /usr/local/mailman/cron/senddigests
#
This invokes version 2.5.
From senddigests:
#! /usr/local/bin/python
This invokes version 2.5
Take a look at /usr/local/lib/python2.5/email/charset.py. At around
line 196, you should see
  def __init__(self, input_charset=DEFAULT_CHARSET):
followed by 4 comment lines and
    try:
      if isinstance(input_charset, unicode):
        input_charset.encode('ascii')
      else:
        input_charset = unicode(input_charset, 'ascii')
    except UnicodeError:
      raise errors.CharsetError(input_charset)
    input_charset = input_charset.lower()
This may be a problem, although others who've had this problem with a
different email package have switched to this one and it solved the
problem. Try changing
      else:
        input_charset = unicode(input_charset, 'ascii')
to
      else:
        unicode(input_charset, 'ascii')
and then restart Mailman.
If that fixes the problem for you, I don't know why others don't have
this problem with email 4.0.1, but at least you will be OK.
--
Mark Sapiro m...@msapiro.net     The highway is for gamblers,
San Francisco Bay Area, California   better use your sense - B. Dylan
--
Christopher Adams
adam...@gmail.com
--
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] digests/Python/2.1.12 upgrade
I just upgraded to Mailman 2.1.12. I noticed that the digests are not going out. When I run the /bin/senddigests script manually, it goes through all list digest mailboxes and I get this message: List: mylistnamer: problem processing /usr/local/mailman/lists/mylistname/digest.mbox: decoding Unicode is not supported If I try to generate a specific list digest from the admin interface, it results in the You've Hit a Bug message. I have read some about possible reasons for this error and it seems to point to Python. I am running RedHat ES 3 and Python 2.5. There is a plan to move to a new server with a newer OS, but for the short-term I am wondering if this is a Python issue and if Python should be upgraded. The Mailman wiki says: It is highly recommended that you upgrade to the latest patch release of one of the following: * Python 2.4 * Python 2.5 For now, we recommend using Python 2.5.2. Can someone verify whether this is a Python issue and will an upgrade to 2.5.2 make a difference. Of course, I'm not sure Python 2.5 is really designed to run on RH ES 3, but it has been doing fine up til now. Thanks, Chriistopher Adams -- Christopher Adams adam...@gmail.com -- 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
Re: [Mailman-Users] digests/Python/2.1.12 upgrade
Mark,
If I issue the python command, I get this:
Python 2.5 (r25:51908, Jul 17 2007, 11:25:13)
[GCC 3.2.3 20030502 (Red Hat Linux 3.2.3-20)] on linux2
I also have this in the mailman directory:
/usr/local/mailman/pythonlib/lib/python2.5
From the error log:
Jul 18 13:36:37 2009 admin(29902):
admin(29902): [- Mailman Version: 2.1.12 -]
admin(29902): [- Traceback --]
admin(29902): Traceback (most recent call last):
admin(29902): File /usr/local/mailman/scripts/driver, line 112, in run_main
admin(29902): main()
admin(29902): File /usr/local/mailman/Mailman/Cgi/admin.py, line
173, in main
admin(29902): change_options(mlist, category, subcat, cgidata, doc)
admin(29902): File /usr/local/mailman/Mailman/Cgi/admin.py, line
1296, in change_options
admin(29902): gui.handleForm(mlist, category, subcat, cgidata, doc)
admin(29902): File /usr/local/mailman/Mailman/Gui/GUIBase.py, line
176, in handleForm
admin(29902): self._setValue(mlist, property, val, doc)
admin(29902): File /usr/local/mailman/Mailman/Gui/Digest.py, line
148, in _setValue
admin(29902): status = mlist.send_digest_now()
admin(29902): File /usr/local/mailman/Mailman/Digester.py, line
60, in send_digest_now
admin(29902): ToDigest.send_digests(self, mboxfp)
admin(29902): File
/usr/local/mailman/Mailman/Handlers/ToDigest.py, line 142, in
send_digests
admin(29902): send_i18n_digests(mlist, mboxfp)
admin(29902): File
/usr/local/mailman/Mailman/Handlers/ToDigest.py, line 339, in
send_i18n_digests
admin(29902): mcset = msg.get_content_charset('')
admin(29902): File /usr/local/lib/python2.5/email/message.py, line
759, in get_content_charset
admin(29902): charset = unicode(charset, 'us-ascii').encode('us-ascii')
admin(29902): TypeError: decoding Unicode is not supported
admin(29902): [- Python Information -]
admin(29902): sys.version = 2.5 (r25:51908, Jul 17 2007, 11:25:13)
[GCC 3.2.3 20030502 (Red Hat Linux 3.2.3-20)]
admin(29902): sys.executable = /usr/local/bin/python
admin(29902): sys.prefix = /usr/local
admin(29902): sys.exec_prefix = /usr/local
admin(29902): sys.path= /usr/local
admin(29902): sys.platform= linux2
admin(29902): [- Environment Variables -]
admin(29902): HTTP_COOKIE:
test7+admin=28020069602b624a73280039393136383039663362343739636134303861623336376235663537396466393436643463613665
admin(29902): SERVER_SOFTWARE: Apache/2.2.4 (Unix)
admin(29902): SCRIPT_NAME: /mailman/admin
admin(29902): SERVER_SIGNATURE:
admin(29902): REQUEST_METHOD: POST
admin(29902): HTTP_KEEP_ALIVE: 300
admin(29902): SERVER_PROTOCOL: HTTP/1.1
admin(29902): QUERY_STRING:
admin(29902): CONTENT_LENGTH: 438
admin(29902): HTTP_ACCEPT_CHARSET: ISO-8859-1,utf-8;q=0.7,*;q=0.7
admin(29902): HTTP_USER_AGENT: Mozilla/5.0 (Windows; U; Windows NT
5.1; en-US; rv:1.9.0.11) Gecko/2009060215 Firefox/3.0.11 (.NET CLR
3.5.30729)
admin(29902): HTTP_CONNECTION: keep-alive
admin(29902): HTTP_REFERER:
http://listsmart.osl.state.or.us/mailman/admin/test7/digest
admin(29902): SERVER_NAME: listsmart.osl.state.or.us
admin(29902): REMOTE_ADDR: 71.215.130.72
admin(29902): PATH_TRANSLATED: /usr/local/apache2/htdocs/test7/digest
admin(29902): SERVER_PORT: 80
admin(29902): SERVER_ADDR: 159.121.122.233
admin(29902): DOCUMENT_ROOT: /usr/local/apache2/htdocs
admin(29902): PYTHONPATH: /usr/local/mailman
admin(29902): SCRIPT_FILENAME: /usr/local/mailman/cgi-bin/admin
admin(29902): SERVER_ADMIN: r...@swiki.osl.state.or.us
admin(29902): HTTP_HOST: listsmart.osl.state.or.us
admin(29902): REQUEST_URI: /mailman/admin/test7/digest
admin(29902): HTTP_ACCEPT:
text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
admin(29902): GATEWAY_INTERFACE: CGI/1.1
admin(29902): REMOTE_PORT: 1809
admin(29902): HTTP_ACCEPT_LANGUAGE: en-us,en;q=0.5
admin(29902): CONTENT_TYPE: application/x-www-form-urlencoded
admin(29902): HTTP_ACCEPT_ENCODING: gzip,deflate
admin(29902): PATH_INFO: /test7/digest
On Sat, Jul 18, 2009 at 1:18 PM, Mark Sapirom...@msapiro.net wrote:
Christopher Adams wrote:
I just upgraded to Mailman 2.1.12. I noticed that the digests are not
going out. When I run the /bin/senddigests script manually, it goes
through all list digest mailboxes and I get this message:
List: mylistnamer: problem processing
/usr/local/mailman/lists/mylistname/digest.mbox:
decoding Unicode is not supported
If I try to generate a specific list digest from the admin interface,
it results in the You've Hit a Bug message.
I have read some about possible reasons for this error and it seems to
point to Python.
I am running RedHat ES 3 and Python 2.5. There is a plan to move to a
new server with a newer OS, but for the short-term I am wondering if
this is a Python issue and if Python should be upgraded. The Mailman
wiki says:
It is highly recommended that you upgrade to the latest patch release
Re: [Mailman-Users] digests/Python/2.1.12 upgrade
Mark, It says __version__ = '4.0.1' I guess my only alernative is to upgrade to 2.5.2, though I am not sure if the OS will support it. On Sat, Jul 18, 2009 at 2:05 PM, Mark Sapirom...@msapiro.net wrote: Christopher Adams wrote: If I issue the python command, I get this: Python 2.5 (r25:51908, Jul 17 2007, 11:25:13) [GCC 3.2.3 20030502 (Red Hat Linux 3.2.3-20)] on linux2 What do you see for the line beginning __version__ = in /usr/local/lib/python2.5/email/__init__.py The traceback appears to be the same error that I've seen with email 3.0.2. I know that Python 2.5.1 shipped with email 4.0.1, and that doesn't seem to have this issue. I'm not sure about Python 2.5. Upgrading to Python 2.5.2 has solved this issue for some people. -- Mark Sapiro m...@msapiro.net     The highway is for gamblers, San Francisco Bay Area, California   better use your sense - B. Dylan -- Christopher Adams adam...@gmail.com -- 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] digest question
I have over 700 lists on my server. Recently, a user called about not receiving a message to a list. I investigated and found that she was subscribed to the digest version of the list. I understand how digests work and have the cron set to send the digests every night at midnight. However, if I do a listing of all the lists and the time of creation of the digest.mbox, I see several dozen that are more than 1 day old, including the list in question. I know that I can generate the digest immediately from the admin interface, but I am wondering why *all* lists with digest.mbox files are not generating digests each night? -- Christopher Adams adam...@gmail.com -- 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
Re: [Mailman-Users] Detailed list of features for version 2.1.11 ?
Thanks, Mark. Yes, that was the page I was accessing it from. On Thu, Dec 4, 2008 at 2:00 PM, Mark Sapiro [EMAIL PROTECTED] wrote: Christopher Adams wrote: This link leads to an error. Is there another source for this information? http://cvs.sourceforge.net/viewcvs.py/mailman/mailman/NEWS?only_with_tag=Release_2_1-maint I assume you found that link at http://www.list.org/features.html or one of the mirrors. Sorry about that. I'll get it fixed. The correct link is http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/annotate/head:/NEWS. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Christopher Adams [EMAIL PROTECTED] -- 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] Detailed list of features for version 2.1.11 ?
This link leads to an error. Is there another source for this information? http://cvs.sourceforge.net/viewcvs.py/mailman/mailman/NEWS?only_with_tag=Release_2_1-maint -- Christopher Adams [EMAIL PROTECTED] -- 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] question about recurring gate_news command
I looked through the list archives and didn't see where this issue was resolved. My cron log show a recurring (every 5 minutes) entry like this: Aug 4 11:20:00 swiki CROND[21998]: (mailman) CMD (/usr/local/bin/python -S /usr/local/mailman/cron/gate_news) Can someone suggest a fix? -- Christopher Adams [EMAIL PROTECTED] -- 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
Re: [Mailman-Users] question about recurring gate_news command
Thanks to all. I was concerned because I hadn't seen so many log entries before from gate_news. Does this likely mean that a list was configured to run the mail-news gateway or has it been running like that all along? Anyway, I hadcommented out the entry in the crontab.in previously, but I didn't think to re-run the crontab command to update it. It seems to have stopped now. On Mon, Aug 4, 2008 at 2:00 PM, Mark Sapiro [EMAIL PROTECTED] wrote: Terri Oda wrote: Are you actually trying to update a news server? Because if you're not, you should probably turn off the mail-news gateway for your lists. I think it's obvious on the options page. That won't stop the cron running every 5 minutes. The only way to do that is to edit Mailman's crontab. If you are not actually gating from a newsgroup to a list (and never plan to), you don't need to run cron/gate_news and you can comment it out in the crontab. Gating from a list to a newsgroup is triggered by the post and cron/gate_news is not involved. cron/gate_news polls the newsgroups accociated with lists that have gateway_to_mail set to Yes. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Christopher Adams [EMAIL PROTECTED] -- 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] question about Nomail in admin
I recently noticed an address on a list and there is a checkmark and a ? (question mark) in the Nomail column. I understand what that means and the longer description is: Note: your list delivery is currently disabled; it was disabled for unknown reasons Fine, but I know for a fact that this particular address hasn't existed for several years. So, why hasn't it been disabled and unsubscribed? The bounce settings for this list are 5.0, 7, 3, 7. I looked through the logs and see no reference to this address. What could be happening? -- Christopher Adams [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] problem with subscription confirmation string
Yes, that is the exact string that is in the To: header of the reply. On Wed, Jun 4, 2008 at 9:01 AM, Mark Sapiro [EMAIL PROTECTED] wrote: Christopher Adams [EMAIL PROTECTED] Date: Wed, 4 Jun 2008 08:31:21 -0700 To: mailman-users@python.org I have previously had problems with this and since moving to a new server, it doesn't seem to work quite right. I use Postfix. In my Postfix main.cf, I have a line: recipient_delimiter = + In mm_cfg.py, I have this line: VERP_CONFIRMATIONS = Yes If I send a message to test7-request and add the word 'subscribe', I get a message back like this: From: [EMAIL PROTECTED]; on behalf of; [EMAIL PROTECTED][EMAIL PROTECTED] [EMAIL PROTECTED][EMAIL PROTECTED] This is almost certainly a Microsoft Outlook issue. What exact address does Outlook put in the To: header of the reply? It should be To: [EMAIL PROTECTED][EMAIL PROTECTED] in this case. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Christopher Adams [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] another question about invitation confirmationsubject line/VERP
Thanks to all for the plethora of information about VERP and how it is used by the MTAs and Mailman. Just for clarification, I don't have a list of 250,000 subscribers, just a site that has a total of 250,000 subscribers over 500+ lists. I think the largest is about 40,000. So, if all I want to do (which was my original question) is to VERP confirmations, I only have to add this to Postfix: default_verp_delimiters = += verp_delimiter_filter = -+=x and this to mm_cfgy.py: VERP_CONFIRMATIONS = Yes All other VERP setting are whatever is the default in Defaults.py. VERPing the confirmations seems to work as expectedc and I assume that there is not much of a burden on the server without VERPing every message or even VERPing a sample of messages. Thanks again for the good information. On Nov 27, 2007 8:38 PM, Brad Knowles [EMAIL PROTECTED] wrote: On 11/27/07, Mark Sapiro wrote: As a point of reference however, there are lots of lists on python.org and some are quite busy (e.g. [EMAIL PROTECTED]) and they are personalized and it seems to work OK. Brad has posted on this in the past http://mail.python.org/pipermail/mailman-users/2007-September/058231.html. I also updated FAQ 1.15 with the latest information about python.org. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq01.015.htp. -- Brad Knowles [EMAIL PROTECTED] LinkedIn Profile: http://tinyurl.com/y8kpxu -- Christopher Adams [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] another question about invitation confirmation subject line/VERP
I have read the FAQ about modifying the mm_cfg.py file to create a more user friendly subject for confirmations. I implemented this with my Mailman/Postfix setup. I mainly wanted it for Invitation confirmations, but I understand that for newer versions of Mailman, it works for other confirmations as well. One question- Since the subject line is changed and replaces the confirmation ID code with other text, does that mean that simple replying to the message to confirmm will no work? I have tested this and found that I can confirm by clicking on the link and going to the web page or by composing a new message with the confirm code in the body, sent to the list-request address. By default, Postfix allows VERP to rewrite the subject, but is other configuration necessary to make the Reply to the confirmation message work, or is that feature lost when VERPing? -- Christopher Adams [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] another question about invitation confirmationsubject line/VERP
Thank you for clarifying that. I assumed from the Postfix/VERP configuration documentation (below) that the '+' delimiter would be used regardless of entering it in the Postfix main.cf file. I should tried adding it anyway, but I hadn't gotten to that step yet. Thanks, it works as it should. Quoted from documentation: With Postfix, the whole process is controlled by four configuration parameters. default_verp_delimiters (default value: +=) On Nov 27, 2007 1:35 PM, Mark Sapiro [EMAIL PROTECTED] wrote: Christopher Adams wrote: One question- Since the subject line is changed and replaces the confirmation ID code with other text, does that mean that simple replying to the message to confirmm will no work? It will still work if your incoming MTA recognizes addresses of the form [EMAIL PROTECTED] as an address to be delivered to [EMAIL PROTECTED] I have tested this and found that I can confirm by clicking on the link and going to the web page or by composing a new message with the confirm code in the body, sent to the list-request address. The confirmation message the user receives is From: an address like the one above. Simply replying to that message (i.e.sending the reply to [EMAIL PROTECTED]) will work if the MTA delivers it to mailman properly. By default, Postfix allows VERP to rewrite the subject, but is other configuration necessary to make the Reply to the confirmation message work, or is that feature lost when VERPing? In Postfix, you need recipient_delimiter = + for this to work. VERP should not affect this as it manipulates the envelope sender, not the From: header. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Christopher Adams [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] another question about invitation confirmation subject line/VERP
Geez, now I don't know who to listen to. :). Anyway, my assumption was wrong and I based it on the invitation confirmation not completely working. Now it does and I thank you both. One concern - Charles mentioned how 'expensive' it was to use VERP with Postfix. I am wondering what kind of hit on the responsiveness of my Mailman server will be. I have over 500 lists and 250,000 subscribers. If VERP being used for Mailman causes more mail activity, could this result in slowness of list message delivery? On Nov 27, 2007 4:19 PM, Brad Knowles [EMAIL PROTECTED] wrote: On 11/27/07, Mark Sapiro wrote: Quoting from http://www.postfix.org/postconf.5.html, aka 'man 5 postconf' recipient_delimiter (default: empty) That man page may or may not describe the current state of affairs, and of course even if it does then you might be dealing with an older installation that may not implement the same default status. If you want to find out what your current postfix defaults are, you use the command postconf -d. If you want to see what you've got configured that is different from the built-in defaults, use the command postconf -n. A plain postconf will tell you what is configured, but you won't know whether that setting comes from the default or is being over-ridden by the configuration file. -- Brad Knowles [EMAIL PROTECTED] LinkedIn Profile: http://tinyurl.com/y8kpxu -- 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/adamsca%40gmail.com Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp -- Christopher Adams [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] override list owner ability to approve messages over the max_message_size?
Is there a way to for a system override of the ability of list owners to approve messages that are larger than what they have set in max_message_size? We have a limit at the MTA level, as we need to accomodate non-Mailman mail on the same server. List owners are sending large attachments, then just going to the admin and approving them. -- Christopher Adams [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] more help with mailman configure and GID
Okay, another migration, another GID problem. I configured mailman to run as mail GID=mailman (which is 502) and cgi-gid = apache (which is 48). The configuration and installation went fine and check_perms showed no problems. Setting up lists works okay. However, when I try to send a mesage to the list, I get this: [EMAIL PROTECTED] on 8/29/2007 11:36 AM Failed (Command died with status 8: /usr/local/mailman/mail/mailman post test7. Command output: Failure tofind group name for GID 1004. Mailman expected the mail wrapper to beexecuted as group mailman, but the system's mail server executed thewrapper as GID 1004 for which the name could not be found. Try adding GID1004 to your system as mailman, or tweak your mail server to run thewrapper as group mailman.) Why is it looking at mailman GID=1004 when it is 502? Mailman UID is 1004, but not GID. I tried reconfiguring it with mail GID = nobody, which I have done before, but still get this message. Help is most welcome. -- Christopher Adams [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] more help with mailman configure and GID
I honestly like it when my questions are skimmed over. It makes me realize that I have way more resources to fix things than I initially think. In this case, it was a simple case of the mailman /etc/passwd user entry showing a GID that didn't match the /etc/group mailman entry. I did try changing the /etc/group mailman entry to the actual GID that it was looking for, but the mailman installation broke. Eventually, I noticed that there was a mismatch. So, all should be okay. Thanks for ignoring me. On 8/29/07, Christopher Adams [EMAIL PROTECTED] wrote: Okay, another migration, another GID problem. I configured mailman to run as mail GID=mailman (which is 502) and cgi-gid = apache (which is 48). The configuration and installation went fine and check_perms showed no problems. Setting up lists works okay. However, when I try to send a mesage to the list, I get this: [EMAIL PROTECTED] on 8/29/2007 11:36 AM Failed (Command died with status 8: /usr/local/mailman/mail/mailman post test7. Command output: Failure tofind group name for GID 1004. Mailman expected the mail wrapper to beexecuted as group mailman, but the system's mail server executed thewrapper as GID 1004 for which the name could not be found. Try adding GID1004 to your system as mailman, or tweak your mail server to run thewrapper as group mailman.) Why is it looking at mailman GID=1004 when it is 502? Mailman UID is 1004, but not GID. I tried reconfiguring it with mail GID = nobody, which I have done before, but still get this message. Help is most welcome. -- Christopher Adams [EMAIL PROTECTED] -- Christopher Adams [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] Is there a way to export my list of members to an excel spreadsheet?
Joellen, If you have command line access, you can runt the /bin/list_members command to get a list of addresses. If you don't have command line access, you can send an email to the list-request address and include this in the first line of your message: who yourlistpassword In either case, you can then take the text and open it in Excel. I hope that helps. On 8/7/07, Joellen Leavelle [EMAIL PROTECTED] wrote: Hi, I'm trying to export one of my lists into an excel spreadsheet. I'm not sure how to do it. Any help would be greatly appreciated! Thanks in advance. Joellen Leavelle Communications Coordinator and Logistics Manager Pension Rights Center 1350 Connecticut Avenue, NW Suite 206 Washington, DC 20036 Phone: (202) 296-3776 Fax: (202) 296-1571 www.pensionrights.org -- 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/adamsca%40gmail.com Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp -- Christopher Adams [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] question about entries in Mailman logs
A list subscriber ([EMAIL PROTECTED]) regularly posts to his list (listX) successfully. However, the mailman logs fill up daily with these kind of entries, coming seconds apart. They have the same message-id. I don't know how to interpret this and if it is a Postfix problem or related to Mailman. I would appreciate some clarification. smtp.log.6:Aug 01 03:56:06 2007 (10919) [EMAIL PROTECTED] smtp to listX for 72 recips, completed in 17.070 seconds post.log.4:Aug 03 03:56:25 2007 (30474) post to listX from [EMAIL PROTECTED], size=5318, message-id=[EMAIL PROTECTED], 72 failures smtp-failure.log.4:Aug 03 03:56:25 2007 (30474) Low level smtp error: Server not connected, msgid: [EMAIL PROTECTED] -- Christopher Adams [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] Digest not being sent
At least a couple (maybe all) of my lists are not sending out the digest automatically. I can see the digest.mbox file and it is up to date, but a couple of weeks old. Subscribers who have chosen digest mode alerted me that they weren't getting messages. I looked at one list and the threshold is set to 200 KB and daily if the threshold is not reached. I know there is a senddigests cron, but how does this actually work, and what could be the reason that no lists are sending the digest unless I manually choose that it be sent? -- Christopher Adams [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] Digest not being sent
Actually, I have read the FAQ, but didn't seem to reap any useful information in this regard. I did find something in my search of the mailman-users list that talks about a corrupt digest.mbox file. Before I had a chance to check that out, the digest was sent. Odd. So, what controls the time that the daily digest is sent out if the threshold hasn't been reached? There is a 'senddigests' script in the /mailman/cron directory, but I am at a loss as to when it is fired off. I can generate digests based on threshold with no problem, and I know the daily delivery problem is happening with more than one list, so what else to look for? On 8/2/07, Brad Knowles [EMAIL PROTECTED] wrote: On 8/2/07, Christopher Adams wrote: I know there is a senddigests cron, but how does this actually work, and what could be the reason that no lists are sending the digest unless I manually choose that it be sent? Did you search the FAQ wizard on this matter? -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 -- Christopher Adams [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] Digest not being sent
Okay, I think I found it. I'm not sure how I missed it during install. I didn't find the answer in the FAQ, but rather in the Mailman install doc: http://www.gnu.org/software/mailman/mailman-install/node41.html So, I have installed the mailman crontab and the digests that haven't been sent by reaching the threshold should now be sent out at 12 am every night. On 8/2/07, Christopher Adams [EMAIL PROTECTED] wrote: Actually, I have read the FAQ, but didn't seem to reap any useful information in this regard. I did find something in my search of the mailman-users list that talks about a corrupt digest.mbox file. Before I had a chance to check that out, the digest was sent. Odd. So, what controls the time that the daily digest is sent out if the threshold hasn't been reached? There is a 'senddigests' script in the /mailman/cron directory, but I am at a loss as to when it is fired off. I can generate digests based on threshold with no problem, and I know the daily delivery problem is happening with more than one list, so what else to look for? On 8/2/07, Brad Knowles [EMAIL PROTECTED] wrote: On 8/2/07, Christopher Adams wrote: I know there is a senddigests cron, but how does this actually work, and what could be the reason that no lists are sending the digest unless I manually choose that it be sent? Did you search the FAQ wizard on this matter? -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 -- Christopher Adams [EMAIL PROTECTED] -- Christopher Adams [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] question about mail-gid
I have over 500 lists that were migrated a couple of weeks ago to a new server. When configuring, I tinkered with the gids until I got it to work using mail-gid=mailman and cgi-gid=apache. Lists information was moved to the new server. Everything has been working fine. When I create a new list from the web and try to post to it, I get this message: Failed (Command died with status 2: /usr/local/mailman/mail/mailman post test7. Command output: Group mismatch error. Mailman expected the mail wrapper script to be executed asgroup mailman, but the system's mail server executed the mail script asgroup nobody. Try tweaking the mail server to run the script as groupmailman, or re-run configure, providing the command line option`--with-mail-gid) I look at the ownership of new lists and they are apache mailman. That is the only difference I see between new lists and other lists that were migrated, which have permissons mailman.mailman. So, I changed the ownership of the new lists and tried to post and get the same message. I am a bit confused as to whether I need to run configure again, using 'nobody' as the mail-gid or something else is going on. -- Christopher Adams [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] question about mail-gid
Aaron, Thanks for the tip, but I'm not quite sure what you mean about the 'user' in the httpd.conf file. On 7/3/07, Aaron Schubert [EMAIL PROTECTED] wrote: Make sure the user in the httpd.conf file is set to apapche if you configrued mailman with apache. By default apache runs as nobody. Change the httpd.conf file from the user nobody to apache and give it a try. Christopher Adams [EMAIL PROTECTED] 7/3/2007 10:51 AM I have over 500 lists that were migrated a couple of weeks ago to a new server. When configuring, I tinkered with the gids until I got it to work using mail-gid=mailman and cgi-gid=apache. Lists information was moved to the new server. Everything has been working fine. When I create a new list from the web and try to post to it, I get this message: Failed (Command died with status 2: /usr/local/mailman/mail/mailman post test7. Command output: Group mismatch error. Mailman expected the mail wrapper script to be executed asgroup mailman, but the system's mail server executed the mail script asgroup nobody. Try tweaking the mail server to run the script as groupmailman, or re-run configure, providing the command line option`--with-mail-gid) I look at the ownership of new lists and they are apache mailman. That is the only difference I see between new lists and other lists that were migrated, which have permissons mailman.mailman. So, I changed the ownership of the new lists and tried to post and get the same message. I am a bit confused as to whether I need to run configure again, using 'nobody' as the mail-gid or something else is going on. -- Christopher Adams [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/aaron.schubert%40dhss.mo.gov Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp -- Christopher Adams [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] question about mail-gid
Okay, I found the User and Group specification in httpd.conf file and both are already set to 'apache'. On 7/3/07, Aaron Schubert [EMAIL PROTECTED] wrote: Make sure the user in the httpd.conf file is set to apapche if you configrued mailman with apache. By default apache runs as nobody. Change the httpd.conf file from the user nobody to apache and give it a try. Christopher Adams [EMAIL PROTECTED] 7/3/2007 10:51 AM I have over 500 lists that were migrated a couple of weeks ago to a new server. When configuring, I tinkered with the gids until I got it to work using mail-gid=mailman and cgi-gid=apache. Lists information was moved to the new server. Everything has been working fine. When I create a new list from the web and try to post to it, I get this message: Failed (Command died with status 2: /usr/local/mailman/mail/mailman post test7. Command output: Group mismatch error. Mailman expected the mail wrapper script to be executed asgroup mailman, but the system's mail server executed the mail script asgroup nobody. Try tweaking the mail server to run the script as groupmailman, or re-run configure, providing the command line option`--with-mail-gid) I look at the ownership of new lists and they are apache mailman. That is the only difference I see between new lists and other lists that were migrated, which have permissons mailman.mailman. So, I changed the ownership of the new lists and tried to post and get the same message. I am a bit confused as to whether I need to run configure again, using 'nobody' as the mail-gid or something else is going on. -- Christopher Adams [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/aaron.schubert%40dhss.mo.gov Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp -- Christopher Adams [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] question about mail-gid
Yep, it's Postfix. Yep, there are two different files. /etc/postfix/aliases is owned by root.root /etc/postfix/aliases.db is owned by root.root /usr/local/mailman/data/aliases is owned by root.mailman /usr/local/mailman/data/aliases is owned by mailman.mailman When I first configured Mailman, I tried to use mail-gid=postfix (or the GID number) and it didn't work. When I create a new list from the web and try to post to it, I get this message: Failed (Command died with status 2: /usr/local/mailman/mail/mailman post test7. Command output: Group mismatch error. Mailman expected the mail wrapper script to be executed asgroup mailman, but the system's mail server executed the mail script asgroup nobody. Try tweaking the mail server to run the script as groupmailman, or re-run configure, providing the command line option`--with-mail-gid) I look at the ownership of new lists and they are apache mailman. That is the only difference I see between new lists and other lists that were migrated, which have permissons mailman.mailman. So, I changed the ownership of the new lists and tried to post and get the same message. This is not related to the ownership of the lists. It is also not related to anything in the Apache config. I am a bit confused as to whether I need to run configure again, using 'nobody' as the mail-gid or something else is going on. Maybe, but if that's all you do, the new lists will work and the old lists won't. Is this Postfix? Are the aliases in two different files? Postfix executes the mail wrapper with the user:group of the owner of the alias files in which the alias is found. If aliases are split in two files with different ownership, one set won't work. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Christopher Adams [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] Mailman installation problem/permissions
Thank you for pointing that out. Mailman is now working okay. On 6/18/07, Mark Sapiro [EMAIL PROTECTED] wrote: Christopher Adams wrote: Yes, I see that it is an Apache issue. In httpd.conf, for the Document Root, I have set: Directory / RewriteEngine On Options FollowSymLinks ExecCGI AllowOverride None Order deny,allow Deny from all So you are denying access to everyone not matching an applicable Allow. Do you have an Allow directive somewhere that would allow access to the mailman CGIs? -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Christopher Adams [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] problem creating new list on the web - Unkown Virtual Host
When I create a list via the web, I get the dreaded 'Unknown Virtual Host mailinglists.state.or.us' message. I consulted the FAQ, but I couldn't see what was wrong: http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.036.htp I didn't configure the DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST during the configuration of Mailman, so I added them to mm_cfg.py and restarted mailman. My entry looks like this: #Virtual Host and Email Host add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) DEFAULT_EMAIL_HOST = 'mailinglists.state.or.us' DEFAULT_URL_HOST = 'mailinglists.state.or.us' Other list admin functions from the web work and I can create lists from the command line. Any tips on what to look for? -- Christopher Adams [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] problem creating new list on the web - Unkown Virtual Host
Brad, Sorry for putting you through that. 'mailinglists.state.or.us' is not the actual domain name. I used it as an example. The actual name is 'listsmart.osl.state.or.us' and does exist in DNS. I have a server with 2 NICs. One of the NICs has the 'listsmart.osl.state.or.us' IP attached to it along with another IP. I don't know if that makes any difference. On 6/19/07, Brad Knowles [EMAIL PROTECTED] wrote: On 6/19/07, Christopher Adams wrote: When I create a list via the web, I get the dreaded 'Unknown Virtual Host mailinglists.state.or.us' message. That name does not exist in the DNS: % dig mailinglists.state.or.us. any ; DiG 9.3.4 mailinglists.state.or.us. any ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NXDOMAIN, id: 49283 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;mailinglists.state.or.us. IN ANY ;; Query time: 3 msec ;; SERVER: 192.168.1.1#53(192.168.1.1) ;; WHEN: Tue Jun 19 18:30:48 2007 ;; MSG SIZE rcvd: 42 % dig @lynx.state.or.us. mailinglists.state.or.us. any ; DiG 9.3.4 @lynx.state.or.us. mailinglists.state.or.us. any ; (1 server found) ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NXDOMAIN, id: 12659 ;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;mailinglists.state.or.us. IN ANY ;; AUTHORITY SECTION: state.or.us.3600IN SOA lynx.state.or.us. dns-admin.state.or.us. 2007061500 10800 1800 604800 3600 ;; Query time: 72 msec ;; SERVER: 159.121.107.82#53(159.121.107.82) ;; WHEN: Tue Jun 19 18:31:44 2007 ;; MSG SIZE rcvd: 93 You might want to get that fixed. While you're at it, you should have your nameserver administrators look into fixing the other things wrong with the domain -- see http://www.dnsstuff.com/tools/dnsreport.ch?%26domain%3Dstate.or.us. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 -- Christopher Adams [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 installation problem/permissions
After a hardware failure, I am trying to install Mailman on another server. As per the documentation, I added myself to the Mailman group and ran the configure as me. I used --with-mail-gid=mailman and --with-cgi-gid=www. I then ran make install. It seemed to work okay. I ran ./check_perms -f and all looks okay. I went to the mailman directory and did this: cd /usr/local/mailman chgrp mailman . chmod a+rx,g+ws I added a ScriptAlias entry in the apache conf file: ScriptAlias /mailman/ /usr/local/mailman/cgi-bin/ I restarted Apache, Postfix, and Mailman. No matter what I do, if I go to the URL: http://mydomain.com/mailman/admin/create I get the message: You don't have permission to access /mailman/ on this server. I tried doing the configure with actual gid number and tried using different combinations such as mail-gid=postfix and cgi-gid=nobody. None of that seems to make a difference. I would appreciate any ideas as to what is going on. It appears to be a permissions problem but I would like to narrow it down one way or another. Thanks -- Christopher Adams [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] Mailman installation problem/permissions
You don't trust check_perms? Not sure about that. What does the apache error_log say about this? client denied by server configuration: /usr/local/mailman/cgi-bin/create What are the ownership and permissions of the files in /usr/local/mailman/cgi-bin/ ? mailman.mailman rwxr-sr-x -- 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 installation problem/permissions
On 6/18/07, Mark Sapiro [EMAIL PROTECTED] wrote: Christopher Adams wrote: What does the apache error_log say about this? client denied by server configuration: /usr/local/mailman/cgi-bin/create So this is an apache configuration issue, not a Mailman permissions issue. Do you have ExecCGI implicitly or explicitly on the /usr/local/mailman/cgi-bin/ directory in the apache config plus all the other apache stuff like mod_cgi? Yes, I see that it is an Apache issue. In httpd.conf, for the Document Root, I have set: Directory / RewriteEngine On Options FollowSymLinks ExecCGI AllowOverride None Order deny,allow Deny from all /Directory Options All I also have a Directory entry for the /usr/local/mailman directory, with ExecCGI specified, which I guess is redundant if I have it above. As for mod_cgi, Apache says that it is loading it on startup. I know this isn't and Apache mailing list, but if you have suggestions, they are most welcome. Chris -- 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] question about moving list and archives
I have moved a list from another mailman installation. I moved the list files and the archives and then ran fix_url. Everything looks good except for the To: address in individual messages in the archive. It still has the old URL/mail address. Also, the link labeled 'More Info on this List still points to the old URL. So, what else do I need to do? Does the arch utility take care of this? It was my understanding that the arch utility was for rebuilding an archive after editing it or removing messages. Also, the documentation says something like this: /bin/arch mylist archives/private/mylist.mbox/mylist.mbox My lists don't have a mylist.mbox file in the mylist.mbox directory. Any advice would be helpful. -- Christopher Adams [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] question about moving list and archives
Mark, Yes, you're right about the list.mbox file. This was given to me by someone else and I was surprised that the mbox file wasn't included. Does this mean that a new mbox file will be created with the next post? How do messages append to the archive if there is no mbox file? I have other lists that have been archiving for years and have no mbox file. I guess I am a bit confused by the use of the mbox file for archives. On 6/5/07, Mark Sapiro [EMAIL PROTECTED] wrote: Christopher Adams wrote: I have moved a list from another mailman installation. I moved the list files and the archives and then ran fix_url. Everything looks good except for the To: address in individual messages in the archive. It still has the old URL/mail address. Also, the link labeled 'More Info on this List still points to the old URL. So, what else do I need to do? Does the arch utility take care of this? It was my understanding that the arch utility was for rebuilding an archive after editing it or removing messages. Also, the documentation says something like this: /bin/arch mylist archives/private/mylist.mbox/mylist.mbox My lists don't have a mylist.mbox file in the mylist.mbox directory. Any advice would be helpful. You don't have the mylist.mbox file, because you didn't move it from the old installation. It was really the only archive file you needed to move. Without it, you can't rebuild the archives, and rebuilding is the way to fix the issues above. If you can get the .mbox file, then simply running bin/arch --wipe mylist will recreate the HTML archive and will fix the 'More Info on this List' links. However, it is a good idea to first check the .mbox for unescaped From_ lines using bin/cleanarch. Where are you seeing the To: address in individual messages in the archive? Normally the HTML archive contains no message headers. If you are seeing this in quotes of prior posts, the only way to change that is to edit the .mbox prior to running bin/arch. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Christopher Adams [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] mailman aliases
Thank you for all your ideas. I was just a bit surprised that a list would be available for anyone to post to, since we emphasize to our users that their lists are protected from spam, as all lists require you to be a subscribe to post, and many require mod permissions to post. That is still true and they are well protected, except for the message sent directly to listname-owner. Anyway, I will have to figure out a way to deal with the increase in spam that I get at the mailman posting address. It is better to have valid messages getting to me than to go nowhere, as they did before I set up the mailman aliases for the mailman list. Thanks for your answers. On 5/23/07, Mark Sapiro [EMAIL PROTECTED] wrote: Christopher Adams wrote: Thanks, Mark. That seemed too obvious. Doesn't setting generic_nonmember_action to accept result in a lot of spam to the Mailman site admin? How are others dealing with this? First, let me say that if your listinfo overview page says If you are having trouble using the lists, please contact [EMAIL PROTECTED], you should actually look at that mail. Unfortunately, changing the overview pages to not say that requires patching Mailman code so it isn't always feasable to remove the message. This will change in some future release, but that doesn't help the immediate situation. You can do other things with the list settings, but setting the list to reject or discard non-member posts is not right IMO. Setting the list to hold non-member posts is OK, but then the list admin or moderator has to deal with them anyway, so why not just accept them, at least if the person who receives them from the list is the same person who has to deal with them if they're held. You can also set some header_filter_rules to try to discard some spam if you can identify it that way. The first step though is to have some kind of spam filtering and/or greylisting on incoming mail so as little spam as possible even gets to Mailman in the first place. That's what I do for my lists and the list admins have to deal with the rest. And yes, I still spend an inordinate amount of time checking spam at least cursorily for legitimate messages. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Christopher Adams [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] mailman aliases
Thanks, Mark. That seemed too obvious. Doesn't setting generic_nonmember_action to accept result in a lot of spam to the Mailman site admin? How are others dealing with this? On 5/22/07, Mark Sapiro [EMAIL PROTECTED] wrote: Christopher Adams wrote: Thanks,Mark. That helps explaining the purpose of the mailman list. All our lists use the form [EMAIL PROTECTED] (wherever.com is the DEFAULT_EMAIL_HOST set in mm_cfg.py). In my Postfix aliases file, I have all the list aliases including aliases for the mailman list: ## mailman mailing list mailman-admin:|/var/mailman/mail/mailman admin mailman mailman-bounces: |/var/mailman/mail/mailman bounces mailman mailman-confirm: |/var/mailman/mail/mailman confirm mailman mailman-join: |/var/mailman/mail/mailman join mailman mailman-leave:|/var/mailman/mail/mailman leave mailman mailman-request: |/var/mailman/mail/mailman request mailman mailman-subscribe:|/var/mailman/mail/mailman subscribe mailman mailman-unsubscribe: |/var/mailman/mail/mailman unsubscribe mailman So, in the general list info page, there is a line that says: If you are having trouble using the lists, please contact [EMAIL PROTECTED] Since that address is a post to the mailman mailing list, how does it actually get delivered anywhere? The same as any other list. You subscribe the Mailman site admin(s) to it and you set generic_nonmember_action to accept. I don't quite understand what you mean about the general listinfo and admin pages exposing the mailman@ address in their own domain. I am unclear as to what that domain should be. That doesn't apply in your case. I misunderstood your situation and thought you had multiple virtual domains. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Christopher Adams [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 aliases
Just for clarification, what is the use for the mailman list that is listed in the aliases file? Is this a required list and if so, what is it's purpose. If that is not required, what are the necessary entries in the aliases file to take care of mailman-bounces, mailman-owner, etc? Would that just be aliases to individual email addresses to take care of messages pointed to those mailman addresses. I have been runnning mailman for a number of years and it recently was pointed out that the [EMAIL PROTECTED] didn't go anywhere. So, I added an alias to it and to mailman-owner and mailman-bounces to my email address in the aliases file. Maybe I'm barking up the wrong tree here, but these have to point somewhere. I have read through the Mailman installation docs and FAQ, but can't find a definitive answer. Pointing me to some documentation would be sufficient. Thanks -- Christopher Adams [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] mailman aliases
Thanks,Mark. That helps explaining the purpose of the mailman list. All our lists use the form [EMAIL PROTECTED] (wherever.com is the DEFAULT_EMAIL_HOST set in mm_cfg.py). In my Postfix aliases file, I have all the list aliases including aliases for the mailman list: ## mailman mailing list mailman-admin:|/var/mailman/mail/mailman admin mailman mailman-bounces: |/var/mailman/mail/mailman bounces mailman mailman-confirm: |/var/mailman/mail/mailman confirm mailman mailman-join: |/var/mailman/mail/mailman join mailman mailman-leave:|/var/mailman/mail/mailman leave mailman mailman-request: |/var/mailman/mail/mailman request mailman mailman-subscribe:|/var/mailman/mail/mailman subscribe mailman mailman-unsubscribe: |/var/mailman/mail/mailman unsubscribe mailman So, in the general list info page, there is a line that says: If you are having trouble using the lists, please contact [EMAIL PROTECTED] Since that address is a post to the mailman mailing list, how does it actually get delivered anywhere? I don't quite understand what you mean about the general listinfo and admin pages exposing the mailman@ address in their own domain. I am unclear as to what that domain should be. On 5/22/07, Mark Sapiro [EMAIL PROTECTED] wrote: Christopher Adams wrote: Just for clarification, what is the use for the mailman list that is listed in the aliases file? Is this a required list and if so, what is it's purpose. It is a required list in Mailman 2.1. bin/mailmanctl will not start Mailman if it isn't present. It is used as the apparent source of monthly password reminders and certain other notifications, the former because reminders are for all subscribed lists in a domain, not for individual lists, and the latter to avoid bounce loops on list-owner notices. It will go away in Mailman 2.2. If that is not required, what are the necessary entries in the aliases file to take care of mailman-bounces, mailman-owner, etc? Would that just be aliases to individual email addresses to take care of messages pointed to those mailman addresses. I have been runnning mailman for a number of years and it recently was pointed out that the [EMAIL PROTECTED] didn't go anywhere. So, I added an alias to it and to mailman-owner and mailman-bounces to my email address in the aliases file. Maybe I'm barking up the wrong tree here, but these have to point somewhere. I have read through the Mailman installation docs and FAQ, but can't find a definitive answer. Pointing me to some documentation would be sufficient. Thanks The issue is somewhat tricky as the mailman list and its aliases are usually created in the DEFAULT_EMAIL_HOST domain, but the listinfo and admin overview pages expose a mailman@ address in their own domain, so these addresses ought to be deliverable too. Likewise the mailman-bounces address. Aliases will point to e.g. |/usr/local/mailman/mail/mailman post mailman, |/usr/local/mailman/mail/mailman bounces mailman, etc. which is the one and only 'mailman' list in the installation. I hope this helps. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Christopher Adams [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] modifying admin page - create new lists
I would like to remove the reference to creating new lists that is included in the admin page. I have looked in the Templates folder and in the Mailman folder, but haven't been able to find where that is included. -- Christopher Adams [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] join script
A user had been sending subscription requests to the listname-join address and was being rejected. I realized that I hadn't even thought about mailman's alias addresses. So, I began to investigate and some user manual says that a user can send to the listname-join or listname-subscribe to request to be subscribed. I assume that means that no commands are sent, as is done with the listname-request address. So, I sent a message to the listname-join address of one of my test lists, with no commands. The result was: [EMAIL PROTECTED] on 12/14/2006 9:59 AM Failed (cannot append message to destination file /|/var/mailman/mail/mailman join listname: cannot create file exclusively: Nosuch file or directory) It appears that mailman is trying to write some temp file or something and doesn't have write permissions. Can anyone clarify what I need to modify to make this work? -- Christopher Adams [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] join script
Mark, Thanks for spotting that. I don't know why the aliases were formatted that way. It looks like the pipe was being escaped or something. I hadn't thought that it was an alias problem because most everything seemed to be working, including sending subscription requests to the listname-request address. That's another question - what is the difference between subscribing by sending a blank message or a 'subscribe' command to listname-join and sendilng a 'subscribe' command to listname-request? It appears that they do the same thing. I guess that's why we call them aliases. :) On 12/14/06, Mark Sapiro [EMAIL PROTECTED] wrote: Christopher Adams wrote: So, I sent a message to the listname-join address of one of my test lists, with no commands. The result was: [EMAIL PROTECTED] on 12/14/2006 9:59 AM Failed (cannot append message to destination file /|/var/mailman/mail/mailman join listname: cannot create file exclusively: Nosuch file or directory) It looks like the alias that should look something like listname-join: |/var/mailman/mail/mailman join listname has an extraneous '/' as perhaps listname-join: /|/var/mailman/mail/mailman join listname -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Christopher Adams [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
