From mark at msapiro.net Tue Sep 1 03:12:40 2015 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 31 Aug 2015 18:12:40 -0700 Subject: [Mailman-Users] {Disarmed} Re: importing archived Maildir email lists into Mailman lists archives In-Reply-To: References: <55E265E9.3040305@msapiro.net> Message-ID: <55E4FB88.7080408@msapiro.net> On 08/31/2015 05:58 AM, [IDIS Technical Secretariat] Ricardo Rodr?guez wrote: > > This has been more or less my entry point to this issue. Perhaps I've > not been able to explain the issue correctly or I'm missing something. > What I'm looking to move into mbox is a set of archives of Maildir > mailing lists. Why do you refer to these archives as being of Maildir mailing lists? What is the actual software that created them. > Those archives don't contain new, cur and tmp folders all > the scripts I've spotted at looked for. This is the structure of each > archived email list folder I have here... > > Ricardo-Rodriguezs-Mac-Pro:r.users rrodriguez$ ls > Log bounce digissue headerremove lock mod outlocal remote > allow bouncer dignum indexed lockbounce modsub owner subscribers > archive config editor inlocal mailinglist num prefix text > archived digest headeradd key manager outhost public tstdig > > > Within /archive, there are two folders, 0 and 1, with a number of files, > each of them containing one message, and an index file. This looks vaguely like Maildir, except Maildir has no index file. What is in the index file(s)? What is the difference between 0 and 1? Do they each contain some complete (including all headers) messages, i.e. each contains a set of messages that combined are all the messages, or does one of them contain message headers and the other bodies, or does one contain messages and the other contain metadata about the messages? > Please, does this made sense for you? Am I completely lost? How could I > deal with this "archives" to move them to mbox files and get them > imported our brand new Mailman server? You just need to add a *nix From_ separator to the beginning of each complete message and concatenate them. If you can show me what's actually in some of those files, I could possibly create a conversion script for you. It could be as simple as something like cat archives/0/* archives/1/* > mbox except for the index files, but probably not. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From stephen at xemacs.org Tue Sep 1 03:19:47 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Tue, 01 Sep 2015 10:19:47 +0900 Subject: [Mailman-Users] importing archived Maildir email lists into Mailman lists archives In-Reply-To: References: <55E265E9.3040305@msapiro.net> Message-ID: <87oahn3pho.fsf@uwakimon.sk.tsukuba.ac.jp> [IDIS Technical Secretariat] Ricardo Rodr?guez writes: > Thanks Mark, all, > > On Sun, Aug 30, 2015 at 4:09 AM, Mark Sapiro wrote: > > > On 08/28/2015 12:52 AM, [IDIS Technical Secretariat] Ricardo Rodr?guez > > wrote: > > > > > > I have a number of Maildir format mailing lists archives No, you don't have Maildir, at least not "Maildir" as most of the Internet understands it. Here's what Dan Bernstein (the inventor or at least popularizer of Maildir) says: Can a maildir contain more than tmp, new, cur? Yes: .qmail: used to do direct deliveries with qmail-local. bulletintime: empty file, used by system-wide bulletin programs. bulletinlock: empty file, used by system-wide bulletin programs. seriallock: empty file, used to serialize AutoTURN. > Ricardo-Rodriguezs-Mac-Pro:r.users rrodriguez$ ls > Log bounce digissue headerremove lock mod outlocal remote "Lock" -- no, this isn't Maildir. The whole point of Maildir is that you don't need locks because reading and writing are done in different directories, and changes happen atomically. (This can even work with editing.) > allow bouncer dignum indexed lockbounce modsub owner subscribers > archive config editor inlocal mailinglist num prefix text > archived digest headeradd key manager outhost public tstdig > > Within /archive, there are two folders, 0 and 1, with a number of files, > each of them containing one message, and an index file. > > Please, does this made sense for you? I don't recall anything like that. Please try to find an explanation of the structure in the system documentation, or ask the vendor. However, since you think they're "Maildir", probably what is meant is that they have a structure that is one message per file rather than many messages per file. You probably just need to figure out how to get the order of messages right, then concatenate the messages. Most likely, all you need for each list are the archive folders and the single messages, and maybe the index file will be of some use depending on what it contains. If your documentation and/or the old vendor are of no help, see if you can find a whole message file you can send to us *as a file attachment* -- we want to see what headers are included (it probably doesn't really matter, though, except for the "Unix From_" which they probably don't have). If for privacy reasons you don't want to broadcast any message on a public mailing list, you can send it to Mark and me personally. Also it may be helpful to figure out the rule for the folders whose names are numbers: are they the leading digits where files are named 000 to 999? Are they months? Years? etc. > Am I completely lost? No, of course not. Just don't delete anything until you're sure the new system is working. I did qualify everything with "probably", it may take a couple of guesses to get it right. :-) From waldbiec at lafayette.edu Tue Sep 1 15:33:04 2015 From: waldbiec at lafayette.edu (Waldbieser, Carl) Date: Tue, 1 Sep 2015 09:33:04 -0400 (EDT) Subject: [Mailman-Users] Pluggable authentication for Mailman web interface? In-Reply-To: References: <854480980.1021293.1440619708372.JavaMail.zimbra@lafayette.edu> Message-ID: <433539833.747495.1441114384963.JavaMail.zimbra@lafayette.edu> I know that currently, mailman roles are set up such that the roles themselves have a shared password per role. I want to be able to move away from that model and have roles assigned to individual user accounts that would allow access to the admin interfaces for individual lists. For example, say we have mail lists "Campus" and "Board of Trustees". I might have roles "campus_moderators", "campus_admins", "boardoftrustees_moderators", and "boardoftrustees_admins". If I assign the role campus_admins to user "johnsmith", I would like this user to be able to access the mailman admin interface for the "Campus" list using his own credentials. Ideally, "johnsmith" would not have to present his primary credentials to the mailman interface because our institution has a web single sign-on infrastructure (Web SSO). I can take this conversation to mailman-developers if that is the more appropriate forum. Thanks, Carl Waldbieser ITS Systems Programmer Lafayette College ----- Original Message ----- From: "Andrew Stuart" To: "waldbiec" Cc: "Mailman-Users" Sent: Monday, August 31, 2015 5:08:11 PM Subject: Re: [Mailman-Users] Pluggable authentication for Mailman web interface? Can you say more about what you are trying to achieve? There is an authenticating reverse proxy server for the Mailman REST API at https://gitlab.com/astuart/mailmania But I don?t think anyone has run it yet - it?s pretty raw, not much more than alpha but fully functional. I?m sorry but I?ve been dragged to other priorities so there?s no real documentation but I?m happy to answer any questions if you want to give it a try. This thread really should like on Mailman Developers though. as On 27 Aug 2015, at 6:08 am, Waldbieser, Carl wrote: Are there any guidelines for adding authentication and /or authorization mechanisms to the Mailman web user interface? Specifically, I was wondering if there is any kind of guidance for authenticating the user via an HTTP header (e.g. HTTP_REMOTE_USER) so that an authenticating reverse proxy could be placed in front of the Mailman web interface. If there is no such built-in mechanism or pluggable mechanism, is there any kind of guidance on how the existing authentication mechanism might be replaced from a technical standpoint? Thanks, Carl Waldbieser ITS Systems Programmer Lafayette College ------------------------------------------------------ Mailman-Users mailing list Mailman-Users at 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/andrew.stuart%40supercoders.com.au From dmagda at ee.ryerson.ca Tue Sep 1 13:22:58 2015 From: dmagda at ee.ryerson.ca (David Magda) Date: Tue, 1 Sep 2015 07:22:58 -0400 Subject: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6 Message-ID: <7915CC9E-0B0F-41D4-9B79-7FCEBE2107B8@ee.ryerson.ca> [Not sure if my first attempt made it out.] Hello, We recently upgrade from Debian 5 to 6, and are now having issues with Mailman. Messages are still flowing properly, but the web archives are not being generated since the upgrade. When I run 'bin/arch mylistname' I get the following: [...] figuring article archives 2005-October /usr/local/mailman-2.1.20/Mailman/Archiver/HyperDatabase.py:176: UnicodeWarning: Unicode equal comparison failed to convert both arguments to Unicode - interpreting them as being unequal self.dict = marshal.load(fp) /usr/local/mailman-2.1.20/Mailman/Archiver/HyperDatabase.py:74: UnicodeWarning: Unicode equal comparison failed to convert both arguments to Unicode - interpreting them as being unequal self.sorted.sort() Updating index files for archive [2004-December] [...] Updating HTML for article 214 Pickling archive state into /usr/local/mailman-2.1.20/archives/private/mylistname/pipermail.pck Traceback (most recent call last): File "bin/arch", line 201, in main() File "bin/arch", line 189, in main archiver.processUnixMailbox(fp, start, end) File "/usr/local/mailman-2.1.20/Mailman/Archiver/pipermail.py", line 586, in processUnixMailbox self.add_article(a) File "/usr/local/mailman-2.1.20/Mailman/Archiver/pipermail.py", line 638, in add_article article.parentID = parentID = self.get_parent_info(arch, article) File "/usr/local/mailman-2.1.20/Mailman/Archiver/pipermail.py", line 658, in get_parent_info if self.database.hasArticle(archive, article.in_reply_to): File "/usr/local/mailman-2.1.20/Mailman/Archiver/HyperDatabase.py", line 279, in hasArticle self.__openIndices(archive) File "/usr/local/mailman-2.1.20/Mailman/Archiver/HyperDatabase.py", line 257, in __openIndices t = DumbBTree(os.path.join(arcdir, archive + '-' + i)) File "/usr/local/mailman-2.1.20/Mailman/Archiver/HyperDatabase.py", line 66, in __init__ self.load() File "/usr/local/mailman-2.1.20/Mailman/Archiver/HyperDatabase.py", line 185, in load self.__sort(dirty=1) File "/usr/local/mailman-2.1.20/Mailman/Archiver/HyperDatabase.py", line 74, in __sort self.sorted.sort() UnicodeDecodeError: 'ascii' codec can't decode byte 0xea in position 3: ordinal not in range(128) We're running 2.1.13, but as you can see, the problem persists even with the latest release. We're using the stock Debian Python (2.6.6), but Mailman for tarballs. Thanks for any info. Regards, David From nestor.praslin at gmail.com Tue Sep 1 04:27:07 2015 From: nestor.praslin at gmail.com (Nestor Praslin) Date: Mon, 31 Aug 2015 21:27:07 -0500 Subject: [Mailman-Users] (no subject) Message-ID: Hi dear, how are you doing, I have a question?can anybody help me install mailman and make it run? I like to get in touch with you if so so that maybe ca help me installl it in my server because I have installed via webmin once but didn`t get it to run. -- Nestor Praslin International sihay.com USA 239 603 7693 PMA 507 399 4843 From nestor.praslin at gmail.com Tue Sep 1 04:35:33 2015 From: nestor.praslin at gmail.com (Nestor Praslin) Date: Mon, 31 Aug 2015 21:35:33 -0500 Subject: [Mailman-Users] (no subject) In-Reply-To: References: Message-ID: Hi dear mailman user is there any step by step video in youtube maybe with the requirements and the installation process? On Mon, Aug 31, 2015 at 9:27 PM, Nestor Praslin wrote: > Hi dear, how are you doing, I have a question?can anybody help me install > mailman and make it run? I like to get in touch with you if so so that > maybe ca help me installl it in my server because I have installed via > webmin once but didn`t get it to run. > > -- > Nestor Praslin > International sihay.com > USA 239 603 7693 > PMA 507 399 4843 > > > > > -- Nestor Praslin International sihay.com USA 239 603 7693 PMA 507 399 4843 From lac at openend.se Tue Sep 1 16:08:31 2015 From: lac at openend.se (Laura Creighton) Date: Tue, 01 Sep 2015 16:08:31 +0200 Subject: [Mailman-Users] (no subject) In-Reply-To: References: Message-ID: <201509011408.t81E8Vn7030031@fido.openend.se> In a message of Mon, 31 Aug 2015 21:35:33 -0500, Nestor Praslin writes: >Hi dear mailman user is there any step by step video in youtube maybe with >the requirements and the installation process? I went to youtube. I searched for "mailman tutorial". The first 3 hits seem to be what you are looking for, one for 'with Cpanel' - so either exactly what you are looking for or 'you can skip this one'. Laura From brennan at columbia.edu Tue Sep 1 16:27:18 2015 From: brennan at columbia.edu (Joseph Brennan) Date: Tue, 01 Sep 2015 10:27:18 -0400 Subject: [Mailman-Users] Archive looping Message-ID: We have a list with a very large archive, over 137,000 messages in a month. It catches system alerts. This might just be a bad idea. Maybe we should archive by day. But it's been all right for many months up to now. I'm looking for ideas on how to solve a problem with the archives. Yesterday the archive got into a weird state that I could not break by a shutdown and fresh start. For each incoming message, it rewrites all of the old messages with one extra newline. This useless activity takes quite a while and has caused mail to accumulate in the in/ directory. Inspection of a sample message in a backup from about 24 hours ago shows hundreds of newlines added to the message in that time. The newlines are always added at the same place, between this:--- -------------- next part -------------- An HTML attachment was scrubbed... URL: < References: <7915CC9E-0B0F-41D4-9B79-7FCEBE2107B8@ee.ryerson.ca> Message-ID: <87egii3yl6.fsf@uwakimon.sk.tsukuba.ac.jp> David Magda writes: > When I run 'bin/arch mylistname' I get the following: > > [...] > figuring article archives > 2005-October > /usr/local/mailman-2.1.20/Mailman/Archiver/HyperDatabase.py:176: > UnicodeWarning: Unicode equal comparison failed to convert both arguments > to Unicode - interpreting them as being unequal > self.dict = marshal.load(fp) > /usr/local/mailman-2.1.20/Mailman/Archiver/HyperDatabase.py:74: > UnicodeWarning: Unicode equal comparison failed to convert both arguments > to Unicode - interpreting them as being unequal > self.sorted.sort() > Updating index files for archive [2004-December] > [...] > Updating HTML for article 214 > Pickling archive state into > /usr/local/mailman-2.1.20/archives/private/mylistname/pipermail.pck > Traceback (most recent call last): It would appear that you have non-ASCII character in the header of the 214th message of December 2004 (or maybe it's the 214th message overall). That message doesn't conform to the mail standards and should be repaired. Since pipermail is constructing an index, I would guess that you have a localized date header, a display name with an accented character in it, or a subject with an accented character in it. The character in question is e with a caret in the Latin-1 set, I don't know if that's the intended character set though. From sm at noisynotes.com Tue Sep 1 19:00:27 2015 From: sm at noisynotes.com (Steve Matzura) Date: Tue, 01 Sep 2015 13:00:27 -0400 Subject: [Mailman-Users] cron log looks odd Message-ID: I get Mailman job logs that look like this: Sep 1 08:00:01 {my_node} CROND[29280]: (mailman) CMD (/usr/bin/python -S /usr/local/mailman/cron/checkdbs^M) Sep 1 09:00:01 {my_node} CROND[30120]: (mailman) CMD (/usr/bin/python -S /usr/local/mailman/cron/disabled^M) Sep 1 12:00:01 {my_node} atronus CROND[32514]: (mailman) CMD (/usr/bin/python -S /usr/local/mailman/cron/senddigests^M) Sep 1 05:00:01 {my-node} CROND[2654]: (mailman) CMD (/usr/bin/python -S /usr/local/mailman/cron/mailpasswds^M) Where does the '^M' come from, and is it bad that it's there? From mark at msapiro.net Tue Sep 1 19:24:24 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 1 Sep 2015 10:24:24 -0700 Subject: [Mailman-Users] cron log looks odd In-Reply-To: References: Message-ID: <55E5DF48.6040802@msapiro.net> On 09/01/2015 10:00 AM, Steve Matzura wrote: > I get Mailman job logs that look like this: > > Sep 1 08:00:01 {my_node} CROND[29280]: (mailman) CMD (/usr/bin/python > -S /usr/local/mailman/cron/checkdbs^M) > Sep 1 09:00:01 {my_node} CROND[30120]: (mailman) CMD (/usr/bin/python > -S /usr/local/mailman/cron/disabled^M) > Sep 1 12:00:01 {my_node} atronus CROND[32514]: (mailman) CMD > (/usr/bin/python -S /usr/local/mailman/cron/senddigests^M) > Sep 1 05:00:01 {my-node} CROND[2654]: (mailman) CMD (/usr/bin/python > -S /usr/local/mailman/cron/mailpasswds^M) > > Where does the '^M' come from, and is it bad that it's there? It's a . Your Mailman crontab file is a MS-Dos format file with line endings instead of *nix format with line endings. If your crons run OK, it's not a real problem, but if it were me, I'd fix the crontab file. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From dmagda at ee.ryerson.ca Tue Sep 1 19:26:12 2015 From: dmagda at ee.ryerson.ca (David Magda) Date: Tue, 1 Sep 2015 13:26:12 -0400 Subject: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6 In-Reply-To: <87egii3yl6.fsf@uwakimon.sk.tsukuba.ac.jp> References: <7915CC9E-0B0F-41D4-9B79-7FCEBE2107B8@ee.ryerson.ca> <87egii3yl6.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <74744c9fe512b6fd6c6d88f0893e101b.squirrel@webmail.ee.ryerson.ca> [Actually send the reply to the list as well.] On Tue, September 1, 2015 12:15, Stephen J. Turnbull wrote: > David Magda writes: > > > When I run 'bin/arch mylistname' I get the following: > > > > [...] > > figuring article archives > > 2005-October > > /usr/local/mailman-2.1.20/Mailman/Archiver/HyperDatabase.py:176: > > UnicodeWarning: Unicode equal comparison failed to convert both arguments > > to Unicode - interpreting them as being unequal > > self.dict = marshal.load(fp) > > /usr/local/mailman-2.1.20/Mailman/Archiver/HyperDatabase.py:74: > > UnicodeWarning: Unicode equal comparison failed to convert both arguments > > to Unicode - interpreting them as being unequal > > self.sorted.sort() > > Updating index files for archive [2004-December] > > [...] > > Updating HTML for article 214 > > Pickling archive state into > > /usr/local/mailman-2.1.20/archives/private/mylistname/pipermail.pck > > Traceback (most recent call last): > > It would appear that you have non-ASCII character in the header of the > 214th message of December 2004 (or maybe it's the 214th message > overall). That message doesn't conform to the mail standards and > should be repaired. > > Since pipermail is constructing an index, I would guess that you have > a localized date header, a display name with an accented character in > it, or a subject with an accented character in it. The character in > question is e with a caret in the Latin-1 set, I don't know if that's > the intended character set though. Looking at the mbox, there was only one place where \xea was in the header, in a Subject line, using `grep --color='auto' -P -n "\xea"`. I manually edited the mbox (making a copy first) and remove the accented-e character with an ASCII "e", and I'm still getting the error (I did this before e-mail the list). There are other places which have \xea, but not in any headers. The 214 is the message count from a state file. Every time I rerun the command the number is higher, but it seems to die in the same place. In the middle of the output we have a "UnicodeWarning": [...] #00104 <... at acm.org> figuring article archives 2005-September #00105 <... at mikep> figuring article archives 2005-September #00106 <... at acm.org> figuring article archives 2005-September #00107 <... at mail.gmail.com> figuring article archives 2005-October /usr/local/mailman-2.1.20/Mailman/Archiver/HyperDatabase.py:176: UnicodeWarning: Unicode equal comparison failed to convert both arguments to Unicode - interpreting them as being unequal self.dict = marshal.load(fp) /usr/local/mailman-2.1.20/Mailman/Archiver/HyperDatabase.py:74: UnicodeWarning: Unicode equal comparison failed to convert both arguments to Unicode - interpreting them as being unequal self.sorted.sort() Updating index files for archive [2004-December] Date Subject Author Thread Computing threaded index Updating HTML for article 757 Updating HTML for article 864 Updating HTML for article 866 Updating index files for archive [2005-April] Date [...] Then the error at the end: [...] Updating index files for archive [2005-August] [...] Updating HTML for article 947 Updating HTML for article 840 Updating index files for archive [2005-September] Date Subject Author Thread Computing threaded index Updating HTML for article 841 Updating HTML for article 842 Updating HTML for article 843 Updating HTML for article 952 Updating HTML for article 845 Updating HTML for article 966 Updating HTML for article 846 Updating HTML for article 847 Updating HTML for article 848 Updating HTML for article 957 Updating HTML for article 958 Updating HTML for article 961 Updating HTML for article 962 Updating HTML for article 963 Updating HTML for article 964 Updating HTML for article 965 Updating HTML for article 851 Updating HTML for article 960 Updating HTML for article 861 Updating HTML for article 859 Updating HTML for article 860 Updating HTML for article 970 Pickling archive state into /usr/local/mailman-2.1.20/archives/private/reactome-help/pipermail.pck Traceback (most recent call last): File "bin/arch", line 201, in main() File "bin/arch", line 189, in main archiver.processUnixMailbox(fp, start, end) File "/usr/local/mailman-2.1.20/Mailman/Archiver/pipermail.py", line 586, in processUnixMailbox self.add_article(a) File "/usr/local/mailman-2.1.20/Mailman/Archiver/pipermail.py", line 638, in add_article article.parentID = parentID = self.get_parent_info(arch, article) File "/usr/local/mailman-2.1.20/Mailman/Archiver/pipermail.py", line 658, in get_parent_info if self.database.hasArticle(archive, article.in_reply_to): File "/usr/local/mailman-2.1.20/Mailman/Archiver/HyperDatabase.py", line 279, in hasArticle self.__openIndices(archive) File "/usr/local/mailman-2.1.20/Mailman/Archiver/HyperDatabase.py", line 257, in __openIndices t = DumbBTree(os.path.join(arcdir, archive + '-' + i)) File "/usr/local/mailman-2.1.20/Mailman/Archiver/HyperDatabase.py", line 66, in __init__ self.load() File "/usr/local/mailman-2.1.20/Mailman/Archiver/HyperDatabase.py", line 185, in load self.__sort(dirty=1) File "/usr/local/mailman-2.1.20/Mailman/Archiver/HyperDatabase.py", line 74, in __sort self.sorted.sort() UnicodeDecodeError: 'ascii' codec can't decode byte 0xea in position 3: ordinal not in range(128) It gets to 2005-September, creates the index files, enumerates 22 articles, pickles the archive state, and then dies. The 23rd (and later) message/s don't appear to have non-ASCII. Can I patched pipermail.py or HyperDatabase.py (or ???) in some way to work around this? I have LANG=en_US.UTF-8 and LC_TIME=en_DK.UTF8 in my shell environment: does that make a difference? This used to work just fine, so I'm wonder what happened with the OS upgrade. I should have a copy of the VM pre-upgrade in case that's helpful. Thanks for the help. From brennan at columbia.edu Tue Sep 1 19:35:03 2015 From: brennan at columbia.edu (Joseph Brennan) Date: Tue, 01 Sep 2015 13:35:03 -0400 Subject: [Mailman-Users] Archive looping In-Reply-To: References: Message-ID: <20D55552D3AC7D11EFB9C056@sodor.cc.columbia.edu> I must correct myself. First-- The monthly archive is 9,000 messages (137,000 is the total in the entire archive going back for years). Second-- Not all messages are getting rewritten one newline at a time. Only those with "An HTML attachment was scrubbed..." get the rewrite. Still happening Joseph Brennan Manager, Email and Systems Applications Columbia University Information Technology From mark at msapiro.net Tue Sep 1 19:53:09 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 1 Sep 2015 10:53:09 -0700 Subject: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6 In-Reply-To: <74744c9fe512b6fd6c6d88f0893e101b.squirrel@webmail.ee.ryerson.ca> References: <7915CC9E-0B0F-41D4-9B79-7FCEBE2107B8@ee.ryerson.ca> <87egii3yl6.fsf@uwakimon.sk.tsukuba.ac.jp> <74744c9fe512b6fd6c6d88f0893e101b.squirrel@webmail.ee.ryerson.ca> Message-ID: <55E5E605.50208@msapiro.net> On 09/01/2015 10:26 AM, David Magda wrote: > > Looking at the mbox, there was only one place where \xea was in the > header, in a Subject line, using `grep --color='auto' -P -n "\xea"`. I > manually edited the mbox (making a copy first) and remove the accented-e > character with an ASCII "e", and I'm still getting the error (I did this > before e-mail the list). There are other places which have \xea, but not > in any headers. There shouldn't be any non-ascii in a mbox. Well, maybe in a "Content-Transfer-Encoding: 8bit" (or binary?) body part, but certainly not in any headers. I don't know what you are grepping, but if it's the mbox, you shouldn't be looking for "\xea", you should be looking for "?". > The 214 is the message count from a state file. Every time I rerun the > command the number is higher, but it seems to die in the same place. In > the middle of the output we have a "UnicodeWarning": Are you running bin/arch with the --wipe option? If not, you are repeatedly adding the same messages to the archive which is why the number increases. ... > Can I patched pipermail.py or HyperDatabase.py (or ???) in some way to > work around this? I have LANG=en_US.UTF-8 and LC_TIME=en_DK.UTF8 in my > shell environment: does that make a difference? Probably not. > This used to work just fine, so I'm wonder what happened with the OS > upgrade. I should have a copy of the VM pre-upgrade in case that's > helpful. Python's default encoding could make a difference if it was something other than ascii previously. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Tue Sep 1 20:33:53 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 1 Sep 2015 11:33:53 -0700 Subject: [Mailman-Users] Archive looping In-Reply-To: References: Message-ID: <55E5EF91.50106@msapiro.net> On 09/01/2015 07:27 AM, Joseph Brennan wrote: > > Yesterday the archive got into a weird state that I could not break by a > shutdown and fresh start. For each incoming message, it rewrites all of > the old messages with one extra newline. This useless activity takes > quite a while and has caused mail to accumulate in the in/ directory. This really shouldn't affect the /in queue as IncomingRunner only puts the message in the archive/ queue for ArchRunner. > Inspection of a sample message in a backup from about 24 hours ago shows > hundreds of newlines added to the message in that time. The newlines are > always added at the same place, between this:--- > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <" and "" are created by HyperArch.py and I don't think HyperArch.py knows or cares if what Scrubber.py did. Then the whole thing is written at once by pipermail.py. Nothing in Mailman would be writting one \n at a time to disk in the middle of an article. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From stephen at xemacs.org Tue Sep 1 20:35:13 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Wed, 02 Sep 2015 03:35:13 +0900 Subject: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6 In-Reply-To: <55E5E605.50208@msapiro.net> References: <7915CC9E-0B0F-41D4-9B79-7FCEBE2107B8@ee.ryerson.ca> <87egii3yl6.fsf@uwakimon.sk.tsukuba.ac.jp> <74744c9fe512b6fd6c6d88f0893e101b.squirrel@webmail.ee.ryerson.ca> <55E5E605.50208@msapiro.net> Message-ID: <87a8t63s4e.fsf@uwakimon.sk.tsukuba.ac.jp> Mark Sapiro writes: > I don't know what you are grepping, but if it's the mbox, you shouldn't > be looking for "\xea", you should be looking for "?". At least on recent BSD-based systems "\xea" is a well-defined escape sequence, interpreted as the hexadecimal representation of a byte. Dunno about GNU or proprietary systems. (POSIX.2) > > Can I patched pipermail.py or HyperDatabase.py (or ???) in some way to > > work around this? I have LANG=en_US.UTF-8 and LC_TIME=en_DK.UTF8 in my > > shell environment: does that make a difference? > > Probably not. Actually, yes, it may. If you previously had LANG=en_US.ISO8859-1 (or similar), then Python's default encoding may have allowed all bytes. On the other hand, 0xEA is not a legal byte in modern UTF-8 (it's out of the range of legal Unicode scalars as a leading byte and it can't be a trailing byte). > > This used to work just fine, s/just fine/incorrectly but conveniently for the sysadmin/. :-) I suppose it's possible that a Python upgrade wiped out a patch or configuration that told Python to use a Latin-N default encoding, so it reverted to ASCII. I suspect that Mailman's copy of the email libraries has also evolved quite a bit since 2.1.9 (I think that's what you upgraded from?), and if it was a Mailman provided by the OS vendor, all bets are off. Who knows what patches they may have applied. From dmagda at ee.ryerson.ca Tue Sep 1 21:09:23 2015 From: dmagda at ee.ryerson.ca (David Magda) Date: Tue, 1 Sep 2015 15:09:23 -0400 Subject: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6 In-Reply-To: <55E5E605.50208@msapiro.net> References: <7915CC9E-0B0F-41D4-9B79-7FCEBE2107B8@ee.ryerson.ca> <87egii3yl6.fsf@uwakimon.sk.tsukuba.ac.jp> <74744c9fe512b6fd6c6d88f0893e101b.squirrel@webmail.ee.ryerson.ca> <55E5E605.50208@msapiro.net> Message-ID: <97793451d21a7677057597440f6aa5bf.squirrel@webmail.ee.ryerson.ca> On Tue, September 1, 2015 13:53, Mark Sapiro wrote: > There shouldn't be any non-ascii in a mbox. Well, maybe in a > "Content-Transfer-Encoding: 8bit" (or binary?) body part, but certainly > not in any headers. > > I don't know what you are grepping, but if it's the mbox, you shouldn't > be looking for "\xea", you should be looking for "?". Yes, there are a number of messages with a C-T-E of 8bit. > Are you running bin/arch with the --wipe option? If not, you are > repeatedly adding the same messages to the archive which is why the > number increases. Doing a run with "--wipe" seems to have fixed things. Doing a complete 're-build' (from message 0) finished without errors, and sending a test message seems to have now generated a proper archive HTML page for September 2015. Previously the last archive web page was for a message sent August 25, even though a few messages had come between then and now. Could the new version of Python been chocking on a binary file whose format has changed from the old version? Is it prudent to do an "arch --wipe" when changing versions of Python? From dmagda at ee.ryerson.ca Tue Sep 1 21:16:21 2015 From: dmagda at ee.ryerson.ca (David Magda) Date: Tue, 1 Sep 2015 15:16:21 -0400 Subject: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6 In-Reply-To: <87a8t63s4e.fsf@uwakimon.sk.tsukuba.ac.jp> References: <7915CC9E-0B0F-41D4-9B79-7FCEBE2107B8@ee.ryerson.ca> <87egii3yl6.fsf@uwakimon.sk.tsukuba.ac.jp> <74744c9fe512b6fd6c6d88f0893e101b.squirrel@webmail.ee.ryerson.ca> <55E5E605.50208@msapiro.net> <87a8t63s4e.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: On Tue, September 1, 2015 14:35, Stephen J. Turnbull wrote: > Mark Sapiro writes: > > > I don't know what you are grepping, but if it's the mbox, you shouldn't > > be looking for "\xea", you should be looking for "??". > > At least on recent BSD-based systems "\xea" is a well-defined escape > sequence, interpreted as the hexadecimal representation of a byte. > Dunno about GNU or proprietary systems. (POSIX.2) This is GNU grep under Debian. > s/just fine/incorrectly but conveniently for the sysadmin/. :-) > > I suppose it's possible that a Python upgrade wiped out a patch or > configuration that told Python to use a Latin-N default encoding, so > it reverted to ASCII. Debian is fairly conservative about these things, and AFAIK, the OS default was to use UTF-8, either en_US or en_CA. The locale did not change during the upgrade. > I suspect that Mailman's copy of the email libraries has also evolved > quite a bit since 2.1.9 (I think that's what you upgraded from?), and > if it was a Mailman provided by the OS vendor, all bets are off. Who > knows what patches they may have applied. We are running 2.1.13 from tarballs and so the Mailman code did not change when the archive web page generation stopped. The only thing that changed was the version of Python (2.5 -> 2.6?) under the OS. Doing a "arch --wipe mylist" seems to have solved the issue, though now I'm curious to know why \xea was a problem before but suddenly isn't after the wipe. From sm at noisynotes.com Wed Sep 2 01:51:04 2015 From: sm at noisynotes.com (Steve Matzura) Date: Tue, 01 Sep 2015 19:51:04 -0400 Subject: [Mailman-Users] cron log looks odd In-Reply-To: <55E5DF48.6040802@msapiro.net> References: <55E5DF48.6040802@msapiro.net> Message-ID: On Tue, 1 Sep 2015 10:24:24 -0700, you wrote: >On 09/01/2015 10:00 AM, Steve Matzura wrote: >> I get Mailman job logs that look like this: >> >> Sep 1 08:00:01 {my_node} CROND[29280]: (mailman) CMD (/usr/bin/python >> -S /usr/local/mailman/cron/checkdbs^M) >> Sep 1 09:00:01 {my_node} CROND[30120]: (mailman) CMD (/usr/bin/python >> -S /usr/local/mailman/cron/disabled^M) >> Sep 1 12:00:01 {my_node} atronus CROND[32514]: (mailman) CMD >> (/usr/bin/python -S /usr/local/mailman/cron/senddigests^M) >> Sep 1 05:00:01 {my-node} CROND[2654]: (mailman) CMD (/usr/bin/python >> -S /usr/local/mailman/cron/mailpasswds^M) >> >> Where does the '^M' come from, and is it bad that it's there? > > >It's a . Your Mailman crontab file is a MS-Dos format file with > line endings instead of *nix format with line endings. > >If your crons run OK, it's not a real problem, but if it were me, I'd >fix the crontab file. I'll do that. I thought it might be something like that, but I guess I was expecting "\n", not "^M". Will fix it now. Thanks. From mark at msapiro.net Wed Sep 2 02:41:50 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 1 Sep 2015 17:41:50 -0700 Subject: [Mailman-Users] Pluggable authentication for Mailman web interface? In-Reply-To: <433539833.747495.1441114384963.JavaMail.zimbra@lafayette.edu> References: <854480980.1021293.1440619708372.JavaMail.zimbra@lafayette.edu> <433539833.747495.1441114384963.JavaMail.zimbra@lafayette.edu> Message-ID: <55E645CE.2080806@msapiro.net> On 09/01/2015 06:33 AM, Waldbieser, Carl wrote: > > I know that currently, mailman roles are set up such that the roles themselves have a shared password per role. This is true for MM 2.1. It is not true for MM 3. > I want to be able to move away from that model and have roles assigned to individual user accounts that would allow access to the admin interfaces for individual lists. MM 3 already works this way. Please clarify whether you want to do this in MM 2.1 or in MM 3. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Wed Sep 2 03:02:19 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 1 Sep 2015 18:02:19 -0700 Subject: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6 In-Reply-To: References: <7915CC9E-0B0F-41D4-9B79-7FCEBE2107B8@ee.ryerson.ca> <87egii3yl6.fsf@uwakimon.sk.tsukuba.ac.jp> <74744c9fe512b6fd6c6d88f0893e101b.squirrel@webmail.ee.ryerson.ca> <55E5E605.50208@msapiro.net> <87a8t63s4e.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <55E64A9B.2020303@msapiro.net> On 09/01/2015 12:16 PM, David Magda wrote: > On Tue, September 1, 2015 14:35, Stephen J. Turnbull wrote: >> Mark Sapiro writes: >> >> > I don't know what you are grepping, but if it's the mbox, you shouldn't >> > be looking for "\xea", you should be looking for "??". >> >> At least on recent BSD-based systems "\xea" is a well-defined escape >> sequence, interpreted as the hexadecimal representation of a byte. >> Dunno about GNU or proprietary systems. (POSIX.2) > > This is GNU grep under Debian. In my testing with GNU grep on Ubuntu 15.04, 'grep "\xea"' interprets \x as a literal x and therefore looks for the string "xea", not for the character whose hex value is EA. > We are running 2.1.13 from tarballs and so the Mailman code did not change > when the archive web page generation stopped. The only thing that changed > was the version of Python (2.5 -> 2.6?) under the OS. > > Doing a "arch --wipe mylist" seems to have solved the issue, though now > I'm curious to know why \xea was a problem before but suddenly isn't after > the wipe. Here's what I suspect was going on. Your first run of bin/arch encountered some non-ascii in a header and threw the exception, but not before writing bad data to the pipermail database for that month. You then "fixed" the non-ascii in the input mbox, but subsequent runs of bin/arch still encountered the bad data in the database when they got to that month. Finally, you added the --wipe option and that removed everythin and rebuilt from scratch and as there was no non-ascii in the mbox headers, it worked. As to why this didn't happen before, see my next reply. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Wed Sep 2 03:14:57 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 1 Sep 2015 18:14:57 -0700 Subject: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6 In-Reply-To: <97793451d21a7677057597440f6aa5bf.squirrel@webmail.ee.ryerson.ca> References: <7915CC9E-0B0F-41D4-9B79-7FCEBE2107B8@ee.ryerson.ca> <87egii3yl6.fsf@uwakimon.sk.tsukuba.ac.jp> <74744c9fe512b6fd6c6d88f0893e101b.squirrel@webmail.ee.ryerson.ca> <55E5E605.50208@msapiro.net> <97793451d21a7677057597440f6aa5bf.squirrel@webmail.ee.ryerson.ca> Message-ID: <55E64D91.8060707@msapiro.net> On 09/01/2015 12:09 PM, David Magda wrote: > > Could the new version of Python been chocking on a binary file whose > format has changed from the old version? Is it prudent to do an "arch > --wipe" when changing versions of Python? The exception is thrown in Python's sort() method. There are no documented changes in this method's calling sequence between Python 2.5 and 2.6, but it's quite possible there were changes in the details of the key comparison code that are responsible. No it is not prudent to do an "arch --wipe" when changing versions of Python?. It is not a good idea to ever do "arch --wipe" unless it's really necessary. See the section "NOTE ON MBOX ANOMALIES:" at . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From dmagda at ee.ryerson.ca Wed Sep 2 03:38:34 2015 From: dmagda at ee.ryerson.ca (David Magda) Date: Tue, 1 Sep 2015 21:38:34 -0400 Subject: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6 In-Reply-To: <55E64A9B.2020303@msapiro.net> References: <7915CC9E-0B0F-41D4-9B79-7FCEBE2107B8@ee.ryerson.ca> <87egii3yl6.fsf@uwakimon.sk.tsukuba.ac.jp> <74744c9fe512b6fd6c6d88f0893e101b.squirrel@webmail.ee.ryerson.ca> <55E5E605.50208@msapiro.net> <87a8t63s4e.fsf@uwakimon.sk.tsukuba.ac.jp> <55E64A9B.2020303@msapiro.net> Message-ID: <12CA65DE-AD11-4671-8386-5B08A6C4A9CA@ee.ryerson.ca> > On Sep 1, 2015, at 21:02, Mark Sapiro wrote: > > In my testing with GNU grep on Ubuntu 15.04, 'grep "\xea"' interprets \x > as a literal x and therefore looks for the string "xea", not for the > character whose hex value is EA. For the record/archives: GNU grep also as the ?-P? option, which allows Perl regexes (PCRE), and \xhh searches for characters with hex code hh (per pcrepattern(3)): http://stackoverflow.com/questions/3001177/ how-do-i-grep-for-all-non-ascii-characters-in-unix >> Doing a "arch --wipe mylist" seems to have solved the issue, though now >> I'm curious to know why \xea was a problem before but suddenly isn't after >> the wipe. > > > Here's what I suspect was going on. > > Your first run of bin/arch encountered some non-ascii in a header and > threw the exception, but not before writing bad data to the pipermail > database for that month. > > You then "fixed" the non-ascii in the input mbox, but subsequent runs of > bin/arch still encountered the bad data in the database when they got to > that month. > > Finally, you added the --wipe option and that removed everythin and > rebuilt from scratch and as there was no non-ascii in the mbox headers, > it worked. > > As to why this didn't happen before, see my next reply. Sounds plausible. From dmagda at ee.ryerson.ca Wed Sep 2 03:55:39 2015 From: dmagda at ee.ryerson.ca (David Magda) Date: Tue, 1 Sep 2015 21:55:39 -0400 Subject: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6 In-Reply-To: <55E64D91.8060707@msapiro.net> References: <7915CC9E-0B0F-41D4-9B79-7FCEBE2107B8@ee.ryerson.ca> <87egii3yl6.fsf@uwakimon.sk.tsukuba.ac.jp> <74744c9fe512b6fd6c6d88f0893e101b.squirrel@webmail.ee.ryerson.ca> <55E5E605.50208@msapiro.net> <97793451d21a7677057597440f6aa5bf.squirrel@webmail.ee.ryerson.ca> <55E64D91.8060707@msapiro.net> Message-ID: > On Sep 1, 2015, at 21:14, Mark Sapiro wrote: > > On 09/01/2015 12:09 PM, David Magda wrote: >> >> Could the new version of Python been chocking on a binary file whose >> format has changed from the old version? Is it prudent to do an "arch >> --wipe" when changing versions of Python? > > > The exception is thrown in Python's sort() method. There are no > documented changes in this method's calling sequence between Python 2.5 > and 2.6, but it's quite possible there were changes in the details of > the key comparison code that are responsible. > > No it is not prudent to do an "arch --wipe" when changing versions of > Python?. It is not a good idea to ever do "arch --wipe" unless it's > really necessary. See the section "NOTE ON MBOX ANOMALIES:" at > . The message in question seems to be from October 2005, and it has the "Subject: Voc? [?]? header. Running under Debian 5 (Python 2.5), archive processing wasn?t an issue: messages were coming into the mbox and the HTML page was being generated until August 25. I then did the upgrade on that day. The mbox then no longer has messages until September 1, the day when I did ?arch ?wipe?, even though the mail.log shows messages coming in (and going out AFAICT). So would there be anything besides a ??wipe? that could otherwise be done to prevent this archive breakage? Attempt a ?cleanarch" first? Seems strange that a message from 2005 could stop archive processing for current years/months. From mark at msapiro.net Wed Sep 2 04:43:28 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 1 Sep 2015 19:43:28 -0700 Subject: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6 In-Reply-To: References: <7915CC9E-0B0F-41D4-9B79-7FCEBE2107B8@ee.ryerson.ca> <87egii3yl6.fsf@uwakimon.sk.tsukuba.ac.jp> <74744c9fe512b6fd6c6d88f0893e101b.squirrel@webmail.ee.ryerson.ca> <55E5E605.50208@msapiro.net> <97793451d21a7677057597440f6aa5bf.squirrel@webmail.ee.ryerson.ca> <55E64D91.8060707@msapiro.net> Message-ID: <55E66250.6030207@msapiro.net> On 09/01/2015 06:55 PM, David Magda wrote: > > The message in question seems to be from October 2005, and it has the "Subject: Voc? [?]? header. Running under Debian 5 (Python 2.5), archive processing wasn?t an issue: messages were coming into the mbox and the HTML page was being generated until August 25. I then did the upgrade on that day. > > The mbox then no longer has messages until September 1, the day when I did ?arch ?wipe?, even though the mail.log shows messages coming in (and going out AFAICT). So what has probably happened is that archiving has been broken since the upgrade on Aug 25. There should be a an error message with traceback in Mailman's 'error' log for each message that wasn't archived. More importantly, the unarchived messages should all be in Mailman's 'shunt' queue and running Mailman's bin/unshunt should process them for the archive. > So would there be anything besides a ??wipe? that could otherwise be done to prevent this archive breakage? Attempt a ?cleanarch" first? Seems strange that a message from 2005 could stop archive processing for current years/months. Presumably, you did some kind of bin/arch process on Aug 25. The answer is don't do that. Or if you didn't do that, then the answer may lie in whatever changed in Python. You should never be running bin/arch without --wipe unless you are importing archives from elsewhere to be added to an existing archive, and even in that case, it might be preferable to stop Mailman, concatenate the existing Mailman mbox and import mbox into a combined mbox and run 'bin/arch --wipe'. Then after success, start Mailman again. You should also consider running the contrib/mmdsr script from the Mailman source distro or if not that, somehow looking a Mailman's error log frequently for problems to discover them sooner. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ryanadanderson at gmail.com Tue Sep 1 19:43:17 2015 From: ryanadanderson at gmail.com (Ryan Anderson) Date: Tue, 1 Sep 2015 13:43:17 -0400 Subject: [Mailman-Users] at Slayter 7pm TOMORROW Wed., FREE Beginner lesson, Live Band Message-ID: Why won't this message send to my group? I have sent things before, including a message that said "help" as the subject. I tried using "help" as a subject but it didn't go. What do you all see? Ryan ---------- Forwarded message ---------- From: Ryan Anderson Date: Tue, Sep 1, 2015 at 1:02 PM Subject: Swing at Slayter 7pm TOMORROW Wed., FREE Beginner lesson, Live Band To: "One List, Mass e-mail" *Purdue Night Train Weekly Update* Sorry for the email issue. There was a gremlin. It left. Everything is okay. Did you know the "help" command doesn't go in the subject of our group email system? Neither did Ryan. Whoops! CALLOUT TOMORROW! Wed. @ Slayter Hill 7pm Beginner Lesson Live Band Free FUN! Just try it. Bring a water bottle. Stay fresh. No experience, partner, or coordination required. *One day 20% off SALE! * *Unlimited lessons (Only $20) *That's about 5 pages of that textbook you just purchased. It'd say it's worth it. Questions? Ask them! *swingpurdue at gmail.com* If you miss the callout, don't worry. You can join us in lessons. --------------------------------------------------------------------- You should check the newspaper on Wednesday. No reason. None. --------------------------------------------------------------------- *LAST CALL, teachers!* Click here to show your interest. --------------------------------------------------------------------- Thanks to Funto, Ashley, Sierra, and Ryan for helping advertise on Sunday. They put in over 20 hours of labor! If you want to help advertise, join us tonight at 5pm in Stew G6 for more flyer/chalking fun. [image: Inline image 1] Events this Week The Last Big Chalking/Flyer-ing STEW G6 - 5 pm Help get more people in to the callout! Click the link above to join the event. *Lindy Bomb!** Wed. 5:10pm at the Engineering Fountain. [set up helpers (anyone who wants to help) meet at 4:45pm in Stew G6] Check the facebook group for more info. Drake will be heading it up. **Lindy Bomb - To swing dance as a group in a place where it is not normally done.* *Lesson/Callout* Slayter Hill - Wed. 7PM Try to arrive early. We're expecting a great turnout! Bring a bottle of water! P.S. Sorry if you receive this message more than once! The system has been super glitchy. From jason at fayre.me Tue Sep 1 21:32:32 2015 From: jason at fayre.me (Jason Fayre) Date: Tue, 1 Sep 2015 15:32:32 -0400 Subject: [Mailman-Users] integrating htdig with cpanel mailman Message-ID: <000d01d0e4ec$f28dabd0$d7a90370$@fayre.me> Hello, I'm attempting to get Mailman 2.1.20 working with htdig. I've installed the htdig patch for this version of Mailman from Mark's site. When I run a search from the archive pages, I get a blank page. I've seen others asking this, but have never seen a solution. I think I may have had this working a few years ago, but don't remember what I did to fix it. It broke when cpanel updated mailman. When I try running the mmsearch script by itself, I get the following error, which is expected as I under stand it: htdig Archives Access Failure CGI problem. -5-Field count -4- fields: If you want to make another attempt to access a list archive then go via the list users information page. If this problem persists then please e-mail the following information to the mailman at nfbnet.org: Referer not known /mailman/mmsearch/blparent_nfbnet.org Running the htsearch command by itself doesn't yield any results with a keyword and the short format. The version of htdig is 3.2.0b6. I noticed that there are patched versions of rundig and the nightly scripts on the patch site, but don't know if that applies to newer patches or not. Any help would be appreciated. From mark at msapiro.net Wed Sep 2 08:24:40 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 1 Sep 2015 23:24:40 -0700 Subject: [Mailman-Users] at Slayter 7pm TOMORROW Wed., FREE Beginner lesson, Live Band In-Reply-To: References: Message-ID: <55E69628.5020308@msapiro.net> On 09/01/2015 10:43 AM, Ryan Anderson wrote: > Why won't this message send to my group? I have sent things before, > including a message that said "help" as the subject. I tried using "help" > as a subject but it didn't go. What do you all see? > > Ryan > > ---------- Forwarded message ---------- > From: Ryan Anderson > Date: Tue, Sep 1, 2015 at 1:02 PM > Subject: Swing at Slayter 7pm TOMORROW Wed., FREE Beginner lesson, Live Band > To: "One List, Mass e-mail" (body snipped) I see your message. It is archived at which means it was processed by the list and sent out to the list members. I suspect the issue is the one described here . As far as messages to a list with subject "help" are concerned, if the list's administrivia attribute is set to Yes, messages that appear to be commands that should be sent to the -request address (e.g., nighttrain_onelist-request at lists.purdue.edu) will be held for approval. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From stephen at xemacs.org Wed Sep 2 08:31:51 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Wed, 02 Sep 2015 15:31:51 +0900 Subject: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6 In-Reply-To: References: <7915CC9E-0B0F-41D4-9B79-7FCEBE2107B8@ee.ryerson.ca> <87egii3yl6.fsf@uwakimon.sk.tsukuba.ac.jp> <74744c9fe512b6fd6c6d88f0893e101b.squirrel@webmail.ee.ryerson.ca> <55E5E605.50208@msapiro.net> <87a8t63s4e.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <87613t49ig.fsf@uwakimon.sk.tsukuba.ac.jp> David Magda writes: > Debian is fairly conservative about these things, Debian may be conservative, but individual maintainers vary. Cf. that OpenSSL patch fiasco. There was no excuse for that patch, the maintainer just thought he was smarter than the OpenSSL people. Mailman itself has spent a fair amount of time on questions that ended up being related to Debian patches (specifically the execrable mailman-to-postfix script, although that did at least have a good reason behind it from the point of view of the distro, it was very fragile but Debian saw no need to fix it). > and AFAIK, the OS default was to use UTF-8, either en_US or > en_CA. The locale did not change during the upgrade. OK, unless your old Debian was *really* old, that's very likely true and a locale change was not the source of any of the issues. > We are running 2.1.13 from tarballs Sorry, I confused your thread with somebody else's, then. At 2.1.13, don't you have any DMARC problems? Or do you just prohibit users from posting from p=reject addresses? > and so the Mailman code did not change when the archive web page > generation stopped. The only thing that changed was the version of > Python (2.5 -> 2.6?) under the OS. Python 2.5 was released in September 2006. That's long enough ago that I'm sure handling of Unicode and charsets changed significantly between then and the release of 2.6 in October 2008, although I'm not familiar with the details. In Python 2, str is "promoted" to unicode when operated on (eg, concatenation and comparison), but that is inherently fragile, and it's quite likely the rules (eg, default codecs and error handlers) changed between Python 2.5 and 2.6. Stability of the system is of course a concern, but you may want to consider installing python2.7 as an alternative (but *not* the system default), and pointing Mailman at that in setup.py. Going forward, it's unlikely that python2.7 will see more changes (barring a major security issue, there will be no more releases AFAIK), and Mailman 2.1.20 is very near the end of the line for Mailman 2, as well (but keep your fingers crossed against a Yahoo!-style email security debacle that DMARC doesn't handle -- who knows what the freemail services might come up with in that scenario :-( ). > Doing a "arch --wipe mylist" seems to have solved the issue, though > now I'm curious to know why \xea was a problem before but suddenly > isn't after the wipe. I expect Mark's explanation is correct, that without --wipe you had an existing partial archive and processing that is where the error occurred. From mark at msapiro.net Wed Sep 2 09:03:43 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 2 Sep 2015 00:03:43 -0700 Subject: [Mailman-Users] integrating htdig with cpanel mailman In-Reply-To: <000d01d0e4ec$f28dabd0$d7a90370$@fayre.me> References: <000d01d0e4ec$f28dabd0$d7a90370$@fayre.me> Message-ID: <55E69F4F.6050306@msapiro.net> On 09/01/2015 12:32 PM, Jason Fayre wrote: > Hello, > I'm attempting to get Mailman 2.1.20 working with htdig. > I've installed the htdig patch for this version of Mailman from Mark's site. I'd be surprised if this doesn't have conflicts with cPanel's mods. What happened when you ran patch? were there any rejects? > When I run a search from the archive pages, I get a blank page. > I've seen others asking this, but have never seen a solution. > I think I may have had this working a few years ago, but don't remember what > I did to fix it. It broke when cpanel updated mailman. Not surprising. cPanel's mailman has many patches of its own, mostly because of the list name = name_domain feature to allow lists of the same 'name' in different domains. > When I try running the mmsearch script by itself, I get the following error, > which is expected as I under stand it: > htdig Archives Access Failure > CGI problem. -5-Field count -4- fields: Yes, this is expected. You could try going to a URL like > If you want to make another attempt to access a list archive then go via the > list users information page. > > If this problem persists then please e-mail the following information to the > mailman at nfbnet.org: > Referer not known > /mailman/mmsearch/blparent_nfbnet.org The above is not familiar to me. It may be a cPanel thing. > Running the htsearch command by itself doesn't yield any results with a > keyword and the short format. Do you specify the -c option with an appropriate config file? > The version of htdig is 3.2.0b6. I noticed that there are patched versions > of rundig and the nightly scripts on the patch site, but don't know if that > applies to newer patches or not. Those patches allow the nightly update to do an update rather than a complete rebuild of the htdig search index. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From lac at openend.se Wed Sep 2 09:30:50 2015 From: lac at openend.se (Laura Creighton) Date: Wed, 02 Sep 2015 09:30:50 +0200 Subject: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6 In-Reply-To: <87613t49ig.fsf@uwakimon.sk.tsukuba.ac.jp> References: <7915CC9E-0B0F-41D4-9B79-7FCEBE2107B8@ee.ryerson.ca> <87egii3yl6.fsf@uwakimon.sk.tsukuba.ac.jp> <74744c9fe512b6fd6c6d88f0893e101b.squirrel@webmail.ee.ryerson.ca> <55E5E605.50208@msapiro.net> <87a8t63s4e.fsf@uwakimon.sk.tsukuba.ac.jp> <87613t49ig.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <201509020730.t827UoBL032055@fido.openend.se> If some code has from __future__ import unicode_literals that might go a long way to explaining things. see: see: https://docs.python.org/2/whatsnew/2.6.html From ricardo.rodriguez at idisantiago.es Wed Sep 2 11:32:53 2015 From: ricardo.rodriguez at idisantiago.es (=?UTF-8?Q?=5BIDIS_Technical_Secretariat=5D_Ricardo_Rodr=C3=ADguez?=) Date: Wed, 2 Sep 2015 11:32:53 +0200 Subject: [Mailman-Users] {Disarmed} Re: importing archived Maildir email lists into Mailman lists archives In-Reply-To: <55E4FB88.7080408@msapiro.net> References: <55E265E9.3040305@msapiro.net> <55E4FB88.7080408@msapiro.net> Message-ID: Thanks for the answer! Please, read below... On Tue, Sep 1, 2015 at 3:12 AM, Mark Sapiro wrote: > On 08/31/2015 05:58 AM, [IDIS Technical Secretariat] Ricardo Rodr?guez > wrote: > > > > This has been more or less my entry point to this issue. Perhaps I've > > not been able to explain the issue correctly or I'm missing something. > > What I'm looking to move into mbox is a set of archives of Maildir > > mailing lists. > > > Why do you refer to these archives as being of Maildir mailing lists? > What is the actual software that created them. > > The original sentence I got from the provider said, translated to English: the format is vpopmail (qmail - courier). I must recognise that I'm not able to reconstruct the pathway that has led me to say that we were using Maildir. Ezmlm was the actual software that created that lists. Both, regular maildir account subfolders and ezmlm subfolders are stored in the same folder in the archives structure. I think this was the reason why I interpreted all of them are Maildir subfolders. > Those archives don't contain new, cur and tmp folders all > > the scripts I've spotted at looked for. This is the structure of each > > archived email list folder I have here... > > > > Ricardo-Rodriguezs-Mac-Pro:r.users rrodriguez$ ls > > Log bounce digissue headerremove lock > mod outlocal remote > > allow bouncer dignum indexed > lockbounce modsub owner subscribers > > archive config editor inlocal > mailinglist num prefix text > > archived digest headeradd key manager > outhost public tstdig > > > > > > Within /archive, there are two folders, 0 and 1, with a number of files, > > each of them containing one message, and an index file. > > > This looks vaguely like Maildir, except Maildir has no index file. What > is in the index file(s)? What is the difference between 0 and 1? Do they > each contain some complete (including all headers) messages, i.e. each > contains a set of messages that combined are all the messages, or does > one of them contain message headers and the other bodies, or does one > contain messages and the other contain metadata about the messages? > Here you can access to the whole structure of one of the subfolders... http://datasource.idisantiago.es/r.users/ Here the indexes of subfolders 0 and 1 (ISO Latin 1 encoding required for a correct rendering of all the characters)... http://datasource.idisantiago.es/r.users/archive/0/index http://datasource.idisantiago.es/r.users/archive/1/index It looks like each subfolder in the row within /archive holds a maximum of 100 messages numbered from 0 to 99. Each file within subfolders 0 and 1 contains a complete message, including attachments (this is a guess, as files' size ranges from few Kbs to several Mbs). > > > > Please, does this made sense for you? Am I completely lost? How could I > > deal with this "archives" to move them to mbox files and get them > > imported our brand new Mailman server? > > > You just need to add a *nix From_ separator to the beginning of each > complete message and concatenate them. > > If you can show me what's actually in some of those files, I could > The link above gives access to a whole subfolder! > possibly create a conversion script for you. > > It could be as simple as something like > > cat archives/0/* archives/1/* > mbox > > except for the index files, but probably not. > I founded this... [Mailman-Users] Moving to mailman from ezmlm https://mail.python.org/pipermail/mailman-users/2003-November/032591.html [Mailman-Users] Migrate from EZMLM to Mailman https://mail.python.org/pipermail/mailman-users/2012-November/074408.html But I'm afraid I have been not able to find any message with more detailed information. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > Once again: thank you for your help and, please, accept my apologies if I'm not able to provide accurate and clear information about the issue: at least for me, it is by no means easy to sail this sea plenty of different standards! All the best, Ricardo -- Ricardo Rodr?guez Research Management and Promotion Technician Technical Secretariat Health Research Institute of Santiago de Compostela (IDIS) http://www.idisantiago.es From andrew at hodgsonfamily.org Wed Sep 2 11:43:09 2015 From: andrew at hodgsonfamily.org (Andrew Hodgson) Date: Wed, 2 Sep 2015 09:43:09 +0000 Subject: [Mailman-Users] {Disarmed} Re: importing archived Maildir email lists into Mailman lists archives In-Reply-To: References: <55E265E9.3040305@msapiro.net> <55E4FB88.7080408@msapiro.net>, Message-ID: [IDIS Technical Secretariat] Ricardo Rodr?guez wrote: [...] >> > Ricardo-Rodriguezs-Mac-Pro:r.users rrodriguez$ ls >> > Log bounce digissue headerremove lock >> mod outlocal remote >> > allow bouncer dignum indexed That's Ezmlm. Have you tried something like this: http://www.arctic.org/~dean/scripts/ezmlm2mbox Get your Ezmlm archives to Mbox then that can be used as the basis for the Mailman archive. Andrew. From ricardo.rodriguez at idisantiago.es Wed Sep 2 11:45:32 2015 From: ricardo.rodriguez at idisantiago.es (=?UTF-8?Q?=5BIDIS_Technical_Secretariat=5D_Ricardo_Rodr=C3=ADguez?=) Date: Wed, 2 Sep 2015 11:45:32 +0200 Subject: [Mailman-Users] importing archived Maildir email lists into Mailman lists archives In-Reply-To: <87oahn3pho.fsf@uwakimon.sk.tsukuba.ac.jp> References: <55E265E9.3040305@msapiro.net> <87oahn3pho.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: Thanks for your reply! Please, read below! On Tue, Sep 1, 2015 at 3:19 AM, Stephen J. Turnbull wrote: > [IDIS Technical Secretariat] Ricardo Rodr?guez writes: > > Thanks Mark, all, > > > > On Sun, Aug 30, 2015 at 4:09 AM, Mark Sapiro wrote: > > > > > On 08/28/2015 12:52 AM, [IDIS Technical Secretariat] Ricardo Rodr?guez > > > wrote: > > > > > > > > I have a number of Maildir format mailing lists archives > > No, you don't have Maildir, at least not "Maildir" as most of the > Internet understands it. Here's what Dan Bernstein (the inventor or > at least popularizer of Maildir) says: > > Can a maildir contain more than tmp, new, cur? > > Yes: > .qmail: used to do direct deliveries with qmail-local. > bulletintime: empty file, used by system-wide bulletin programs. > bulletinlock: empty file, used by system-wide bulletin programs. > seriallock: empty file, used to serialize AutoTURN. > > > Ricardo-Rodriguezs-Mac-Pro:r.users rrodriguez$ ls > > Log bounce digissue headerremove lock mod outlocal remote > > "Lock" -- no, this isn't Maildir. The whole point of Maildir is that > you don't need locks because reading and writing are done in different > directories, and changes happen atomically. (This can even work with > editing.) > That's now far clear for me! As stated in a previous message replying to a Mark's post, I make a mess interpreting wrongly several messages from our services provider and some googled information. Ezmlm was behind the scene. Sorry for the misinformation! > > > allow bouncer dignum indexed lockbounce modsub owner subscribers > > archive config editor inlocal mailinglist num prefix text > > archived digest headeradd key manager outhost public tstdig > > > > Within /archive, there are two folders, 0 and 1, with a number of files, > > each of them containing one message, and an index file. > > > > Please, does this made sense for you? > > I don't recall anything like that. Please try to find an explanation > of the structure in the system documentation, or ask the vendor. > However, since you think they're "Maildir", probably what is meant is > that they have a structure that is one message per file rather than > many messages per file. You probably just need to figure out how to > get the order of messages right, then concatenate the messages. > > That's correct: messages are stored in separated files ordered in subfolders named with a series from 0 onward. 0, 1... each subfolder holds one hundred files, each of them with a complete message. I think the global order could be provided by the subfolder order plus the name of each file within a subfolder. Mark's reply contents a simple line to get some concatenation. I'll play with this idea and report back! > Most likely, all you need for each list are the archive folders and > the single messages, and maybe the index file will be of some use > depending on what it contains. If your documentation and/or the old > vendor are of no help, see if you can find a whole message file you > can send to us *as a file attachment* -- we want to see what headers > are included (it probably doesn't really matter, though, except for > the "Unix From_" which they probably don't have). If for privacy > reasons you don't want to broadcast any message on a public mailing > list, you can send it to Mark and me personally. Also it may be > helpful to figure out the rule for the folders whose names are > numbers: are they the leading digits where files are named 000 to 999? > Are they months? Years? etc. > Most lists are public, so privacy is not a concern! You can find here the complete folders' structure for one of the lists... http://datasource.idisantiago.es/r.users/ > > > Am I completely lost? > > No, of course not. Just don't delete anything until you're sure the > new system is working. I did qualify everything with "probably", it > may take a couple of guesses to get it right. :-) > > Thanks for your help! Ricardo -- Ricardo Rodr?guez Research Management and Promotion Technician Technical Secretariat Health Research Institute of Santiago de Compostela (IDIS) http://www.idisantiago.es From adam-mailman at amyl.org.uk Wed Sep 2 12:15:43 2015 From: adam-mailman at amyl.org.uk (Adam McGreggor) Date: Wed, 2 Sep 2015 11:15:43 +0100 Subject: [Mailman-Users] at Slayter 7pm TOMORROW Wed., FREE Beginner lesson, Live Band In-Reply-To: References: Message-ID: <20150902101543.GN9573@hendricks.amyl.org.uk> On Tue, Sep 01, 2015 at 01:43:17PM -0400, Ryan Anderson wrote: > Why won't this message send to my group? I have sent things before, > including a message that said "help" as the subject. I tried using "help" > as a subject but it didn't go. What do you all see? Is it a case of that wonderful gmail feature: https://support.google.com/mail/answer/6588 > ---------- Forwarded message ---------- > From: Ryan Anderson > Date: Tue, Sep 1, 2015 at 1:02 PM > Subject: Swing at Slayter 7pm TOMORROW Wed., FREE Beginner lesson, Live Band > To: "One List, Mass e-mail" -- "Cabbage-- the opinions of taxi drivers." (new definitions, from `I'm Sorry I Haven't a Clue') From ricardo.rodriguez at idisantiago.es Wed Sep 2 12:45:26 2015 From: ricardo.rodriguez at idisantiago.es (=?UTF-8?Q?=5BIDIS_Technical_Secretariat=5D_Ricardo_Rodr=C3=ADguez?=) Date: Wed, 2 Sep 2015 12:45:26 +0200 Subject: [Mailman-Users] {Disarmed} Re: importing archived Maildir email lists into Mailman lists archives In-Reply-To: References: <55E265E9.3040305@msapiro.net> <55E4FB88.7080408@msapiro.net> Message-ID: Thanks! It worked like a charm for at least two of our old mailing lists! Script, ezmlm structure and mbox output keeps stored at... http://datasource.idisantiago.es ... for easier reference. Now, I only have to import that mbox contents into the actual list. I guess this is the right path... 5.1. How do I import an archive into a new mailing list? http://wiki.list.org/DOC/How%20do%20I%20import%20an%20archive%20into%20a%20new%20mailing%20list%3F Thank you so much for all your support! Cheers, Ricardo On Wed, Sep 2, 2015 at 11:43 AM, Andrew Hodgson wrote: > [IDIS Technical Secretariat] Ricardo Rodr?guez wrote: > > [...] > > >> > Ricardo-Rodriguezs-Mac-Pro:r.users rrodriguez$ ls > >> > Log bounce digissue headerremove lock > >> mod outlocal remote > >> > allow bouncer dignum indexed > > That's Ezmlm. Have you tried something like this: > > http://www.arctic.org/~dean/scripts/ezmlm2mbox > > Get your Ezmlm archives to Mbox then that can be used as the basis for the > Mailman archive. > > Andrew. -- Ricardo Rodr?guez Research Management and Promotion Technician Technical Secretariat Health Research Institute of Santiago de Compostela (IDIS) http://www.idisantiago.es From andrew at hodgsonfamily.org Wed Sep 2 13:03:59 2015 From: andrew at hodgsonfamily.org (Andrew Hodgson) Date: Wed, 2 Sep 2015 11:03:59 +0000 Subject: [Mailman-Users] {Disarmed} Re: importing archived Maildir email lists into Mailman lists archives In-Reply-To: References: <55E265E9.3040305@msapiro.net> <55E4FB88.7080408@msapiro.net> , Message-ID: [IDIS Technical Secretariat] Ricardo Rodr?guez wrote: [...] >Thanks! It worked like a charm for at least two of our old mailing lists! Script, ezmlm structure and mbox output keeps stored at... > >http://datasource.idisantiago.es > >... for easier reference. > >Now, I only have to import that mbox contents into the actual list. I guess this is the right path... > >5.1. How do I import an archive into a new mailing list? >http://wiki.list.org/DOC/How%20do%20I%20import%20an%20archive%20into%20a%20new%20mailing%20list%3F Yup, this is similar to what I did. I recommend running cleanarch on that mbox before importing it, to ensure that it is ok. I took the second option in that FAQ, as it was a new list. Copy the Mbox file into the private directory after running it through cleanarch, then run the arch command to generate the HTML archives for the web interface. Andrew. From ricardo.rodriguez at idisantiago.es Wed Sep 2 13:30:21 2015 From: ricardo.rodriguez at idisantiago.es (=?UTF-8?Q?=5BIDIS_Technical_Secretariat=5D_Ricardo_Rodr=C3=ADguez?=) Date: Wed, 2 Sep 2015 13:30:21 +0200 Subject: [Mailman-Users] {Disarmed} Re: importing archived Maildir email lists into Mailman lists archives In-Reply-To: References: <55E265E9.3040305@msapiro.net> <55E4FB88.7080408@msapiro.net> Message-ID: Thanks! Please, read below... On Wed, Sep 2, 2015 at 1:03 PM, Andrew Hodgson wrote: > [IDIS Technical Secretariat] Ricardo Rodr?guez wrote: > > [...] > > >Thanks! It worked like a charm for at least two of our old mailing lists! > Script, ezmlm structure and mbox output keeps stored at... > > > >http://datasource.idisantiago.es > > > >... for easier reference. > > > >Now, I only have to import that mbox contents into the actual list. I > guess this is the right path... > > > >5.1. How do I import an archive into a new mailing list? > > > http://wiki.list.org/DOC/How%20do%20I%20import%20an%20archive%20into%20a%20new%20mailing%20list%3F > > Yup, this is similar to what I did. I recommend running cleanarch on that > mbox before importing it, to ensure that it is ok. I took the second > option in that FAQ, as it was a new list. Copy the Mbox file into the > private directory after running it through cleanarch, then run the arch > command to generate the HTML archives for the web interface. > > Andrew. Before going ahead, there is one thing I'm curious about as I don't understand it. Please, why does the path to the mbox file include .mbox twice? Here... http://wiki.list.org/DOC/How%20do%20I%20import%20an%20archive%20into%20a%20new%20mailing%20list%3F It reads... archives/private/.mbox/.mbox Thanks! Ricardo -- Ricardo Rodr?guez Research Management and Promotion Technician Technical Secretariat Health Research Institute of Santiago de Compostela (IDIS) http://www.idisantiago.es From lac at openend.se Wed Sep 2 14:10:23 2015 From: lac at openend.se (Laura Creighton) Date: Wed, 02 Sep 2015 14:10:23 +0200 Subject: [Mailman-Users] Wonderful gmail (was: at Slayter 7pm TOMORROW Wed., FREE Beginner lesson, Live Band) In-Reply-To: <20150902101543.GN9573@hendricks.amyl.org.uk> References: <20150902101543.GN9573@hendricks.amyl.org.uk> Message-ID: <201509021210.t82CANab005089@fido.openend.se> In a message of Wed, 02 Sep 2015 11:15:43 +0100, Adam McGreggor writes: >Is it a case of that wonderful gmail feature: > > https://support.google.com/mail/answer/6588 Gmail doesn't give android users the ability to send plain text emails. The desktop users are supposed to be able to, but it does not work properly. As happened recently to me, let us say you are a brand new would-be python programmer who has a posted some complicated code to the list, complaining that it 'doesn't work' (give the correct answer). I read the thing and notice that you are removing elements from the list you are iterating over, and reply. Simplified, you have this problem: >>> mylist = [1, 2, 3, 4] >>> for i in mylist: ... mylist.pop() >>> print mylist [1, 2] You need to make a copy of your list and iteratre over that. >>> import copy >>> mylist = [1, 2, 3, 4] >>> mylistcopy = copy.copy(mylist) >>> for i in mylistcopy: ... mylist.pop() >>> print mylist [] Note the series of lines beginning with '>>>' Despite the fact that I sent the mail in plain text, and the gmail user is also sending mail in plain text, _Gmail reserves the right to reflow all the lines you are quoting which begin with some number of '>'._ The conversation immediately goes to utter confusion, as people can no longer paste in 'exactly what happened when I tried this at the console' any more. (Well, you can. Only flush to the margin matters, so my PS1 prompt is now ' >>>'. But all the python users on this planet should not have to change their PS1 prompts because Google just cannot leave 'plain text' alone. But we may be at 'friends don't let friends use gmail' time, if not right now, then fairly soon. Exactly how many things can you do to break mail, Google? Laura From rsk at gsp.org Wed Sep 2 14:25:49 2015 From: rsk at gsp.org (Rich Kulawiec) Date: Wed, 2 Sep 2015 08:25:49 -0400 Subject: [Mailman-Users] Wonderful gmail (was: at Slayter 7pm TOMORROW Wed., FREE Beginner lesson, Live Band) In-Reply-To: <201509021210.t82CANab005089@fido.openend.se> References: <20150902101543.GN9573@hendricks.amyl.org.uk> <201509021210.t82CANab005089@fido.openend.se> Message-ID: <20150902122549.GA29109@gsp.org> On Wed, Sep 02, 2015 at 02:10:23PM +0200, Laura Creighton wrote: > But we may be at 'friends don't let friends use gmail' time, if > not right now, then fairly soon. Exactly how many things can you > do to break mail, Google? I (a) strongly concur with this and (b) will add that this sentiment also applies to MSN/Hotmail, Yahoo, and, sadly [1], AOL. ---rsk [1] Why "sadly"? Because some years ago Carl Hutzler and his team managed to fight an uphill battle against AOL management apathy and cluelessness, and made significant progress toward the goal of making AOL's mail service a quality operation. AOL welcomed this success by dismissing the entire team and the slide back into incompetence and negligence began almost immediately. Not that I agreed with everything Carl et.al. did, because I didn't; but I recognized that they had good intentions and they worked hard. To see all that effort discarded is appalling. From jason at fayre.me Wed Sep 2 15:22:49 2015 From: jason at fayre.me (Jason Fayre) Date: Wed, 2 Sep 2015 09:22:49 -0400 Subject: [Mailman-Users] integrating htdig with cpanel mailman In-Reply-To: <55E69F4F.6050306@msapiro.net> References: <000d01d0e4ec$f28dabd0$d7a90370$@fayre.me> <55E69F4F.6050306@msapiro.net> Message-ID: <002201d0e582$76e431c0$64ac9540$@fayre.me> Hello, I do not get any rejects when applying the patch. I did pass the config file for the list to htsearch with the -c option. Any other ideas? How are people typically handling archive search? I know I could use mail-archive, but would rather handle things on our end if we can. Occasionally we need to remove messages from the archives and not sure how easy that is with mail-archive. -----Original Message----- From: Mailman-Users [mailto:mailman-users-bounces+jason=fayre.me at python.org] On Behalf Of Mark Sapiro Sent: Wednesday, September 02, 2015 3:04 AM To: mailman-users at python.org Subject: Re: [Mailman-Users] integrating htdig with cpanel mailman On 09/01/2015 12:32 PM, Jason Fayre wrote: > Hello, > I'm attempting to get Mailman 2.1.20 working with htdig. > I've installed the htdig patch for this version of Mailman from Mark's site. I'd be surprised if this doesn't have conflicts with cPanel's mods. What happened when you ran patch? were there any rejects? > When I run a search from the archive pages, I get a blank page. > I've seen others asking this, but have never seen a solution. > I think I may have had this working a few years ago, but don't > remember what I did to fix it. It broke when cpanel updated mailman. Not surprising. cPanel's mailman has many patches of its own, mostly because of the list name = name_domain feature to allow lists of the same 'name' in different domains. > When I try running the mmsearch script by itself, I get the following > error, which is expected as I under stand it: > htdig Archives Access Failure > CGI problem. -5-Field count -4- fields: Yes, this is expected. You could try going to a URL like > If you want to make another attempt to access a list archive then go > via the list users information page. > > If this problem persists then please e-mail the following information > to the > mailman at nfbnet.org: > Referer not known > /mailman/mmsearch/blparent_nfbnet.org The above is not familiar to me. It may be a cPanel thing. > Running the htsearch command by itself doesn't yield any results with > a keyword and the short format. Do you specify the -c option with an appropriate config file? > The version of htdig is 3.2.0b6. I noticed that there are patched > versions of rundig and the nightly scripts on the patch site, but > don't know if that applies to newer patches or not. Those patches allow the nightly update to do an update rather than a complete rebuild of the htdig search index. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users at 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/jason%40fayre.me From dmagda at ee.ryerson.ca Wed Sep 2 16:31:04 2015 From: dmagda at ee.ryerson.ca (David Magda) Date: Wed, 2 Sep 2015 10:31:04 -0400 Subject: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6 In-Reply-To: <55E66250.6030207@msapiro.net> References: <7915CC9E-0B0F-41D4-9B79-7FCEBE2107B8@ee.ryerson.ca> <87egii3yl6.fsf@uwakimon.sk.tsukuba.ac.jp> <74744c9fe512b6fd6c6d88f0893e101b.squirrel@webmail.ee.ryerson.ca> <55E5E605.50208@msapiro.net> <97793451d21a7677057597440f6aa5bf.squirrel@webmail.ee.ryerson.ca> <55E64D91.8060707@msapiro.net> <55E66250.6030207@msapiro.net> Message-ID: <07b60f749fdc5b6102e8e9336fd60b04.squirrel@webmail.ee.ryerson.ca> On Tue, September 1, 2015 22:43, Mark Sapiro wrote: > On 09/01/2015 06:55 PM, David Magda wrote: >> >> The message in question seems to be from October 2005, and it has the >> "Subject: Voc? [ ]? header. Running under Debian 5 (Python 2.5), archive >> processing wasn?t an issue: messages were coming into the mbox and the >> HTML page was being generated until August 25. I then did the upgrade on >> that day. >> >> The mbox then no longer has messages until September 1, the day when I >> did ?arch ?wipe?, even though the mail.log shows messages coming in (and >> going out AFAICT). > > > So what has probably happened is that archiving has been broken since > the upgrade on Aug 25. There should be a an error message with traceback > in Mailman's 'error' log for each message that wasn't archived. More > importantly, the unarchived messages should all be in Mailman's 'shunt' > queue and running Mailman's bin/unshunt should process them for the > archive. The last error message that is in the 'error' log is from Aug 24: mailman at mail1:~$ ls -lrth logs/ total 16M -rw-rw-r-- 1 mailman mailman 1.2K Mar 2 2014 fromusenet -rw-rw-r-- 1 mailman mailman 63K Mar 18 09:57 locks -rw-rw-r-- 1 www-data mailman 3.1K Mar 31 18:04 mischief -rw-rw-r-- 1 mailman mailman 808K Aug 24 08:00 smtp-failure -rw-rw-r-- 1 mailman mailman 354K Aug 24 08:14 bounce -rw-rw-r-- 1 www-data mailman 1.1M Aug 24 13:14 error -rw-rw-r-- 1 mailman mailman 584K Aug 31 10:45 qrunner -rw-rw-r-- 1 www-data mailman 1.6M Sep 1 12:09 vette -rw-rw-r-- 1 www-data mailman 278K Sep 2 09:03 subscribe -rw-rw-r-- 1 mailman mailman 3.8M Sep 2 09:48 smtp -rw-rw-r-- 1 mailman mailman 2.7M Sep 2 09:48 post >> So would there be anything besides a ??wipe? that could otherwise be >> done to prevent this archive breakage? Attempt a ?cleanarch" first? >> Seems strange that a message from 2005 could stop archive processing for >> current years/months. > > Presumably, you did some kind of bin/arch process on Aug 25. The answer > is don't do that. Or if you didn't do that, then the answer may lie in > whatever changed in Python. Not that I'm aware of, unless the Debian package runs it in some way pre-/post-upgrade. I didn't start looking at bin/arch until I noticed the breakage. > You should never be running bin/arch without --wipe unless you are > importing archives from elsewhere to be added to an existing archive, > and even in that case, it might be preferable to stop Mailman, > concatenate the existing Mailman mbox and import mbox into a combined > mbox and run 'bin/arch --wipe'. Then after success, start Mailman again. > > You should also consider running the contrib/mmdsr script from the > Mailman source distro or if not that, somehow looking a Mailman's error > log frequently for problems to discover them sooner. We have a few more hosts to upgrade, so I'll have to look more closely at this. However some of these hosts have quite a few lists, so I'm not sure how practical it will be examine every one to see if they're working properly. From mark at msapiro.net Wed Sep 2 17:16:56 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 2 Sep 2015 08:16:56 -0700 Subject: [Mailman-Users] importing archived Maildir email lists into Mailman lists archives In-Reply-To: References: <55E265E9.3040305@msapiro.net> <55E4FB88.7080408@msapiro.net> Message-ID: <55E712E8.2090105@msapiro.net> On 09/02/2015 04:30 AM, [IDIS Technical Secretariat] Ricardo Rodr?guez wrote: > > Before going ahead, there is one thing I'm curious about as I don't > understand it. Please, why does the path to the mbox file > include .mbox twice? Here... > > http://wiki.list.org/DOC/How%20do%20I%20import%20an%20archive%20into%20a%20new%20mailing%20list%3F > > It reads... > > archives/private/.mbox/.mbox That's just the way Mailman does it. archives/private/ contains two directories per list. The archives/private// directory contains the full pipermail archive (various files and directories) and The archives/private/.mbox/ directory contains the cumulative archive mbox file also named .mbox. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From andrew at hodgsonfamily.org Wed Sep 2 13:57:14 2015 From: andrew at hodgsonfamily.org (Andrew Hodgson) Date: Wed, 2 Sep 2015 11:57:14 +0000 Subject: [Mailman-Users] {Disarmed} Re: importing archived Maildir email lists into Mailman lists archives In-Reply-To: References: <55E265E9.3040305@msapiro.net> <55E4FB88.7080408@msapiro.net> , Message-ID: [IDIS Technical Secretariat] Ricardo Rodr?guez wrote: > >Before going ahead, there is one thing I'm curious about as I don't understand it. Please, why does the path to the mbox file include .mbox twice? Here... > >http://wiki.list.org/DOC/How%20do%20I%20import%20an%20archive%20into%20a%20new%20mailing%20list%3F > >It reads... > >archives/private/.mbox/.mbox Yup, the file needs to be called listname.mbox in the directory ~/archives/private/listname.mbox. So for example, to copy the mailman-users archive into your home directory, assuming Mailman was installed in the default location, you would enter a command like: cp /usr/local/mailman/private/mailman-users.mbox/mailman-users.mbox ~ That would give you a file called mailman-users.mbox in your home directory with all the archives in mbox format. If your list is new then after running cleanarch on that mbox file, I would copy it to ~archives/private/listname.mbox/listname.mbox, ensure perms are correct by running check_perms, then run arch with the wipe parameter to build all the HTML indexes for the web pages. If you have a list already, I would stop Mailman, then cat the mbox file in place at the location ~archives/private/listname.mbox/listname.mbox to a copy of your converted archives. I would then run cleanarch on the resulting file, then put that in place in ~archives/private/listname.mbox/listname.mbox before checking perms and running arch with the wipe parameter. Hope this clears things up for you. Andrew. From mark at msapiro.net Wed Sep 2 17:46:07 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 2 Sep 2015 08:46:07 -0700 Subject: [Mailman-Users] integrating htdig with cpanel mailman In-Reply-To: <002201d0e582$76e431c0$64ac9540$@fayre.me> References: <000d01d0e4ec$f28dabd0$d7a90370$@fayre.me> <55E69F4F.6050306@msapiro.net> <002201d0e582$76e431c0$64ac9540$@fayre.me> Message-ID: <55E719BF.6040708@msapiro.net> On 09/02/2015 06:22 AM, Jason Fayre wrote: > Hello, > I do not get any rejects when applying the patch. > I did pass the config file for the list to htsearch with the -c option. > Any other ideas? The attached htsearch.txt is a transcript of an htsearch interaction on my system. If you do the same do you get similar output? If not, your htdig installation is broken. > How are people typically handling archive search? I know I could use > mail-archive, but would rather handle things on our end if we can. I use htdig with Richard Barrett's patches as forward ported by me. Other suggestions are in the FAQ at . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -------------- next part -------------- mark at sbh16:~$ /opt/www/cgi-bin/htsearch -c /var/lib/mailman/archives/htdig/mailman.conf Enter value for words: two words Content-type: text/html Enter value for format: short No match for '(two or twos) and (words or word or worded or wording or wordings)'

ht://Dig Search results


No matches were found for '(two or twos) and (words or word or worded or wording or wordings)'

Check the spelling of the search word(s) you used. If the spelling is correct and you only used one word, try using one or more similar search words with "Any."

If the spelling is correct and you used more than one word with "Any," try using one or more similar search words with "Any."

If the spelling is correct and you used more than one word with "All," try using one or more of the same words with "Any."


Match: Format: Sort by:
Refine search:

ht://Dig 3.2.0b6 mark at sbh16:~$ From jason at fayre.me Wed Sep 2 17:54:30 2015 From: jason at fayre.me (Jason Fayre) Date: Wed, 2 Sep 2015 11:54:30 -0400 Subject: [Mailman-Users] integrating htdig with cpanel mailman In-Reply-To: <55E719BF.6040708@msapiro.net> References: <000d01d0e4ec$f28dabd0$d7a90370$@fayre.me> <55E69F4F.6050306@msapiro.net> <002201d0e582$76e431c0$64ac9540$@fayre.me> <55E719BF.6040708@msapiro.net> Message-ID: <002a01d0e597$a76a7a60$f63f6f20$@fayre.me> Ok, I will try that. What version of htdig are you running? -----Original Message----- From: Mark Sapiro [mailto:mark at msapiro.net] Sent: Wednesday, September 02, 2015 11:46 AM To: Jason Fayre ; mailman-users at python.org Subject: Re: [Mailman-Users] integrating htdig with cpanel mailman On 09/02/2015 06:22 AM, Jason Fayre wrote: > Hello, > I do not get any rejects when applying the patch. > I did pass the config file for the list to htsearch with the -c option. > Any other ideas? The attached htsearch.txt is a transcript of an htsearch interaction on my system. If you do the same do you get similar output? If not, your htdig installation is broken. > How are people typically handling archive search? I know I could use > mail-archive, but would rather handle things on our end if we can. I use htdig with Richard Barrett's patches as forward ported by me. Other suggestions are in the FAQ at . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Wed Sep 2 18:30:30 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 2 Sep 2015 09:30:30 -0700 Subject: [Mailman-Users] integrating htdig with cpanel mailman In-Reply-To: <002a01d0e597$a76a7a60$f63f6f20$@fayre.me> References: <000d01d0e4ec$f28dabd0$d7a90370$@fayre.me> <55E69F4F.6050306@msapiro.net> <002201d0e582$76e431c0$64ac9540$@fayre.me> <55E719BF.6040708@msapiro.net> <002a01d0e597$a76a7a60$f63f6f20$@fayre.me> Message-ID: <55E72426.8030101@msapiro.net> On 09/02/2015 08:54 AM, Jason Fayre wrote: > Ok, I will try that. > What version of htdig are you running? 3.2.0b6 with the rundig.0 patch from and with this patch the source of which I no longer remember and can't find. RCS file: /cvsroot/htdig/htdig/htsearch/Collection.h,v retrieving revision 1.4 diff -r1.4 Collection.h 39c39 < void Collection::Open(); --- > void Open(); 41c41 < void Collection::Close(); --- > void Close(); Also, in an earlier reply I wrote: >> If you want to make another attempt to access a list archive then go via the >> list users information page. >> >> If this problem persists then please e-mail the following information to the >> mailman at nfbnet.org: >> Referer not known >> /mailman/mmsearch/blparent_nfbnet.org > > > The above is not familiar to me. It may be a cPanel thing. Actually, that is also part of the normal expected output from running mmsearch with no parameters. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ben.copeland at linaro.org Wed Sep 2 15:43:13 2015 From: ben.copeland at linaro.org (Benjamin Copeland) Date: Wed, 2 Sep 2015 14:43:13 +0100 Subject: [Mailman-Users] high amount of spam subscriptions Message-ID: Hello all, I have a issue where I am getting a high amount of subscriptions on mailman using the web form. I found that a option had been added to mailman (SUBSCRIBE_FORM_SECRET). I have added this to my configuration but am still getting large amount of spam subscriptions. The addresses all tend to be in similar format, user+alias at gmail.com (e.g. knuckles9048+51770730 at gmail.com). For experiment, I blocked email subscriptions to a mailing, to see if the requests are coming from mail or web form. knuckles9048+51770730 at gmail.com Tue Sep 1 14:14:50 2015 knuckles9048+14145395 at gmail.com Tue Sep 1 23:06:45 2015 Also 2 for another list (different users). So, now we know that web form is the attack vector. What can I do to get this under control? I am running postfix + spamd. Thanks! Ben From lac at openend.se Wed Sep 2 18:46:31 2015 From: lac at openend.se (Laura Creighton) Date: Wed, 02 Sep 2015 18:46:31 +0200 Subject: [Mailman-Users] high amount of spam subscriptions In-Reply-To: References: Message-ID: <201509021646.t82GkV8A009982@fido.openend.se> deepest sympathies. Poor you. Welcome to the club. We've been seeing this recently too. See the thread beginning here: https://mail.python.org/pipermail/mailman-users/2015-August/079627.html The damn things seem to be adapting, which isn't good. Laura From mark at msapiro.net Wed Sep 2 19:04:04 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 2 Sep 2015 10:04:04 -0700 Subject: [Mailman-Users] high amount of spam subscriptions In-Reply-To: <201509021646.t82GkV8A009982@fido.openend.se> References: <201509021646.t82GkV8A009982@fido.openend.se> Message-ID: <55E72C04.1070200@msapiro.net> On 09/02/2015 09:46 AM, Laura Creighton wrote: > deepest sympathies. Poor you. Welcome to the club. We've been seeing > this recently too. See the thread beginning here: > https://mail.python.org/pipermail/mailman-users/2015-August/079627.html > Also see the thread including . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From jason at fayre.me Wed Sep 2 20:13:18 2015 From: jason at fayre.me (Jason Fayre) Date: Wed, 2 Sep 2015 14:13:18 -0400 Subject: [Mailman-Users] integrating htdig with cpanel mailman In-Reply-To: <55E72426.8030101@msapiro.net> References: <000d01d0e4ec$f28dabd0$d7a90370$@fayre.me> <55E69F4F.6050306@msapiro.net> <002201d0e582$76e431c0$64ac9540$@fayre.me> <55E719BF.6040708@msapiro.net> <002a01d0e597$a76a7a60$f63f6f20$@fayre.me> <55E72426.8030101@msapiro.net> Message-ID: <003501d0e5ab$0bd1ede0$2375c9a0$@fayre.me> Absolutely unbelievable! I got results to come up by simlinking /var/www/html/htdig to /usr/share/htdig. Apparently this path is hard-coded in the binaries. I installed htdig from the Centos 6.7 packages. It wouldn't compile from source for some reason. -----Original Message----- From: Mark Sapiro [mailto:mark at msapiro.net] Sent: Wednesday, September 02, 2015 12:31 PM To: Jason Fayre ; mailman-users at python.org Subject: Re: [Mailman-Users] integrating htdig with cpanel mailman On 09/02/2015 08:54 AM, Jason Fayre wrote: > Ok, I will try that. > What version of htdig are you running? 3.2.0b6 with the rundig.0 patch from and with this patch the source of which I no longer remember and can't find. RCS file: /cvsroot/htdig/htdig/htsearch/Collection.h,v retrieving revision 1.4 diff -r1.4 Collection.h 39c39 < void Collection::Open(); --- > void Open(); 41c41 < void Collection::Close(); --- > void Close(); Also, in an earlier reply I wrote: >> If you want to make another attempt to access a list archive then go >> via the list users information page. >> >> If this problem persists then please e-mail the following information >> to the mailman at nfbnet.org: >> Referer not known >> /mailman/mmsearch/blparent_nfbnet.org > > > The above is not familiar to me. It may be a cPanel thing. Actually, that is also part of the normal expected output from running mmsearch with no parameters. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From jason at fayre.me Wed Sep 2 21:02:45 2015 From: jason at fayre.me (Jason Fayre) Date: Wed, 2 Sep 2015 15:02:45 -0400 Subject: [Mailman-Users] integrating htdig with cpanel mailman In-Reply-To: <55E72426.8030101@msapiro.net> References: <000d01d0e4ec$f28dabd0$d7a90370$@fayre.me> <55E69F4F.6050306@msapiro.net> <002201d0e582$76e431c0$64ac9540$@fayre.me> <55E719BF.6040708@msapiro.net> <002a01d0e597$a76a7a60$f63f6f20$@fayre.me> <55E72426.8030101@msapiro.net> Message-ID: <003b01d0e5b1$f40ae070$dc20a150$@fayre.me> Hi, Almost got it. Since some of our lists are very large and the archives go back almost 7 years, generating the indexes can take a very long time. To be able to update the indexes, do I need both the rundig and nightly_htdig patches from msapiro.net/mm? The rundig patch failed when I tried to patch the rundig from 3.2.0b6. -----Original Message----- From: Mark Sapiro [mailto:mark at msapiro.net] Sent: Wednesday, September 02, 2015 12:31 PM To: Jason Fayre ; mailman-users at python.org Subject: Re: [Mailman-Users] integrating htdig with cpanel mailman On 09/02/2015 08:54 AM, Jason Fayre wrote: > Ok, I will try that. > What version of htdig are you running? 3.2.0b6 with the rundig.0 patch from and with this patch the source of which I no longer remember and can't find. RCS file: /cvsroot/htdig/htdig/htsearch/Collection.h,v retrieving revision 1.4 diff -r1.4 Collection.h 39c39 < void Collection::Open(); --- > void Open(); 41c41 < void Collection::Close(); --- > void Close(); Also, in an earlier reply I wrote: >> If you want to make another attempt to access a list archive then go >> via the list users information page. >> >> If this problem persists then please e-mail the following information >> to the mailman at nfbnet.org: >> Referer not known >> /mailman/mmsearch/blparent_nfbnet.org > > > The above is not familiar to me. It may be a cPanel thing. Actually, that is also part of the normal expected output from running mmsearch with no parameters. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ricardo.rodriguez at idisantiago.es Wed Sep 2 21:27:42 2015 From: ricardo.rodriguez at idisantiago.es (=?UTF-8?Q?=5BIDIS_Technical_Secretariat=5D_Ricardo_Rodr=C3=ADguez?=) Date: Wed, 2 Sep 2015 21:27:42 +0200 Subject: [Mailman-Users] {Disarmed} Re: importing archived Maildir email lists into Mailman lists archives In-Reply-To: References: <55E265E9.3040305@msapiro.net> <55E4FB88.7080408@msapiro.net> Message-ID: Thanks Andrew and Mark! As a general rule of thumb, I usually avoid to reply to a message without reflecting for some hours on its content! Sorry for asking things with an obvious answer: I was using a sftp client to access /private and didn't realise that there is a folder, then a file, with the same name! listname.mbox. And thanks for the explanation! Please, read below... On Wed, Sep 2, 2015 at 1:57 PM, Andrew Hodgson wrote: > [IDIS Technical Secretariat] Ricardo Rodr?guez wrote: > > > >Before going ahead, there is one thing I'm curious about as I don't > understand it. Please, why does the path to the mbox file include > .mbox twice? Here... > > > > > http://wiki.list.org/DOC/How%20do%20I%20import%20an%20archive%20into%20a%20new%20mailing%20list%3F > > > >It reads... > > > >archives/private/.mbox/.mbox > > Yup, the file needs to be called listname.mbox in the directory > ~/archives/private/listname.mbox. So for example, to copy the > mailman-users archive into your home directory, assuming Mailman was > installed in the default location, you would enter a command like: > > cp /usr/local/mailman/private/mailman-users.mbox/mailman-users.mbox ~ > > That would give you a file called mailman-users.mbox in your home > directory with all the archives in mbox format. > > If your list is new then after running cleanarch on that mbox file, I > would copy it to ~archives/private/listname.mbox/listname.mbox, ensure > perms are correct by running check_perms, then run arch with the wipe > parameter to build all the HTML indexes for the web pages. > If you have a list already, I would stop Mailman, then cat the mbox file > in place at the location ~archives/private/listname.mbox/listname.mbox to a > copy of your converted archives. I would then run cleanarch on the > resulting file, then put that in place in > ~archives/private/listname.mbox/listname.mbox before checking perms and > running arch with the wipe parameter. > > Hope this clears things up for you. > Andrew. It worked! Thank you very much! I've learnt a lot, about a lot of things! Together with a great programe I've discovered a great community. Who knows? Perhaps in the future I'll be able to contribute in any way :-) Here we have our first "complete" list by consolidating former ezmlm managed contents with our brand new Mailman list with the same name... http://lists.idisantiago.es/pipermail/r.users/ Still, I've a doubt about the syntax of Mailman commands. I do need to do... [root at idis2 r.users.mbox]# cleanarch r.users.all.clean.mbox While <> are not required in command arch... [root at idis2 r.users.mbox]# arch --wipe r.users r.users.mbox If I don't use <> to enclose the input file name in cleanarch, I get the help page! Usage of both commands as per their help pages are close to similar... Usage: cleanarch [options] < inputfile > outputfile Usage: /usr/lib/mailman/bin/arch [options] [] Also, arch alone shows its help page whereas cleanarch alone do "nothing". Those usage lines and command behaviour aren't to consistent, are they? Could this behaviour be caused by my local configuration? Thanks!!! Ricardo -- Ricardo Rodr?guez Research Management and Promotion Technician Technical Secretariat Health Research Institute of Santiago de Compostela (IDIS) http://www.idisantiago.es From mark at msapiro.net Wed Sep 2 22:13:52 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 2 Sep 2015 13:13:52 -0700 Subject: [Mailman-Users] {Disarmed} Re: importing archived Maildir email lists into Mailman lists archives In-Reply-To: References: <55E265E9.3040305@msapiro.net> <55E4FB88.7080408@msapiro.net> Message-ID: <55E75880.7000807@msapiro.net> On 09/02/2015 12:27 PM, [IDIS Technical Secretariat] Ricardo Rodr?guez wrote: > > Still, I've a doubt about the syntax of Mailman commands. I do need to do... > > [root at idis2 r.users.mbox]# cleanarch r.users.all.clean.mbox > > > While <> are not required in command arch... > > > [root at idis2 r.users.mbox]# arch --wipe r.users r.users.mbox > > > If I don't use <> to enclose the input file name in cleanarch, I get the > help page! You are not 'enclosing' the input file name in cleanarch with <>. cleanarch reads the input mailbox from stdin and writes the output mbox to stdout. You are actually saying ' r.users.all.clean.mbox' which redirects stdout from the terminal to the file r.users.all.clean.mbox. Note that you didn't need to do this as the script already writes a 'clean' mbox. On the other hand if you give a second argument to bin/arch, it assumes that is the mbox. It doesn't read stdin in any case and writes various progress info to stdout. > Usage of both commands as per their help pages are close to similar... > > > Usage: cleanarch [options] < inputfile > outputfile This means use shell redirection to read the input from inputfile and write the output to outputfile. > Usage: /usr/lib/mailman/bin/arch [options] [] Here the notation means that is a variable to be replaced with the actual list name and [] means that is a variable to be replaced with the actual mbox, but the [] mean it's optional - if not provided it is computed as archives/private/.mbox/.mbox. > Also, arch alone shows its help page because arch without at least a argument is invalid > whereas cleanarch alone do > "nothing". Actually cleanarch alone is valid and both reads its input from and writes its output to the terminal. That's why if you type just 'cleanarch', it doesn't return immediately to a command prompt but waits for input from the terminal. Consider mark at msapiro:~$ /var/MM/21/bin/cleanarch - it's waiting for input- I type >From someone - it responds >From someone - to stdout, and Unix-From line changed: 1 >From someone - to stderr. then I type ^D (control-D - end of file) and it responds 0 messages found - and exits. > Those usage lines and command behaviour aren't to consistent, > are they? Could this behaviour be caused by my local configuration? No. They are caused by two different programs written by at least two different people. So yes, they aren't exactly consistent, but if you understand the different commands and the shell redirection, it may make more sense. True, cleanarch could have been written to require an input file argument instead of using stdin, but using stdin and stdout makes it easy to insert it into a pipeline of commands as in for example ezmlm2mbox [-d] ezmlm_dir | cleanarch | arch --wipe - except for the fact that arch doesn't read its stdin even if the conventional '-' is used as the mbox file name. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Wed Sep 2 22:23:26 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 2 Sep 2015 13:23:26 -0700 Subject: [Mailman-Users] integrating htdig with cpanel mailman In-Reply-To: <003b01d0e5b1$f40ae070$dc20a150$@fayre.me> References: <000d01d0e4ec$f28dabd0$d7a90370$@fayre.me> <55E69F4F.6050306@msapiro.net> <002201d0e582$76e431c0$64ac9540$@fayre.me> <55E719BF.6040708@msapiro.net> <002a01d0e597$a76a7a60$f63f6f20$@fayre.me> <55E72426.8030101@msapiro.net> <003b01d0e5b1$f40ae070$dc20a150$@fayre.me> Message-ID: <55E75ABE.60505@msapiro.net> On 09/02/2015 12:02 PM, Jason Fayre wrote: > Hi, > Almost got it. Since some of our lists are very large and the archives go > back almost 7 years, generating the indexes can take a very long time. > To be able to update the indexes, do I need both the rundig and > nightly_htdig patches from msapiro.net/mm? The rundig patch failed when I > tried to patch the rundig from 3.2.0b6. Yes, you need both. How did the rundig patch fail? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Wed Sep 2 22:33:34 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 2 Sep 2015 13:33:34 -0700 Subject: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6 In-Reply-To: <07b60f749fdc5b6102e8e9336fd60b04.squirrel@webmail.ee.ryerson.ca> References: <7915CC9E-0B0F-41D4-9B79-7FCEBE2107B8@ee.ryerson.ca> <87egii3yl6.fsf@uwakimon.sk.tsukuba.ac.jp> <74744c9fe512b6fd6c6d88f0893e101b.squirrel@webmail.ee.ryerson.ca> <55E5E605.50208@msapiro.net> <97793451d21a7677057597440f6aa5bf.squirrel@webmail.ee.ryerson.ca> <55E64D91.8060707@msapiro.net> <55E66250.6030207@msapiro.net> <07b60f749fdc5b6102e8e9336fd60b04.squirrel@webmail.ee.ryerson.ca> Message-ID: <55E75D1E.5050509@msapiro.net> On 09/02/2015 07:31 AM, David Magda wrote: > On Tue, September 1, 2015 22:43, Mark Sapiro wrote: >> >> So what has probably happened is that archiving has been broken since >> the upgrade on Aug 25. There should be a an error message with traceback >> in Mailman's 'error' log for each message that wasn't archived. More >> importantly, the unarchived messages should all be in Mailman's 'shunt' >> queue and running Mailman's bin/unshunt should process them for the >> archive. > > The last error message that is in the 'error' log is from Aug 24: Hmmm... >> Presumably, you did some kind of bin/arch process on Aug 25. The answer >> is don't do that. Or if you didn't do that, then the answer may lie in >> whatever changed in Python. > > Not that I'm aware of, unless the Debian package runs it in some way > pre-/post-upgrade. I didn't start looking at bin/arch until I noticed the > breakage. No. The package wouldn't do that. It is difficult to understand why a list would stop archiving without throwing and logging exceptions. Even if ArchRunner were somehow not running, the messages would be queued in its queue and processed when it eventually started. >> You should also consider running the contrib/mmdsr script from the >> Mailman source distro or if not that, somehow looking a Mailman's error >> log frequently for problems to discover them sooner. > > We have a few more hosts to upgrade, so I'll have to look more closely at > this. However some of these hosts have quite a few lists, so I'm not sure > how practical it will be examine every one to see if they're working > properly. mmdsr (Mailman daily summary report) is a daily summary for the whole server run at midnight by cron. It won't directly tell you if messages are not being archived, but it will give you a listing of what's in Mailman's queues and various error log entries. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ricardo.rodriguez at idisantiago.es Wed Sep 2 23:13:27 2015 From: ricardo.rodriguez at idisantiago.es (=?UTF-8?Q?=5BIDIS_Technical_Secretariat=5D_Ricardo_Rodr=C3=ADguez?=) Date: Wed, 2 Sep 2015 23:13:27 +0200 Subject: [Mailman-Users] {Disarmed} Re: importing archived Maildir email lists into Mailman lists archives In-Reply-To: <55E75880.7000807@msapiro.net> References: <55E265E9.3040305@msapiro.net> <55E4FB88.7080408@msapiro.net> <55E75880.7000807@msapiro.net> Message-ID: It does make sense indeed! I do hope to be able to take into account all these details when posting my next question to this list. In the meantime, I keep learning! Thank you so much for your time! On Wed, Sep 2, 2015 at 10:13 PM, Mark Sapiro wrote: > On 09/02/2015 12:27 PM, [IDIS Technical Secretariat] Ricardo Rodr?guez > wrote: > > > > Still, I've a doubt about the syntax of Mailman commands. I do need to > do... > > > > [root at idis2 r.users.mbox]# cleanarch > r.users.all.clean.mbox > > > > > > While <> are not required in command arch... > > > > > > [root at idis2 r.users.mbox]# arch --wipe r.users r.users.mbox > > > > > > If I don't use <> to enclose the input file name in cleanarch, I get the > > help page! > > > You are not 'enclosing' the input file name in cleanarch with <>. > cleanarch reads the input mailbox from stdin and writes the output mbox > to stdout. You are actually saying ' stdin from the terminal to the file r.users.all.mbox and '> > r.users.all.clean.mbox' which redirects stdout from the terminal to the > file r.users.all.clean.mbox. > > Note that you didn't need to do this as the > script already writes a > 'clean' mbox. > > On the other hand if you give a second argument to bin/arch, it assumes > that is the mbox. It doesn't read stdin in any case and writes various > progress info to stdout. > > > > Usage of both commands as per their help pages are close to similar... > > > > > > Usage: cleanarch [options] < inputfile > outputfile > > > This means use shell redirection to read the input from inputfile and > write the output to outputfile. > > > > Usage: /usr/lib/mailman/bin/arch [options] [] > > Here the notation means that is a variable to be replaced > with the actual list name and [] means that is a variable > to be replaced with the actual mbox, but the [] mean it's optional - if > not provided it is computed as > archives/private/.mbox/.mbox. > > > > Also, arch alone shows its help page > > because arch without at least a argument is invalid > > > > whereas cleanarch alone do > > "nothing". > > Actually cleanarch alone is valid and both reads its input from and > writes its output to the terminal. That's why if you type just > 'cleanarch', it doesn't return immediately to a command prompt but waits > for input from the terminal. > > Consider > > mark at msapiro:~$ /var/MM/21/bin/cleanarch > - it's waiting for input- I type > From someone > - it responds > >From someone > - to stdout, and > Unix-From line changed: 1 > From someone > - to stderr. then I type ^D (control-D - end of file) and it responds > 0 messages found > - and exits. > > > Those usage lines and command behaviour aren't to consistent, > > are they? Could this behaviour be caused by my local configuration? > > > No. They are caused by two different programs written by at least two > different people. So yes, they aren't exactly consistent, but if you > understand the different commands and the shell redirection, it may make > more sense. > > True, cleanarch could have been written to require an input file > argument instead of using stdin, but using stdin and stdout makes it > easy to insert it into a pipeline of commands as in for example > > ezmlm2mbox [-d] ezmlm_dir | cleanarch | arch --wipe - > > except for the fact that arch doesn't read its stdin even if the > conventional '-' is used as the mbox file name. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > -- Ricardo Rodr?guez Research Management and Promotion Technician Technical Secretariat Health Research Institute of Santiago de Compostela (IDIS) http://www.idisantiago.es From jason at fayre.me Thu Sep 3 01:44:07 2015 From: jason at fayre.me (Jason Fayre) Date: Wed, 2 Sep 2015 19:44:07 -0400 Subject: [Mailman-Users] integrating htdig with cpanel mailman In-Reply-To: <55E75ABE.60505@msapiro.net> References: <000d01d0e4ec$f28dabd0$d7a90370$@fayre.me> <55E69F4F.6050306@msapiro.net> <002201d0e582$76e431c0$64ac9540$@fayre.me> <55E719BF.6040708@msapiro.net> <002a01d0e597$a76a7a60$f63f6f20$@fayre.me> <55E72426.8030101@msapiro.net> <003b01d0e5b1$f40ae070$dc20a150$@fayre.me> <55E75ABE.60505@msapiro.net> Message-ID: <55E789C7.9050603@fayre.me> Hi, Here is a script from when I ran the patch: Script started on Wed 02 Sep 2015 11:35:43 PM UTC root at host [/usr/bin]# patch < ~/rundig patching file rundig Hunk #1 succeeded at 16 with fuzz 2 (offset 1 line). Hunk #2 FAILED at 59. Hunk #3 succeeded at 78 (offset 4 lines). 1 out of 3 hunks FAILED -- saving rejects to file rundig.rej root at host [/usr/bin]# cat rundig.rej --- rundig 2008-12-26 15:55:25.000000000 -0800 +++ rundig 2008-12-26 17:41:43.000000000 -0800 @@ -59,7 +61,7 @@ TMPDIR=$DBDIR export TMPDIR -$BINDIR/htdig -i $opts $stats $alt +$BINDIR/htdig $init $opts $stats $alt $BINDIR/htpurge $opts $alt case "$alt" in -a) root at host [/usr/bin]# On 2015-09-02 4:23 PM, Mark Sapiro wrote: > On 09/02/2015 12:02 PM, Jason Fayre wrote: >> Hi, >> Almost got it. Since some of our lists are very large and the archives go >> back almost 7 years, generating the indexes can take a very long time. >> To be able to update the indexes, do I need both the rundig and >> nightly_htdig patches from msapiro.net/mm? The rundig patch failed when I >> tried to patch the rundig from 3.2.0b6. > > Yes, you need both. How did the rundig patch fail? > From mark at msapiro.net Thu Sep 3 02:02:18 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 2 Sep 2015 17:02:18 -0700 Subject: [Mailman-Users] integrating htdig with cpanel mailman In-Reply-To: <55E789C7.9050603@fayre.me> References: <000d01d0e4ec$f28dabd0$d7a90370$@fayre.me> <55E69F4F.6050306@msapiro.net> <002201d0e582$76e431c0$64ac9540$@fayre.me> <55E719BF.6040708@msapiro.net> <002a01d0e597$a76a7a60$f63f6f20$@fayre.me> <55E72426.8030101@msapiro.net> <003b01d0e5b1$f40ae070$dc20a150$@fayre.me> <55E75ABE.60505@msapiro.net> <55E789C7.9050603@fayre.me> Message-ID: <55E78E0A.7040407@msapiro.net> On 09/02/2015 04:44 PM, Jason Fayre wrote: > Hi, > Here is a script from when I ran the patch: > Script started on Wed 02 Sep 2015 11:35:43 PM UTC > root at host [/usr/bin]# patch < ~/rundig > patching file rundig > Hunk #1 succeeded at 16 with fuzz 2 (offset 1 line). > Hunk #2 FAILED at 59. > Hunk #3 succeeded at 78 (offset 4 lines). > 1 out of 3 hunks FAILED -- saving rejects to file rundig.rej > root at host [/usr/bin]# cat rundig.rej > --- rundig 2008-12-26 15:55:25.000000000 -0800 > +++ rundig 2008-12-26 17:41:43.000000000 -0800 > @@ -59,7 +61,7 @@ > TMPDIR=$DBDIR > export TMPDIR > > -$BINDIR/htdig -i $opts $stats $alt > +$BINDIR/htdig $init $opts $stats $alt > $BINDIR/htpurge $opts $alt > case "$alt" in > -a) > root at host [/usr/bin]# I don't understand this. My rundig is probably different from yours in that I applied the patch from before creating the rundig patch you are applying, but this should only result in a couple of line # offsets, not a failure of hunk 2 or fuzz in hunk 1. Send me a copy of your rundig off list and I'll look at it. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Sep 3 02:33:33 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 2 Sep 2015 17:33:33 -0700 Subject: [Mailman-Users] integrating htdig with cpanel mailman In-Reply-To: <55E7947A.1070409@msapiro.net> References: <000d01d0e4ec$f28dabd0$d7a90370$@fayre.me> <55E69F4F.6050306@msapiro.net> <002201d0e582$76e431c0$64ac9540$@fayre.me> <55E719BF.6040708@msapiro.net> <002a01d0e597$a76a7a60$f63f6f20$@fayre.me> <55E72426.8030101@msapiro.net> <003b01d0e5b1$f40ae070$dc20a150$@fayre.me> <55E75ABE.60505@msapiro.net> <55E789C7.9050603@fayre.me> <55E78E0A.7040407@msapiro.net> <55E78F37.7090104@fayre.me> <55E7947A.1070409@msapiro.net> Message-ID: <55E7955D.1020204@msapiro.net> Forwarding to mailman-users for completeness. On 09/02/2015 05:29 PM, Mark Sapiro wrote: > On 09/02/2015 05:07 PM, Jason Fayre wrote: >> Here you go. >> Thanks so much for your help on this! >> This rundig is from the centos 6.7 htdig package. > > > Your rundig has been modified from the 3.2.0b6 htdig base. The base > rundig always does a full rebuild of the index My patch to rundig adds a > '-u' option to do an 'update' rather than a full rebuild. Your > RedHat/Centos package rundig already has this option only it's '-i' for > incremental. > > Thus, you don't need to patch your rundig at all unless you want to > uncomment line 79 (which my patch does) per lines 77-79 > > # If you want to use the soundex and (or) metaphone fuzzy matchings, > # Uncomment the following line > # $BINDIR/htfuzzy $opts soundex metaphone > > What you do need to do however is change nightly_htdig. My patch added > amongst other things the line > > init_or_update = ' -u' > > per > > @@ -109,6 +109,7 @@ > # test if the archive volume directories mod times have > # changed > recent_posts = None > + init_or_update = ' -u' > rundig_run_file = os.path.join(list_htdig_dir, 'rundig_last_run') > archive = HyperArch.HyperArchive(mlist) > try: > > You need to change that to > > init_or_update = ' -i' > > because in your rundig the 'incremental' option is '-i', not '-u'. > -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From jason at fayre.me Thu Sep 3 17:02:18 2015 From: jason at fayre.me (Jason Fayre) Date: Thu, 3 Sep 2015 11:02:18 -0400 Subject: [Mailman-Users] integrating htdig with cpanel mailman In-Reply-To: <55E7955D.1020204@msapiro.net> References: <000d01d0e4ec$f28dabd0$d7a90370$@fayre.me> <55E69F4F.6050306@msapiro.net> <002201d0e582$76e431c0$64ac9540$@fayre.me> <55E719BF.6040708@msapiro.net> <002a01d0e597$a76a7a60$f63f6f20$@fayre.me> <55E72426.8030101@msapiro.net> <003b01d0e5b1$f40ae070$dc20a150$@fayre.me> <55E75ABE.60505@msapiro.net> <55E789C7.9050603@fayre.me> <55E78E0A.7040407@msapiro.net> <55E78F37.7090104@fayre.me> <55E7947A.1070409@msapiro.net> <55E7955D.1020204@msapiro.net> Message-ID: <000001d0e659$871088f0$95319ad0$@fayre.me> Hello, I made the modifications you suggested. Now when I run nightly_htdig on a list, I get an error back that "I" is an invalid option for htfuzzy. I uncommented that line in the rundig script. Any ideas? If it isn't critical, I can just re-comment that line. -----Original Message----- From: Mailman-Users [mailto:mailman-users-bounces+jason=fayre.me at python.org] On Behalf Of Mark Sapiro Sent: Wednesday, September 02, 2015 8:34 PM To: Mailman Users Subject: Re: [Mailman-Users] integrating htdig with cpanel mailman Forwarding to mailman-users for completeness. On 09/02/2015 05:29 PM, Mark Sapiro wrote: > On 09/02/2015 05:07 PM, Jason Fayre wrote: >> Here you go. >> Thanks so much for your help on this! >> This rundig is from the centos 6.7 htdig package. > > > Your rundig has been modified from the 3.2.0b6 htdig base. The base > rundig always does a full rebuild of the index My patch to rundig adds > a '-u' option to do an 'update' rather than a full rebuild. Your > RedHat/Centos package rundig already has this option only it's '-i' > for incremental. > > Thus, you don't need to patch your rundig at all unless you want to > uncomment line 79 (which my patch does) per lines 77-79 > > # If you want to use the soundex and (or) metaphone fuzzy matchings, # > Uncomment the following line # $BINDIR/htfuzzy $opts soundex metaphone > > What you do need to do however is change nightly_htdig. My patch added > amongst other things the line > > init_or_update = ' -u' > > per > > @@ -109,6 +109,7 @@ > # test if the archive volume directories mod times have > # changed > recent_posts = None > + init_or_update = ' -u' > rundig_run_file = os.path.join(list_htdig_dir, 'rundig_last_run') > archive = HyperArch.HyperArchive(mlist) > try: > > You need to change that to > > init_or_update = ' -i' > > because in your rundig the 'incremental' option is '-i', not '-u'. > -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users at 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/jason%40fayre.me From mark at msapiro.net Thu Sep 3 19:11:00 2015 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 3 Sep 2015 10:11:00 -0700 Subject: [Mailman-Users] integrating htdig with cpanel mailman In-Reply-To: <000001d0e659$871088f0$95319ad0$@fayre.me> References: <000d01d0e4ec$f28dabd0$d7a90370$@fayre.me> <55E69F4F.6050306@msapiro.net> <002201d0e582$76e431c0$64ac9540$@fayre.me> <55E719BF.6040708@msapiro.net> <002a01d0e597$a76a7a60$f63f6f20$@fayre.me> <55E72426.8030101@msapiro.net> <003b01d0e5b1$f40ae070$dc20a150$@fayre.me> <55E75ABE.60505@msapiro.net> <55E789C7.9050603@fayre.me> <55E78E0A.7040407@msapiro.net> <55E78F37.7090104@fayre.me> <55E7947A.1070409@msapiro.net> <55E7955D.1020204@msapiro.net> <000001d0e659$871088f0$95319ad0$@fayre.me> Message-ID: <55E87F24.6090604@msapiro.net> On 09/03/2015 08:02 AM, Jason Fayre wrote: > Hello, > I made the modifications you suggested. > Now when I run nightly_htdig on a list, I get an error back that "I" is an > invalid option for htfuzzy. I uncommented that line in the rundig script. > Any ideas? > If it isn't critical, I can just re-comment that line. I'm sorry. I didn't keep the rundig you sent me so I can't be sure, but it appears that RedHat's modified rundig may be broken in some way. On the other hand, if in making the mod to nightly_htdig you have init_or_update = ' -I' that is the problem. it needs to be lower case ' -i'. If that doesn't explain it, you can send me the rundig again and I'll look further. Whether or not you want the uncommented $BINDIR/htfuzzy $opts soundex metaphone line is up to you. What this does is enable the search to match alternate spellings of the search words that 'sound alike'. However, even if you re-comment that line, there may be other problems even if it doesn't complain. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From jason at fayre.me Thu Sep 3 20:29:37 2015 From: jason at fayre.me (Jason Fayre) Date: Thu, 3 Sep 2015 14:29:37 -0400 Subject: [Mailman-Users] integrating htdig with cpanel mailman In-Reply-To: <55E87F24.6090604@msapiro.net> References: <000d01d0e4ec$f28dabd0$d7a90370$@fayre.me> <55E69F4F.6050306@msapiro.net> <002201d0e582$76e431c0$64ac9540$@fayre.me> <55E719BF.6040708@msapiro.net> <002a01d0e597$a76a7a60$f63f6f20$@fayre.me> <55E72426.8030101@msapiro.net> <003b01d0e5b1$f40ae070$dc20a150$@fayre.me> <55E75ABE.60505@msapiro.net> <55E789C7.9050603@fayre.me> <55E78E0A.7040407@msapiro.net> <55E78F37.7090104@fayre.me> <55E7947A.1070409@msapiro.net> <55E7955D.1020204@msapiro.net> <000001d0e659$871088f0$95319ad0$@fayre.me> <55E87F24.6090604@msapiro.net> Message-ID: <000d01d0e676$7d352a30$779f7e90$@fayre.me> Hi, I finally got htdig to compile from source. So, I got rid of the centos package and am now using a vanilla build. The rundig patch applied correctly now. -----Original Message----- From: Mark Sapiro [mailto:mark at msapiro.net] Sent: Thursday, September 03, 2015 1:11 PM To: Jason Fayre ; 'Mailman Users' Subject: Re: [Mailman-Users] integrating htdig with cpanel mailman On 09/03/2015 08:02 AM, Jason Fayre wrote: > Hello, > I made the modifications you suggested. > Now when I run nightly_htdig on a list, I get an error back that "I" > is an invalid option for htfuzzy. I uncommented that line in the rundig script. > Any ideas? > If it isn't critical, I can just re-comment that line. I'm sorry. I didn't keep the rundig you sent me so I can't be sure, but it appears that RedHat's modified rundig may be broken in some way. On the other hand, if in making the mod to nightly_htdig you have init_or_update = ' -I' that is the problem. it needs to be lower case ' -i'. If that doesn't explain it, you can send me the rundig again and I'll look further. Whether or not you want the uncommented $BINDIR/htfuzzy $opts soundex metaphone line is up to you. What this does is enable the search to match alternate spellings of the search words that 'sound alike'. However, even if you re-comment that line, there may be other problems even if it doesn't complain. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From nitinics at gmail.com Thu Sep 3 16:21:15 2015 From: nitinics at gmail.com (Nitin Sharma) Date: Thu, 3 Sep 2015 10:21:15 -0400 Subject: [Mailman-Users] All confirmation emails going to SPAM on gmail Message-ID: Hi All, So I set up mailman ( mailman-2.1.15-21.20 ) and have my SPF/DKIM/DMARC set for my domain. All of the confirmation emails sent are classified under Gmail as "Spam". The list postings however are correctly sent to Forum Tab. I see that "Precedence:bulk" is set on the confirmation emails, whereas "Precedence:list" is set on the posting. I think that's okay. Confirmation emails are important and I want to increase the likelihood of it not being classified as spam. Any help or suggestions would be appreciated. I opened a discussion in here too , which contain all the headers - https://productforums.google.com/forum/?utm_medium=email&utm_source=footer#!msg/gmail/mxkNC3b_KK0/8xEoHtksLRoJ According to the Bulk sender's guidelines : I have mostly all done correct except the below 1. Unsubscribe option - Don't have it since confirmation email means the user hasn't subscribed yet. 2. Use the same address in the 'From:' header on every bulk mail you send. - This on mailman's confirmation email is sent as list+confirm+@domain , and this changes every time. Is there a way to make this consistent? Thanks Nitin From lac at openend.se Thu Sep 3 23:50:27 2015 From: lac at openend.se (Laura Creighton) Date: Thu, 03 Sep 2015 23:50:27 +0200 Subject: [Mailman-Users] integrating htdig with cpanel mailman In-Reply-To: <000d01d0e676$7d352a30$779f7e90$@fayre.me> References: <000d01d0e4ec$f28dabd0$d7a90370$@fayre.me> <55E69F4F.6050306@msapiro.net> <002201d0e582$76e431c0$64ac9540$@fayre.me> <55E719BF.6040708@msapiro.net> <002a01d0e597$a76a7a60$f63f6f20$@fayre.me> <55E72426.8030101@msapiro.net> <003b01d0e5b1$f40ae070$dc20a150$@fayre.me> <55E75ABE.60505@msapiro.net> <55E789C7.9050603@fayre.me> <55E78E0A.7040407@msapiro.net> <55E78F37.7090104@fayre.me> <55E7947A.1070409@msapiro.net> <55E7955D.1020204@msapiro.net> <000001d0e659$871088f0$95319ad0$@fayre.me> <55E87F24.6090604@msapiro.net> <000d01d0e676$7d352a30$779f7e90$@fayre.me> Message-ID: <201509032150.t83LoRbK025783@fido.openend.se> In a message of Thu, 03 Sep 2015 14:29:37 -0400, "Jason Fayre" writes: >Hi, >I finally got htdig to compile from source. So, I got rid of the centos >package and am now using a vanilla build. The rundig patch applied correctly >now. > cheer! :) Laura From mark at msapiro.net Fri Sep 4 01:01:57 2015 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 3 Sep 2015 16:01:57 -0700 Subject: [Mailman-Users] All confirmation emails going to SPAM on gmail In-Reply-To: References: Message-ID: <55E8D165.5010708@msapiro.net> On 09/03/2015 07:21 AM, Nitin Sharma wrote: > > So I set up mailman ( mailman-2.1.15-21.20 ) and have my > SPF/DKIM/DMARC set for my domain. I too have SPF and DKIM sign my outgoing mail, but I don't publish a DMARC policy. > All of the confirmation emails sent are classified under Gmail as > "Spam". The list postings however are correctly sent to Forum Tab. I just requested subscription of a gmail address to a list and the confirmation request arrived in my gmail inbox. > I see that "Precedence:bulk" is set on the confirmation emails, > whereas "Precedence:list" is set on the posting. I think that's okay. > > Confirmation emails are important and I want to increase the > likelihood of it not being classified as spam. Agreed. > Any help or suggestions would be appreciated. Here are the headers of the message from my gmail inbox. Some lines may be wrapped, but otherwise this is an exact copy. Delivered-To: marksapiro at gmail.com Received: by 10.79.28.84 with SMTP id c81csp55822ivc; Thu, 3 Sep 2015 14:04:07 -0700 (PDT) X-Received: by 10.107.160.196 with SMTP id j187mr192882ioe.80.1441314247111; Thu, 03 Sep 2015 14:04:07 -0700 (PDT) Return-Path: Received: from sbh16.songbird.com (sbh16.songbird.com. [72.52.113.16]) by mx.google.com with ESMTP id w5si175300igl.33.2015.09.03.14.04.06 for ; Thu, 03 Sep 2015 14:04:06 -0700 (PDT) Received-SPF: pass (google.com: domain of wed_ride-bounces+marksapiro=gmail.com at grizz.org designates 72.52.113.16 as permitted sender) client-ip=72.52.113.16; Authentication-Results: mx.google.com; spf=pass (google.com: domain of wed_ride-bounces+marksapiro=gmail.com at grizz.org designates 72.52.113.16 as permitted sender) smtp.mailfrom=wed_ride-bounces+marksapiro=gmail.com at grizz.org; dkim=pass header.i=@grizz.org Received: from sbh16.songbird.com (localhost.localdomain [127.0.0.1]) by sbh16.songbird.com (Postfix) with ESMTP id EB6C111E0075 for ; Thu, 3 Sep 2015 14:03:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=grizz.org; s=default; t=1441314203; bh=yEUb4ckS6Fc1HbEAgDUhqOHNgu/RDCrA6+1VBSmCVRA=; h=From:To:Subject:Reply-To:Date:List-Id; b=Y29kTn45HV3hl9P8uVmdDoZFAm8kCCA9CFxj+sX9ip3gJcXktosI8ih86hSM55lxE af74YrR1zzc0RrnLaQLni1iIr+lErigt8zU5TcchUO3Xf+rdZzR/WNzPfFhdC/MtP9 KZy/l1rZWlB/RHDFxsM4xW1MIUmrNoUyJ0hl9Ix4= MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit From: wed_ride-confirm+1e5aa844ab20f780c82596c0f41b178ff5d9eb25 at grizz.org To: marksapiro at gmail.com Subject: Your confirmation is required to join the Wed_ride mailing list Reply-To: wed_ride-confirm+1e5aa844ab20f780c82596c0f41b178ff5d9eb25 at grizz.org Auto-Submitted: auto-generated Message-ID: Date: Thu, 03 Sep 2015 14:03:14 -0700 Precedence: bulk X-BeenThere: wed_ride at grizz.org X-Mailman-Version: 2.1.20 List-Id: GPC Wednesday Ride List X-List-Administrivia: yes Errors-To: wed_ride-bounces+marksapiro=gmail.com at grizz.org > I opened a discussion in here too , which contain all the headers - > https://productforums.google.com/forum/?utm_medium=email&utm_source=footer#!msg/gmail/mxkNC3b_KK0/8xEoHtksLRoJ The only significant difference I see in headers is your Received: from ip-10-73-187-221.ec2.internal (mail.nypny.com. [2001:470:1f07:12b5::2]) by mx.google.com which I think says your MTA identifies itself in EHLO as ip-10-73-187-221.ec2.internal and not as mail.nypny.com. This could make a difference. > According to the Bulk sender's guidelines : > I have mostly all done correct except the below > 1. Unsubscribe option - Don't have it since confirmation email means > the user hasn't subscribed yet. > 2. Use the same address in the 'From:' header on every bulk mail you > send. - This on mailman's confirmation email is sent as > list+confirm+@domain , and this changes every time. Is there a > way to make this consistent? It is that way because you have VERP_CONFIRMATIONS = Yes in mm_cfg.py for 'friendlier' confirmations. You can remove that in which case the From: will be (in your case) From: wg-request at nypny.com and the Subject: will be Subject: confirm+cf8341f8018591fef49bbfd5c5a8bf4a2f3b9066 Sending confirmations with that Subject: is probably just as bad as having some end up in spam. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From wetz.peter at gmail.com Fri Sep 4 15:13:32 2015 From: wetz.peter at gmail.com (Peter Wetz) Date: Fri, 4 Sep 2015 15:13:32 +0200 Subject: [Mailman-Users] message to list does not get forwarded to all list members Message-ID: Currently I experience the following issue on my list: If one specific subscriber posts a message to the list, it does not get forwarded to all list members. However, some (at least one) receives his messages. But most, don't receive his message. The message also shows up properly in the list archive. What is the problem? How can I debug this? Why does the message not get through to all list members? The domain of the source mail is yahoo.com Thanks and best, Peter From jason at fayre.me Fri Sep 4 16:40:25 2015 From: jason at fayre.me (Jason Fayre) Date: Fri, 4 Sep 2015 10:40:25 -0400 Subject: [Mailman-Users] creating a htdig global search Message-ID: <000001d0e71f$a3244510$e96ccf30$@fayre.me> Hello, After getting HTDig to work on a per-list basis, I'd now like to set up a global search for all of our lists. Has anyone done this? I'm not sure what to put in the config file for start_url to have it build a master index of all the archives. Any help would be appreciated. From mark at msapiro.net Fri Sep 4 17:25:10 2015 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 4 Sep 2015 08:25:10 -0700 Subject: [Mailman-Users] message to list does not get forwarded to all list members In-Reply-To: References: Message-ID: <55E9B7D6.3030103@msapiro.net> On 09/04/2015 06:13 AM, Peter Wetz wrote: > > What is the problem? How can I debug this? Why does the message not get > through to all list members? > > The domain of the source mail is yahoo.com See the wiki at and . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From nitinics at gmail.com Fri Sep 4 18:06:12 2015 From: nitinics at gmail.com (Nitin Sharma) Date: Fri, 4 Sep 2015 12:06:12 -0400 Subject: [Mailman-Users] All confirmation emails going to SPAM on gmail In-Reply-To: <55E8D165.5010708@msapiro.net> References: <55E8D165.5010708@msapiro.net> Message-ID: On Thu, Sep 3, 2015 at 7:01 PM, Mark Sapiro wrote: > On 09/03/2015 07:21 AM, Nitin Sharma wrote: >> >> So I set up mailman ( mailman-2.1.15-21.20 ) and have my >> SPF/DKIM/DMARC set for my domain. > > > I too have SPF and DKIM sign my outgoing mail, but I don't publish a > DMARC policy. > > >> All of the confirmation emails sent are classified under Gmail as >> "Spam". The list postings however are correctly sent to Forum Tab. > > > I just requested subscription of a gmail address to a list and the > confirmation request arrived in my gmail inbox. > > >> I see that "Precedence:bulk" is set on the confirmation emails, >> whereas "Precedence:list" is set on the posting. I think that's okay. >> >> Confirmation emails are important and I want to increase the >> likelihood of it not being classified as spam. > > > Agreed. > > >> Any help or suggestions would be appreciated. > > > Here are the headers of the message from my gmail inbox. Some lines may > be wrapped, but otherwise this is an exact copy. > > Delivered-To: marksapiro at gmail.com > Received: by 10.79.28.84 with SMTP id c81csp55822ivc; > Thu, 3 Sep 2015 14:04:07 -0700 (PDT) > X-Received: by 10.107.160.196 with SMTP id j187mr192882ioe.80.1441314247111; > Thu, 03 Sep 2015 14:04:07 -0700 (PDT) > Return-Path: > Received: from sbh16.songbird.com (sbh16.songbird.com. [72.52.113.16]) > by mx.google.com with ESMTP id w5si175300igl.33.2015.09.03.14.04.06 > for ; > Thu, 03 Sep 2015 14:04:06 -0700 (PDT) > Received-SPF: pass (google.com: domain of > wed_ride-bounces+marksapiro=gmail.com at grizz.org designates 72.52.113.16 > as permitted sender) client-ip=72.52.113.16; > Authentication-Results: mx.google.com; > spf=pass (google.com: domain of > wed_ride-bounces+marksapiro=gmail.com at grizz.org designates 72.52.113.16 > as permitted sender) > smtp.mailfrom=wed_ride-bounces+marksapiro=gmail.com at grizz.org; > dkim=pass header.i=@grizz.org > Received: from sbh16.songbird.com (localhost.localdomain [127.0.0.1]) > by sbh16.songbird.com (Postfix) with ESMTP id EB6C111E0075 > for ; Thu, 3 Sep 2015 14:03:23 -0700 (PDT) > DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=grizz.org; s=default; > t=1441314203; bh=yEUb4ckS6Fc1HbEAgDUhqOHNgu/RDCrA6+1VBSmCVRA=; > h=From:To:Subject:Reply-To:Date:List-Id; > b=Y29kTn45HV3hl9P8uVmdDoZFAm8kCCA9CFxj+sX9ip3gJcXktosI8ih86hSM55lxE > af74YrR1zzc0RrnLaQLni1iIr+lErigt8zU5TcchUO3Xf+rdZzR/WNzPfFhdC/MtP9 > KZy/l1rZWlB/RHDFxsM4xW1MIUmrNoUyJ0hl9Ix4= > MIME-Version: 1.0 > Content-Type: text/plain; charset="us-ascii" > Content-Transfer-Encoding: 7bit > From: wed_ride-confirm+1e5aa844ab20f780c82596c0f41b178ff5d9eb25 at grizz.org > To: marksapiro at gmail.com > Subject: Your confirmation is required to join the Wed_ride mailing list > Reply-To: > wed_ride-confirm+1e5aa844ab20f780c82596c0f41b178ff5d9eb25 at grizz.org > Auto-Submitted: auto-generated > Message-ID: > Date: Thu, 03 Sep 2015 14:03:14 -0700 > Precedence: bulk > X-BeenThere: wed_ride at grizz.org > X-Mailman-Version: 2.1.20 > List-Id: GPC Wednesday Ride List > X-List-Administrivia: yes > Errors-To: wed_ride-bounces+marksapiro=gmail.com at grizz.org > > >> I opened a discussion in here too , which contain all the headers - >> https://productforums.google.com/forum/?utm_medium=email&utm_source=footer#!msg/gmail/mxkNC3b_KK0/8xEoHtksLRoJ > > > The only significant difference I see in headers is your > > Received: from ip-10-73-187-221.ec2.internal (mail.nypny.com. > [2001:470:1f07:12b5::2]) > by mx.google.com > > which I think says your MTA identifies itself in EHLO as > ip-10-73-187-221.ec2.internal and not as mail.nypny.com. This could make > a difference. > That was it. I didn't think that would make much of a difference, but I changed the EHLO and it is no longer spam. Thanks for the pointer. > >> According to the Bulk sender's guidelines : >> I have mostly all done correct except the below >> 1. Unsubscribe option - Don't have it since confirmation email means >> the user hasn't subscribed yet. >> 2. Use the same address in the 'From:' header on every bulk mail you >> send. - This on mailman's confirmation email is sent as >> list+confirm+@domain , and this changes every time. Is there a >> way to make this consistent? > > > It is that way because you have > > VERP_CONFIRMATIONS = Yes > > in mm_cfg.py for 'friendlier' confirmations. You can remove that in > which case the From: will be (in your case) > > From: wg-request at nypny.com > > and the Subject: will be > > Subject: confirm+cf8341f8018591fef49bbfd5c5a8bf4a2f3b9066 > > Sending confirmations with that Subject: is probably just as bad as > having some end up in spam. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at 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/nitinics%40gmail.com From rosenbaumlm at ornl.gov Fri Sep 4 18:39:44 2015 From: rosenbaumlm at ornl.gov (Rosenbaum, Larry M.) Date: Fri, 4 Sep 2015 16:39:44 +0000 Subject: [Mailman-Users] Question about spam directory Message-ID: <5f241b77e4d1475893415b9eded5a2e3@EXCHCS31.ornl.gov> There are several files in our Mailman spam directory /var/lib/mailman/spam. These have filenames like spam-listname-number.msg Some of them are zero length; some are not. Where are these coming from? The spam filters are set to the default values, which shouldn't be blocking anything. Larry M. Rosenbaum Oak Ridge National Laboratory From mark at msapiro.net Fri Sep 4 19:02:55 2015 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 4 Sep 2015 10:02:55 -0700 Subject: [Mailman-Users] Question about spam directory In-Reply-To: <5f241b77e4d1475893415b9eded5a2e3@EXCHCS31.ornl.gov> References: <5f241b77e4d1475893415b9eded5a2e3@EXCHCS31.ornl.gov> Message-ID: <55E9CEBF.7040507@msapiro.net> On 09/04/2015 09:39 AM, Rosenbaum, Larry M. wrote: > There are several files in our Mailman spam directory /var/lib/mailman/spam. These have filenames like > spam-listname-number.msg > Some of them are zero length; some are not. > > Where are these coming from? The spam filters are set to the default values, which shouldn't be blocking anything. When a moderator checks the "preserve message for site administrator" box when handling a held message, the message is put in that spam/ directory. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Fri Sep 4 23:35:27 2015 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 4 Sep 2015 14:35:27 -0700 Subject: [Mailman-Users] creating a htdig global search In-Reply-To: <000001d0e71f$a3244510$e96ccf30$@fayre.me> References: <000001d0e71f$a3244510$e96ccf30$@fayre.me> Message-ID: <55EA0E9F.2030509@msapiro.net> On 09/04/2015 07:40 AM, Jason Fayre wrote: > Hello, > After getting HTDig to work on a per-list basis, I'd now like to set up a > global search for all of our lists. > Has anyone done this? I'm not sure what to put in the config file for > start_url to have it build a master index of all the archives. > Any help would be appreciated. If you're only concerned about building the index, start_url can be anything. The key is that start_url should equate to archives/private/ in a local_urls attribute. E.g., start_url: http://example.com/mailman/searchall ... local_urls: http://example.com/mailman/searchall=/var/lib/mailman/archives/private/ You will also need to provide some actual URLs to a) a page that presents a search form and b) a CGI (or WSGI) to post the form data to. You can't use mmsearch for b) because it requires a list name. Also, if you have any private archives, you have an authentication problem. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From stephen at xemacs.org Sat Sep 5 09:30:22 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Sat, 05 Sep 2015 16:30:22 +0900 Subject: [Mailman-Users] All confirmation emails going to SPAM on gmail In-Reply-To: References: <55E8D165.5010708@msapiro.net> Message-ID: <87k2s52ui9.fsf@uwakimon.sk.tsukuba.ac.jp> Nitin Sharma writes: > On Thu, Sep 3, 2015 at 7:01 PM, Mark Sapiro wrote: > > Received: from ip-10-73-187-221.ec2.internal (mail.nypny.com. > > [2001:470:1f07:12b5::2]) > > by mx.google.com > > > > which I think says your MTA identifies itself in EHLO as > > ip-10-73-187-221.ec2.internal and not as mail.nypny.com. This > > could make a difference. > > That was it. I didn't think that would make much of a difference, but > I changed the EHLO and it is no longer spam. This actually is huge. Any indication that your mail was handled by a machine with a dynamically assigned IP is going to bump your spam points by quite a bit. The IP itself is impossible to connect to your domain, because IPs that start with 10 are not on the Internet. Those IPs are defined to be for internal use only (as the rest of the original EHLO domain also hints). Tell your friends and colleagues! :-) From lac at openend.se Sun Sep 6 11:15:31 2015 From: lac at openend.se (Laura Creighton) Date: Sun, 6 Sep 2015 11:15:31 +0200 Subject: [Mailman-Users] Does mailman care about mail aliases? Message-ID: <201509060915.t869FVVP015013@fido.openend.se> Somebody has subscribed 'webmaster at python.org' to their wretched Portuguese Language Mailing List. My Portuguese is none too good, but the messages all seem to be of the 'kill this mailing list' and 'get me off this mailing list' sort. So I went to the user webpage for this list, stuck in 'webmaster at python.org' and asked it to send me my password. Nothing has happened, except getting more mail from the list. Mailing guardasmailing-owner hasn't done anything either, but well, it is Sunday. Is there some sort of special processing that I have forgotten about that can keep me from getting a password for webmaster at python.org so I can unsubscribe us from this thing? Laura --------------------------- Here are all the headers I get, in case it is of use. Return-Path: Received: from mail.python.org (mail.python.org [82.94.164.166]) by theraft.openend.se (8.14.4/8.14.4/Debian-4) with ESMTP id t85Gl0Aj026 936 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO ) for ; Sat, 5 Sep 2015 18:47:02 +0200 Received: by mail.python.org (Postfix) id 3n7hc420YrzQ8b; Sat, 5 Sep 2015 18:47:00 +0200 (CEST) Delivered-To: webmaster at mail.python.org Received: from albatross.python.org (localhost [127.0.0.1]) by mail.python.org (Postfix) with ESMTP id 3n7hc41gWmzMyg for ; Sat, 5 Sep 2015 18:47:00 +0200 (CEST) X-Spam-Status: UNSURE 0.691 X-Spam-Level: ****** Received: from localhost (HELO mail.python.org) (127.0.0.1) by albatross.python.org with SMTP; 05 Sep 2015 18:47:00 +0200 Received: from brs28.brs.com.br (host54-175.brs.com.br [177.11.54.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.python.org (Postfix) with ESMTPS for ; Sat, 5 Sep 2015 18:46:59 +0200 (CEST) Received: from localhost ([127.0.0.1]:50163 helo=brs28.brs.com.br) by brs28.brs.com.br with esmtp (Exim 4.85) (envelope-from ) id 1ZYGUq-0002uZ-OB; Sat, 05 Sep 2015 13:39:20 -0300 Received: from mail-ig0-f176.google.com ([209.85.213.176]:37598) by brs28.brs.com.br with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.85) (envelope-from ) id 1ZYGUf-0002sy-Q9 for guardasmailing at guardasmunicipais.com.br; Sat, 05 Sep 2015 13:39:10 -0300 Received: by igbni9 with SMTP id ni9so33685262igb.0 for ; Sat, 05 Sep 2015 09:39:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=HS7YzbpvP3V2kRn4J0APX3JnzEgHwfDEr6KUGqex8/0=; b=rzO4Gt8RgdFdbBY0BpHc2OwUt773y2NIAr1hixjGc1BBEbQRlFodmYpdkmQVOFcRa6 I0ClmdhSwJ+xjxVmFgtRrLV/9wHvWLW7/fmAF66dkZeYsejyMl3GLHNbDsYxlCov4IF0 tGcj0qgPU8G4tLiKpIqY2Hxr8vbMpVDOkSmmNcWTG/YZpxDvOYURQKtxEFtQgsmrWotr LLWnYb8EozOP0DDuZfP8Q7RU5EPUpaHG2+AxzEJkvmvzpH80eOODtO1ex5SRikl+loNH Npr9x4UQSgGAz7ibJTKtDU7wIvanBcCxQFBWDKOJz08Bpk+FYYph3T/LzJR9wcSkIlra +WkA== MIME-Version: 1.0 X-Received: by 10.50.13.72 with SMTP id f8mr17209489igc.50.1441471147066; Sat, 05 Sep 2015 09:39:07 -0700 (PDT) Received: by 10.107.47.96 with HTTP; Sat, 5 Sep 2015 09:39:06 -0700 (PDT) Received: by 10.107.47.96 with HTTP; Sat, 5 Sep 2015 09:39:06 -0700 (PDT) In-Reply-To: References: <55E9CFA3.50204 at terra.com.br> Date: Sat, 5 Sep 2015 13:39:06 -0300 Message-ID: From: Eduardo Borges To: Raquel Rosan Christino Gitahy Subject: Re: [Guardasmailing] =?utf-8?q?Urgente=3A_Solicita=C3=A7=C3=A3o_de_In?= =?utf-8?b?Zm9ybWHDp8O1ZXM=?= X-BeenThere: guardasmailing at guardasmunicipais.com.br X-Mailman-Version: 2.1.20 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Joao Werner Falk , "guardasmailing at guardasmunicipais.com.br" Content-Type: multipart/mixed; boundary="===============0204601574603855756==" Errors-To: guardasmailing-bounces at guardasmunicipais.com.br Sender: "Guardasmailing" X-AntiAbuse: This header was added to track abuse, please include it with any ab use report X-AntiAbuse: Primary Hostname - brs28.brs.com.br X-AntiAbuse: Original Domain - python.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - guardasmunicipais.com.br X-Get-Message-Sender-Via: brs28.brs.com.br: acl_c_authenticated_local_user: mail man/mailman From mark at msapiro.net Sun Sep 6 17:28:34 2015 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 6 Sep 2015 08:28:34 -0700 Subject: [Mailman-Users] Does mailman care about mail aliases? In-Reply-To: <201509060915.t869FVVP015013@fido.openend.se> References: <201509060915.t869FVVP015013@fido.openend.se> Message-ID: <55EC5BA2.8060907@msapiro.net> On 09/06/2015 02:15 AM, Laura Creighton wrote: > > So I went to the user webpage for this list, stuck in > 'webmaster at python.org' and asked it to send me my password. > Nothing has happened, except getting more mail from the list. > Mailing guardasmailing-owner hasn't done anything either, but > well, it is Sunday. > > Is there some sort of special processing that I have forgotten about > that can keep me from getting a password for webmaster at python.org > so I can unsubscribe us from this thing? The list should send the reminder if 'webmaster at python.org' is a member. The header below indicates that mail is being sent from the server to so that would appear to be the subscribed address unless it is being somehow rewritten by the sending server which seems unlikely. > Received: from brs28.brs.com.br (host54-175.brs.com.br [177.11.54.175]) > (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) > (No client certificate requested) > by mail.python.org (Postfix) with ESMTPS > for ; Sat, 5 Sep 2015 18:46:59 +0200 (CEST) I have looked through the mail logs on mail.python.org for Sept 5 and 6 (CEST) and I see no evidence of any reminder from the guardasmailing at guardasmunicipais.com.br list having arrives although I do see posts from the list, some accepted and some rejected by spambayes. I have requested unsubscribe of webmaster at python.org from guardasmailing at guardasmunicipais.com.br both by email and by web and another reminder by web. We'll see if the confirmations arrive. And I've now looked in the mail.log, and it seems all 3 of these messages are rejected by spambayes. I don't have time to look further, but there may be some ways to temporarily whitelist this server. They all come from host54-175.brs.com.br[177.11.54.175]. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From lac at openend.se Sun Sep 6 18:56:43 2015 From: lac at openend.se (Laura Creighton) Date: Sun, 06 Sep 2015 18:56:43 +0200 Subject: [Mailman-Users] Does mailman care about mail aliases? (fwd) Message-ID: <201509061656.t86Guhui031980@fido.openend.se> Trying to get us off that Portuguese mailing list. Seems spambayes thinks the unsubscribe mail it sends us is spam ... ------- Forwarded Message To: mailman-users at python.org References: <201509060915.t869FVVP015013 at fido.openend.se> From: Mark Sapiro Message-ID: <55EC5BA2.8060907 at msapiro.net> Date: Sun, 6 Sep 2015 08:28:34 -0700 On 09/06/2015 02:15 AM, Laura Creighton wrote: > > So I went to the user webpage for this list, stuck in > 'webmaster at python.org' and asked it to send me my password. > Nothing has happened, except getting more mail from the list. > Mailing guardasmailing-owner hasn't done anything either, but > well, it is Sunday. > > Is there some sort of special processing that I have forgotten about > that can keep me from getting a password for webmaster at python.org > so I can unsubscribe us from this thing? The list should send the reminder if 'webmaster at python.org' is a member. The header below indicates that mail is being sent from the server to so that would appear to be the subscribed address unless it is being somehow rewritten by the sending server which seems unlikely. > Received: from brs28.brs.com.br (host54-175.brs.com.br [177.11.54.175]) > (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) > (No client certificate requested) > by mail.python.org (Postfix) with ESMTPS > for ; Sat, 5 Sep 2015 18:46:59 +0200 (CEST) I have looked through the mail logs on mail.python.org for Sept 5 and 6 (CEST) and I see no evidence of any reminder from the guardasmailing at guardasmunicipais.com.br list having arrives although I do see posts from the list, some accepted and some rejected by spambayes. I have requested unsubscribe of webmaster at python.org from guardasmailing at guardasmunicipais.com.br both by email and by web and another reminder by web. We'll see if the confirmations arrive. And I've now looked in the mail.log, and it seems all 3 of these messages are rejected by spambayes. I don't have time to look further, but there may be some ways to temporarily whitelist this server. They all come from host54-175.brs.com.br[177.11.54.175]. - -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan - ------------------------------------------------------ Mailman-Users mailing list Mailman-Users at 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/lac%40openend.se ------- End of Forwarded Message From borjariesgo at gmail.com Mon Sep 7 11:47:12 2015 From: borjariesgo at gmail.com (Borja Riesgo Juan) Date: Mon, 7 Sep 2015 11:47:12 +0200 Subject: [Mailman-Users] Fwd: BCC and bounces In-Reply-To: References: Message-ID: Hello My hosting doesn?t allow since mid August sending emails using BCC. I can send only 50 mails per hour. They recommend me to use mailman. I would like to use mailman just for sending mails for one or two users of the list. the rest of the members won?t be allow. So they must be moderated. yesterday i was trying, and this seems to work. the problems are: - if i send the messages using BCC, that is all at mydomian.com they see undisclosed recipients and the message is sent by all-bopunces at mydomain.com. I don?t want users see all-bounces at mydomain.com. I want the see that i send the message and they as the receivers. _ Secondly if i sent in CC, they see all at mydomain.com. i don't want them to see that. To sum up, i want that the list is something that they don?t know. how can i do that? Best regards, Borja Best regards, Borja From stephen at xemacs.org Mon Sep 7 14:10:49 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Mon, 07 Sep 2015 21:10:49 +0900 Subject: [Mailman-Users] Fwd: BCC and bounces In-Reply-To: References: Message-ID: <8737yq2zw6.fsf@uwakimon.sk.tsukuba.ac.jp> Borja Riesgo Juan writes: > I want the see that i send the message and they as the receivers. For a sufficiently recent mailman (I think that includes everything in common use nowadays) in the *administrative interface* to the list in the *Non-digest options* screen, you will find an option to *personalize* messages. In my Mailman that is the second option from the top in that screen. Set it to "Full Personalization". That should be all you need to achieve what you have asked for in this post. Then send your messages with To: all at mydomain.com From: borjariesgo at gmail.com (or borja at mydomain.com or ...) Mailman will *remove* "all at mydomain.com" and substitute each person's address in To:, in a separate email for each address. Then person at example.net will see To: "M. A. Person" From: borjariesgo at gmail.com (only one "To" address no matter how many people are on the list). From lac at openend.se Mon Sep 7 15:58:00 2015 From: lac at openend.se (Laura Creighton) Date: Mon, 07 Sep 2015 15:58:00 +0200 Subject: [Mailman-Users] Fwd: BCC and bounces In-Reply-To: <8737yq2zw6.fsf@uwakimon.sk.tsukuba.ac.jp> References: <8737yq2zw6.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <201509071358.t87Dw0up023672@fido.openend.se> Should we get rid of this page/FAQ entry http://wiki.list.org/DOC/How%20do%20I%20hide%20the%20fact%20that%20I%27m%20using%20a%20mailing%20list%20management%20system%3F then? And talk about Full Personalisation instead? Laura From stephen at xemacs.org Mon Sep 7 17:36:44 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Tue, 08 Sep 2015 00:36:44 +0900 Subject: [Mailman-Users] Fwd: BCC and bounces In-Reply-To: <201509071358.t87Dw0up023672@fido.openend.se> References: <8737yq2zw6.fsf@uwakimon.sk.tsukuba.ac.jp> <201509071358.t87Dw0up023672@fido.openend.se> Message-ID: <87zj0y1bsj.fsf@uwakimon.sk.tsukuba.ac.jp> Laura Creighton writes: > Should we get rid of this page/FAQ entry > http://wiki.list.org/DOC/How%20do%20I%20hide%20the%20fact%20that%20I%27m%20using%20a%20mailing%20list%20management%20system%3F > > then? And talk about Full Personalisation instead? I think adding a mention of Full Personalization might be in order if that's all that is wanted. However, it appears to me that the original question that resulted in this FAQ entry wanted to completely eradicate Mailman from the headers, no List-*, no Sender, and maybe even no Received header mentioning that the message was apparently to a Mailman list. And that's a different kettle of fish. My understanding of Borja's request is that he simply wants normal traffic to appear to go To the recipient From him, but that he's not concerned in completely hiding the presence of the list from people who know where to look. From stephen at xemacs.org Mon Sep 7 18:01:58 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Tue, 08 Sep 2015 01:01:58 +0900 Subject: [Mailman-Users] Fwd: BCC and bounces In-Reply-To: References: <8737yq2zw6.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <87y4gi1amh.fsf@uwakimon.sk.tsukuba.ac.jp> Please make sure the list is Cc'ed (use Reply to All). Borja Riesgo Juan writes: > Sorry stpehen. Than you but i don?t find *personalize* messages ni full > personalization in my adminsitrative interface. i have this option "Header > added to mail sent to regular list members" bu ti think it?s not the > correct one. No, that's not the right one. I guess your system is not set up to permit personalized delivery. To enable it, you need to add OWNERS_CAN_ENABLE_PERSONALIZATION = Yes to the mm_cfg.py configuration file. Unfortunately, it sounds like you are using a cheap shared host for your domain, and it's probable that you don't have access to that file and your ISP won't make this change for you (it can put a lot of pressure on their mail server). In that case, there's really nothing you can do to get Mailman to send mail that appears to be addressed "To: One Recipient" -- it's just against your ISP's rules. But try asking your ISP. If not, the best you can do is use Mailman as a mailing list manager, and hope people don't mind. From stephen at xemacs.org Mon Sep 7 18:41:16 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Tue, 08 Sep 2015 01:41:16 +0900 Subject: [Mailman-Users] Fwd: BCC and bounces In-Reply-To: <87zj0y1bsj.fsf@uwakimon.sk.tsukuba.ac.jp> References: <8737yq2zw6.fsf@uwakimon.sk.tsukuba.ac.jp> <201509071358.t87Dw0up023672@fido.openend.se> <87zj0y1bsj.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <87vbbm18sz.fsf@uwakimon.sk.tsukuba.ac.jp> Stephen J. Turnbull writes: > Laura Creighton writes: > > Should we get rid of this page/FAQ entry "How do I hide the fact > > that I%27m using a mailing list management system?" > > > > then? And talk about Full Personalisation instead? > > I think adding a mention of Full Personalization might be in order if > that's all that is wanted. OK, I've done this and a little bit more; see: http://wiki.list.org/DOC/How%20do%20I%20hide%20the%20fact%20that%20I%27m%2\ 0using%20a%20mailing%20list%20management%20system%3F WDYT? Steve From lac at openend.se Mon Sep 7 19:57:37 2015 From: lac at openend.se (Laura Creighton) Date: Mon, 07 Sep 2015 19:57:37 +0200 Subject: [Mailman-Users] Fwd: BCC and bounces In-Reply-To: <87vbbm18sz.fsf@uwakimon.sk.tsukuba.ac.jp> References: <8737yq2zw6.fsf@uwakimon.sk.tsukuba.ac.jp> <201509071358.t87Dw0up023672@fido.openend.se> <87zj0y1bsj.fsf@uwakimon.sk.tsukuba.ac.jp> <87vbbm18sz.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <201509071757.t87HvbKx019338@fido.openend.se> In a message of Tue, 08 Sep 2015 01:41:16 +0900, "Stephen J. Turnbull" writes: >http://wiki.list.org/DOC/How%20do%20I%20hide%20the%20fact%20that%20I%27m%2\ >0using%20a%20mailing%20list%20management%20system%3F > >WDYT? > >Steve Looks reasonable to me. By the way, CiviCRM advertises mailman integration. http://wiki.civicrm.org/confluence/display/CRMDOC/Mailman+synchronization though I don't suppose we should be recommending any particular CRM. Laura From billynoah at zuma-design.com Tue Sep 8 15:14:29 2015 From: billynoah at zuma-design.com (billy noah) Date: Tue, 8 Sep 2015 09:14:29 -0400 Subject: [Mailman-Users] Error updating mailman Ubuntu 14.04.3 In-Reply-To: <55E264BC.5050002@msapiro.net> References: <55E264BC.5050002@msapiro.net> Message-ID: Thanks everyone. I am pretty sure no newer version was ever installed from source and it remains a mystery what went wrong. Asked on askubuntu.com and got this recommendation which did resolve the issue: cd /var/lib/dpkg/info/ rm mailman* apt-get clean all On Sat, Aug 29, 2015 at 10:04 PM, Mark Sapiro wrote: > On 08/25/2015 04:28 PM, billy noah wrote: > > Tried running an update today and received this message: > > > > Setting up mailman (1:2.1.16-2ubuntu0.1) ... > ... > > Downgrade detected, from version 0x20112f1 to version 0x20110f0 > > > I'm with Steve on this. This is very wierd. The first message says you > are setting up 2.1.16-2 and the later message says you are downgrading > from 2.1.12-1 to 2.1.10. > > > > Any ideas what I can do to remedy this? > > > You can run Mailman's 'bin/update --force' manually, but I wouldn't > recommend it, because something unknown is messed up. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at 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/billynoah%40zuma-design.com > From harrison at utm.edu Tue Sep 8 15:43:41 2015 From: harrison at utm.edu (Bruce Harrison) Date: Tue, 8 Sep 2015 13:43:41 +0000 Subject: [Mailman-Users] strange postings to non-existant lists Message-ID: For the last month or two, I get anywhere from 3 or 4 to 20 to 30 postings to non-existent lists on our mailman server. I've been reading of course about the subscribe spamming that folks have been talking about. Is this just someone poking at our mailman machine trying to find something to send spam to, or something more sinister? We use Microsoft filtering for spam, viruses, etc. so all mail I see comes from one of their servers. It's not causing any problems, but just strange to me. Comments? Bruce Harrison Univ. of Tennessee at Maritn From andrew at hodgsonfamily.org Tue Sep 8 15:57:51 2015 From: andrew at hodgsonfamily.org (Andrew Hodgson) Date: Tue, 8 Sep 2015 13:57:51 +0000 Subject: [Mailman-Users] strange postings to non-existant lists In-Reply-To: References: Message-ID: Bruce Harrison wrote: >For the last month or two, I get anywhere from 3 or 4 to 20 to 30 postings to non-existent lists on our mailman server. I've been reading of course about the subscribe spamming that folks have been talking about. >Is this just someone poking at our mailman machine trying to find something to send spam to, or something more sinister? We use Microsoft filtering for spam, viruses, etc. so all mail I see comes from one of their servers. >It's not causing any problems, but just strange to me. I haven't seen spammers subscribe to the lists properly (i.e, respond to the Mailman response), but I've had a lot of messages going to invalid users at the list domains and also to the subscribe/unsubscribe/request address, which was creating a lot of backscatter. >From my point of view I want to try and avoid accepting and processing spam mail and mail to invalid lists/recipients to try and avoid backscatter. I installed a local copy of SpamAssassin which seems to be working really well and rejects spam over a score of around 7. This seems to let list traffic through whilst blocking the spam messages. I also removed frontline MX servers from the lists domain so they get handled by the Exim server doing the processing, so that any 5XX response that the server sends out causes the spam server to give up, rather than a frontline MX server having to generate the NDR and send it out to the probably innocent party. To this end we used to use MS Office 365 spam scanning on the list domains, but don't use it anymore for this reason. Hope this helps, Andrew. From harrison at utm.edu Tue Sep 8 16:12:16 2015 From: harrison at utm.edu (Bruce Harrison) Date: Tue, 8 Sep 2015 14:12:16 +0000 Subject: [Mailman-Users] strange postings to non-existant lists In-Reply-To: References: Message-ID: Interesting, I may give SpamAssassin a look. Thanks! Mine are almost always mail to invalid lists. My box talks to our local mail processor, which in turn runs off-campus thru the MS filters/scanners and on out. Bruce UTM -----Original Message----- From: Andrew Hodgson [mailto:andrew at hodgsonfamily.org] Sent: Tuesday, September 08, 2015 8:58 AM To: Bruce Harrison; mailman-users at python.org Subject: RE: strange postings to non-existant lists Bruce Harrison wrote: >For the last month or two, I get anywhere from 3 or 4 to 20 to 30 postings to non-existent lists on our mailman server. I've been reading of course about the subscribe spamming that folks have been talking about. >Is this just someone poking at our mailman machine trying to find something to send spam to, or something more sinister? We use Microsoft filtering for spam, viruses, etc. so all mail I see comes from one of their servers. >It's not causing any problems, but just strange to me. I haven't seen spammers subscribe to the lists properly (i.e, respond to the Mailman response), but I've had a lot of messages going to invalid users at the list domains and also to the subscribe/unsubscribe/request address, which was creating a lot of backscatter. >From my point of view I want to try and avoid accepting and processing spam mail and mail to invalid lists/recipients to try and avoid backscatter. I installed a local copy of SpamAssassin which seems to be working really well and rejects spam over a score of around 7. This seems to let list traffic through whilst blocking the spam messages. I also removed frontline MX servers from the lists domain so they get handled by the Exim server doing the processing, so that any 5XX response that the server sends out causes the spam server to give up, rather than a frontline MX server having to generate the NDR and send it out to the probably innocent party. To this end we used to use MS Office 365 spam scanning on the list domains, but don't use it anymore for this reason. Hope this helps, Andrew. From stephen at xemacs.org Tue Sep 8 19:12:12 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Wed, 09 Sep 2015 02:12:12 +0900 Subject: [Mailman-Users] strange postings to non-existant lists In-Reply-To: References: Message-ID: <87h9n425ub.fsf@uwakimon.sk.tsukuba.ac.jp> Bruce Harrison writes: > Mine are almost always mail to invalid lists. What makes you think these are "lists"? Simply the fact that they're addressed to the Mailman machine? Or are they decommissioned lists or something like that? In general, spammers often seem to pick random mailboxes or common ones (like "webmaster"), or ones that appear on websites. A computer users' group once posted "Our meeting will be held in the seminar room at sponsor.com" (the familiar name of the company, like Amazon.com), and sure enough, a couple of spams to "room at sponsor.com" were received. For spam filtering, besides SpamAssassin, many Mailman lists use SpamBayes. (SpamAssassin is the most popular, but SpamBayes uses a somewhat different approach, so might catch spam that SpamAssassin doesn't.) From andrew at hodgsonfamily.org Tue Sep 8 19:22:47 2015 From: andrew at hodgsonfamily.org (Andrew Hodgson) Date: Tue, 8 Sep 2015 17:22:47 +0000 Subject: [Mailman-Users] strange postings to non-existant lists In-Reply-To: References: Message-ID: Bruce Harrison wrote: >Interesting, I may give SpamAssassin a look. Thanks! One thing here which I forgot is if your machine is not receiving mail directly, you may have less luck with SpamAssassin due to the mail always coming in from a downstream server. It is easy to overcome but needs more configuration. >Mine are almost always mail to invalid lists. Are these lists which used to exist, or just random addresses on the system? >My box talks to our local mail processor, which in turn runs off-campus thru the MS filters/scanners and on out. It's incoming mail we're interested in here, does that get handled directly or via filtering machines to? Andrew. From harrison at utm.edu Tue Sep 8 19:25:46 2015 From: harrison at utm.edu (Bruce Harrison) Date: Tue, 8 Sep 2015 17:25:46 +0000 Subject: [Mailman-Users] strange postings to non-existant lists In-Reply-To: References: Message-ID: These are just random addresses, never existed on my mailman machine. Incoming gets filtered by Microsoft setup. Bruce UTM -----Original Message----- From: Andrew Hodgson [mailto:andrew at hodgsonfamily.org] Sent: Tuesday, September 08, 2015 12:23 PM To: Bruce Harrison; mailman-users at python.org Subject: RE: strange postings to non-existant lists Bruce Harrison wrote: >Interesting, I may give SpamAssassin a look. Thanks! One thing here which I forgot is if your machine is not receiving mail directly, you may have less luck with SpamAssassin due to the mail always coming in from a downstream server. It is easy to overcome but needs more configuration. >Mine are almost always mail to invalid lists. Are these lists which used to exist, or just random addresses on the system? >My box talks to our local mail processor, which in turn runs off-campus thru the MS filters/scanners and on out. It's incoming mail we're interested in here, does that get handled directly or via filtering machines to? Andrew. From pete at bossley.me Tue Sep 8 23:32:42 2015 From: pete at bossley.me (Peter Bossley) Date: Tue, 8 Sep 2015 21:32:42 +0000 Subject: [Mailman-Users] Fwd: BCC and bounces In-Reply-To: <8737yq2zw6.fsf@uwakimon.sk.tsukuba.ac.jp> References: <8737yq2zw6.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: But it appears as though the list posting address still winds up in the CC: field even with FP turned on. It does send a message to each recipient but I am wondering how one would go about removing the list address in the CC: field to avoid people replying all. -----Original Message----- From: Mailman-Users [mailto:mailman-users-bounces+pete=bossley.me at python.org] On Behalf Of Stephen J. Turnbull Sent: Monday, September 7, 2015 8:11 AM To: borjariesgo at gmail.com Cc: mailman-users at python.org Subject: [Mailman-Users] Fwd: BCC and bounces Borja Riesgo Juan writes: > I want the see that i send the message and they as the receivers. For a sufficiently recent mailman (I think that includes everything in common use nowadays) in the *administrative interface* to the list in the *Non-digest options* screen, you will find an option to *personalize* messages. In my Mailman that is the second option from the top in that screen. Set it to "Full Personalization". That should be all you need to achieve what you have asked for in this post. Then send your messages with To: all at mydomain.com From: borjariesgo at gmail.com (or borja at mydomain.com or ...) Mailman will *remove* "all at mydomain.com" and substitute each person's address in To:, in a separate email for each address. Then person at example.net will see To: "M. A. Person" From: borjariesgo at gmail.com (only one "To" address no matter how many people are on the list). ------------------------------------------------------ Mailman-Users mailing list Mailman-Users at 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/pete%40bossley.me From mark at tafn.org.uk Wed Sep 9 00:12:44 2015 From: mark at tafn.org.uk (Mark Tyler) Date: Tue, 8 Sep 2015 23:12:44 +0100 Subject: [Mailman-Users] can any one help Message-ID: <55EF5D5C.3050004@tafn.org.uk> Hi i keep getting the folowing emails Clamscan reports Sanesecurity honeynet.hdb database integrity tested BAD - SKIPPING rsync: link_stat "/var/cache/clamav-unofficial-sigs/si-dbs/honeynet.hdb" failed: No such file or directory (2) rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1070) [sender=3.0.9] Failed to successfully update SecuriteInfo production database file: honeynet.hdb - SKIPPING Clamscan reports Sanesecurity securiteinfobat.hdb database integrity tested BAD - SKIPPING rsync: link_stat "/var/cache/clamav-unofficial-sigs/si-dbs/securiteinfobat.hdb" failed: No such file or directory (2) rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1070) [sender=3.0.9] Failed to successfully update SecuriteInfo production database file: securiteinfobat.hdb - SKIPPING Clamscan reports Sanesecurity securiteinfodos.hdb database integrity tested BAD - SKIPPING rsync: link_stat "/var/cache/clamav-unofficial-sigs/si-dbs/securiteinfodos.hdb" failed: No such file or directory (2) rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1070) [sender=3.0.9] Failed to successfully update SecuriteInfo production database file: securiteinfodos.hdb - SKIPPING Clamscan reports Sanesecurity securiteinfoelf.hdb database integrity tested BAD - SKIPPING rsync: link_stat "/var/cache/clamav-unofficial-sigs/si-dbs/securiteinfoelf.hdb" failed: No such file or directory (2) rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1070) [sender=3.0.9] Failed to successfully update SecuriteInfo production database file: securiteinfoelf.hdb - SKIPPING Clamscan reports Sanesecurity securiteinfooffice.hdb database integrity tested BAD - SKIPPING rsync: link_stat "/var/cache/clamav-unofficial-sigs/si-dbs/securiteinfooffice.hdb" failed: No such file or directory (2) rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1070) [sender=3.0.9] Failed to successfully update SecuriteInfo production database file: securiteinfooffice.hdb - SKIPPING Clamscan reports Sanesecurity securiteinfopdf.hdb database integrity tested BAD - SKIPPING rsync: link_stat "/var/cache/clamav-unofficial-sigs/si-dbs/securiteinfopdf.hdb" failed: No such file or directory (2) rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1070) [sender=3.0.9] Failed to successfully update SecuriteInfo production database file: securiteinfopdf.hdb - SKIPPING Clamscan reports Sanesecurity securiteinfosh.hdb database integrity tested BAD - SKIPPING rsync: link_stat "/var/cache/clamav-unofficial-sigs/si-dbs/securiteinfosh.hdb" failed: No such file or directory (2) rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1070) [sender=3.0.9] Failed to successfully update SecuriteInfo production database file: securiteinfosh.hdb - SKIPPING From mark at msapiro.net Wed Sep 9 03:09:05 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 8 Sep 2015 18:09:05 -0700 Subject: [Mailman-Users] Fwd: BCC and bounces In-Reply-To: References: <8737yq2zw6.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <55EF86B1.5040702@msapiro.net> On 09/08/2015 02:32 PM, Peter Bossley wrote: > But it appears as though the list posting address still winds up in the CC: field even with FP turned on. It does send a message to each recipient but I am wondering how one would go about removing the list address in the CC: field to avoid people replying all. Mailman is not designed to hide the fact that its messages come from a mailing list. If a list is fully personalized, the list posting address is put in Cc: intentionally to facilitate replying to the list. This is a design decision and can only be changed by modifying the code in Mailman/Handlers/CookHeaders.py. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Wed Sep 9 03:19:13 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 8 Sep 2015 18:19:13 -0700 Subject: [Mailman-Users] can any one help In-Reply-To: <55EF5D5C.3050004@tafn.org.uk> References: <55EF5D5C.3050004@tafn.org.uk> Message-ID: <55EF8911.7070001@msapiro.net> On 09/08/2015 03:12 PM, Mark Tyler wrote: > Hi i keep getting the folowing emails > Clamscan reports Sanesecurity honeynet.hdb database integrity tested BAD > - SKIPPING > rsync: link_stat "/var/cache/clamav-unofficial-sigs/si-dbs/honeynet.hdb" > failed: No such file or directory (2) > rsync error: some files/attrs were not transferred (see previous errors) > (code 23) at main.c(1070) [sender=3.0.9] > Failed to successfully update SecuriteInfo production database file: > honeynet.hdb - SKIPPING > Clamscan reports Sanesecurity securiteinfobat.hdb database integrity > tested BAD - SKIPPING ... These messages have nothing to do with Mailman. Are you sure you didn't mean to send this to ? The messages appear to originate from Bill Landry's clamav-unofficial-sigs script . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Wed Sep 9 03:43:46 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 8 Sep 2015 18:43:46 -0700 Subject: [Mailman-Users] Fwd: BCC and bounces In-Reply-To: References: Message-ID: <55EF8ED2.1040907@msapiro.net> On 09/07/2015 02:47 AM, Borja Riesgo Juan wrote: > > - if i send the messages using BCC, that is all at mydomian.com they see > undisclosed recipients and the message is sent by all-bopunces at mydomain.com. > I don?t want users see all-bounces at mydomain.com. I want the see that i send > the message and they as the receivers. I'm coming in late here and most of this thread has been covered, but with respect to the above, the all-bounces at mydomain.com address is the list bounce processing address. Mailman sets the envelope sender and also the Sender: and Errors-To: headers to this value. If your users are seeing this address, it is probably because they are using a Microsoft mail client that displays something like "From: (the Sender: address) on behalf of (the From: address)". Since Mailman 2.1.14, if a site allows it, there is a list admin General Options -> include_sender_header setting which can be set to No to not include the Sender: header. The all-bounces at mydomain.com address will still be the envelope sender and in the Errors-To: header, but most users won't see it. Also see my other reply in this thread at . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From andrew at hodgsonfamily.org Wed Sep 9 00:41:19 2015 From: andrew at hodgsonfamily.org (Andrew Hodgson) Date: Tue, 8 Sep 2015 22:41:19 +0000 Subject: [Mailman-Users] can any one help In-Reply-To: <55EF5D5C.3050004@tafn.org.uk> References: <55EF5D5C.3050004@tafn.org.uk> Message-ID: Hi, This is nothing to do with Mailman, I suggest looking at a ClamAV related list or if your system was set up by someone speak to them to find out how it was set up. If you are still stuck over the weekend give me a shout and I can give you some options as I am hosting some mailing lists for blind specific charities in the UK at the moment. Andrew. -----Original Message----- From: Mailman-Users [mailto:mailman-users-bounces+andrew=hodgsonfamily.org at python.org] On Behalf Of Mark Tyler Sent: 08 September 2015 23:13 To: Mailman-Users at python.org Subject: [Mailman-Users] can any one help Hi i keep getting the folowing emails Clamscan reports Sanesecurity honeynet.hdb database integrity tested BAD - SKIPPING rsync: link_stat "/var/cache/clamav-unofficial-sigs/si-dbs/honeynet.hdb" failed: No such file or directory (2) rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1070) [sender=3.0.9] Failed to successfully update SecuriteInfo production database file: honeynet.hdb - SKIPPING Clamscan reports Sanesecurity securiteinfobat.hdb database integrity tested BAD - SKIPPING rsync: link_stat "/var/cache/clamav-unofficial-sigs/si-dbs/securiteinfobat.hdb" failed: No such file or directory (2) rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1070) [sender=3.0.9] Failed to successfully update SecuriteInfo production database file: securiteinfobat.hdb - SKIPPING Clamscan reports Sanesecurity securiteinfodos.hdb database integrity tested BAD - SKIPPING rsync: link_stat "/var/cache/clamav-unofficial-sigs/si-dbs/securiteinfodos.hdb" failed: No such file or directory (2) rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1070) [sender=3.0.9] Failed to successfully update SecuriteInfo production database file: securiteinfodos.hdb - SKIPPING Clamscan reports Sanesecurity securiteinfoelf.hdb database integrity tested BAD - SKIPPING rsync: link_stat "/var/cache/clamav-unofficial-sigs/si-dbs/securiteinfoelf.hdb" failed: No such file or directory (2) rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1070) [sender=3.0.9] Failed to successfully update SecuriteInfo production database file: securiteinfoelf.hdb - SKIPPING Clamscan reports Sanesecurity securiteinfooffice.hdb database integrity tested BAD - SKIPPING rsync: link_stat "/var/cache/clamav-unofficial-sigs/si-dbs/securiteinfooffice.hdb" failed: No such file or directory (2) rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1070) [sender=3.0.9] Failed to successfully update SecuriteInfo production database file: securiteinfooffice.hdb - SKIPPING Clamscan reports Sanesecurity securiteinfopdf.hdb database integrity tested BAD - SKIPPING rsync: link_stat "/var/cache/clamav-unofficial-sigs/si-dbs/securiteinfopdf.hdb" failed: No such file or directory (2) rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1070) [sender=3.0.9] Failed to successfully update SecuriteInfo production database file: securiteinfopdf.hdb - SKIPPING Clamscan reports Sanesecurity securiteinfosh.hdb database integrity tested BAD - SKIPPING rsync: link_stat "/var/cache/clamav-unofficial-sigs/si-dbs/securiteinfosh.hdb" failed: No such file or directory (2) rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1070) [sender=3.0.9] Failed to successfully update SecuriteInfo production database file: securiteinfosh.hdb - SKIPPING ------------------------------------------------------ Mailman-Users mailing list Mailman-Users at 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/andrew%40hodgsonfamily.org From pete at bossley.me Wed Sep 9 14:04:00 2015 From: pete at bossley.me (Peter Bossley) Date: Wed, 9 Sep 2015 12:04:00 +0000 Subject: [Mailman-Users] Fwd: BCC and bounces In-Reply-To: <55EF86B1.5040702@msapiro.net> References: <8737yq2zw6.fsf@uwakimon.sk.tsukuba.ac.jp> <55EF86B1.5040702@msapiro.net> Message-ID: I think the easiest approach here is to simply set the list to FP, and live with the list address in the CC. At that point, you simply set everyone to moderated and set that action to discard. (I'm only using this for wedding updates anyway, and anyone that really knows where to look will find the list headers anyway.) -----Original Message----- From: Mailman-Users [mailto:mailman-users-bounces+pete=bossley.me at python.org] On Behalf Of Mark Sapiro Sent: Tuesday, September 8, 2015 9:09 PM To: mailman-users at python.org Subject: Re: [Mailman-Users] Fwd: BCC and bounces On 09/08/2015 02:32 PM, Peter Bossley wrote: > But it appears as though the list posting address still winds up in the CC: field even with FP turned on. It does send a message to each recipient but I am wondering how one would go about removing the list address in the CC: field to avoid people replying all. Mailman is not designed to hide the fact that its messages come from a mailing list. If a list is fully personalized, the list posting address is put in Cc: intentionally to facilitate replying to the list. This is a design decision and can only be changed by modifying the code in Mailman/Handlers/CookHeaders.py. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users at 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/pete%40bossley.me From cybergram at eastlink.ca Thu Sep 10 02:26:29 2015 From: cybergram at eastlink.ca (Nancy C) Date: Wed, 09 Sep 2015 21:26:29 -0300 Subject: [Mailman-Users] Potential "Bounce" Question Message-ID: <03eb01d0eb5f$568ce880$03a6b980$@eastlink.ca> I am the admin for a group & some members frequently get warning messages like this: "Your current bounce score is 3.0 out of a maximum of 5.0" The subscriber has done nothing wrong & these messages are usually Hotmail, yahoo & aol accounts. What can be done to reduce / eliminate these messages? Thank you Nancy From brian at emwd.com Thu Sep 10 04:35:34 2015 From: brian at emwd.com (Brian Carpenter) Date: Wed, 9 Sep 2015 22:35:34 -0400 Subject: [Mailman-Users] Potential "Bounce" Question In-Reply-To: <03eb01d0eb5f$568ce880$03a6b980$@eastlink.ca> References: <03eb01d0eb5f$568ce880$03a6b980$@eastlink.ca> Message-ID: <1d7901d0eb71$5eb5a9e0$1c20fda0$@emwd.com> What version of Mailman are you using? It sounds like a DMARC issue going on. Brian Carpenter Owner Providing Cloud Services and more for over 15 years. T: 336.755.0685 E: brian at emwd.com www.emwd.com ? > -----Original Message----- > From: Mailman-Users [mailto:mailman-users- > bounces+brian=emwd.com at python.org] On Behalf Of Nancy C > Sent: Wednesday, September 09, 2015 8:26 PM > To: mailman-users at python.org > Subject: [Mailman-Users] Potential "Bounce" Question > > I am the admin for a group & some members frequently get warning > messages > like this: > > > > "Your current bounce score is 3.0 out of a maximum of 5.0" > > > > The subscriber has done nothing wrong & these messages are usually > Hotmail, > yahoo & aol accounts. > > > > What can be done to reduce / eliminate these messages? > > > > Thank you > > Nancy > > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at 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/brian%40emwd.com From mark at msapiro.net Thu Sep 10 07:26:31 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 9 Sep 2015 22:26:31 -0700 Subject: [Mailman-Users] Potential "Bounce" Question In-Reply-To: <03eb01d0eb5f$568ce880$03a6b980$@eastlink.ca> References: <03eb01d0eb5f$568ce880$03a6b980$@eastlink.ca> Message-ID: <55F11487.2010006@msapiro.net> On 09/09/2015 05:26 PM, Nancy C wrote: > > The subscriber has done nothing wrong & these messages are usually Hotmail, > yahoo & aol accounts. As Brian says, it sounds like DMARC. See the FAQ article at . Also, see for background information. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From beakerboy99 at yahoo.com Wed Sep 9 22:44:03 2015 From: beakerboy99 at yahoo.com (Kevin Nowaczyk) Date: Wed, 9 Sep 2015 13:44:03 -0700 Subject: [Mailman-Users] Forbidden Mailman Archive Message-ID: <1441831443.87002.YahooMailBasic@web181704.mail.ne1.yahoo.com> This seems to be a somewhat common problem, so I've looked at the archives at all the suggestions, tried everything that is recent and nothing has worked. It looks like no archives are actually being created, despite the "yes" option being selected in the list configuration. Thanks for any help. Kevin Nowaczyk I'm running mailman 2.1.18 on debian 8.2 (Jessie) mm_cfg.py has the line DEFAULT_URL_PATTERN = 'http://%s/' and no value for PUBLIC_ARCHIVE_URL. messing with these setting seemed to be a 10 year old issue, so I didn't play around with this for fear of breaking something else My apache config: ServerName lists.example.com DocumentRoot /usr/lib/cgi-bin/mailman ErrorLog /var/log/apache2/lists-error.log CustomLog /var/log/apache2/lists-access.log combined Alias /pipermail/ /var/lib/mailman/archives/public/ Options +FollowSymLinks Order allow,deny Allow from all Alias /images/mailman/ /usr/share/images/mailman/ ScriptAlias /admin /usr/lib/cgi-bin/mailman/admin ScriptAlias /admindb /usr/lib/cgi-bin/mailman/admindb ScriptAlias /confirm /usr/lib/cgi-bin/mailman/confirm ScriptAlias /create /usr/lib/cgi-bin/mailman/create ScriptAlias /edithtml /usr/lib/cgi-bin/mailman/edithtml ScriptAlias /listinfo /usr/lib/cgi-bin/mailman/listinfo ScriptAlias /options /usr/lib/cgi-bin/mailman/options ScriptAlias /private /usr/lib/cgi-bin/mailman/private ScriptAlias /rmlist /usr/lib/cgi-bin/mailman/rmlist ScriptAlias /roster /usr/lib/cgi-bin/mailman/roster ScriptAlias /subscribe /usr/lib/cgi-bin/mailman/subscribe ScriptAlias /mailman/ /usr/lib/cgi-bin/mailman/ Directory Listing: .: total 16 drwxrwsr-x 4 root list 4096 Sep 9 20:35 . drwxrwsr-x 8 root list 4096 Jul 6 11:55 .. -rw-r--r-- 1 root list 0 Sep 9 20:35 list drwxrws--- 8 www-data list 4096 Feb 24 2015 private drwxrwsr-x 2 root list 4096 Sep 9 20:04 public ./private: total 32 drwxrws--- 8 www-data list 4096 Feb 24 2015 . drwxrwsr-x 4 root list 4096 Sep 9 20:35 .. drwxrwsr-x 2 root list 4096 Sep 9 19:40 LISTNAME drwxrwsr-x 2 root list 4096 Feb 14 2014 LISTNAME.mbox drwxrwsr-x 2 root list 4096 Feb 13 2014 mailman drwxrwsr-x 2 root list 4096 Feb 13 2014 mailman.mbox ./private/LISTNAME: total 12 drwxrwsr-x 2 root list 4096 Sep 9 19:40 . drwxrws--- 8 www-data list 4096 Feb 24 2015 .. -rw-rw-r-- 1 root list 493 Feb 14 2014 index.html ./private/LISTNAME.mbox: total 8 drwxrwsr-x 2 root list 4096 Feb 14 2014 . drwxrws--- 8 www-data list 4096 Feb 24 2015 .. ./private/mailman: total 12 drwxrwsr-x 2 root list 4096 Feb 13 2014 . drwxrws--- 8 www-data list 4096 Feb 24 2015 .. -rw-rw-r-- 1 root list 506 Feb 13 2014 index.html ./private/mailman.mbox: total 8 drwxrwsr-x 2 root list 4096 Feb 13 2014 . drwxrws--- 8 www-data list 4096 Feb 24 2015 .. ./public: total 8 drwxrwsr-x 2 root list 4096 Sep 9 20:04 . drwxrwsr-x 4 root list 4096 Sep 9 20:35 .. lrwxrwxrwx 1 root list 42 Feb 14 2014 LISTNAME -> /var/lib/mailman/archives/private/LISTNAME lrwxrwxrwx 1 root list 41 Feb 13 2014 mailman -> /var/lib/mailman/archives/private/mailman From mark at msapiro.net Thu Sep 10 09:10:06 2015 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 10 Sep 2015 00:10:06 -0700 Subject: [Mailman-Users] Forbidden Mailman Archive In-Reply-To: <1441831443.87002.YahooMailBasic@web181704.mail.ne1.yahoo.com> References: <1441831443.87002.YahooMailBasic@web181704.mail.ne1.yahoo.com> Message-ID: <55F12CCE.5000803@msapiro.net> On 09/09/2015 01:44 PM, Kevin Nowaczyk via Mailman-Users wrote: > It looks like no archives are actually being > created, despite the "yes" option being selected in the list > configuration. > > Thanks for any help. Kevin Nowaczyk > > I'm running mailman 2.1.18 on debian 8.2 (Jessie) > > mm_cfg.py has the line DEFAULT_URL_PATTERN = 'http://%s/' and no > value for PUBLIC_ARCHIVE_URL. messing with these setting seemed to be > a 10 year old issue, so I didn't play around with this for fear of > breaking something else These are irrelevant to your problem. > My apache config: As is your apache config. It is not a web server issue. > > Directory Listing: > > > .: > total 16 > drwxrwsr-x 4 root list 4096 Sep 9 20:35 . > drwxrwsr-x 8 root list 4096 Jul 6 11:55 .. > -rw-r--r-- 1 root list 0 Sep 9 20:35 list > drwxrws--- 8 www-data list 4096 Feb 24 2015 private > drwxrwsr-x 2 root list 4096 Sep 9 20:04 public This looks OK > ./private: > total 32 > drwxrws--- 8 www-data list 4096 Feb 24 2015 . > drwxrwsr-x 4 root list 4096 Sep 9 20:35 .. > drwxrwsr-x 2 root list 4096 Sep 9 19:40 LISTNAME > drwxrwsr-x 2 root list 4096 Feb 14 2014 LISTNAME.mbox > drwxrwsr-x 2 root list 4096 Feb 13 2014 mailman > drwxrwsr-x 2 root list 4096 Feb 13 2014 mailman.mbox As does this > ./private/LISTNAME: > total 12 > drwxrwsr-x 2 root list 4096 Sep 9 19:40 . > drwxrws--- 8 www-data list 4096 Feb 24 2015 .. > -rw-rw-r-- 1 root list 493 Feb 14 2014 index.html And this says the archive is empty. > ./private/LISTNAME.mbox: > total 8 > drwxrwsr-x 2 root list 4096 Feb 14 2014 . > drwxrws--- 8 www-data list 4096 Feb 24 2015 .. And no LISTNAME.mbox/LISTNAME.mbox file says archiving never got far. > ./private/mailman: > total 12 > drwxrwsr-x 2 root list 4096 Feb 13 2014 . > drwxrws--- 8 www-data list 4096 Feb 24 2015 .. > -rw-rw-r-- 1 root list 506 Feb 13 2014 index.html > > ./private/mailman.mbox: > total 8 > drwxrwsr-x 2 root list 4096 Feb 13 2014 . > drwxrws--- 8 www-data list 4096 Feb 24 2015 .. Ditto for the mailman list, but it may never have gotten a post. > ./public: > total 8 > drwxrwsr-x 2 root list 4096 Sep 9 20:04 . > drwxrwsr-x 4 root list 4096 Sep 9 20:35 .. > lrwxrwxrwx 1 root list 42 Feb 14 2014 LISTNAME -> /var/lib/mailman/archives/private/LISTNAME > lrwxrwxrwx 1 root list 41 Feb 13 2014 mailman -> /var/lib/mailman/archives/private/mailman OK, but not really relevant to the issue. Is ArchRunner running? Is anything in /var/lib/mailman/queue/archive? What's in /var/lib/mailman/logs/qrunner and /var/lib/mailman/logs/error? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Sep 10 09:22:46 2015 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 10 Sep 2015 00:22:46 -0700 Subject: [Mailman-Users] Forbidden Mailman Archive In-Reply-To: <1441831443.87002.YahooMailBasic@web181704.mail.ne1.yahoo.com> References: <1441831443.87002.YahooMailBasic@web181704.mail.ne1.yahoo.com> Message-ID: <55F12FC6.4050700@msapiro.net> On 09/09/2015 01:44 PM, Kevin Nowaczyk via Mailman-Users wrote: > This seems to be a somewhat common problem, so I've looked at the archives at all the suggestions, tried everything that is recent and nothing has worked. It looks like no archives are actually being created, despite the "yes" option being selected in the list configuration. My previous reply assumed that there had been successful posts to the list that weren't archived, but the "Forbidden" in the subject may imply that there have been no posts, but you are getting a 403 Forbidden status from apache when attempting to go to the archives. If this is the issue, the problem is probably that you have apache 2.4 and this > Alias /pipermail/ /var/lib/mailman/archives/public/ > > Options +FollowSymLinks > Order allow,deny > Allow from all > needs to be Alias /pipermail/ /var/lib/mailman/archives/public/ Options +FollowSymLinks Require all granted If that isn't the answer, but the issue is 403 Forbidden, what's in /var/log/apache2/lists-error.log? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From stephen at xemacs.org Thu Sep 10 10:42:37 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Thu, 10 Sep 2015 17:42:37 +0900 Subject: [Mailman-Users] Potential "Bounce" Question In-Reply-To: <03eb01d0eb5f$568ce880$03a6b980$@eastlink.ca> References: <03eb01d0eb5f$568ce880$03a6b980$@eastlink.ca> Message-ID: <8737ym1x8i.fsf@uwakimon.sk.tsukuba.ac.jp> @Mark & anybody else familiar with the FAQ: Some of the information below isn't in the DMARC FAQ, and some of it doesn't seem to be in FAQ at all. Pointers to relevant FAQs would be appreciated as I will update & xref in the next few days as I find time. Nancy C writes: > I am the admin for a group & some members frequently get warning messages > like this: > > "Your current bounce score is 3.0 out of a maximum of 5.0" > > The subscriber has done nothing wrong & these messages are usually > Hotmail, yahoo & aol accounts. The subscriber may have done nothing wrong -- but they chose evil and incompetent providers. "Friends don't let friends use Yahoo! or AOL." In practice, it's really hard to get people to change providers, so I don't recommend that you try. However, these sites are actively disrupting the whole mail system (not just mailing lists) to cover up for massive security breaches leading to the leakage of millions of contact lists to professional spammers. Not nice. > What can be done to reduce / eliminate these messages? The first thing I would suggest is to upgrade Mailman. As far as I can tell, Mailman 2.1.20 doesn't send those messages, period (there's a template for it, but I can't find anywhere it's used). It sends a message when the account is disabled, and then at intervals thereafter. (Mark Sapiro would know better, though.) If it *does* send those messages, I'm sure it's triggered by actual bounces: those users are losing posts. As Brian and Mark point out, a likely cause of frequent bounces is the DMARC p=reject policy used by Yahoo! and AOL. This policy effectively requires that mail "From" a user of one of those sites be delivered directly by a mail server at those sites, a condition which cannot be satisfied by a public mailing list.[1] The most popular[2] way to address this condition is to use Mailman >= 2.1.18-1, and set the "Privacy Options > Sender Filters > dmarc_moderation_action" to "Munge From". You should review your settings in the "Reply-To header munging" section of the "General Options", as there are interactions between the DMARC moderation action and Reply-To. (In Mailman 2.1.20 several adjustments were made to improve the default settings and options available, but 2.1.18-1 and 2.1.19 are usable with care.) There are other options for your consideration, but this is by far the most popular. Another possibility is that those systems have become very paranoid about spam, and reject mail for various and sundry (ie, quite random) reasons that have nothing to do with spammy content. 1. Your external mail server should have consistent A, MX, and PTR records, and announce itself with the public domain. 2. You should publish SPF and DKIM records for the external mail server, and DKIM sign outgoing mail yourself. 3. It may help to register as a bona fide mailing list with the problem providers, and get on their feedback loops. 4. If you have a lot of resources, you could publish a DMARC record and get feedback about who is spoofing your domain, and how much. But keeping up with and analyzing that feedback could easily be somebody's full-time job, although there are options to just get summaries. Some people think that removing broken DKIM signatures is a good idea, but we recommend against that. See Mailman/Defaults.py, the setting for REMOVE_DKIM_HEADERS and the comment above it. Footnotes: [1] That's not quite true: a pure "pass through" mailing list that doesn't change any of the received content will pass the digital signature test (such a list can add header fields, but not edit subject or add a heading or footer to the body). This is unpleasant at best, and may be legally risky in some cases where the list needs to add a disclaimer. ("Legal risk" may be an urban legend, and certainly varies by jurisdiction.) [2] Personally, I just conform to Japanese Ministry of Education policy that prohibits use of Yahoo for "official communications", and for once enjoy conformance to policy hugely. ;-) From beakerboy99 at yahoo.com Thu Sep 10 13:24:31 2015 From: beakerboy99 at yahoo.com (Kevin Nowaczyk) Date: Thu, 10 Sep 2015 04:24:31 -0700 Subject: [Mailman-Users] Forbidden Mailman Archive In-Reply-To: <1441884231.67205.YahooMailBasic@web181701.mail.ne1.yahoo.com> Message-ID: <1441884271.97579.YahooMailBasic@web181703.mail.ne1.yahoo.com> Changing this apache configuration allows me to see the archive. The archive only shows one message, one that I posted yesterday. There must have been some other permissions issue which prevented mailman from saving all the previous messages to the archive. Thanks for the help! Kevin Nowaczyk -------------------------------------------- On Thu, 9/10/15, Kevin Nowaczyk wrote: Subject: Re: [Mailman-Users] Forbidden Mailman Archive To: "Mark Sapiro" Date: Thursday, September 10, 2015, 7:23 AM Changing this apache configuration allows me to see the archive. The archive only shows one message, one that I posted yesterday. There must have been some other permissions issue which prevented mailman from saving all the previous messages to the archive. Thanks for the help! Kevin Nowaczyk -------------------------------------------- On Thu, 9/10/15, Mark Sapiro wrote: Subject: Re: [Mailman-Users] Forbidden Mailman Archive To: mailman-users at python.org Date: Thursday, September 10, 2015, 3:22 AM On 09/09/2015 01:44 PM, Kevin Nowaczyk via Mailman-Users wrote: > This seems to be a somewhat common problem, so I've looked at the archives at all the suggestions, tried everything that is recent and nothing has worked. It looks like no archives are actually being created, despite the "yes" option being selected in the list configuration. My previous reply assumed that there had been successful posts to the list that weren't archived, but the "Forbidden" in the subject may imply that there have been no posts, but you are getting a 403 Forbidden status from apache when attempting to go to the archives. If this is the issue, the problem is probably that you have apache 2.4 and this > Alias /pipermail/ /var/lib/mailman/archives/public/ > >? ???Options +FollowSymLinks >? ???Order allow,deny >? ???Allow from all > needs to be Alias /pipermail/ /var/lib/mailman/archives/public/ ? ? Options +FollowSymLinks ? ? Require all granted If that isn't the answer, but the issue is 403 Forbidden, what's in /var/log/apache2/lists-error.log? -- Mark Sapiro ? ? ? ? The highway is for gamblers, San Francisco Bay Area, California? ? better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users at 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/beakerboy99%40yahoo.com From beakerboy99 at yahoo.com Thu Sep 10 17:19:12 2015 From: beakerboy99 at yahoo.com (Kevin Nowaczyk) Date: Thu, 10 Sep 2015 08:19:12 -0700 Subject: [Mailman-Users] Mailing List Bounce Problems Message-ID: <1441898352.77977.YahooMailBasic@web181705.mail.ne1.yahoo.com> Hey everyone. The mailing list archive issue that I was inquiring about is a pretty low-volume list. When looking into the archive problem, i saw there were some messages listed in /var/lib/mailman/logs/post that I never received. When looking at the member list, most of my list members were no longer receiving emails due to excessive bounces. I have it set to notify the admin (my gmail account) when a user is disabled, but I've never received a notification. I enabled notification when a message I send to the list is sent out, and I receive that notification, but nobody receives the message. Admin emails from mailman go through just fine, but any message posted to the list does not. I have an IMAP email account on the same server which hosts the mailman instance, and it seems to get all my test messages that I post just fine, but all yahoo, windstream, gmail, etc get bounced. an example line from the /var/log/mail.info file is: Sep 10 12:49:21 bunsen postfix/smtp[4616]: 0DF621C375: to=, relay=mail-tester.com[94.23.206.89]:25, delay=2.6, delays=0.03/0.07/0.86/1.6, dsn=5.0.0, status=bounced (host mail-tester.com[94.23.206.89] said: 550 Message Contains SUSPECT Content :: Please contact abuse at fortressitx.com for further information. (in reply to end of DATA command)) I've been using the services at mail-tester.com to ensure that my domain keys, DMARC, and SPF are all set well. You can see those results here (http://www.mail-tester.com/web-p6036H). I deleted the entire mailing list after exporting the 114 email address, and remade the list, and it behaves the same. The odd thing is, I have another mailing list on the same server with only 6 members, and it seems to be working fine! Any clue where to look? I've contacted abuse at fortressitx.com and received no reply. Thanks, Kevin Nowaczyk From mark at msapiro.net Thu Sep 10 17:44:06 2015 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 10 Sep 2015 08:44:06 -0700 Subject: [Mailman-Users] Forbidden Mailman Archive In-Reply-To: <1441884271.97579.YahooMailBasic@web181703.mail.ne1.yahoo.com> References: <1441884271.97579.YahooMailBasic@web181703.mail.ne1.yahoo.com> Message-ID: <55F1A546.4090201@msapiro.net> On 09/10/2015 04:24 AM, Kevin Nowaczyk via Mailman-Users wrote: > Changing this apache configuration allows me to see the archive. The archive only shows one message, one that I posted yesterday. There must have been some other permissions issue which prevented mailman from saving all the previous messages to the archive. If there was some issue that prevented earlier messages from being archived, the messages may have encountered some exception causing them to be shunted. If so, Mailman's error log (/var/lib/mailman/logs/error in your case) will have more info, and the messages will probably be in the shunt queue (/var/lib/mailman/qfiles/shunt/). The shunted messages can be viewed with Mailman's bin/show_qfiles tool and requeued for the archive with bin/unshunt. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Sep 10 18:43:34 2015 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 10 Sep 2015 09:43:34 -0700 Subject: [Mailman-Users] Mailing List Bounce Problems In-Reply-To: <1441898352.77977.YahooMailBasic@web181705.mail.ne1.yahoo.com> References: <1441898352.77977.YahooMailBasic@web181705.mail.ne1.yahoo.com> Message-ID: <55F1B336.2080409@msapiro.net> On 09/10/2015 08:19 AM, Kevin Nowaczyk via Mailman-Users wrote: > I have it set to notify the admin (my gmail > account) when a user is disabled, but I've never received a > notification. Was bounce_notify_owner_on_disable set to yes before the member's delivery was disabled? If so, what does your postfix log say about the notification mail to you? > I enabled notification when a message I send to the > list is sent out, and I receive that notification, but nobody > receives the message. And what does postfix say about those deliveries, assuming the member's delivery was enabled. Note that if you are posting from Yahoo and you don't have DMARC mitigations enabled for your list, that is likely a reason. See the wiki at and . > Admin emails from mailman go through just fine, > but any message posted to the list does not. I have an IMAP email > account on the same server which hosts the mailman instance, and it > seems to get all my test messages that I post just fine, but all > yahoo, windstream, gmail, etc get bounced. > > an example line from the /var/log/mail.info file is: > > Sep 10 12:49:21 bunsen postfix/smtp[4616]: 0DF621C375: > to=, > relay=mail-tester.com[94.23.206.89]:25, delay=2.6, > delays=0.03/0.07/0.86/1.6, dsn=5.0.0, status=bounced (host > mail-tester.com[94.23.206.89] said: 550 Message Contains SUSPECT > Content :: Please contact abuse at fortressitx.com for further > information. (in reply to end of DATA command)) So the MX at mail-tester.com is not accepting the mail because they say the Message Contains SUSPECT Content. Only they can tell you why. But is this a list message? If so, why is it being relayed to mail-tester.com. What are some log messages for mail to list members that is undeliverable?. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Sep 10 18:56:49 2015 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 10 Sep 2015 09:56:49 -0700 Subject: [Mailman-Users] Potential "Bounce" Question In-Reply-To: <8737ym1x8i.fsf@uwakimon.sk.tsukuba.ac.jp> References: <03eb01d0eb5f$568ce880$03a6b980$@eastlink.ca> <8737ym1x8i.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <55F1B651.5010907@msapiro.net> On 09/10/2015 01:42 AM, Stephen J. Turnbull wrote: > @Mark & anybody else familiar with the FAQ: Some of the information > below isn't in the DMARC FAQ, and some of it doesn't seem to be in FAQ > at all. Pointers to relevant FAQs would be appreciated as I will > update & xref in the next few days as I find time. Thanks Steve. Currently, the only two wiki articles are and . Updating, xrefing and possibly a new article will all be good. > Nancy C writes: > > > I am the admin for a group & some members frequently get warning messages > > like this: > > > > "Your current bounce score is 3.0 out of a maximum of 5.0" ... > > What can be done to reduce / eliminate these messages? > > The first thing I would suggest is to upgrade Mailman. As far as I > can tell, Mailman 2.1.20 doesn't send those messages, period (there's > a template for it, but I can't find anywhere it's used). That actual message is not sent in an email notice, but it does appear on the user's 'options' page if the user's score is > 0. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From dmofot at gmail.com Thu Sep 10 17:17:39 2015 From: dmofot at gmail.com (DT) Date: Thu, 10 Sep 2015 11:17:39 -0400 Subject: [Mailman-Users] Admin Approval Emails Not Sent Message-ID: Mailman version 2.1.16 Installed via apt-get Server OS is Ubuntu 14.04.3 LTS MTA is postfix version 2.11.0 When a user subscribes to the email list, an approval email is not being sent to the admins/moderators. The variables admin_immed_notify and admin_notify_mchanges are set to yes. The subscribe requests are getting picked up during the daily cron job and an email is then sent at 8:00 AM. Test emails to -owner work internally from postfix and when sent externally from gmail. Here's a link to all the log file snippets from the time of the subscribe request: https://gist.github.com/dmofot/c367151ba262f476c2c6 Any ideas where to start troubleshooting this issue? DT From dmofot at gmail.com Thu Sep 10 17:53:32 2015 From: dmofot at gmail.com (DT) Date: Thu, 10 Sep 2015 11:53:32 -0400 Subject: [Mailman-Users] Deleted initial mailman list Message-ID: Recently, I was troubleshooting another issue and decided to get rid of some old testing lists. I removed the mailman list that I initially created on setup. Looking through the archives, I found this thread - http://www.mail-archive.com/mailman-users%40python.org/msg30391.html - which basically says don't delete. The thread is from 2005, but does this still hold true? If so, can I simply issue a newlist command and recreate the mailman list or is there some other method? Thanks! DT From mark at msapiro.net Fri Sep 11 01:43:29 2015 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 10 Sep 2015 16:43:29 -0700 Subject: [Mailman-Users] Deleted initial mailman list In-Reply-To: References: Message-ID: <55F215A1.8080804@msapiro.net> On 09/10/2015 08:53 AM, DT wrote: > Recently, I was troubleshooting another issue and decided to get rid of > some old testing lists. I removed the mailman list that I initially > created on setup. Looking through the archives, I found this thread - > http://www.mail-archive.com/mailman-users%40python.org/msg30391.html - > which basically says don't delete. The thread is from 2005, but does this > still hold true? You must have the site list for various reasons, the most important of which is that mailmanctl will refuse to start Mailman if it isn't there. > If so, can I simply issue a newlist command and recreate the mailman list > or is there some other method? Thanks! Yes, you can use newlist to create it. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Fri Sep 11 02:06:00 2015 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 10 Sep 2015 17:06:00 -0700 Subject: [Mailman-Users] Admin Approval Emails Not Sent In-Reply-To: References: Message-ID: <55F21AE8.3050009@msapiro.net> On 09/10/2015 08:17 AM, DT wrote: > > Test emails to -owner work internally from postfix and when sent externally > from gmail. OK. > Here's a link to all the log file snippets from the time of the subscribe > request: > https://gist.github.com/dmofot/c367151ba262f476c2c6 > > Any ideas where to start troubleshooting this issue? There are things missing, perhaps because they didn't happen or because you didn't include them. Here's what I see and what I expect. Your smtp log: Sep 09 14:41:45 2015 (7788) smtp to wort for 1 recips, completed in 0.052 seconds This is the notice being sent to wort-owner. There should be a subsequent entry with the same message-id for 'n' recips where n is the total number of owners and moderators. That is the delivery of the message from wort-owner to the owners and moderators. log :: mail.log ... Sep 9 14:41:45 davidtodd postfix/pickup[9566]: 79FF9C0727: uid=1001 from= Sep 9 14:41:45 davidtodd postfix/cleanup[9597]: 79FF9C0727: message-id= Sep 9 14:41:45 davidtodd opendkim[1226]: 79FF9C0727: no signing table match for 'wort-owner at wort.org' Sep 9 14:41:45 davidtodd opendkim[1226]: 79FF9C0727: no signature data Sep 9 14:41:45 davidtodd postfix/qmgr[8528]: 79FF9C0727: from=, size=1492, nrcpt=1 (queue active) Sep 9 14:41:51 davidtodd postfix/smtp[9602]: 79FF9C0727: to=, relay=mailroom5.hostrocket.com[66.147.229.200]:25, delay=6.2, delays=0.02/0.01/5.4/0.73, dsn=2.0.0, status=sent (250 OK id=1ZZkJb-0003U2-Lm) Sep 9 14:41:51 davidtodd postfix/qmgr[8528]: 79FF9C0727: removed The above is the delivery of the message to wort-owner. It should be delivered to a pipe "|/var/lib/mailman/mail/mailman wort owner" to get to mailman, not relayed to mailroom5.hostrocket.com. This may explain the issue, but then how does mail simply sent to wort-owner work? log :: error You apparently have enabled smtplib debugging as in the FAQ at , but this tells us nothing new that we don't already see in the smtp and mail.log logs. log :: syslog And likewise syslog Bottom line - If you are showing everything, the notice to wort-owner is being relayed to mailroom5.hostrocket.com and never gets to Mailman for delivery to the actual owner and moderator addresses. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Fri Sep 11 02:11:58 2015 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 10 Sep 2015 17:11:58 -0700 Subject: [Mailman-Users] Admin Approval Emails Not Sent In-Reply-To: <55F21AE8.3050009@msapiro.net> References: <55F21AE8.3050009@msapiro.net> Message-ID: <55F21C4E.6090603@msapiro.net> On 09/10/2015 05:06 PM, Mark Sapiro wrote: > > The above is the delivery of the message to wort-owner. It should be > delivered to a pipe "|/var/lib/mailman/mail/mailman wort owner" ... Actually, the pipe should be something like "|/var/lib/mailman/mail/mailman owner wort" rather than 'wort owner'. This is one of the 10 required aliases for the list unless you deliver to Mailman via some other method. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From dmofot at gmail.com Fri Sep 11 02:44:47 2015 From: dmofot at gmail.com (DT) Date: Thu, 10 Sep 2015 20:44:47 -0400 Subject: [Mailman-Users] Deleted initial mailman list In-Reply-To: <55F215A1.8080804@msapiro.net> References: <55F215A1.8080804@msapiro.net> Message-ID: Great, thanks Mark. I ran newlist and did a mailmanctl restart and everything came right back up and appears to be working. Thanks again! On Thu, Sep 10, 2015 at 7:43 PM, Mark Sapiro wrote: > On 09/10/2015 08:53 AM, DT wrote: > > Recently, I was troubleshooting another issue and decided to get rid of > > some old testing lists. I removed the mailman list that I initially > > created on setup. Looking through the archives, I found this thread - > > http://www.mail-archive.com/mailman-users%40python.org/msg30391.html - > > which basically says don't delete. The thread is from 2005, but does > this > > still hold true? > > > You must have the site list for various reasons, the most important of > which is that mailmanctl will refuse to start Mailman if it isn't there. > > > > If so, can I simply issue a newlist command and recreate the mailman list > > or is there some other method? Thanks! > > > Yes, you can use newlist to create it. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at 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/dmofot%40gmail.com > From dmofot at gmail.com Fri Sep 11 03:01:21 2015 From: dmofot at gmail.com (DT) Date: Thu, 10 Sep 2015 21:01:21 -0400 Subject: [Mailman-Users] Admin Approval Emails Not Sent In-Reply-To: <55F21AE8.3050009@msapiro.net> References: <55F21AE8.3050009@msapiro.net> Message-ID: Ok, so maybe this has to do with the setup. The list is for a club who has shared hosting for web and email at HostRocket for wort.org. The list was always hosted somewhere else. They were having some other issues and I migrated the list to my server, davidtodd.info. All the wort.org emails (even the list ones) are on the HostRocket server and they forward to the same address with a davidtodd.info domain. So wort-owner at wort.org is at HostRocket and forwards to wort-owner at davidtodd.info where the list is actually hosted. When users post to the list, they send to wort at wort.org, which forwards to wort at davidtodd.info...and on and on. Users have no issues posting to the list and sending an email to wort-owner at wort.org (which forwards) works. An email to wort-admin at wort.org successfully results in a bounce. On Thu, Sep 10, 2015 at 8:06 PM, Mark Sapiro wrote: > On 09/10/2015 08:17 AM, DT wrote: > > > > Test emails to -owner work internally from postfix and when sent > externally > > from gmail. > > > OK. > > > > Here's a link to all the log file snippets from the time of the subscribe > > request: > > https://gist.github.com/dmofot/c367151ba262f476c2c6 > > > > Any ideas where to start troubleshooting this issue? > > > There are things missing, perhaps because they didn't happen or because > you didn't include them. Here's what I see and what I expect. > > > Your smtp log: > Sep 09 14:41:45 2015 (7788) > smtp to wort for 1 recips, completed in 0.052 seconds > > This is the notice being sent to wort-owner. There should be a > subsequent entry with the same message-id for 'n' recips where n is the > total number of owners and moderators. That is the delivery of the > message from wort-owner to the owners and moderators. > > log :: mail.log > > ... > Sep 9 14:41:45 davidtodd postfix/pickup[9566]: 79FF9C0727: uid=1001 > from= > Sep 9 14:41:45 davidtodd postfix/cleanup[9597]: 79FF9C0727: > message-id= > Sep 9 14:41:45 davidtodd opendkim[1226]: 79FF9C0727: no signing table > match for 'wort-owner at wort.org' > Sep 9 14:41:45 davidtodd opendkim[1226]: 79FF9C0727: no signature data > Sep 9 14:41:45 davidtodd postfix/qmgr[8528]: 79FF9C0727: > from=, size=1492, nrcpt=1 (queue active) > Sep 9 14:41:51 davidtodd postfix/smtp[9602]: 79FF9C0727: > to=, > relay=mailroom5.hostrocket.com[66.147.229.200]:25, delay=6.2, > delays=0.02/0.01/5.4/0.73, dsn=2.0.0, status=sent (250 OK > id=1ZZkJb-0003U2-Lm) > Sep 9 14:41:51 davidtodd postfix/qmgr[8528]: 79FF9C0727: removed > > > The above is the delivery of the message to wort-owner. It should be > delivered to a pipe "|/var/lib/mailman/mail/mailman wort owner" to get > to mailman, not relayed to mailroom5.hostrocket.com. This may explain > the issue, but then how does mail simply sent to wort-owner work? > > > log :: error > > > You apparently have enabled smtplib debugging as in the FAQ at > , but this tells us nothing new that we > don't already see in the smtp and mail.log logs. > > > log :: syslog > > And likewise syslog > > Bottom line - If you are showing everything, the notice to wort-owner is > being relayed to mailroom5.hostrocket.com and never gets to Mailman for > delivery to the actual owner and moderator addresses. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at 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/dmofot%40gmail.com > From mark at msapiro.net Fri Sep 11 03:11:16 2015 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 10 Sep 2015 18:11:16 -0700 Subject: [Mailman-Users] Admin Approval Emails Not Sent In-Reply-To: References: <55F21AE8.3050009@msapiro.net> Message-ID: <55F22A34.5030301@msapiro.net> On 09/10/2015 06:01 PM, DT wrote: > > All the wort.org emails (even the list ones) are on > the HostRocket server and they forward to the same address with a > davidtodd.info domain. So wort-owner at wort.org > is at HostRocket and forwards to > wort-owner at davidtodd.info where the > list is actually hosted. > > log :: mail.log > > ... > Sep 9 14:41:45 davidtodd postfix/pickup[9566]: 79FF9C0727: uid=1001 from= > Sep 9 14:41:45 davidtodd postfix/cleanup[9597]: 79FF9C0727: message-id= > Sep 9 14:41:45 davidtodd opendkim[1226]: 79FF9C0727: no signing table match for 'wort-owner at wort.org' > Sep 9 14:41:45 davidtodd opendkim[1226]: 79FF9C0727: no signature data > Sep 9 14:41:45 davidtodd postfix/qmgr[8528]: 79FF9C0727: from=, size=1492, nrcpt=1 (queue active) > Sep 9 14:41:51 davidtodd postfix/smtp[9602]: 79FF9C0727: to=, relay=mailroom5.hostrocket.com[66.147.229.200]:25, delay=6.2, delays=0.02/0.01/5.4/0.73, dsn=2.0.0, status=sent (250 OK id=1ZZkJb-0003U2-Lm) > Sep 9 14:41:51 davidtodd postfix/qmgr[8528]: 79FF9C0727: removed OK, so the above message was delivered to mailroom5.hostrocket.com for wort-owner at wort.org with mailroom5.hostrocket.com smtp id 1ZZkJb-0003U2-Lm and should have come back to wort-owner at davidtodd.info. Did it come back? Was it delivered to Mailman. What do the logs on davidtodd.info say about it? If it didn't come back, hostrocket accepted it and then discarded it. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From dmofot at gmail.com Fri Sep 11 05:39:44 2015 From: dmofot at gmail.com (DT) Date: Thu, 10 Sep 2015 23:39:44 -0400 Subject: [Mailman-Users] Admin Approval Emails Not Sent In-Reply-To: <55F22A34.5030301@msapiro.net> References: <55F21AE8.3050009@msapiro.net> <55F22A34.5030301@msapiro.net> Message-ID: Nothing in the logs on davidtodd.info indicate that it came back. Unfortunately, HostRocket doesn't allow shared users access to any of the system logs other than apache, so I can't easily check to see if they received it and discarded it. I'll submit a trouble ticket to see if I can get access. On Thu, Sep 10, 2015 at 9:11 PM, Mark Sapiro wrote: > On 09/10/2015 06:01 PM, DT wrote: > > > > All the wort.org emails (even the list ones) are on > > the HostRocket server and they forward to the same address with a > > davidtodd.info domain. So wort-owner at wort.org > > is at HostRocket and forwards to > > wort-owner at davidtodd.info where the > > list is actually hosted. > > > > log :: mail.log > > > > ... > > Sep 9 14:41:45 davidtodd postfix/pickup[9566]: 79FF9C0727: uid=1001 > from= > > Sep 9 14:41:45 davidtodd postfix/cleanup[9597]: 79FF9C0727: message-id=< > mailman.0.1441824103.9593.wort at wort.org> > > Sep 9 14:41:45 davidtodd opendkim[1226]: 79FF9C0727: no signing table > match for 'wort-owner at wort.org' > > Sep 9 14:41:45 davidtodd opendkim[1226]: 79FF9C0727: no signature data > > Sep 9 14:41:45 davidtodd postfix/qmgr[8528]: 79FF9C0727: from=< > wort-bounces at wort.org>, size=1492, nrcpt=1 (queue active) > > Sep 9 14:41:51 davidtodd postfix/smtp[9602]: 79FF9C0727: to=< > wort-owner at wort.org>, relay=mailroom5.hostrocket.com[66.147.229.200]:25, > delay=6.2, delays=0.02/0.01/5.4/0.73, dsn=2.0.0, status=sent (250 OK > id=1ZZkJb-0003U2-Lm) > > Sep 9 14:41:51 davidtodd postfix/qmgr[8528]: 79FF9C0727: removed > > > OK, so the above message was delivered to mailroom5.hostrocket.com for > wort-owner at wort.org with mailroom5.hostrocket.com smtp id > 1ZZkJb-0003U2-Lm and should have come back to wort-owner at davidtodd.info. > > Did it come back? Was it delivered to Mailman. What do the logs on > davidtodd.info say about it? > > If it didn't come back, hostrocket accepted it and then discarded it. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > From mark at msapiro.net Fri Sep 11 06:02:11 2015 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 10 Sep 2015 21:02:11 -0700 Subject: [Mailman-Users] Admin Approval Emails Not Sent In-Reply-To: References: <55F21AE8.3050009@msapiro.net> <55F22A34.5030301@msapiro.net> Message-ID: <55F25243.7010900@msapiro.net> On 09/10/2015 08:39 PM, DT wrote: > Nothing in the logs on davidtodd.info indicate > that it came back. Unfortunately, HostRocket doesn't allow shared users > access to any of the system logs other than apache, so I can't easily > check to see if they received it and discarded it. I'll submit a > trouble ticket to see if I can get access. This message says they received and accepted it. > Sep 9 14:41:51 davidtodd postfix/smtp[9602]: 79FF9C0727: to=, relay=mailroom5.hostrocket.com[66.147.229.200]:25, delay=6.2, delays=0.02/0.01/5.4/0.73, dsn=2.0.0, status=sent (250 OK id=1ZZkJb-0003U2-Lm) They responded to the SMTP delivery with (250 OK id=1ZZkJb-0003U2-Lm) which means they accepted it at SMTP time. Ask them what happened to this message that they received at Sep 9 14:41:51 with their smtp id 1ZZkJb-0003U2-Lm because it was supposed to be relayed back to wort-owner at davidtodd.info and never arrived. You might be better off teaching your postfix to deliver Mailman mail directly rather that relaying it through hostrocket. Given that you said earlier that mail you send directly to wort-owner at wort.org does get properly delivered as does the daily summary, I suspect that hostrocket for some reason thinks the immediate notice is spam and just tosses it. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From dmofot at gmail.com Fri Sep 11 06:48:51 2015 From: dmofot at gmail.com (DT) Date: Fri, 11 Sep 2015 00:48:51 -0400 Subject: [Mailman-Users] Admin Approval Emails Not Sent In-Reply-To: <55F25243.7010900@msapiro.net> References: <55F21AE8.3050009@msapiro.net> <55F22A34.5030301@msapiro.net> <55F25243.7010900@msapiro.net> Message-ID: Ok, trouble ticket submitted to see if they can confirm why they are discarding the immediate notice. Off to read up on postfix to see if I can figure out the teaching it to deliver directly to Mailman. Thanks for the suggestion and I'll be sure to update once I hear back from my ticket. On Fri, Sep 11, 2015 at 12:02 AM, Mark Sapiro wrote: > On 09/10/2015 08:39 PM, DT wrote: > > Nothing in the logs on davidtodd.info indicate > > that it came back. Unfortunately, HostRocket doesn't allow shared users > > access to any of the system logs other than apache, so I can't easily > > check to see if they received it and discarded it. I'll submit a > > trouble ticket to see if I can get access. > > > This message says they received and accepted it. > > > > Sep 9 14:41:51 davidtodd postfix/smtp[9602]: 79FF9C0727: to=< > wort-owner at wort.org>, relay=mailroom5.hostrocket.com[66.147.229.200]:25, > delay=6.2, delays=0.02/0.01/5.4/0.73, dsn=2.0.0, status=sent (250 OK > id=1ZZkJb-0003U2-Lm) > > > They responded to the SMTP delivery with (250 OK id=1ZZkJb-0003U2-Lm) > which means they accepted it at SMTP time. Ask them what happened to > this message that they received at Sep 9 14:41:51 with their smtp id > 1ZZkJb-0003U2-Lm because it was supposed to be relayed back to > wort-owner at davidtodd.info and never arrived. > > You might be better off teaching your postfix to deliver Mailman mail > directly rather that relaying it through hostrocket. > > Given that you said earlier that mail you send directly to > wort-owner at wort.org does get properly delivered as does the daily > summary, I suspect that hostrocket for some reason thinks the immediate > notice is spam and just tosses it. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > From mark at msapiro.net Fri Sep 11 17:16:59 2015 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 11 Sep 2015 08:16:59 -0700 Subject: [Mailman-Users] Admin Approval Emails Not Sent In-Reply-To: References: <55F21AE8.3050009@msapiro.net> <55F22A34.5030301@msapiro.net> <55F25243.7010900@msapiro.net> Message-ID: <55F2F06B.8000809@msapiro.net> On 09/10/2015 09:48 PM, DT wrote: > > Off to read up on postfix to see if I can figure out the teaching it to > deliver directly to Mailman. Thanks for the suggestion and I'll be sure > to update once I hear back from my ticket. You may find the FAQ article at helpful. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From dmofot at gmail.com Mon Sep 14 20:47:27 2015 From: dmofot at gmail.com (DT) Date: Mon, 14 Sep 2015 14:47:27 -0400 Subject: [Mailman-Users] Admin Approval Emails Not Sent In-Reply-To: References: <55F21AE8.3050009@msapiro.net> <55F22A34.5030301@msapiro.net> <55F25243.7010900@msapiro.net> Message-ID: Here's a final update now that this is finally sorted out. It was just as Mark said, HostRocket was catching the immediate notifications in some spam filter. After submitting a trouble ticket, they adjusted their filter and it hasn't been a problem since. > You may find the FAQ article at helpful. Thanks again Mark. All the examples appear to be for doing a transport of an entire domain, but I did find this - http://www.docunext.com/blog/2011/01/using-postfix-transport-maps-for-email-address-specific-aliasing.html - which I think will allow me to internally route just the mailman specific addresses for the wort.org domain locally. On Fri, Sep 11, 2015 at 12:48 AM, DT wrote: > Ok, trouble ticket submitted to see if they can confirm why they are > discarding the immediate notice. > > Off to read up on postfix to see if I can figure out the teaching it to > deliver directly to Mailman. Thanks for the suggestion and I'll be sure to > update once I hear back from my ticket. > > On Fri, Sep 11, 2015 at 12:02 AM, Mark Sapiro wrote: > >> On 09/10/2015 08:39 PM, DT wrote: >> > Nothing in the logs on davidtodd.info indicate >> > that it came back. Unfortunately, HostRocket doesn't allow shared users >> > access to any of the system logs other than apache, so I can't easily >> > check to see if they received it and discarded it. I'll submit a >> > trouble ticket to see if I can get access. >> >> >> This message says they received and accepted it. >> >> >> > Sep 9 14:41:51 davidtodd postfix/smtp[9602]: 79FF9C0727: to=< >> wort-owner at wort.org>, relay=mailroom5.hostrocket.com[66.147.229.200]:25, >> delay=6.2, delays=0.02/0.01/5.4/0.73, dsn=2.0.0, status=sent (250 OK >> id=1ZZkJb-0003U2-Lm) >> >> >> They responded to the SMTP delivery with (250 OK id=1ZZkJb-0003U2-Lm) >> which means they accepted it at SMTP time. Ask them what happened to >> this message that they received at Sep 9 14:41:51 with their smtp id >> 1ZZkJb-0003U2-Lm because it was supposed to be relayed back to >> wort-owner at davidtodd.info and never arrived. >> >> You might be better off teaching your postfix to deliver Mailman mail >> directly rather that relaying it through hostrocket. >> >> Given that you said earlier that mail you send directly to >> wort-owner at wort.org does get properly delivered as does the daily >> summary, I suspect that hostrocket for some reason thinks the immediate >> notice is spam and just tosses it. >> >> -- >> Mark Sapiro The highway is for gamblers, >> San Francisco Bay Area, California better use your sense - B. Dylan >> > > From mark at msapiro.net Tue Sep 15 04:55:59 2015 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 14 Sep 2015 19:55:59 -0700 Subject: [Mailman-Users] Admin Approval Emails Not Sent In-Reply-To: References: <55F21AE8.3050009@msapiro.net> <55F22A34.5030301@msapiro.net> <55F25243.7010900@msapiro.net> Message-ID: <55F788BF.1040501@msapiro.net> On 09/14/2015 11:47 AM, DT wrote: > Here's a final update now that this is finally sorted out. It was just > as Mark said, HostRocket was catching the immediate notifications in > some spam filter. After submitting a trouble ticket, they adjusted > their filter and it hasn't been a problem since. > >> You may find the FAQ article at helpful. > > Thanks again Mark. All the examples appear to be for doing a transport > of an entire domain, but I did find this > - http://www.docunext.com/blog/2011/01/using-postfix-transport-maps-for-email-address-specific-aliasing.html > - which I think will allow me to internally route just the mailman > specific addresses for the wort.org domain locally. Actually, the FAQ article at tells you how to modify Mailman's existing postfix integration facility to create transport maps to route list addresses only to Postfix's local transport. I don't know what you saw in that article, but the third paragraph specifically says "Some people find these features insufficient as they want to use some specific transport or other mapping for Mailman list addresses that is *not* applied to all addresses in the list domain(s). The following is a way to automate the generation of some Postfix map via editing the Mailman generated virtual-mailman file." (emphasis mine) -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From fsantiago at deviltracks.net Mon Sep 14 21:31:54 2015 From: fsantiago at deviltracks.net (fsantiago at deviltracks.net) Date: Mon, 14 Sep 2015 15:31:54 -0400 Subject: [Mailman-Users] Mailman 3.0 + Qmail support Message-ID: Hello, Any plans to support qmail with Mailman 3.0+ ? From mark at msapiro.net Tue Sep 15 05:38:03 2015 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 14 Sep 2015 20:38:03 -0700 Subject: [Mailman-Users] Mailman 3.0 + Qmail support In-Reply-To: References: Message-ID: <55F7929B.7070800@msapiro.net> On 09/14/2015 12:31 PM, fsantiago at deviltracks.net wrote: > Hello, > > Any plans to support qmail with Mailman 3.0+ ? Questions about Mailman 3 and particularly Postorius and Hyperkitty are better posted to the mailman-developers at python.org list . Please join that list if you are not already a member and post there. That said, we would gladly accept a contribution. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From stephen at xemacs.org Tue Sep 15 10:29:18 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Tue, 15 Sep 2015 17:29:18 +0900 Subject: [Mailman-Users] Mailman 3.0 + Qmail support In-Reply-To: <55F7929B.7070800@msapiro.net> References: <55F7929B.7070800@msapiro.net> Message-ID: <87y4g8xezl.fsf@uwakimon.sk.tsukuba.ac.jp> Mark Sapiro writes: > On 09/14/2015 12:31 PM, fsantiago at deviltracks.net wrote: > > Hello, > > > > Any plans to support qmail with Mailman 3.0+ ? > > Questions about Mailman 3 and particularly Postorius and Hyperkitty are > better posted to the mailman-developers at python.org list ML Meta: Now that Mailman 3 has been released, I think we're just going to have to deal with "what can Mailman 3 do?" questions on this list. There are no *plans* to support Qmail: none of the Mailman developers use it. I would imagine there will be no support in Mailman 3.0, since it's already been released. I think it very unlikely that there will be support in Mailman 3.1, since noone has stepped forward to offer it yet, and we're hoping to release Mailman 3.1 on a time scale of months. > That said, we would gladly accept a contribution. +0.5, or +1 if it comes with expectation of continued support from the contributor for a couple of years. Please do discuss contributions on the developers' list. From tom.browder at gmail.com Tue Sep 15 16:25:42 2015 From: tom.browder at gmail.com (Tom Browder) Date: Tue, 15 Sep 2015 09:25:42 -0500 Subject: [Mailman-Users] Is there a preferred owner and group of the MM2 directory "/usr/local/mailman?" Message-ID: The installation instructions are a little confusing, but I take away from them the best (almost default) choice for owner:group for the "/usr/local/mailman" ($prefix) directory is 'mailman'. Any other opinions or recommendations? Thanks. Best regards, -Tom From ovh at forum-pc.net Tue Sep 15 15:50:43 2015 From: ovh at forum-pc.net (=?UTF-8?Q?Camille_Olli=c3=a9?=) Date: Tue, 15 Sep 2015 15:50:43 +0200 Subject: [Mailman-Users] Multiple "Re:" in subject Message-ID: <55F82233.3010606@forum-pc.net> Hi, i've installed Mailman3 on my Debian server. It works fine but i have a little problem : all replied messages have more "Re:" in Subject and i've not found where to control/remove it. Any idea ? Regards. PS : google not helped me. From mark at msapiro.net Tue Sep 15 17:07:39 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 15 Sep 2015 08:07:39 -0700 Subject: [Mailman-Users] Multiple "Re:" in subject In-Reply-To: <55F82233.3010606@forum-pc.net> References: <55F82233.3010606@forum-pc.net> Message-ID: <55F8343B.1070606@msapiro.net> On 09/15/2015 06:50 AM, Camille Olli? wrote: > > i've installed Mailman3 on my Debian server. > > It works fine but i have a little problem : all replied messages have > more "Re:" in Subject and i've not found where to control/remove it. This reply will have Re: in the subject. I don't think Mailman will try to remove either my Re: or your original "Re:", but it may. so my subject as sent will be: Subject: Re: [Mailman-Users] Multiple "Re:" in subject And I think it will go to the list that way. The issue is someone else may reply to my reply and her MUA (mail client) may create a subject Subject: Re: Re: [Mailman-Users] Multiple "Re:" in subject This is strictly an issue with her MUA and depends on the MUA she uses. Mailman does make some modifications to the Subject: header involved with prefixing (adding [Mailman-Users] in this case), and those modifications also attempt to collapse multiple Re: but they aren't perfect, and the algorithm varies depending on site settings and whether or not the list is set up for numbering in subject_prefix. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Tue Sep 15 17:15:07 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 15 Sep 2015 08:15:07 -0700 Subject: [Mailman-Users] Is there a preferred owner and group of the MM2 directory "/usr/local/mailman?" In-Reply-To: References: Message-ID: <55F835FB.2060707@msapiro.net> On 09/15/2015 07:25 AM, Tom Browder wrote: > The installation instructions are a little confusing, but I take away > from them the best (almost default) choice for owner:group for the > "/usr/local/mailman" ($prefix) directory is 'mailman'. The group must be 'mailman' (or whatever name you configured via the --with-groupname option to configure). The owner is not critical. It is usually also 'mailman' (or whatever name you configured via the --with-username option to configure), but it really can be anything. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From tom.browder at gmail.com Tue Sep 15 17:17:05 2015 From: tom.browder at gmail.com (Tom Browder) Date: Tue, 15 Sep 2015 10:17:05 -0500 Subject: [Mailman-Users] Is there a preferred owner and group of the MM2 directory "/usr/local/mailman?" In-Reply-To: <55F835FB.2060707@msapiro.net> References: <55F835FB.2060707@msapiro.net> Message-ID: On Tue, Sep 15, 2015 at 10:15 AM, Mark Sapiro wrote: > On 09/15/2015 07:25 AM, Tom Browder wrote: >> The installation instructions are a little confusing, but I take away >> from them the best (almost default) choice for owner:group for the >> "/usr/local/mailman" ($prefix) directory is 'mailman'. ... > --with-groupname option to configure). The owner is not critical. It is > usually also 'mailman' (or whatever name you configured via the > --with-username option to configure), but it really can be anything. Thanks so much, Mark! Best, -Tom From david at midrange.com Tue Sep 15 18:17:27 2015 From: david at midrange.com (Gibbs, David) Date: Tue, 15 Sep 2015 11:17:27 -0500 Subject: [Mailman-Users] Blocking or holding subscribe requests when email address contains "+" Message-ID: Folks: I'm looking for a way to block, or preferably hold for approval, subscribe requests where the email address contains a plus sign. I've been getting a lot of subscribe requests from bogus email addresses that look like: adfslij+32987234 at gmail.com. Any suggestions? Thanks! david -- IBM i on Power Systems: For when you can't afford to be out of business! I'm riding 100 miles (a full century) in the American Diabetes Association's Tour de Cure to raise money for diabetes research, education, advocacy, and awareness. You can make a tax deductible donation to my ride by visiting http://gmanesig.diabetessucks.net. My goal is $6000 but any amount is appreciated. See where I get my donations from ... visit http://gmanesig.diabetessucks.net/map for an interactive map (it's a geeky thing). From stephen at xemacs.org Tue Sep 15 18:30:17 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Wed, 16 Sep 2015 01:30:17 +0900 Subject: [Mailman-Users] Is there a preferred owner and group of the MM2 directory "/usr/local/mailman?" In-Reply-To: References: Message-ID: <87vbbby7ae.fsf@uwakimon.sk.tsukuba.ac.jp> Tom Browder writes: > The installation instructions are a little confusing, but I take away > from them the best (almost default) choice for owner:group for the > "/usr/local/mailman" ($prefix) directory is 'mailman'. It doesn't matter what the name is. You may wish to use a predefined name provided by the OS distribution (for example, Debian uses "list", not "mailman"). AFAIK there is no particular need to have the owner of Mailman code or data be the mailman user. For example, on Debian systems root is the owner of all the executables mentioned below, as well as most of the data directories. The important thing about the mailman user is that it is a member of the mailman group (typically the only member of that group). It is important that the cgi-bin executables be setgid and have the mailman group, that scripts/mailman have the mailman group, and that the Mailman writable data (archives, data, lists, messages, qfiles, spam) have the mailman group. It also does matter that the user and group have privileges only in Mailman file hierarchies, that there be no other members of the group (except possibly an admin's account, but I consider that an unnecessary risk) and that the name be used appropriately in any application that setuids or setgids to manipulate Mailman data (ISTR there may be some MTA that does). Bottom line: If I were you, I'd make sure that the mailman group and user are set up properly, and then do "chown root:mailman /usr/local/mailman" (root because I suppose Debian has a reason for doing that ;-). From Richard at Damon-family.org Tue Sep 15 18:31:00 2015 From: Richard at Damon-family.org (Richard Damon) Date: Tue, 15 Sep 2015 12:31:00 -0400 Subject: [Mailman-Users] Blocking or holding subscribe requests when email address contains "+" In-Reply-To: References: Message-ID: <5D9E0355-7423-4FAA-A147-CD3679EDECC3@Damon-family.org> The only thing I can think of is to require approval of all subscriptions (and maybe confirmation) and then build a regexp to auto approve all addresses without a + in them. I don't know how this will interact with the ban list (if you need that). > On Sep 15, 2015, at 12:17 PM, Gibbs, David wrote: > > Folks: > > I'm looking for a way to block, or preferably hold for approval, subscribe requests where the email address contains a plus sign. > > I've been getting a lot of subscribe requests from bogus email addresses that look like: adfslij+32987234 at gmail.com. > > Any suggestions? > > Thanks! > > david > > -- > IBM i on Power Systems: For when you can't afford to be out of business! > > I'm riding 100 miles (a full century) in the American Diabetes Association's Tour de Cure to raise money for diabetes research, education, advocacy, and awareness. You can make a tax deductible donation to my ride by visiting http://gmanesig.diabetessucks.net. My goal is $6000 but any amount is appreciated. > > See where I get my donations from ... visit http://gmanesig.diabetessucks.net/map for an interactive map (it's a geeky thing). > > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at 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/richard%40damon-family.org From david at midrange.com Tue Sep 15 18:33:35 2015 From: david at midrange.com (David Gibbs) Date: Tue, 15 Sep 2015 11:33:35 -0500 Subject: [Mailman-Users] Blocking or holding subscribe requests when email address contains "+" In-Reply-To: <5D9E0355-7423-4FAA-A147-CD3679EDECC3@Damon-family.org> References: <5D9E0355-7423-4FAA-A147-CD3679EDECC3@Damon-family.org> Message-ID: <55F8485F.3050502@midrange.com> On 9/15/2015 11:31 AM, Richard Damon wrote: > The only thing I can think of is to require approval of all > subscriptions (and maybe confirmation) and then build a regexp to > auto approve all addresses without a + in them. I don't know how this > will interact with the ban list (if you need that). Unfortunately, Mailman sends out the confirmation email before requiring approval. I want to stop (or hold) the subscription request before the confirmation message goes out. Maybe I have to look into a captcha integration? david -- IBM i on Power Systems: For when you can't afford to be out of business! I'm riding 100 miles (a full century) in the American Diabetes Association's Tour de Cure to raise money for diabetes research, education, advocacy, and awareness. You can make a tax deductible donation to my ride by visiting http://emailsig.diabetessucks.net. My goal is $6000 but any amount is appreciated. See where I get my donations from ... visit http://emailsig.diabetessucks.net/map for an interactive map (it's a geeky thing). From tom.browder at gmail.com Tue Sep 15 18:45:27 2015 From: tom.browder at gmail.com (Tom Browder) Date: Tue, 15 Sep 2015 11:45:27 -0500 Subject: [Mailman-Users] Is there a preferred owner and group of the MM2 directory "/usr/local/mailman?" In-Reply-To: <87vbbby7ae.fsf@uwakimon.sk.tsukuba.ac.jp> References: <87vbbby7ae.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: On Tue, Sep 15, 2015 at 11:30 AM, Stephen J. Turnbull wrote: > Tom Browder writes: > > > The installation instructions are a little confusing, but I take away > > from them the best (almost default) choice for owner:group for the > > "/usr/local/mailman" ($prefix) directory is 'mailman'. > > It doesn't matter what the name is. You may wish to use a predefined ... > Bottom line: If I were you, I'd make sure that the mailman group and > user are set up properly, and then do "chown root:mailman Steve, thanks for some good info, but no 'chown -R'? Best, -Tom From mark at msapiro.net Tue Sep 15 18:58:32 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 15 Sep 2015 09:58:32 -0700 Subject: [Mailman-Users] Is there a preferred owner and group of the MM2 directory "/usr/local/mailman?" In-Reply-To: References: <87vbbby7ae.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: On September 15, 2015 9:45:27 AM PDT, Tom Browder wrote: >On Tue, Sep 15, 2015 at 11:30 AM, Stephen J. Turnbull > wrote: >> Bottom line: If I were you, I'd make sure that the mailman group and >> user are set up properly, and then do "chown root:mailman > >Steve, thanks for some good info, but no 'chown -R'? If you have Mailman-Postfix integration, you don't want to set the owner of Mailman's data/aliases.db to root. Mailman's bin/check_perms is the safer way to fix ownership and permissions. -- Mark Sapiro Sent from my Not_an_iThing with standards compliant, open source software. From tom.browder at gmail.com Tue Sep 15 19:35:06 2015 From: tom.browder at gmail.com (Tom Browder) Date: Tue, 15 Sep 2015 12:35:06 -0500 Subject: [Mailman-Users] Is there a preferred owner and group of the MM2 directory "/usr/local/mailman?" In-Reply-To: References: <87vbbby7ae.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: On Tue, Sep 15, 2015 at 11:58 AM, Mark Sapiro wrote: ... > If you have Mailman-Postfix integration, you don't want to set the owner of Mailman's data/aliases.db to root. > > Mailman's bin/check_perms is the safer way to fix ownership and permissions. Ah I forgot about that. Thanks, Mark. -Tom From mark at msapiro.net Tue Sep 15 20:13:28 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 15 Sep 2015 11:13:28 -0700 Subject: [Mailman-Users] Blocking or holding subscribe requests when email address contains "+" In-Reply-To: <55F8485F.3050502@midrange.com> References: <5D9E0355-7423-4FAA-A147-CD3679EDECC3@Damon-family.org> <55F8485F.3050502@midrange.com> Message-ID: <8D288ADF-EF3C-4AEB-B41A-04BED18506CF@msapiro.net> On September 15, 2015 9:33:35 AM PDT, David Gibbs wrote: >Unfortunately, Mailman sends out the confirmation email before >requiring approval. I want to stop (or hold) the subscription request >before the confirmation message goes out. > >Maybe I have to look into a captcha integration? Recent Mailman has a SUBSCRIBE_FORM_SECRET setting which helps but doesn't stop them all. Because of these, there is now a GLOBAL_BAN_LIST, but that isn't released yet. You want a regexp in the ban_list for each list. For the python.org lists we use ^.*\+.*\d{3,}@ I.e., + followed by anything followed by at least 3 digits followed by @. This has been effective so far. The bots are doing web subscribe so there's no backscatter from this. -- Mark Sapiro Sent from my Not_an_iThing with standards compliant, open source software. From david at midrange.com Tue Sep 15 20:57:04 2015 From: david at midrange.com (David Gibbs) Date: Tue, 15 Sep 2015 13:57:04 -0500 Subject: [Mailman-Users] Blocking or holding subscribe requests when email address contains "+" In-Reply-To: <8D288ADF-EF3C-4AEB-B41A-04BED18506CF@msapiro.net> References: <5D9E0355-7423-4FAA-A147-CD3679EDECC3@Damon-family.org> <55F8485F.3050502@midrange.com> <8D288ADF-EF3C-4AEB-B41A-04BED18506CF@msapiro.net> Message-ID: <55F86A00.4080801@midrange.com> On 9/15/2015 1:13 PM, Mark Sapiro wrote: >> Unfortunately, Mailman sends out the confirmation email before >> requiring approval. I want to stop (or hold) the subscription >> request before the confirmation message goes out. >> > > You want a regexp in the ban_list for each list. For the python.org > lists we use > > ^.*\+.*\d{3,}@ > > I.e., + followed by anything followed by at least 3 digits followed > by @. THANK YOU! This is exactly the solution I was looking for. david -- IBM i on Power Systems: For when you can't afford to be out of business! I'm riding 100 miles (a full century) in the American Diabetes Association's Tour de Cure to raise money for diabetes research, education, advocacy, and awareness. You can make a tax deductible donation to my ride by visiting http://emailsig.diabetessucks.net. My goal is $6000 but any amount is appreciated. See where I get my donations from ... visit http://emailsig.diabetessucks.net/map for an interactive map (it's a geeky thing). From ricardo at americasnet.com Wed Sep 16 01:01:51 2015 From: ricardo at americasnet.com (Ricardo Kleemann) Date: Tue, 15 Sep 2015 16:01:51 -0700 Subject: [Mailman-Users] has anyone built a package (or bundle) for Mailman 3 on Ubuntu? Message-ID: I wanted to give it a try. I understand it requires multiple packages to get it working, and wondering if there's already anywhere I can point to to install via apt-get. thanks Ricardo From stephen at xemacs.org Wed Sep 16 01:53:04 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Wed, 16 Sep 2015 08:53:04 +0900 Subject: [Mailman-Users] Is there a preferred owner and group of the MM2 directory "/usr/local/mailman?" In-Reply-To: References: <87vbbby7ae.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <87si6fxmsf.fsf@uwakimon.sk.tsukuba.ac.jp> Mark Sapiro writes: > Mailman's bin/check_perms is the safer way to fix ownership and > permissions. Oops, yeah, that's the simplest way to get things consistent. Thanks for the followup! From stephen at xemacs.org Wed Sep 16 02:02:50 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Wed, 16 Sep 2015 09:02:50 +0900 Subject: [Mailman-Users] has anyone built a package (or bundle) for Mailman 3 on Ubuntu? In-Reply-To: References: Message-ID: <87r3lzxmc5.fsf@uwakimon.sk.tsukuba.ac.jp> Ricardo Kleemann writes: > I wanted to give it a try. I understand it requires multiple > packages to get it working, and wondering if there's already > anywhere I can point to to install via apt-get. Not that has been announced on this list, and it seems unlikely. Mailman 3.0 is a source release only. There's a volunteer to produce a Debian package, targeting release of 3.1 in a few months (we hope). For us, that will also be a source-only release, which is the traditional practice in any case. I suppose that with improvements in the Python package distribution system, Mailman might eventually move toward releases of the various components as wheels. Further discussion should be directed to the developers' list. From mark at msapiro.net Wed Sep 16 05:27:45 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 15 Sep 2015 20:27:45 -0700 Subject: [Mailman-Users] Multiple "Re:" in subject In-Reply-To: <55F8D153.2090309@forum-pc.net> References: <55F82233.3010606@forum-pc.net> <55F8343B.1070606@msapiro.net> <55F8D153.2090309@forum-pc.net> Message-ID: <55F8E1B1.2000707@msapiro.net> On 09/15/2015 07:17 PM, Camille Olli? wrote: > > i don't have this issue with Sympa on postfix and ezmlm on Qmail on > other mailing lists. > > Here is an example : [Bar] Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: > Re: Re: Re: IMP tice > > Even with thunderbird i have the issue. (Including list in reply) Well, judging by the subject in your reply to me, your MUA does the right thing, with Subjects that begin with Re: But there are other issues here. The example above is from a list at a site which has configured OLD_STYLE_PREFIXING = No So that Mailman puts the subject_prefix ([Bar]) at the beginning of the Subject: so a list post will be distributed with a Subject: like Subject: [Mailman-Users] Re: Multiple "Re:" in subject rather than Subject: Re: [Mailman-Users] Multiple "Re:" in subject With this subject, a replying MUA probably creates the subject like Subject: Re: [Mailman-Users] Re: Multiple "Re:" in subject but Mailman has logic in the subject prefixing code to remove redundant Re:, Aw:, Sv: and Vs: from the beginning of the subject in this case so Subject: headers with multiple Re: such as your example should not be occurring, however there appears a bug in that code. It will remove all the redundant Re:s from Subject: Re: [Bar] Re: Re: Re: Re: Re: Re: IMP tice but not from Subject: [Bar] Re: Re: Re: Re: Re: Re: IMP tice I will fix it. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From clare at catspaw.plus.com Wed Sep 16 17:17:45 2015 From: clare at catspaw.plus.com (Clare Redstone) Date: Wed, 16 Sep 2015 16:17:45 +0100 Subject: [Mailman-Users] Ban list - correct regular expression? Message-ID: <025e01d0f092$d7bf8a10$873e9e30$@plus.com> I get lots of spam held for moderation from email addresses that begin Hayley@ . I go to the moderation queue, discard each email address and tick to ban that address from every subscribing. And to discard anything coming from that address automatically. It would save me a lot of time if I can have this happen automatically. But am not entirely sure how. I've tried adding ^hayley to the list of addresses banned from membership (subscription rules). And to the List of non-member addresses whose postings will be automatically discarded (sender filters.) Is that the right expression? And are those the right places to add it? I didn't put them in the reject messages list as I thought that might send an automatic message back saying the message had been rejected. Which would be evidence ours is a real address and maybe encourage even more spam. Have I set this up correctly? Any other suggestions? Thanks. (And if you're called Hayley and want to join the list - um - tough?!) Clare From mark at msapiro.net Wed Sep 16 17:38:39 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 16 Sep 2015 08:38:39 -0700 Subject: [Mailman-Users] Ban list - correct regular expression? In-Reply-To: <025e01d0f092$d7bf8a10$873e9e30$@plus.com> References: <025e01d0f092$d7bf8a10$873e9e30$@plus.com> Message-ID: <55F98CFF.1090807@msapiro.net> On 09/16/2015 08:17 AM, Clare Redstone wrote: > > I've tried adding ^hayley to the list of addresses banned from membership > (subscription rules). And to the List of non-member addresses whose postings > will be automatically discarded (sender filters.) > > Is that the right expression? And are those the right places to add it? Yes and yes assuming what you want to ban/discard is any address beginning with hayley regardless of capitalization (these matches are all case-insensitive). -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ovh at forum-pc.net Wed Sep 16 21:03:15 2015 From: ovh at forum-pc.net (=?UTF-8?Q?Camille_Olli=c3=a9?=) Date: Wed, 16 Sep 2015 21:03:15 +0200 Subject: [Mailman-Users] Multiple "Re:" in subject In-Reply-To: <55F8E1B1.2000707@msapiro.net> References: <55F82233.3010606@forum-pc.net> <55F8343B.1070606@msapiro.net> <55F8D153.2090309@forum-pc.net> <55F8E1B1.2000707@msapiro.net> Message-ID: <55F9BCF3.6090401@forum-pc.net> Le 16/09/2015 05:27, Mark Sapiro a ?crit : > Well, judging by the subject in your reply to me, your MUA does the > right thing, with Subjects that begin with Re: > > But there are other issues here. The example above is from a list at a > site which has configured > > OLD_STYLE_PREFIXING = No > > So that Mailman puts the subject_prefix ([Bar]) at the beginning of the > Subject: so a list post will be distributed with a Subject: like > > Subject: [Mailman-Users] Re: Multiple "Re:" in subject > > rather than > > Subject: Re: [Mailman-Users] Multiple "Re:" in subject > > With this subject, a replying MUA probably creates the subject like > > Subject: Re: [Mailman-Users] Re: Multiple "Re:" in subject > > but Mailman has logic in the subject prefixing code to remove redundant > Re:, Aw:, Sv: and Vs: from the beginning of the subject in this case so > Subject: headers with multiple Re: such as your example should not be > occurring, however there appears a bug in that code. It will remove all > the redundant Re:s from > > Subject: Re: [Bar] Re: Re: Re: Re: Re: Re: IMP tice > > but not from > > Subject: [Bar] Re: Re: Re: Re: Re: Re: IMP tice > > I will fix it. Hi, sorry to send the answer ony to you, i've not seen the To: address in Thunderbird (shame on me !) So, how can i fix it ? I've downloaded and installed mailman 3 and it was very difficult because there is no deb package. -- Camille Olli? www.forum-pc.net / www.scoot-boost.com LinkedIn : http://lnkd.in/_K65k5 From dmofot at gmail.com Wed Sep 16 22:07:24 2015 From: dmofot at gmail.com (DT) Date: Wed, 16 Sep 2015 16:07:24 -0400 Subject: [Mailman-Users] Admin Approval Emails Not Sent In-Reply-To: <55F788BF.1040501@msapiro.net> References: <55F21AE8.3050009@msapiro.net> <55F22A34.5030301@msapiro.net> <55F25243.7010900@msapiro.net> <55F788BF.1040501@msapiro.net> Message-ID: I must have been confused when first reading through the wiki. Followed the directions and it's working as intended - all mailman specific wort.org emails are delivered locally and all other wort.org emails are relayed to HostRocket. Thanks again Mark! On Mon, Sep 14, 2015 at 10:55 PM, Mark Sapiro wrote: > On 09/14/2015 11:47 AM, DT wrote: > > Here's a final update now that this is finally sorted out. It was just > > as Mark said, HostRocket was catching the immediate notifications in > > some spam filter. After submitting a trouble ticket, they adjusted > > their filter and it hasn't been a problem since. > > > >> You may find the FAQ article at > helpful. > > > > Thanks again Mark. All the examples appear to be for doing a transport > > of an entire domain, but I did find this > > - > http://www.docunext.com/blog/2011/01/using-postfix-transport-maps-for-email-address-specific-aliasing.html > > - which I think will allow me to internally route just the mailman > > specific addresses for the wort.org domain locally. > > > Actually, the FAQ article at tells you > how to modify Mailman's existing postfix integration facility to create > transport maps to route list addresses only to Postfix's local transport. > > I don't know what you saw in that article, but the third paragraph > specifically says "Some people find these features insufficient as they > want to use some specific transport or other mapping for Mailman list > addresses that is *not* applied to all addresses in the list domain(s). > The following is a way to automate the generation of some Postfix map > via editing the Mailman generated virtual-mailman file." (emphasis mine) > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > From mark at msapiro.net Thu Sep 17 01:20:34 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 16 Sep 2015 16:20:34 -0700 Subject: [Mailman-Users] Multiple "Re:" in subject In-Reply-To: <55F9BCF3.6090401@forum-pc.net> References: <55F82233.3010606@forum-pc.net> <55F8343B.1070606@msapiro.net> <55F8D153.2090309@forum-pc.net> <55F8E1B1.2000707@msapiro.net> <55F9BCF3.6090401@forum-pc.net> Message-ID: <55F9F942.1010307@msapiro.net> On 09/16/2015 12:03 PM, Camille Olli? wrote: > > So, how can i fix it ? I've downloaded and installed mailman 3 and it > was very difficult because there is no deb package. Are you seeing this issue with MM 2.1 or with MM 3? I have created a bug report for MM 2.1 at . I think I know how to fix it, but I need to do some testing before committing a fix. If you are concerned about this issue with respect to delivered mail from Mailman 2.1, when I commit the fix, I will post that fact and you can apply the patch. If this issue also affects archived mail, I need more information to address that. If you can provide a link to a public archive that has the problem, please update the bug report. If you installed Mailman 3 in an attempt to solve this problem, that probably won't help, but if you want to address this issue in Mailman 3, report it at . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Sep 17 04:57:44 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 16 Sep 2015 19:57:44 -0700 Subject: [Mailman-Users] Multiple "Re:" in subject In-Reply-To: <55F9F942.1010307@msapiro.net> References: <55F82233.3010606@forum-pc.net> <55F8343B.1070606@msapiro.net> <55F8D153.2090309@forum-pc.net> <55F8E1B1.2000707@msapiro.net> <55F9BCF3.6090401@forum-pc.net> <55F9F942.1010307@msapiro.net> Message-ID: <55FA2C28.2020005@msapiro.net> On 09/16/2015 04:20 PM, Mark Sapiro wrote: > > If you are concerned about this issue with respect to delivered mail > from Mailman 2.1, when I commit the fix, I will post that fact and you > can apply the patch. The fix for this issue is at . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From VxMr at pge.com Thu Sep 17 00:53:18 2015 From: VxMr at pge.com (Montanez, Victor) Date: Wed, 16 Sep 2015 22:53:18 +0000 Subject: [Mailman-Users] Is there a way to create multiple lists at once via mailman script? Message-ID: Hello, I am wondering if there is a way to have several mailman lists created at once via command line. I am talking about 100 lists or so. Otherwise creating them through the GUI would take forever. Maybe creating a file with list name, password,etc and passing that file to the create binary? Anyone have any experience with that? Thanks in advance Victor Monta?ez From mark at msapiro.net Thu Sep 17 18:10:26 2015 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 17 Sep 2015 09:10:26 -0700 Subject: [Mailman-Users] Is there a way to create multiple lists at once via mailman script? In-Reply-To: References: Message-ID: <55FAE5F2.9010002@msapiro.net> On 09/16/2015 03:53 PM, Montanez, Victor wrote: > > I am wondering if there is a way to have several mailman lists created at once via command line. I am talking about 100 lists or so. Otherwise creating them through the GUI would take forever. > > Maybe creating a file with list name, password,etc and passing that file to the create binary? Create your file with multiple lines of the form list1 owner at example.com password Assume it's named 'lists' Create a script like #! /bin/bash exec 5 The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From rjsparks at nostrum.com Thu Sep 17 20:38:42 2015 From: rjsparks at nostrum.com (Robert Sparks) Date: Thu, 17 Sep 2015 13:38:42 -0500 Subject: [Mailman-Users] Increasing volume of distributed subscription attacks (was Blocking or holding subscribe requests when email address contains "+") Message-ID: <55FB08B2.8060205@nostrum.com> David Gibbs wrote: > I've been getting a lot of subscribe requests from bogus email addresses that look like: adfslij+32987234 at gmail.com. You're not alone. The subscriptions have also moved on to include addresses at SMS gateways after we added filters similar to what the thread suggested. In case others are also dealing with this at volume, some background on what the IETF mailman admin is doing: https://mailarchive.ietf.org/arch/msg/tools-development/p4iI5kxO-J1LZR5CQLerZYflHc0 and https://mailarchive.ietf.org/arch/msg/tools-development/P9mDSeRrvgUAD_tFzYqgDbOkUpM If anyone has a mitigation strategy that's working well, please let me know. RjS From mark at msapiro.net Fri Sep 18 17:57:16 2015 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 18 Sep 2015 08:57:16 -0700 Subject: [Mailman-Users] Increasing volume of distributed subscription attacks (was Blocking or holding subscribe requests when email address contains "+") In-Reply-To: <55FB08B2.8060205@nostrum.com> References: <55FB08B2.8060205@nostrum.com> Message-ID: <55FC345C.8060108@msapiro.net> On 09/17/2015 11:38 AM, Robert Sparks wrote: > > If anyone has a mitigation strategy that's working well, please let me > know. I think much of this has appeared earlier in this thread, but we have seen large volumes of these at mail.python.org. These have all been web subscribes, and in spite of the fact that we have enabled the SUBSCRIBE_FORM_SECRET feature which requires that the web subscribe POST data contain a token which requires that it be a submission of a form retrieved at least SUBSCRIBE_FORM_MIN_TIME (default 5 seconds) and no more than FORM_LIFETIME (default 1 hour) earlier, the bots were sometimes slow enough that even when I increased SUBSCRIBE_FORM_MIN_TIME to 8 seconds, many subscribe requests still succeeded. I then implemented a GLOBAL_BAN_LIST to supplement the individual, per list ban_list. We have been using the regexp ^.*\+.*\d{3,}@ in the GLOBAL_BAN_LIST and this is effective so far. Note that this could just as well be '^.*\+.*\d{3}@'. It is what it is because it evolved from '^.*\+\d{3,}@' after we saw a few of the form 'some.words+more-words123456 at gmail.com' type addresses. Note that since these are web subscribes and the address is banned, there is no backscatter. There is just a 'address is banned' notation on the web response. For those interested, the GLOBAL_BAN_LIST implementation is at . Also, there is a withlist script at (mirrored at ) which can be used to add an address or pattern to the ban_list if all lists in lieu of implementing a GLOBAL_BAN_LIST. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From araasch at gmail.com Sat Sep 19 13:58:59 2015 From: araasch at gmail.com (Arlen Raasch) Date: Sat, 19 Sep 2015 07:58:59 -0400 Subject: [Mailman-Users] How to get the senders email address in the custom footer? Message-ID: I have recently acquired the responsibility of maintaining a small listserver with about 1000 users. We are using version 2.1.16 of Mailman. The emails that currently are sent out via the listserv server have headers that include the original sender's email address as the "From:" address. Yahoo's and Aol's DMARC policy causes these to bounce as our server is not one they recognize. I have seen many posts regarding this problem, but no actual solutions that told me what I should do. This is not my area of expertise, just something that dropped in my lap. A strategy that makes some sense to me is to take ownership of the emails by identifying the listserv as the From and Reply-To addresses, but including a custom footer in the email that exposes the actual sender's email address. This should avoid Yahoo and Aol rejecting the email due to DMARC, as Yahoo and Aol will not be asked for their opinion as to what should or should not be done with this email. I set the annonomous_list setting to yes under general options, and sent a test email. The email went out fine, but nothing in the default email footer allowed others to know who actually sent the email out. I attempted to change the default non-digest footer to include the sender's address, but did not succeed. It appears that this info is regarding the recipient,not the sender's info. I.E. user xxx at mydomain.com sends to yyy at listserver.com, zzz at hisdomain.com is also a member of the listserv and receives an email, but the footer to the email does not show xxx at mydomain, just info about zzz at hisdomain.com. I tried the user_address, user_delivered_to, and user_name variables but none contained info regarding the sender. So, the question is how to get the sender's email address in the footer. Thanks in advance, -Arlen Raasch From lac at openend.se Sun Sep 20 17:20:31 2015 From: lac at openend.se (Laura Creighton) Date: Sun, 20 Sep 2015 17:20:31 +0200 Subject: [Mailman-Users] How to get the senders email address in the custom footer? In-Reply-To: References: Message-ID: <201509201520.t8KFKVZb025901@fido.openend.se> In a message of Sat, 19 Sep 2015 07:58:59 -0400, Arlen Raasch writes: >I have recently acquired the responsibility of maintaining a small >listserver with about 1000 users. > >We are using version 2.1.16 of Mailman. > >The emails that currently are sent out via the listserv server have headers >that include the original sender's email address as the "From:" address. >Yahoo's and Aol's DMARC policy causes these to bounce as our server is not >one they recognize. > >I have seen many posts regarding this problem, but no actual solutions that >told me what I should do. > >This is not my area of expertise, just something that dropped in my lap. > >A strategy that makes some sense to me is to take ownership of the emails >by identifying the listserv as the From and Reply-To addresses, but >including a custom footer in the email that exposes the actual sender's >email address. > >This should avoid Yahoo and Aol rejecting the email due to DMARC, as Yahoo >and Aol will not be asked for their opinion as to what should or should not >be done with this email. > >I set the annonomous_list setting to yes under general options, and sent a >test email. The email went out fine, but nothing in the default email >footer allowed others to know who actually sent the email out. > >I attempted to change the default non-digest footer to include the sender's >address, but did not succeed. It appears that this info is regarding the >recipient,not the sender's info. I.E. user xxx at mydomain.com sends to >yyy at listserver.com, zzz at hisdomain.com is also a member of the listserv and >receives an email, but the footer to the email does not show xxx at mydomain, >just info about zzz at hisdomain.com. I tried the user_address, >user_delivered_to, and user_name variables but none contained info >regarding the sender. > >So, the question is how to get the sender's email address in the footer. > >Thanks in advance, > >-Arlen Raasch The relevant pages to read are: http://wiki.list.org/DEV/DMARC http://wiki.list.org/DOC/What%20can%20I%20do%20about%20members%20being%20unsubscribed%20by%20bounces%20of%20Yahoo%20user%27s%20posts%20for%20DMARC%20policy%20reasons%3F You will be happier if you can upgrade to 2.1.18 You don't have to worry that Reply-To: should be munged to be the list. You re-write the From: and take control of it there, and then you stick the original poster's address to the Reply-To: If you are already munging the Reply-To: address to accomplish something else -- such as all replies go to the list, or all replies go to some_other_list then changing may irritate your users, but I assume you are not, or at any rate the irritation level will be less if you use Reply-To: to hold the original sender's address, since the scheme you outlined above involved rewriting Reply-To: anyway. The advantage of this scheme is that people who have sane, more recent that the 1980s, sorts of mail readers, will find that replying to the sender works without them having to do anything. They will reply, -- their mail reader will interpret the reply as 'reply to the sender, unless there is a Reply-To:, in which case send it there instead' because all mailers are supposed to do this ... and since there will be a Reply-To: which points at the original posters original address, that is where the reply will go. Which is where you want it to. Laura From mark at msapiro.net Sun Sep 20 17:49:26 2015 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 20 Sep 2015 08:49:26 -0700 Subject: [Mailman-Users] How to get the senders email address in the custom footer? In-Reply-To: References: Message-ID: <55FED586.1000509@msapiro.net> On 09/19/2015 04:58 AM, Arlen Raasch wrote: > > We are using version 2.1.16 of Mailman. > > The emails that currently are sent out via the listserv server have headers > that include the original sender's email address as the "From:" address. > Yahoo's and Aol's DMARC policy causes these to bounce as our server is not > one they recognize. > > I have seen many posts regarding this problem, but no actual solutions that > told me what I should do. Have you seen the FAQ article at . > This is not my area of expertise, just something that dropped in my lap. > > A strategy that makes some sense to me is to take ownership of the emails > by identifying the listserv as the From and Reply-To addresses, but > including a custom footer in the email that exposes the actual sender's > email address. Mailman has various mitigation strategies described in the above referenced FAQ article. With Mailman 2.1.16, you are limited to munging the From: header on all list posts, not just those From: domains that publish DMARC reject and optionally quarantine policies. 2.1.18 adds this latter ability and removes the requirement to add ALLOW_FROM_IS_LIST = Yes to mm_cfg.py to enable the from_is_list setting. 2.1.19 has a few minor bug fixes to the features. ... > I set the annonomous_list setting to yes under general options, and sent a > test email. The email went out fine, but nothing in the default email > footer allowed others to know who actually sent the email out. Correct. While anonymous_list = Yes will avoid DMARC issues, that's not what it is designed for. > I attempted to change the default non-digest footer to include the sender's > address, but did not succeed. It appears that this info is regarding the > recipient,not the sender's info. Correct again. There are no footer replacement variables relating to the sender. ... > So, the question is how to get the sender's email address in the footer. You would need to modify the source code, but if you have the ability to do that, a much better solution is to upgrade to the current 2.1.20 release or even the head of the development branch at and use the dmarc_moderation_action settings for this. Note that Mailman's strategy is to put the original From: in Reply-To: or in some cases in 2.1.19+ in Cc: to both expose the address and make 'reply' and 'reply all' work as closely as possible to the non-munged case. Also note that the development branch is actually quite solid for production use. It is what we are using for all the python.org lists. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From jaybird at bluegrasspals.com Mon Sep 21 03:15:31 2015 From: jaybird at bluegrasspals.com (Jayson Smith) Date: Sun, 20 Sep 2015 21:15:31 -0400 Subject: [Mailman-Users] How to get the senders email address in the custom footer? In-Reply-To: <55FED586.1000509@msapiro.net> References: <55FED586.1000509@msapiro.net> Message-ID: <55FF5A33.6000308@bluegrasspals.com> Hi, I've also been looking for a variable giving the sender's Email address, but came to the same conclusion--it doesn't exist. Imho this would be a useful feature. I admin a mailing list where I had to set it up to munge the From: header because of DMARC, and some Email clients--even though they should know better--were replying to the list even though replies were supposed to go to the sender. I've since taken advantage of the DMARC moderation feature, but we've been encouraging people to give their Email address somewhere in their message. If there were a footer variable with the sender's Email address, this wouldn't be necessary. Just my $0.02 worth. Jayson On 9/20/2015 11:49 AM, Mark Sapiro wrote: > On 09/19/2015 04:58 AM, Arlen Raasch wrote: >> We are using version 2.1.16 of Mailman. >> >> The emails that currently are sent out via the listserv server have headers >> that include the original sender's email address as the "From:" address. >> Yahoo's and Aol's DMARC policy causes these to bounce as our server is not >> one they recognize. >> >> I have seen many posts regarding this problem, but no actual solutions that >> told me what I should do. > > Have you seen the FAQ article at . > > >> This is not my area of expertise, just something that dropped in my lap. >> >> A strategy that makes some sense to me is to take ownership of the emails >> by identifying the listserv as the From and Reply-To addresses, but >> including a custom footer in the email that exposes the actual sender's >> email address. > > Mailman has various mitigation strategies described in the above > referenced FAQ article. With Mailman 2.1.16, you are limited to munging > the From: header on all list posts, not just those From: domains that > publish DMARC reject and optionally quarantine policies. > > 2.1.18 adds this latter ability and removes the requirement to add > > ALLOW_FROM_IS_LIST = Yes > > to mm_cfg.py to enable the from_is_list setting. 2.1.19 has a few minor > bug fixes to the features. > > > ... >> I set the annonomous_list setting to yes under general options, and sent a >> test email. The email went out fine, but nothing in the default email >> footer allowed others to know who actually sent the email out. > > Correct. While anonymous_list = Yes will avoid DMARC issues, that's not > what it is designed for. > > >> I attempted to change the default non-digest footer to include the sender's >> address, but did not succeed. It appears that this info is regarding the >> recipient,not the sender's info. > > Correct again. There are no footer replacement variables relating to the > sender. > > > ... >> So, the question is how to get the sender's email address in the footer. > > You would need to modify the source code, but if you have the ability to > do that, a much better solution is to upgrade to the current 2.1.20 > release or even the head of > the development branch at > and use the > dmarc_moderation_action settings for this. > > Note that Mailman's strategy is to put the original From: in Reply-To: > or in some cases in 2.1.19+ in Cc: to both expose the address and make > 'reply' and 'reply all' work as closely as possible to the non-munged case. > > Also note that the development branch is actually quite solid for > production use. It is what we are using for all the python.org lists. > From mark at msapiro.net Mon Sep 21 04:43:06 2015 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 20 Sep 2015 19:43:06 -0700 Subject: [Mailman-Users] How to get the senders email address in the custom footer? In-Reply-To: <55FF5A33.6000308@bluegrasspals.com> References: <55FED586.1000509@msapiro.net> <55FF5A33.6000308@bluegrasspals.com> Message-ID: <55FF6EBA.8060409@msapiro.net> On 09/20/2015 06:15 PM, Jayson Smith wrote: > > I admin a mailing list where I had to set it up to munge the From: > header because of DMARC, and some Email clients--even though they should > know better--were replying to the list even though replies were supposed > to go to the sender. I've since taken advantage of the DMARC moderation > feature, but we've been encouraging people to give their Email address > somewhere in their message. If there were a footer variable with the > sender's Email address, this wouldn't be necessary. Just my $0.02 worth. With Mailman's DMARC mitigations, if the sender's address is removed from the From: header, it is always in either Reply-To: or Cc:. Even if a user's MUA doesn't correctly address a Reply, it seems to me that it's just as easy to copy/paste the address from the Reply-To: or Cc: header of the original post as it is to copy/paste it from somewhere else in the message. What am I missing? Also, in my experience, users tend not to look at how their reply is addressed in the first place and don't even notice that it is addressed say to the list rather than the poster. I think the appropriate solution is for users to use compliant MUAs that will honor Reply-To:, although I understand that that's a lot easier for me to say than it is to get users to actually do it. All that said, if you really want it, it's a one line patch to add a 'sender' replacement to msg_header and/or msg_footer (watch out for wrapped lines). === modified file 'Mailman/Handlers/Decorate.py' --- Mailman/Handlers/Decorate.py 2010-06-05 17:27:39 +0000 +++ Mailman/Handlers/Decorate.py 2015-09-21 02:34:19 +0000 @@ -42,7 +42,7 @@ # Digests and Mailman-craft messages should not get additional headers if msgdata.get('isdigest') or msgdata.get('nodecorate'): return - d = {} + d = {'sender': msg.get_sender()} if msgdata.get('personalize'): # Calculate the extra personalization dictionary. Note that the # length of the recips list better be exactly 1. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ricardo at americasnet.com Mon Sep 21 18:06:44 2015 From: ricardo at americasnet.com (Ricardo Kleemann) Date: Mon, 21 Sep 2015 09:06:44 -0700 Subject: [Mailman-Users] what's the easiest way to export/import a large list? Message-ID: I have a list with around 50k users and I wanted to move from one server to another. Does copying the the specific list's directory (e.g. under /var/lib/mailman/lists) from one server to another work? Or, alternatively, does config_list output sufficient information of all the settings and characteristics such that I can then input on the other server? thanks Ricardo From mark at msapiro.net Mon Sep 21 23:44:45 2015 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 21 Sep 2015 14:44:45 -0700 Subject: [Mailman-Users] what's the easiest way to export/import a large list? In-Reply-To: References: Message-ID: <56007A4D.8020605@msapiro.net> On 09/21/2015 09:06 AM, Ricardo Kleemann wrote: > I have a list with around 50k users and I wanted to move from one server to > another. > > Does copying the the specific list's directory (e.g. under > /var/lib/mailman/lists) from one server to another work? Yes and no. You want to copy the lists/LISTNAME/config.pck file for sure. You may or may not want to copy the others. In particular, if you copy lists/LISTNAME/requests.pck and there are held messages for the list, you also need to copy all the data/heldmsg-LISTNAME-* files or you will wind up with non-existent held messages. > Or, alternatively, does config_list output sufficient information of all > the settings and characteristics such that I can then input on the other > server? It will do for the list's config, but it won't move list members or any of their settings or passwords. Moving the config.pck will move these things assuming you aren't using some non-standard MemberAdaptor. See the FAQ at and the list posts linked therefrom. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ovh at forum-pc.net Tue Sep 22 22:10:19 2015 From: ovh at forum-pc.net (=?UTF-8?Q?Camille_Olli=c3=a9?=) Date: Tue, 22 Sep 2015 22:10:19 +0200 Subject: [Mailman-Users] MM 3 : permit users to manage subscription Message-ID: <5601B5AB.6000600@forum-pc.net> Hi, i have created a ML. I have added users. But they can't access to any account... Any idea ? -- Camille Olli? www.forum-pc.net / www.scoot-boost.com LinkedIn : http://lnkd.in/_K65k5 From stephen at xemacs.org Wed Sep 23 04:54:33 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Wed, 23 Sep 2015 11:54:33 +0900 Subject: [Mailman-Users] MM 3 : permit users to manage subscription In-Reply-To: <5601B5AB.6000600@forum-pc.net> References: <5601B5AB.6000600@forum-pc.net> Message-ID: <87y4fxetg6.fsf@uwakimon.sk.tsukuba.ac.jp> Camille Olli? writes: > i have created a ML. I have added users. > > But they can't access to any account... > > Any idea ? Do you have an account yourself? Have you tried to access it? By "user" do you mean subscribed to receive posts, or do you mean some other role like moderator? Exactly how did you add those users? Using the "Mass Subscribe" web interface? If not, how? If so, did you *subscribe* them or did you *invite* them? If the latter, they need to accept the invitation before they are subscribed. How are the users trying "access accounts"? Through the web? What is in the webserver log when they try to access an account? From stephen at xemacs.org Wed Sep 23 06:15:02 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Wed, 23 Sep 2015 13:15:02 +0900 Subject: [Mailman-Users] MM 3 : permit users to manage subscription In-Reply-To: <87y4fxetg6.fsf@uwakimon.sk.tsukuba.ac.jp> References: <5601B5AB.6000600@forum-pc.net> <87y4fxetg6.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <87vbb1epq1.fsf@uwakimon.sk.tsukuba.ac.jp> Stephen J. Turnbull writes: > How are the users trying "access accounts"? I didn't notice at first that you're using MM 3. Perhaps you tried to install Postorius on a webserver and Mailman on a mail server (different hosts)? You need to install Postorius (and maybe HyperKitty too) on the same host as Mailman, because the REST interface is not secure, and so restricted to access from localhost. From mjs at clemson.edu Thu Sep 24 20:47:49 2015 From: mjs at clemson.edu (Matthew Saltzman) Date: Thu, 24 Sep 2015 18:47:49 +0000 Subject: [Mailman-Users] Regexp for blocking addresses Message-ID: <1443120469.17817.14.camel@fulkerson-math-clemson-edu> I am trying to block variants of ceertain gmail addresses but I'm having trouble concocting the right rexexp to accomplish the task. Gmail addresses can contain embedded periods and can be followed by a '+' and an arbitrary suffix. So all the following are the same address: * joebloe at gmail.com * joe.blow at gmail.com * j.o.e.blow at gmail.com * joe.blow+abcd at gmail.com And so on. I've tried various regexps, but none have worked so far. 1. Could someone show me the right syntax to catch all embedded dots in the part before the '+'? 2. Is there a way to script removing all my experimentation from the ban lists on multiple mailing lists? Things are looking pretty cluttered by now on the privacy admin pages. Thanks very much in advance. -- Matthew Saltzman Clemson University Math Sciences mjs AT clemson DOT edu From mark at msapiro.net Thu Sep 24 21:05:17 2015 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 24 Sep 2015 14:05:17 -0500 Subject: [Mailman-Users] Regexp for blocking addresses In-Reply-To: <1443120469.17817.14.camel@fulkerson-math-clemson-edu> References: <1443120469.17817.14.camel@fulkerson-math-clemson-edu> Message-ID: <5604496D.5030202@msapiro.net> On 9/24/15 1:47 PM, Matthew Saltzman wrote: > > 1. Could someone show me the right syntax to catch all embedded > dots in the part before the '+'? ^.*\..*\+.*@ for any domain or ^.*\..*\+.*@gmail.com$ for only gmail.com. > 2. Is there a way to script removing all my experimentation from > the ban lists on multiple mailing lists? Things are looking > pretty cluttered by now on the privacy admin pages. See the withlist script at . In that script, replace the line mlist.ban_list.append(address) with mlist.ban_list = [] For that script, you would still need to supply an 'address_to_ban' argument even though it's ignored. You could make an even simpler withlist script along the lines of def init_ban_list(mlist): if not mlist.Locked(): mlist.Lock() mlist.ban_list = [] mlist.Save() mlist.Unlock() -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Fri Sep 25 03:57:23 2015 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 24 Sep 2015 20:57:23 -0500 Subject: [Mailman-Users] Regexp for blocking addresses In-Reply-To: <1443120469.17817.14.camel@fulkerson-math-clemson-edu> References: <1443120469.17817.14.camel@fulkerson-math-clemson-edu> Message-ID: <5604AA03.80509@msapiro.net> On 9/24/15 1:47 PM, Matthew Saltzman wrote: > > I am trying to block variants of ceertain gmail addresses but I'm having > trouble concocting the right rexexp to accomplish the task. > > Gmail addresses can contain embedded periods and can be followed by a > '+' and an arbitrary suffix. So all the following are the same address: > * joebloe at gmail.com > * joe.blow at gmail.com > * j.o.e.blow at gmail.com > * joe.blow+abcd at gmail.com In my prior reply , I focused on your literal question and answered accordingly, but it occurs to me that you are trying to deal with bot generated subscriptions of addresses of the form word.word+digits at gmail.com. While this pattern is the most common one I've seen, not all addresses are like that. They are in different domains and while all gmail addresses may have dots, not all addresses do and a rare few have had non-digits after the +, but all I've seen have at least 5 digits following a + and immediately preceding the @. For the lists @python.org, we are now using ^.*\+.*\d{3,}@ For the history, see , and and other posts in those threads. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Fri Sep 25 17:23:45 2015 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 25 Sep 2015 08:23:45 -0700 Subject: [Mailman-Users] Regexp for blocking addresses In-Reply-To: <1443193078.8062.14.camel@gmail.com> References: <1443120469.17817.14.camel@fulkerson-math-clemson-edu> <5604496D.5030202@msapiro.net> <1443193078.8062.14.camel@gmail.com> Message-ID: <56056701.80808@msapiro.net> On 9/25/15 7:57 AM, Matthew Saltzman wrote: > > That's still much more aggressive than what I was trying to say. I > actually want to ban precisely all variants of the one address > > joeblow at gmail.com > > (and about a dozen other addresses) that include embedded periods > anywhere and the suffix, but not other gmail addresses. grep finds > them with > > \.\?j\.\?o\.\?e\.\?b\.\?l\.\?o\.\?w\.\ ?+.*@gmail \.com > > (I might want \.* instead of \.\?) but adding > > ^\.\?j\.\?o\.\?e\.\?b\.\?l\.\?o\.\?w\.\ ?+.*@gmail\.com > > to the ban list doesn't seem to block them. Because in a python RE, \? is a literal '?', not a '0 or 1 of repeat'. For grep you need the \? to give ? its special meaning. a regexp for egrep or grep -E will be closer to what you want for python. You want ^\.?j\.?o\.?e\.?b\.?l\.?o\.?w xxx \+.*@gmail\.com where I'm unsure about the ' xxx ' part because I don't understand what '\ ?' is supposed to do? Or instead of the above and to account for multiple '.' maybe ^\.*j\.*o\.*e\.*b\.*l\.*o\.*w\.*\+.*@gmail\.com which says zero or more dots followed by j followed by zero or more dots followed by o, etc., followed by w followed by zero or more dots followed by + followed by anything followed by @gmail.com. See . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mjs at clemson.edu Fri Sep 25 19:03:21 2015 From: mjs at clemson.edu (Matthew Saltzman) Date: Fri, 25 Sep 2015 17:03:21 +0000 Subject: [Mailman-Users] Regexp for blocking addresses In-Reply-To: <56056701.80808@msapiro.net> References: <1443120469.17817.14.camel@fulkerson-math-clemson-edu> <5604496D.5030202@msapiro.net> <1443193078.8062.14.camel@gmail.com> <56056701.80808@msapiro.net> Message-ID: <1443200600.8062.31.camel@clemson.edu> On Fri, 2015-09-25 at 08:23 -0700, Mark Sapiro wrote: > On 9/25/15 7:57 AM, Matthew Saltzman wrote: > > > > That's still much more aggressive than what I was trying to say. I > > actually want to ban precisely all variants of the one address > > > > joeblow at gmail.com > > > > (and about a dozen other addresses) that include embedded periods > > anywhere and the suffix, but not other gmail addresses. grep finds > > them with > > > > \.\?j\.\?o\.\?e\.\?b\.\?l\.\?o\.\?w\.\ ?+.*@gmail \.com > > > > (I might want \.* instead of \.\?) but adding > > > > ^\.\?j\.\?o\.\?e\.\?b\.\?l\.\?o\.\?w\.\ ?+.*@gmail\.com > > > > to the ban list doesn't seem to block them. > > > Because in a python RE, \? is a literal '?', not a '0 or 1 of > repeat'. > For grep you need the \? to give ? its special meaning. a regexp for > egrep or grep -E will be closer to what you want for python. You want > > ^\.?j\.?o\.?e\.?b\.?l\.?o\.?w xxx \+.*@gmail\.com > > where I'm unsure about the ' xxx ' part because I don't understand > what > '\ ?' is supposed to do? Just a formatting mistake. > > Or instead of the above and to account for multiple '.' maybe > > ^\.*j\.*o\.*e\.*b\.*l\.*o\.*w\.*\+.*@gmail\.com > > which says zero or more dots followed by j followed by zero or more > dots > followed by o, etc., followed by w followed by zero or more dots > followed by + followed by anything followed by @gmail.com. > > See < > https://docs.python.org/2/library/re.html#regular-expression-syntax>. I think that's what my problem is. Will give it a try. Thanks very much. > -- Matthew Saltzman Clemson University Math Sciences mjs AT clemson DOT edu From lee.mager at gmail.com Fri Sep 25 15:17:18 2015 From: lee.mager at gmail.com (George Mager) Date: Fri, 25 Sep 2015 09:17:18 -0400 Subject: [Mailman-Users] How to link two lists? Message-ID: <91EB81C4-061F-4612-8ABC-49DDF1D1330E@gmail.com> I have two mailing lists. One is a complete list for all the members of my community association, and the other is for the board of directors of the community association. I would like to be able to link the two lists so that residents could send emails to the board list without moderation. I know I could embed the residents list in the board list as a full list of emails, but it would be much more efficient to be able to just link to the residents list. Is there a way to do that? Lee Mager lee.mager at gmail.com From theknight883 at yahoo.com Sat Sep 26 00:16:01 2015 From: theknight883 at yahoo.com (The Knight) Date: Fri, 25 Sep 2015 22:16:01 +0000 (UTC) Subject: [Mailman-Users] Fw: Mailman not delivering e-mails sent from Yahoo In-Reply-To: <985365196.1067307.1443218744513.JavaMail.yahoo@mail.yahoo.com> References: <985365196.1067307.1443218744513.JavaMail.yahoo@mail.yahoo.com> Message-ID: <1742979862.1076141.1443219361062.JavaMail.yahoo@mail.yahoo.com> Hello everyone,? We are using Mailman Version 2.1.9 the problem we are facing is when we use a Yahoo e-mail ID to send an e-mail to a mailing list it reaches mailman but when i Accept it as a moderator it's not delivered to subscribers of the list. I tried with Gmail and MSN everything works fine but this only happens when sent from Yahoo. If anyone has had a similar problem please let me know what solution did you apply ? Thank you From mark at msapiro.net Sat Sep 26 06:01:04 2015 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 25 Sep 2015 21:01:04 -0700 Subject: [Mailman-Users] Regexp for blocking addresses In-Reply-To: <56056701.80808@msapiro.net> References: <56056701.80808@msapiro.net> Message-ID: <56061880.3000306@msapiro.net> On 9/25/15 7:57 AM, Matthew Saltzman wrote: > > That's still much more aggressive than what I was trying to say. I > actually want to ban precisely all variants of the one address > > joeblow at gmail.com > > (and about a dozen other addresses) that include embedded periods > anywhere and the suffix, but not other gmail addresses. Here's another idea. Find the following in /path/to/mailman/Mailman/MailList.py def GetBannedPattern(self, email): """Returns matched entry in ban_list if email matches. Otherwise returns None. """ return self.GetPattern(email, self.ban_list) and change it to bad_users = ['joeblow at gmailcom', 'johndoe at gmailcom', 'jackblack at gmailcom', ... (the rest of the addrs to ban) ] def GetBannedPattern(self, email): """Returns matched entry in ban_list if email matches. Otherwise returns None. """ if re.sub('\.', '' re.sub('\+.*@', '@', email.lower())) in bad_users: return 'bad_user' return self.GetPattern(email, self.ban_list) Note that the line if re.sub('\.', '' re.sub('\+.*@', '@', email.lower())) in bad_users: should be indented 8 spaces as shown above, but still all one line. What this does is lower-case the email address, then replace a '+' if any and all that follows up to an '@' with just the '@' and finally removes all the '.' and if the result is in the bad_users list, the address will be banned for matching 'bad_user'. Note too that there is no '.' in the gmailcom part of the bad addresses as we will have removed that before the test. If you do this, you have to restart Mailman after modifying MailList.py. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sat Sep 26 06:04:26 2015 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 25 Sep 2015 21:04:26 -0700 Subject: [Mailman-Users] Fw: Mailman not delivering e-mails sent from Yahoo In-Reply-To: <1742979862.1076141.1443219361062.JavaMail.yahoo@mail.yahoo.com> References: <985365196.1067307.1443218744513.JavaMail.yahoo@mail.yahoo.com> <1742979862.1076141.1443219361062.JavaMail.yahoo@mail.yahoo.com> Message-ID: <5606194A.4060904@msapiro.net> On 09/25/2015 03:16 PM, The Knight via Mailman-Users wrote: > > We are using Mailman Version 2.1.9 the problem we are facing is when we use a Yahoo e-mail ID to send an e-mail to a mailing list it reaches mailman but when i Accept it as a moderator it's not delivered to subscribers of the list. I tried with Gmail and MSN everything works fine but this only happens when sent from Yahoo. > If anyone has had a similar problem please let me know what solution did you apply ? See the wiki articles at and . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sat Sep 26 06:12:02 2015 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 25 Sep 2015 21:12:02 -0700 Subject: [Mailman-Users] How to link two lists? In-Reply-To: <91EB81C4-061F-4612-8ABC-49DDF1D1330E@gmail.com> References: <91EB81C4-061F-4612-8ABC-49DDF1D1330E@gmail.com> Message-ID: <56061B12.1090400@msapiro.net> On 09/25/2015 06:17 AM, George Mager wrote: > I have two mailing lists. One is a complete list for all the members of my community association, and the other is for the board of directors of the community association. I would like to be able to link the two lists so that residents could send emails to the board list without moderation. I know I could embed the residents list in the board list as a full list of emails, but it would be much more efficient to be able to just link to the residents list. Is there a way to do that? Assuming your Mailman is 2.1.10 or newer, put @residents (or @ + whatever the name of the residents list is) in the board list's accept_these_nonmembers. If your Mailman is 2.1.9 or older, it is over 9 years old and you should consider upgrading. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sat Sep 26 06:16:15 2015 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 25 Sep 2015 21:16:15 -0700 Subject: [Mailman-Users] Regexp for blocking addresses In-Reply-To: <56061880.3000306@msapiro.net> References: <56056701.80808@msapiro.net> <56061880.3000306@msapiro.net> Message-ID: <56061C0F.8000006@msapiro.net> On 09/25/2015 09:01 PM, Mark Sapiro wrote: > > Here's another idea. > > Find the following in /path/to/mailman/Mailman/MailList.py > > def GetBannedPattern(self, email): > """Returns matched entry in ban_list if email matches. > Otherwise returns None. > """ > return self.GetPattern(email, self.ban_list) > > and change it to > > bad_users = ['joeblow at gmailcom', > 'johndoe at gmailcom', > 'jackblack at gmailcom', > ... (the rest of the addrs to ban) > ] ... Ooops. In the above addition, the bad_users line needs to be indented 4 spaces to line up with the following ' def ...'. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From borjariesgo at gmail.com Mon Sep 28 11:15:31 2015 From: borjariesgo at gmail.com (Borja Riesgo Juan) Date: Mon, 28 Sep 2015 11:15:31 +0200 Subject: [Mailman-Users] Fwd: BCC and bounces In-Reply-To: References: <8737yq2zw6.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: Hello I restart this thread again. I'm coming in late here and most of this thread has been covered, but with respect to the above, the all-bounces at mydomain.com address is the list bounce processing address. Mailman sets the envelope sender and also the Sender: and Errors-To: headers to this value. If your users are seeing this address, it is probably because they are using a Microsoft mail client that displays something like "From: (the Sender: address) on behalf of (the From: address)". Since Mailman 2.1.14, if a site allows it, there is a list admin General Options -> include_sender_header setting which can be set to No to not include the Sender: header. The all-bounces at mydomain.com address will still be the envelope sender and in the Errors-To: header, but most users won't see it. --> anonymous_list to yes and first_strip_reply_to to yes. and without not success. this paramters are supposed to hide the sender and other parameters no? my version is 2.1.12. I shoyld ask to my isp to change it. (Editar *anonymous_list*) Also see my other reply in this thread at . --> I imagine that it cannot be supress. in my case, only a few users will be able to reply. Un saludo Borja Riesgo borjariesgo at gmail.com 2015-09-08 23:32 GMT+02:00 Peter Bossley : > But it appears as though the list posting address still winds up in the > CC: field even with FP turned on. It does send a message to each recipient > but I am wondering how one would go about removing the list address in the > CC: field to avoid people replying all. > > > -----Original Message----- > From: Mailman-Users [mailto:mailman-users-bounces+pete= > bossley.me at python.org] On Behalf Of Stephen J. Turnbull > Sent: Monday, September 7, 2015 8:11 AM > To: borjariesgo at gmail.com > Cc: mailman-users at python.org > Subject: [Mailman-Users] Fwd: BCC and bounces > > Borja Riesgo Juan writes: > > > I want the see that i send the message and they as the receivers. > > For a sufficiently recent mailman (I think that includes everything in > common use nowadays) in the *administrative interface* to the list in the > *Non-digest options* screen, you will find an option to > *personalize* messages. In my Mailman that is the second option from the > top in that screen. Set it to "Full Personalization". That should be all > you need to achieve what you have asked for in this post. > > Then send your messages with > > To: all at mydomain.com > From: borjariesgo at gmail.com (or borja at mydomain.com or ...) > > Mailman will *remove* "all at mydomain.com" and substitute each person's > address in To:, in a separate email for each address. Then > person at example.net will see > > To: "M. A. Person" > From: borjariesgo at gmail.com > > (only one "To" address no matter how many people are on the list). > > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at 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/pete%40bossley.me > From mjs at clemson.edu Mon Sep 28 16:46:08 2015 From: mjs at clemson.edu (Matthew Saltzman) Date: Mon, 28 Sep 2015 14:46:08 +0000 Subject: [Mailman-Users] Regexp for blocking addresses In-Reply-To: <1443200600.8062.31.camel@clemson.edu> References: <1443120469.17817.14.camel@fulkerson-math-clemson-edu> <5604496D.5030202@msapiro.net> <1443193078.8062.14.camel@gmail.com> <56056701.80808@msapiro.net> <1443200600.8062.31.camel@clemson.edu> Message-ID: <1443451567.459.10.camel@clemson.edu> On Fri, 2015-09-25 at 17:03 +0000, Matthew Saltzman wrote: > On Fri, 2015-09-25 at 08:23 -0700, Mark Sapiro wrote: > > On 9/25/15 7:57 AM, Matthew Saltzman wrote: > > > > > > That's still much more aggressive than what I was trying to say. > > > I > > > actually want to ban precisely all variants of the one address > > > > > > joeblow at gmail.com > > > > > > (and about a dozen other addresses) that include embedded periods > > > anywhere and the suffix, but not other gmail addresses. grep > > > finds > > > them with > > > > > > \.\?j\.\?o\.\?e\.\?b\.\?l\.\?o\.\?w\.\ ?+.*@gmail \.com > > > > > > (I might want \.* instead of \.\?) but adding > > > > > > ^\.\?j\.\?o\.\?e\.\?b\.\?l\.\?o\.\?w\.\ ?+.*@gmail\.com > > > > > > to the ban list doesn't seem to block them. > > > > > > Because in a python RE, \? is a literal '?', not a '0 or 1 of > > repeat'. > > For grep you need the \? to give ? its special meaning. a regexp > > for > > egrep or grep -E will be closer to what you want for python. You > > want > > > > ^\.?j\.?o\.?e\.?b\.?l\.?o\.?w xxx \+.*@gmail\.com > > > > where I'm unsure about the ' xxx ' part because I don't understand > > what > > '\ ?' is supposed to do? > > Just a formatting mistake. > > > > > Or instead of the above and to account for multiple '.' maybe > > > > ^\.*j\.*o\.*e\.*b\.*l\.*o\.*w\.*\+.*@gmail\.com > > > > which says zero or more dots followed by j followed by zero or more > > dots > > followed by o, etc., followed by w followed by zero or more dots > > followed by + followed by anything followed by @gmail.com. > > > > See < > > https://docs.python.org/2/library/re.html#regular-expression-syntax > > >;. > > I think that's what my problem is. Will give it a try. > > Thanks very much. So I used the ban script from http://nigelb.me/2015-08-26-mailman-attacks.html to add regexps of the form "^\.*j\.*o\.*e\.*b\.*l\.*o\.*w \ .*+.*@gmail \.com" to the ban list. They show up in the ban_list window looking correct (without the quotes) but don't seem to be blocking the intended addresses. The same pattern without the \.*'s does block the addresses not containing embedded periods. Not quite sure what I'm missing or where to go here. I'd prefer not to actually hack the code in MailList.py if I can avoid it. -- Matthew Saltzman Clemson University Math Sciences mjs AT clemson DOT edu From mjs at clemson.edu Mon Sep 28 16:52:50 2015 From: mjs at clemson.edu (Matthew Saltzman) Date: Mon, 28 Sep 2015 14:52:50 +0000 Subject: [Mailman-Users] Reenabling users disabled due to bounces Message-ID: <1443451969.459.14.camel@clemson.edu> We had an issue with outgoing mail last week that caused a number of users on multiple lists to be disabled due to bounces. I'd like to clear all those flags and reenable those users. Is there an easy way to take care of that en masse? Or at least to locate all those users without paging through membership lists on the Web? TIA. -- Matthew Saltzman Clemson University Math Sciences mjs AT clemson DOT edu From cnulk at scu.edu Mon Sep 28 19:22:55 2015 From: cnulk at scu.edu (Chris Nulk) Date: Mon, 28 Sep 2015 10:22:55 -0700 Subject: [Mailman-Users] Regexp for blocking addresses In-Reply-To: <56061C0F.8000006@msapiro.net> References: <56056701.80808@msapiro.net> <56061880.3000306@msapiro.net> <56061C0F.8000006@msapiro.net> Message-ID: <5609776F.1070700@scu.edu> On 9/25/2015 9:16 PM, Mark Sapiro wrote: > On 09/25/2015 09:01 PM, Mark Sapiro wrote: >> Here's another idea. >> >> Find the following in /path/to/mailman/Mailman/MailList.py >> >> def GetBannedPattern(self, email): >> """Returns matched entry in ban_list if email matches. >> Otherwise returns None. >> """ >> return self.GetPattern(email, self.ban_list) >> >> and change it to >> >> bad_users = ['joeblow at gmailcom', >> 'johndoe at gmailcom', >> 'jackblack at gmailcom', >> ... (the rest of the addrs to ban) >> ] > ... > > > Ooops. In the above addition, the bad_users line needs to be indented 4 > spaces to line up with the following ' def ...'. > Would it make sense to define the "bad users" in mm_cfg.py? That way it would be a bit easier to add/remove/change addresses when needed. Also, wouldn't updating Mailman replace the modified /path/to/mailman/Mailman/MailList.py? Just a thought, Chris From mjs at clemson.edu Mon Sep 28 21:04:16 2015 From: mjs at clemson.edu (Matthew Saltzman) Date: Mon, 28 Sep 2015 19:04:16 +0000 Subject: [Mailman-Users] Regexp for blocking addresses In-Reply-To: <5604AA03.80509@msapiro.net> References: <1443120469.17817.14.camel@fulkerson-math-clemson-edu> <5604AA03.80509@msapiro.net> Message-ID: <1443467055.459.35.camel@clemson.edu> On Thu, 2015-09-24 at 20:57 -0500, Mark Sapiro wrote: > On 9/24/15 1:47 PM, Matthew Saltzman wrote: > > > > I am trying to block variants of certain gmail addresses but I'm > > having > > trouble concocting the right rexexp to accomplish the task. > > > > Gmail addresses can contain embedded periods and can be followed by > > a > > '+' and an arbitrary suffix. So all the following are the same > > address: > > * joebloe at gmail.com > > * joe.blow at gmail.com > > * j.o.e.blow at gmail.com > > * joe.blow+abcd at gmail.com > > > In my prior reply > 6.html>, > I focused on your literal question and answered accordingly, but it > occurs to me that you are trying to deal with bot generated > subscriptions of addresses of the form word.word+digits at gmail.com. > While > this pattern is the most common one I've seen, not all addresses are > like that. They are in different domains and while all gmail > addresses > may have dots, not all addresses do and a rare few have had non > -digits > after the +, but all I've seen have at least 5 digits following a + > and > immediately preceding the @. > > For the lists @python.org, we are now using > > ^.*\+.*\d{3,}@ > > For the history, see > tml>, > 9.html> > and > 4.html> > and other posts in those threads. Looking back over this thread, I picked up on this. It is a bit more aggressive than I was looking for, but probably works with high probability. When I encountered the original issue, I had enough evidence to find the exact set of addresses that were causing the problem on my server. After I banned those, the same addresses started showing up with embedded periods. FIY, the ones I found were: * ^nkymtky+.*@gmail\.com * ^kihuwzl+.*@gmail\.com * ^kihuotter+.*@gmail\.com * ^hulexchan+.*@gmail\.com * ^ewnetwork+.*@gmail\.com * ^damofah+.*@gmail\.com * ^bustysarahrae+.*@gmail\.com * ^vujovich+.*@usc\.edu * ^yesboobsofficial+.*@gmail\.com * ^yowesephth+.*@gmail\.com * ^ewnetwork2+.*@gmail\.com * ^nwplayer123+.*@gmail\.com So I guessed that if I could just block those (with embedded periods), I'd have the issue covered. Have others seen other addresses? BTW, the part after the '+' in all cases I've seen have been only digits. That might be a better way to go than any three or more characters if one wanted to be as precise as possible. Thanks for your help. -- Matthew Saltzman Clemson University Math Sciences mjs AT clemson DOT edu From phanh at canby.k12.or.us Tue Sep 29 00:42:59 2015 From: phanh at canby.k12.or.us (Hung Phan) Date: Mon, 28 Sep 2015 15:42:59 -0700 Subject: [Mailman-Users] 1-click unsubscribe and Google gmail Message-ID: Hello, We notice that our 1-click unsubscribe option %(user_optionsurl)s?password=%(user_password)s&unsub=1&unsubconfirm=1 doesn't get interpreted correctly by gmail. The whole text get displayed as is while other email systems like yahoo translates it into a clickable link. Anyone has a solution or workaround? Thank you! From mark at msapiro.net Tue Sep 29 04:00:17 2015 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 28 Sep 2015 19:00:17 -0700 Subject: [Mailman-Users] 1-click unsubscribe and Google gmail In-Reply-To: References: Message-ID: <5609F0B1.5090900@msapiro.net> On 09/28/2015 03:42 PM, Hung Phan wrote: > Hello, > > We notice that our 1-click unsubscribe > option %(user_optionsurl)s?password=%(user_password)s&unsub=1&unsubconfirm=1 > doesn't get interpreted correctly by gmail. The whole text get displayed as > is while other email systems like yahoo translates it into a clickable > link. msg_header and msg_footer are either added as plain text to a text/plain message or added as separate text/plain parts to a more complex message. I.e., the footer itself is always plain text. Whether something that looks like a URL in plain text is rendered as a clickable link is completely up to the MUA (mail client) rendering the message. If gmail's web client doesn't render plain text URLs as links, that is up to gmail. It may be (I don't know and haven't tried to verify) that gmail treats plain text that looks like a URL differently depending on whether it is in a plain text message body vs. in a plain text attachment to an HTML or multipart alternative message. If that is the case, the FAQ at may help. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Tue Sep 29 04:03:15 2015 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 28 Sep 2015 19:03:15 -0700 Subject: [Mailman-Users] Reenabling users disabled due to bounces In-Reply-To: <1443451969.459.14.camel@clemson.edu> References: <1443451969.459.14.camel@clemson.edu> Message-ID: <5609F163.8050603@msapiro.net> On 09/28/2015 07:52 AM, Matthew Saltzman wrote: > We had an issue with outgoing mail last week that caused a number of > users on multiple lists to be disabled due to bounces. I'd like to > clear all those flags and reenable those users. > > Is there an easy way to take care of that en masse? Or at least to > locate all those users without paging through membership lists on the > Web? See the scripts at and (mirrored at and ). -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Tue Sep 29 04:25:25 2015 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 28 Sep 2015 19:25:25 -0700 Subject: [Mailman-Users] Regexp for blocking addresses In-Reply-To: <1443467055.459.35.camel@clemson.edu> References: <1443120469.17817.14.camel@fulkerson-math-clemson-edu> <5604AA03.80509@msapiro.net> <1443467055.459.35.camel@clemson.edu> Message-ID: <5609F695.1000605@msapiro.net> On 09/28/2015 12:04 PM, Matthew Saltzman wrote: > > FIY, the ones I found were: > > * ^nkymtky+.*@gmail\.com > * ^kihuwzl+.*@gmail\.com > * ^kihuotter+.*@gmail\.com > * ^hulexchan+.*@gmail\.com > * ^ewnetwork+.*@gmail\.com > * ^damofah+.*@gmail\.com > * ^bustysarahrae+.*@gmail\.com > * ^vujovich+.*@usc\.edu > * ^yesboobsofficial+.*@gmail\.com > * ^yowesephth+.*@gmail\.com > * ^ewnetwork2+.*@gmail\.com > * ^nwplayer123+.*@gmail\.com > > So I guessed that if I could just block those (with embedded periods), > I'd have the issue covered. Have others seen other addresses? These bustys.arahrae+digits at gmail.com dam.ofah+digits at gmail.com ewne.twork2+digits at gmail.com ewnet.work+digits at gmail.com hul.exchan+digits at gmail.com kihuo.tter+digits at gmail.com kih.uwzl+digits at gmail.com nky.mtky+digits at gmail.com nw.player123+digits at gmail.com vujovich+digits at usc.edu yesboo.bsofficial+digits at gmail.com yowesep.hth+digits at gmail.com are just the ones seen at mail.python.org on Sept 28, CEST. I have seen lots of others and other domains. The initial ones a few weeks ago had only 5 digits, but lately, they all have more. As noted in the post at , I checked and there was only one member of one list out of all the python.org list subscribers that had a local part ending with '+' and digits and it only had one digit between the '+' and '@'. There are a few that match the '+' followed by anything followed by at least 3 digits followed by @ RE, so this RE ^.*\+\d(3,}@ which requires 3 or more digits and only digits between + and @ is safer, and ^.*\+\d(5,}@ is safer still and I think would get all the ones I'm currently seeing. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Tue Sep 29 04:41:51 2015 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 28 Sep 2015 19:41:51 -0700 Subject: [Mailman-Users] Regexp for blocking addresses In-Reply-To: <1443451567.459.10.camel@clemson.edu> References: <1443120469.17817.14.camel@fulkerson-math-clemson-edu> <5604496D.5030202@msapiro.net> <1443193078.8062.14.camel@gmail.com> <56056701.80808@msapiro.net> <1443200600.8062.31.camel@clemson.edu> <1443451567.459.10.camel@clemson.edu> Message-ID: <5609FA6F.60506@msapiro.net> On 09/28/2015 07:46 AM, Matthew Saltzman wrote: > > So I used the ban script from > http://nigelb.me/2015-08-26-mailman-attacks.html to add regexps of the > form > > "^\.*j\.*o\.*e\.*b\.*l\.*o\.*w \ .*+.*@gmail \.com" > > to the ban list. They show up in the ban_list window looking correct > (without the quotes) but don't seem to be blocking the intended > addresses. The same pattern without the \.*'s does block the addresses > not containing embedded periods. > > Not quite sure what I'm missing or where to go here. I'd prefer not to > actually hack the code in MailList.py if I can avoid it. I'm not sure either because I don't know if any of that white space is actually there or not. However, this part '.*+' is absolutely wrong. The + needs a preceding \ or the entire RE is invalid. And you don't want to hack the code either because trying to keep a list of actual addresses is futile because there keep being more, the permutations with '.' notwithstanding. You want either the regexp I'm using or one of the 'safer' ones in my reply at . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Tue Sep 29 04:47:24 2015 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 28 Sep 2015 19:47:24 -0700 Subject: [Mailman-Users] Regexp for blocking addresses In-Reply-To: <5609776F.1070700@scu.edu> References: <56056701.80808@msapiro.net> <56061880.3000306@msapiro.net> <56061C0F.8000006@msapiro.net> <5609776F.1070700@scu.edu> Message-ID: <5609FBBC.8070200@msapiro.net> On 09/28/2015 10:22 AM, Chris Nulk wrote: > > Would it make sense to define the "bad users" in mm_cfg.py? That way it > would be a bit easier to add/remove/change addresses when needed. Also, > wouldn't updating Mailman replace the modified > /path/to/mailman/Mailman/MailList.py? Yes, making it an mm_cfg setting might be better and would certainly be done if I were making this a feature, but I'm not, so modifying MailList.py would be required in any case, and yes, these mods would be reversed by an update. That's why if you make local mods to the code, you MUST keep a local patch file or other record so you can figure out after an upgrade which of your local mods are still required and how to apply them. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Tue Sep 29 05:07:20 2015 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 28 Sep 2015 20:07:20 -0700 Subject: [Mailman-Users] Regexp for blocking addresses In-Reply-To: <5609F695.1000605@msapiro.net> References: <5609F695.1000605@msapiro.net> Message-ID: <560A0068.60707@msapiro.net> Mark Sapiro wrote: > These > > bustys.arahrae+digits at gmail.com > dam.ofah+digits at gmail.com > ewne.twork2+digits at gmail.com > ewnet.work+digits at gmail.com > hul.exchan+digits at gmail.com > kihuo.tter+digits at gmail.com > kih.uwzl+digits at gmail.com > nky.mtky+digits at gmail.com > nw.player123+digits at gmail.com > vujovich+digits at usc.edu > yesboo.bsofficial+digits at gmail.com > yowesep.hth+digits at gmail.com > > are just the ones seen at mail.python.org on Sept 28, CEST. I went back further in the logs and have seen the following: admins+@inkedfur.com bustys.arahrae+@gmail.com bustysarahrae+@gmail.com dam.ofah+@gmail.com damofah+@gmail.com ewne.twork2+@gmail.com ewnetwork2+@gmail.com ewnet.work+@gmail.com ewnetwork+@gmail.com hul.exchan+@gmail.com hulexchan+@gmail.com kamilla+@inkedfur.com kihuo.tter+@gmail.com kihuotter+@gmail.com kih.uwzl+@gmail.com kihuwzl+@gmail.com knuckles9048+@gmail.com kory+@korybing.com legal+@thehiveworks.com nky.mtky+@gmail.com nkymtky+@gmail.com nw.player123+@gmail.com nwplayer123+@gmail.com poisonedala+@gmail.com shelbyshuff+@aol.com shelbyshuff+@gmail.com skitty+@outlook.com swizzlecomms+@gmail.com vujovich+@usc.edu yesboo.bsofficial+@gmail.com yesboobsofficial+@gmail.com yowesep.hth+@gmail.com yowesephth+@gmail.com zetaharu.contact+@gmail.com I thought I had seen one, possibly in the inkedfur.com domain, which had some non-digits between the + and the digits, but I don't see it in the logs. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Tue Sep 29 05:54:20 2015 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 28 Sep 2015 20:54:20 -0700 Subject: [Mailman-Users] Regexp for blocking addresses In-Reply-To: <560A0068.60707@msapiro.net> References: <5609F695.1000605@msapiro.net> <560A0068.60707@msapiro.net> Message-ID: <560A0B6C.4020506@msapiro.net> On 09/28/2015 08:07 PM, Mark Sapiro wrote: > > I thought I had seen one, possibly in the inkedfur.com domain, which had > some non-digits between the + and the digits, but I don't see it in the > logs. OK, Here's what I now believe is the complete list we've seen at mail.python.org. admins+@inkedfur.com bustys.arahrae+@gmail.com bustysarahrae+@gmail.com cosith545+add-furrets-on-skype-@gmail.com cosith545+@gmail.com dam.ofah+@gmail.com damofah+@gmail.com dongus3009+@gmail.com ewne.twork2+@gmail.com ewnetwork2+@gmail.com ewnet.work+@gmail.com ewnetwork+@gmail.com hre257.103+add-furrets-on-skype-@gmail.com hre257.103+@gmail.com hul.exchan+@gmail.com hulexchan+@gmail.com kamilla+@inkedfur.com kemo.mart+@gmail.com kemo.mart+@gmail.com; kihuo.tter+@gmail.com kihuotter+@gmail.com kih.uwzl+@gmail.com kihuwzl+@gmail.com knuckles9048+@gmail.com kory+@korybing.com legal+@thehiveworks.com lincoramon+@gmail.com melthehybrid+@gmail.com menominun+add-furrets-on-skype-@gmail.com menominun+@gmail.com mithrilarts+@gmail.com nankasiroino+add-furrets-on-skype-@gmail.com nankasiroino+@gmail.com nkymtky+add-furrets-on-skype-@gmail.com nky.mtky+@gmail.com nkymtky+@gmail.com norphedore+add-furrets-on-skype-@gmail.com norphedore+@gmail.com nw.player123+@gmail.com nwplayer123+@gmail.com poisonedala+@gmail.com purple.kecleon+@gmail.com rara_10_25+add-furrets-on-skype-@hotmail.com rara_10_25+@hotmail.com sample@email.tst shelbyshuff+@aol.com shelbyshuff+@gmail.com skitty+@outlook.com supersatanson+@gmail.com swizzlecomms+@gmail.com techtonik@gmail.com tygurstar+@gmail.com vujovich+@usc.edu yatton7+add-furrets-on-skype-@gmail.com yatton7+@gmail.com yesboo.bsofficial+@gmail.com yesboobsofficial+@gmail.com yowesep.hth+@gmail.com yowesephth+@gmail.com zetaharu.contact+@gmail.com The list I posted at is those for the month of September to date. The above list includes August too. I think in all cases, is a string of at leaser 5 digits. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Tue Sep 29 06:54:28 2015 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 28 Sep 2015 21:54:28 -0700 Subject: [Mailman-Users] Fwd: BCC and bounces In-Reply-To: References: <8737yq2zw6.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <560A1984.7060308@msapiro.net> On 09/28/2015 02:15 AM, Borja Riesgo Juan wrote: > > --> anonymous_list to yes and first_strip_reply_to to yes. and > without not success. this paramters are supposed to hide the sender > and other parameters no? my version is 2.1.12. I shoyld ask to my isp > to change it. anonymous_list = Yes will do its best to conceal the identity of the person who posted to the list. It makes no attempt to conceal the fact that the message came from a list. > --> I imagine that it cannot be supress. in my case, only a few users > will be able to reply. I believe you are trying to do things that Mailman is not designed to do. If the people on your list do not know that they are on a list, How did they get there. Did they get there by confirmed opt-in or did you add them without their informed consent? In your original post, you said > To sum up, i want that the list is something that they don?t know. how can > i do that? The answer is "mailman is not designed to do that". If you need to do that, you'll have to use something else. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From dap1 at bellsouth.net Tue Sep 29 13:32:21 2015 From: dap1 at bellsouth.net (Dennis Putnam) Date: Tue, 29 Sep 2015 07:32:21 -0400 Subject: [Mailman-Users] list-owner getting spammed Message-ID: <560A76C5.2080906@bellsouth.net> The list-owner of one of my lists is getting spammed. Is there an easy way to block that? TIA. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 196 bytes Desc: OpenPGP digital signature URL: From borjariesgo at gmail.com Tue Sep 29 16:05:07 2015 From: borjariesgo at gmail.com (Borja Riesgo Juan) Date: Tue, 29 Sep 2015 16:05:07 +0200 Subject: [Mailman-Users] Fwd: BCC and bounces In-Reply-To: References: <8737yq2zw6.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: I answer: anonymous_list = Yes will do its best to conceal the identity of the person who posted to the list. It makes no attempt to conceal the fact that the message came from a list. >* --> I imagine that it cannot be supress. in my case, only a few users *>* will be able to reply. * I believe you are trying to do things that Mailman is not designed to do. If the people on your list do not know that they are on a list, How did they get there. Did they get there by confirmed opt-in or did you add them without their informed consent? In your original post, you said >* To sum up, i want that the list is something that they don?t know. how can *>* i do that? * The answer is "mailman is not designed to do that". If you need to do that, you'll have to use something else. MY problem is the following. My ISP doen?st allow to send more than 100 messages per hour. I have a music group with 100-150 people in it. I have to sent messages in the CCO field but now this is not allow in my ISP and the only thing they allow me to do is sending using mailman. I want that the aspect of the mail are similiar to the mails that have users in the CCO. That's the rest for hidden the list. i don?t want they reply the list, and i want them to reply to my email address. may change the listname-bounces at domainname? i don?t like this. why is this created? what is the aim of this address? i have asked to update to a new vesion or mailman and the answer from my isp is that is not allowed. the version with the isp 2.1.12. the have to updte the cpanel Best regards Borja Un saludo Borja Riesgo borjariesgo at gmail.com 2015-09-28 11:15 GMT+02:00 Borja Riesgo Juan : > Hello > > > I restart this thread again. > > > I'm coming in late here and most of this thread has been covered, but > with respect to the above, the all-bounces at mydomain.com address is the > list bounce processing address. Mailman sets the envelope sender and > also the Sender: and Errors-To: headers to this value. If your users > are seeing this address, it is probably because they are using a > Microsoft mail client that displays something like "From: (the Sender: > address) on behalf of (the From: address)". > > Since Mailman 2.1.14, if a site allows it, there is a list admin General > Options -> include_sender_header setting which can be set to No to not > include the Sender: header. The all-bounces at mydomain.com address will > still be the envelope sender and in the Errors-To: header, but most > users won't see it. > > --> anonymous_list to yes and first_strip_reply_to to yes. and without not success. this paramters are supposed to hide the sender and other parameters no? my version is 2.1.12. I shoyld ask to my isp to change it. > > (Editar *anonymous_list*) > > > Also see my other reply in this thread at > . > > > --> I imagine that it cannot be supress. in my case, only a few users will be able to reply. > > > Un saludo > > Borja Riesgo > borjariesgo at gmail.com > > 2015-09-08 23:32 GMT+02:00 Peter Bossley : > >> But it appears as though the list posting address still winds up in the >> CC: field even with FP turned on. It does send a message to each recipient >> but I am wondering how one would go about removing the list address in the >> CC: field to avoid people replying all. >> >> >> -----Original Message----- >> From: Mailman-Users [mailto:mailman-users-bounces+pete= >> bossley.me at python.org] On Behalf Of Stephen J. Turnbull >> Sent: Monday, September 7, 2015 8:11 AM >> To: borjariesgo at gmail.com >> Cc: mailman-users at python.org >> Subject: [Mailman-Users] Fwd: BCC and bounces >> >> Borja Riesgo Juan writes: >> >> > I want the see that i send the message and they as the receivers. >> >> For a sufficiently recent mailman (I think that includes everything in >> common use nowadays) in the *administrative interface* to the list in the >> *Non-digest options* screen, you will find an option to >> *personalize* messages. In my Mailman that is the second option from the >> top in that screen. Set it to "Full Personalization". That should be all >> you need to achieve what you have asked for in this post. >> >> Then send your messages with >> >> To: all at mydomain.com >> From: borjariesgo at gmail.com (or borja at mydomain.com or ...) >> >> Mailman will *remove* "all at mydomain.com" and substitute each person's >> address in To:, in a separate email for each address. Then >> person at example.net will see >> >> To: "M. A. Person" >> From: borjariesgo at gmail.com >> >> (only one "To" address no matter how many people are on the list). >> >> ------------------------------------------------------ >> Mailman-Users mailing list Mailman-Users at 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/pete%40bossley.me >> > > From mjs at clemson.edu Tue Sep 29 17:24:27 2015 From: mjs at clemson.edu (Matthew Saltzman) Date: Tue, 29 Sep 2015 15:24:27 +0000 Subject: [Mailman-Users] Regexp for blocking addresses In-Reply-To: <5609FA6F.60506@msapiro.net> References: <1443120469.17817.14.camel@fulkerson-math-clemson-edu> <5604496D.5030202@msapiro.net> <1443193078.8062.14.camel@gmail.com> <56056701.80808@msapiro.net> <1443200600.8062.31.camel@clemson.edu> <1443451567.459.10.camel@clemson.edu> <5609FA6F.60506@msapiro.net> Message-ID: <1443540267.459.52.camel@clemson.edu> On Mon, 2015-09-28 at 19:41 -0700, Mark Sapiro wrote: > On 09/28/2015 07:46 AM, Matthew Saltzman wrote: > > > > So I used the ban script from > > http://nigelb.me/2015-08-26-mailman-attacks.html to add regexps of > > the > > form > > > > "^\.*j\.*o\.*e\.*b\.*l\.*o\.*w \ .*+.*@gmail \.com" > > > > to the ban list. They show up in the ban_list window looking > > correct > > (without the quotes) but don't seem to be blocking the intended > > addresses. The same pattern without the \.*'s does block the > > addresses > > not containing embedded periods. > > > > Not quite sure what I'm missing or where to go here. I'd prefer not > > to > > actually hack the code in MailList.py if I can avoid it. > > > I'm not sure either because I don't know if any of that white space > is > actually there or not. Not. I don't know where it's coming from, as it doesn't look like that when I compose. > However, this part '.*+' is absolutely wrong. The + needs a preceding > \ > or the entire RE is invalid. Ah, that's probably it. > > And you don't want to hack the code either because trying to keep a > list > of actual addresses is futile because there keep being more, the > permutations with '.' notwithstanding. You want either the regexp I'm > using or one of the 'safer' ones in my reply at > 4.html>. > Got it, thanks. I will switch to that one. Now would like to figure out how to delete all my futile attempts from the ban list. Tried modifying the ban script to remove instead of append, but I'm still doing something wrong. Anyway, thanks for your help. -- Matthew Saltzman Clemson University Math Sciences mjs AT clemson DOT edu From take at nerd.fi Tue Sep 29 00:31:02 2015 From: take at nerd.fi (Take) Date: Tue, 29 Sep 2015 01:31:02 +0300 Subject: [Mailman-Users] Problems on mailman3 installation via mailman-bundler Message-ID: <5609BFA6.6040100@nerd.fi> I've been struggling for couple of days to get mailman3 up and running on my Debian Jessie -host. So far I'm in the situation that everything should (more or less) work, I can create lists and receive confirmation emails etc. However, every post I send to the testing-list I created end up in shunting, from log file I get this: Sep 29 00:59:34 2015 (21017) Traceback (most recent call last): File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/core/runner.py", line 165, in _one_iteration self._process_one_file(msg, msgdata) File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/core/runner.py", line 258, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/runners/incoming.py", line 63, in _dispose process(mlist, msg, msgdata, start_chain) File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/core/chains.py", line 86, in process link.function(mlist, msg, msgdata) File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/chains/hold.py", line 182, in _process autorespond_to_sender(mlist, msg.sender, language)): File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/chains/hold.py", line 83, in autorespond_to_sender address = user_manager.create_address(sender) File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/database/transaction.py", line 92, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/model/usermanager.py", line 110, in create_address address = Address(email, display_name) File "", line 4, in __init__ File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/sqlalchemy/orm/state.py", line 306, in _initialize_instance manager.dispatch.init_failure(self, args, kwargs) File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/sqlalchemy/util/langhelpers.py", line 60, in __exit__ compat.reraise(exc_type, exc_value, exc_tb) File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/sqlalchemy/util/compat.py", line 182, in reraise raise value File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/sqlalchemy/orm/state.py", line 303, in _initialize_instance return manager.original_init(*mixed[1:], **kwargs) File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/model/address.py", line 59, in __init__ getUtility(IEmailValidator).validate(email) File "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/email/validate.py", line 64, in validate raise InvalidEmailAddressError(email) mailman.interfaces.address.InvalidEmailAddressError So, apparently something is wrong with member addresses? Since I'm dealing with fresh installation there's only two of my own addresses, both valid (checked via bin/mailman members mylist at example.com) Additionally, for some reason my debug.log is empty. I couldn't find any reference from documentation nor from sample configuration files on how to switch debugging on, is there documentation about mailman.cfg and options I can (or should) have there? -- Take From mark at msapiro.net Tue Sep 29 18:55:30 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 29 Sep 2015 09:55:30 -0700 Subject: [Mailman-Users] Regexp for blocking addresses In-Reply-To: <1443540267.459.52.camel@clemson.edu> References: <1443120469.17817.14.camel@fulkerson-math-clemson-edu> <5604496D.5030202@msapiro.net> <1443193078.8062.14.camel@gmail.com> <56056701.80808@msapiro.net> <1443200600.8062.31.camel@clemson.edu> <1443451567.459.10.camel@clemson.edu> <5609FA6F.60506@msapiro.net> <1443540267.459.52.camel@clemson.edu> Message-ID: <560AC282.8010000@msapiro.net> On 09/29/2015 08:24 AM, Matthew Saltzman wrote: > > Got it, thanks. I will switch to that one. Now would like to figure out > how to delete all my futile attempts from the ban list. Tried modifying > the ban script to remove instead of append, but I'm still doing > something wrong. If the various list's ban_list attributes were empty to start with, use the following withlist script based on ----------------------Cut----------------------------- """Set the ban_list for all lists to a single address or regexp. Save as bin/set_banned.py Run via bin/withlist -a -r set_banned -- where is the actual email address or regexp to be set as ban_list for all lists. """ def set_banned(mlist, address): if not mlist.Locked(): mlist.Lock() mlist.ban_list = [address] mlist.Save() mlist.Unlock() ----------------------Cut----------------------------- If you want to remove individual regexps/addresses from all list's ban_list, changing 'ban_list.append(address)' to 'ban_list.remove(address)' in whatever script you were using should work, but the value of 'address' has to be exactly what is in ban_list that you want to remove. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Tue Sep 29 19:02:53 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 29 Sep 2015 10:02:53 -0700 Subject: [Mailman-Users] list-owner getting spammed In-Reply-To: <560A76C5.2080906@bellsouth.net> References: <560A76C5.2080906@bellsouth.net> Message-ID: <560AC43D.9000002@msapiro.net> On 09/29/2015 04:32 AM, Dennis Putnam wrote: > The list-owner of one of my lists is getting spammed. Is there an easy > way to block that? TIA. Privacy options... --> Spam filters --> header_filter_rules apply to mail to list-owner as well as to list, so the owner may be able to use those to discard the spam. Otherwise, you need more effective spam filtering in the MTA ahead of Mailman. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From mark at msapiro.net Tue Sep 29 19:12:18 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 29 Sep 2015 10:12:18 -0700 Subject: [Mailman-Users] Fwd: BCC and bounces In-Reply-To: References: <8737yq2zw6.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <560AC672.4000602@msapiro.net> On 09/29/2015 07:05 AM, Borja Riesgo Juan wrote: > > MY problem is the following. My ISP doen?st allow to send more than > 100 messages per hour. > I have a music group with 100-150 people in it. > I have to sent messages in the CCO field but now this is not allow in > my ISP and > the only thing they allow me to do is sending using mailman. > I want that the aspect of the mail are similiar to the mails that > have users in the CCO. > That's the rest for hidden the list. i don?t want they reply the > list, and i want them to reply to my email address. The FAQ article at explains how to set up such a list. > may change the listname-bounces at domainname? i don?t like this. why is > this created? what is the aim of this address? This address is used as the envelope sender and as the Sender: and Errors-To: header addresses to enable bounced mail to be returned to the listname-bounces address for Mailman's automated bounce processing. > i have asked to update to a new vesion or mailman and the answer from > my isp is that is not allowed. the version with the isp 2.1.12. the > have to updte the cpanel If you have issues with your hosting provider, there are plenty of others who offer current cPanel which includes Mailman 2.1.20. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Tue Sep 29 19:28:44 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 29 Sep 2015 10:28:44 -0700 Subject: [Mailman-Users] Problems on mailman3 installation via mailman-bundler In-Reply-To: <5609BFA6.6040100@nerd.fi> References: <5609BFA6.6040100@nerd.fi> Message-ID: <560ACA4C.5050108@msapiro.net> On 09/28/2015 03:31 PM, Take wrote: > I've been struggling for couple of days to get mailman3 up and running > on my Debian Jessie -host. So far I'm in the situation that everything > should (more or less) work, I can create lists and receive confirmation > emails etc. > > However, every post I send to the testing-list I created end up in > shunting, from log file I get this: > > Sep 29 00:59:34 2015 (21017) Traceback (most recent call last): > File > "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/core/runner.py", > line 165, in _one_iteration > self._process_one_file(msg, msgdata) > File > "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/core/runner.py", > line 258, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File > "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/runners/incoming.py", > line 63, in _dispose > process(mlist, msg, msgdata, start_chain) > File > "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/core/chains.py", > line 86, in process > link.function(mlist, msg, msgdata) > File > "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/chains/hold.py", > line 182, in _process > autorespond_to_sender(mlist, msg.sender, language)): > File > "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/chains/hold.py", > line 83, in autorespond_to_sender > address = user_manager.create_address(sender) ... > File > "/home/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/email/validate.py", > line 64, in validate > raise InvalidEmailAddressError(email) > mailman.interfaces.address.InvalidEmailAddressError > > So, apparently something is wrong with member addresses? Since I'm > dealing with fresh installation there's only two of my own addresses, > both valid (checked via bin/mailman members mylist at example.com) No. The address which is the problem is the sender address of the post that is being held. Mailman is attempting to notify the poster that her post is being held for moderation and the poster's address appears to be invalid. This is normally the address in the From: header of the post, but can be another address depending on the message itself and the [mailman] -> sender_headers configuration. > Additionally, for some reason my debug.log is empty. I couldn't find any > reference from documentation nor from sample configuration files on how > to switch debugging on, is there documentation about mailman.cfg and > options I can (or should) have there? The debug information is the traceback from the 'error' log which you post above. I'm not completely sure about MM 3, but in MM 2.1 in order to write anything to a debug log, you actually have to insert the logging calls in the code. Questions about Mailman 3 are better posted to the mailman-developers at python.org list . Please join that list if you are not already a member and post there. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mjs at clemson.edu Tue Sep 29 20:06:17 2015 From: mjs at clemson.edu (Matthew Saltzman) Date: Tue, 29 Sep 2015 18:06:17 +0000 Subject: [Mailman-Users] Regexp for blocking addresses In-Reply-To: <560AC282.8010000@msapiro.net> References: <1443120469.17817.14.camel@fulkerson-math-clemson-edu> <5604496D.5030202@msapiro.net> <1443193078.8062.14.camel@gmail.com> <56056701.80808@msapiro.net> <1443200600.8062.31.camel@clemson.edu> <1443451567.459.10.camel@clemson.edu> <5609FA6F.60506@msapiro.net> <1443540267.459.52.camel@clemson.edu> <560AC282.8010000@msapiro.net> Message-ID: <1443549977.459.69.camel@clemson.edu> On Tue, 2015-09-29 at 09:55 -0700, Mark Sapiro wrote: > On 09/29/2015 08:24 AM, Matthew Saltzman wrote: > > > > Got it, thanks. I will switch to that one. Now would like to figure > > out > > how to delete all my futile attempts from the ban list. Tried > > modifying > > the ban script to remove instead of append, but I'm still doing > > something wrong. > > > > If the various list's ban_list attributes were empty to start with, > use > the following withlist script based on > > > ----------------------Cut----------------------------- > """Set the ban_list for all lists to a single address or regexp. > > Save as bin/set_banned.py > > Run via > > bin/withlist -a -r set_banned -- > > where is the actual email address or regexp > to be set as ban_list for all lists. > """ > > def set_banned(mlist, address): > if not mlist.Locked(): > mlist.Lock() > mlist.ban_list = [address] > mlist.Save() > mlist.Unlock() > ----------------------Cut----------------------------- > > If you want to remove individual regexps/addresses from all list's > ban_list, changing 'ban_list.append(address)' to > 'ban_list.remove(address)' in whatever script you were using should > work, but the value of 'address' has to be exactly what is in > ban_list > that you want to remove. > Got it. Thanks for all your help. -- Matthew Saltzman Clemson University Math Sciences mjs AT clemson DOT edu From mjs at clemson.edu Tue Sep 29 20:09:28 2015 From: mjs at clemson.edu (Matthew Saltzman) Date: Tue, 29 Sep 2015 18:09:28 +0000 Subject: [Mailman-Users] Regexp for blocking addresses In-Reply-To: <5609FA6F.60506@msapiro.net> References: <1443120469.17817.14.camel@fulkerson-math-clemson-edu> <5604496D.5030202@msapiro.net> <1443193078.8062.14.camel@gmail.com> <56056701.80808@msapiro.net> <1443200600.8062.31.camel@clemson.edu> <1443451567.459.10.camel@clemson.edu> <5609FA6F.60506@msapiro.net> Message-ID: <1443550168.459.72.camel@clemson.edu> On Mon, 2015-09-28 at 19:41 -0700, Mark Sapiro wrote: > On 09/28/2015 07:46 AM, Matthew Saltzman wrote: > > > > So I used the ban script from > > http://nigelb.me/2015-08-26-mailman-attacks.html to add regexps of > > the > > form > > > > "^\.*j\.*o\.*e\.*b\.*l\.*o\.*w \ .*+.*@gmail \.com" > > > > to the ban list. They show up in the ban_list window looking > > correct > > (without the quotes) but don't seem to be blocking the intended > > addresses. The same pattern without the \.*'s does block the > > addresses > > not containing embedded periods. > > > > Not quite sure what I'm missing or where to go here. I'd prefer not > > to > > actually hack the code in MailList.py if I can avoid it. > > > I'm not sure either because I don't know if any of that white space > is > actually there or not. > > However, this part '.*+' is absolutely wrong. The + needs a preceding > \ > or the entire RE is invalid. > > And you don't want to hack the code either because trying to keep a > list > of actual addresses is futile because there keep being more, the > permutations with '.' notwithstanding. You want either the regexp I'm > using or one of the 'safer' ones in my reply at > 4.html>. The regexp in the linked message has left parens instead of left braces, but otherwise seems to be working so far. I added it with @gmail.com and @usc.edu to be even safer (as those are the only ones I've seen to this point), but will watch for other domains for a while. Thanks! -- Matthew Saltzman Clemson University Math Sciences mjs AT clemson DOT edu From mark at msapiro.net Tue Sep 29 20:29:00 2015 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 29 Sep 2015 11:29:00 -0700 Subject: [Mailman-Users] Regexp for blocking addresses In-Reply-To: <1443550168.459.72.camel@clemson.edu> References: <1443120469.17817.14.camel@fulkerson-math-clemson-edu> <5604496D.5030202@msapiro.net> <1443193078.8062.14.camel@gmail.com> <56056701.80808@msapiro.net> <1443200600.8062.31.camel@clemson.edu> <1443451567.459.10.camel@clemson.edu> <5609FA6F.60506@msapiro.net> <1443550168.459.72.camel@clemson.edu> Message-ID: <560AD86C.4010403@msapiro.net> On 09/29/2015 11:09 AM, Matthew Saltzman wrote: > On Mon, 2015-09-28 at 19:41 -0700, Mark Sapiro wrote: >> You want either the regexp I'm >> using or one of the 'safer' ones in my reply at >> > 4.html>. > > The regexp in the linked message has left parens instead of left > braces, but otherwise seems to be working so far. I added it with > @gmail.com and @usc.edu to be even safer (as those are the only ones > I've seen to this point), but will watch for other domains for a while. My bad. A typo. They should be braces as in ^.*\+\d{3,}@ or ^.*\+\d{5,}@ -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From jaybird at bluegrasspals.com Wed Sep 30 09:00:13 2015 From: jaybird at bluegrasspals.com (Jayson Smith) Date: Wed, 30 Sep 2015 03:00:13 -0400 Subject: [Mailman-Users] list-owner getting spammed In-Reply-To: <560A76C5.2080906@bellsouth.net> References: <560A76C5.2080906@bellsouth.net> Message-ID: <560B887D.9040105@bluegrasspals.com> Hi, I was having this happen, but in my case there was a very easy way to get rid of it. Whoever set up that spam mailing list made a very big mistake. They chose to send their spam to the owner address *and* the address for posting to the list! Normally there is absolutely no valid reason for sending the same message to those two particular recipients, so I installed Milter-Greylist and set it up to block those messages at the SMTP level. Hasn't stopped the spammers, but at least my system doesn't have to process the spam. If something like this is going on in your case, that might be an option. If not, and if the spam has nothing in common, as far as I know there's nothing Mailman can do in this situation, you'll need to employ spam filtering before Mailman sees the mail. Jayson On 9/29/2015 7:32 AM, Dennis Putnam wrote: > The list-owner of one of my lists is getting spammed. Is there an easy > way to block that? TIA. > > > > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at 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/jaybird%40bluegrasspals.com From dap1 at bellsouth.net Wed Sep 30 12:55:41 2015 From: dap1 at bellsouth.net (Dennis Putnam) Date: Wed, 30 Sep 2015 06:55:41 -0400 Subject: [Mailman-Users] list-owner getting spammed In-Reply-To: <560B887D.9040105@bluegrasspals.com> References: <560A76C5.2080906@bellsouth.net> <560B887D.9040105@bluegrasspals.com> Message-ID: <560BBFAD.7080703@bellsouth.net> Hi Jason, Thanks for the reply. I am using fetchmail to retrieve each mailbox. I am familiar with spamassassin but I don't think I can integrate that with fetchmail. I'm not sure what I could use. On 9/30/2015 3:00 AM, Jayson Smith wrote: > Hi, > > I was having this happen, but in my case there was a very easy way to > get rid of it. Whoever set up that spam mailing list made a very big > mistake. They chose to send their spam to the owner address *and* the > address for posting to the list! Normally there is absolutely no valid > reason for sending the same message to those two particular > recipients, so I installed Milter-Greylist and set it up to block > those messages at the SMTP level. Hasn't stopped the spammers, but at > least my system doesn't have to process the spam. > > If something like this is going on in your case, that might be an > option. If not, and if the spam has nothing in common, as far as I > know there's nothing Mailman can do in this situation, you'll need to > employ spam filtering before Mailman sees the mail. > > Jayson > > On 9/29/2015 7:32 AM, Dennis Putnam wrote: >> The list-owner of one of my lists is getting spammed. Is there an easy >> way to block that? TIA. >> >> >> >> ------------------------------------------------------ >> Mailman-Users mailing list Mailman-Users at 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/jaybird%40bluegrasspals.com > > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at 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/dap1%40bellsouth.net > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 196 bytes Desc: OpenPGP digital signature URL: From borjariesgo at gmail.com Wed Sep 30 13:36:14 2015 From: borjariesgo at gmail.com (Borja Riesgo Juan) Date: Wed, 30 Sep 2015 13:36:14 +0200 Subject: [Mailman-Users] Fwd: BCC and bounces In-Reply-To: References: <8737yq2zw6.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: Thank you. i put something below: On 09/29/2015 07:05 AM, Borja Riesgo Juan wrote: > >* MY problem is the following. My ISP doen?st allow to send more than *>* 100 messages per hour. *>* I have a music group with 100-150 people in it. *>* I have to sent messages in the CCO field but now this is not allow in *>* my ISP and *>* the only thing they allow me to do is sending using mailman. *>* I want that the aspect of the mail are similiar to the mails that *>* have users in the CCO. *>* That's the rest for hidden the list. i don?t want they reply the *>* list, and i want them to reply to my email address. * The FAQ article at explains how to set up such a list. --> I did it. i want only two users to write to the list. how can i do for set-reply_goes_to_list? how can i do to reply to the user that write the mail? >* may change the listname-bounces at domainname ? i don?t like this. why is *>* this created? what is the aim of this address? * This address is used as the envelope sender and as the Sender: and Errors-To: header addresses to enable bounced mail to be returned to the listname-bounces address for Mailman's automated bounce processing. --> i imagine that i cannot delete it. is there any possibility? I don?t like this. i try to disable mailman's automated bounce processing and the list is still there. >* i have asked to update to a new vesion or mailman and the answer from *>* my isp is that is not allowed. the version with the isp 2.1.12. the *>* have to updte the cpanel * If you have issues with your hosting provider, there are plenty of others who offer current cPanel which includes Mailman 2.1.20. -- Mark Sapiro > The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan Un saludo Borja Riesgo borjariesgo at gmail.com 2015-09-29 16:05 GMT+02:00 Borja Riesgo Juan : > I answer: > > anonymous_list = Yes will do its best to conceal the identity of the > person who posted to the list. It makes no attempt to conceal the fact > that the message came from a list. > > > >* --> I imagine that it cannot be supress. in my case, only a few users > *>* will be able to reply. > * > > I believe you are trying to do things that Mailman is not designed to > do. If the people on your list do not know that they are on a list, How > did they get there. Did they get there by confirmed opt-in or did you > add them without their informed consent? > > In your original post, you said > > > >* To sum up, i want that the list is something that they don?t know. how can > *>* i do that? > * > > The answer is "mailman is not designed to do that". If you need to do > that, you'll have to use something else. > > MY problem is the following. My ISP doen?st allow to send more than 100 messages per hour. > I have a music group with 100-150 people in it. > I have to sent messages in the CCO field but now this is not allow in my ISP and > the only thing they allow me to do is sending using mailman. > I want that the aspect of the mail are similiar to the mails that have users in the CCO. > That's the rest for hidden the list. i don?t want they reply the list, and i want them to reply to my email address. > > may change the listname-bounces at domainname? i don?t like this. why is this created? what is the aim of this address? > > i have asked to update to a new vesion or mailman and the answer from my isp is that is not allowed. the version with the isp 2.1.12. the have to updte the cpanel > > > Best regards > > > Borja > > > > Un saludo > > Borja Riesgo > borjariesgo at gmail.com > > 2015-09-28 11:15 GMT+02:00 Borja Riesgo Juan : > >> Hello >> >> >> I restart this thread again. >> >> >> I'm coming in late here and most of this thread has been covered, but >> with respect to the above, the all-bounces at mydomain.com address is the >> list bounce processing address. Mailman sets the envelope sender and >> also the Sender: and Errors-To: headers to this value. If your users >> are seeing this address, it is probably because they are using a >> Microsoft mail client that displays something like "From: (the Sender: >> address) on behalf of (the From: address)". >> >> Since Mailman 2.1.14, if a site allows it, there is a list admin General >> Options -> include_sender_header setting which can be set to No to not >> include the Sender: header. The all-bounces at mydomain.com address will >> still be the envelope sender and in the Errors-To: header, but most >> users won't see it. >> >> --> anonymous_list to yes and first_strip_reply_to to yes. and without not success. this paramters are supposed to hide the sender and other parameters no? my version is 2.1.12. I shoyld ask to my isp to change it. >> >> (Editar *anonymous_list*) >> >> >> Also see my other reply in this thread at >> . >> >> >> --> I imagine that it cannot be supress. in my case, only a few users will be able to reply. >> >> >> Un saludo >> >> Borja Riesgo >> borjariesgo at gmail.com >> >> 2015-09-08 23:32 GMT+02:00 Peter Bossley : >> >>> But it appears as though the list posting address still winds up in the >>> CC: field even with FP turned on. It does send a message to each recipient >>> but I am wondering how one would go about removing the list address in the >>> CC: field to avoid people replying all. >>> >>> >>> -----Original Message----- >>> From: Mailman-Users [mailto:mailman-users-bounces+pete= >>> bossley.me at python.org] On Behalf Of Stephen J. Turnbull >>> Sent: Monday, September 7, 2015 8:11 AM >>> To: borjariesgo at gmail.com >>> Cc: mailman-users at python.org >>> Subject: [Mailman-Users] Fwd: BCC and bounces >>> >>> Borja Riesgo Juan writes: >>> >>> > I want the see that i send the message and they as the receivers. >>> >>> For a sufficiently recent mailman (I think that includes everything in >>> common use nowadays) in the *administrative interface* to the list in the >>> *Non-digest options* screen, you will find an option to >>> *personalize* messages. In my Mailman that is the second option from >>> the top in that screen. Set it to "Full Personalization". That should be >>> all you need to achieve what you have asked for in this post. >>> >>> Then send your messages with >>> >>> To: all at mydomain.com >>> From: borjariesgo at gmail.com (or borja at mydomain.com or ...) >>> >>> Mailman will *remove* "all at mydomain.com" and substitute each person's >>> address in To:, in a separate email for each address. Then >>> person at example.net will see >>> >>> To: "M. A. Person" >>> From: borjariesgo at gmail.com >>> >>> (only one "To" address no matter how many people are on the list). >>> >>> ------------------------------------------------------ >>> Mailman-Users mailing list Mailman-Users at 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/pete%40bossley.me >>> >> >> > From ovh at forum-pc.net Wed Sep 30 16:31:45 2015 From: ovh at forum-pc.net (=?UTF-8?Q?Camille_Olli=c3=a9?=) Date: Wed, 30 Sep 2015 16:31:45 +0200 Subject: [Mailman-Users] MM 3 : permit users to manage subscription In-Reply-To: <87k2rhdz8u.fsf@uwakimon.sk.tsukuba.ac.jp> References: <5601B5AB.6000600@forum-pc.net> <87y4fxetg6.fsf@uwakimon.sk.tsukuba.ac.jp> <56027673.4030306@forum-pc.net> <87k2rhdz8u.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <560BF251.3050604@forum-pc.net> Le 23/09/2015 15:46, Stephen J. Turnbull a ?crit : > Camille Olli? writes: > > > > How are the users trying "access accounts"? Through the web? What is > > > in the webserver log when they try to access an account? > > > > no one accessed for now. > > I don't understand, before you said they "couldn't access", now you > say they "didn't access." You need to be a lot more precise about > what your problem is, or nobody's going to be able to help you. > > Please continue the conversation on the mailing list. I myself will > have no time to participate for several days. > > > Hi, they don't have any access. I added them with the mass subscription option in the mailing list manager. -- Camille Olli? www.forum-pc.net / www.scoot-boost.com LinkedIn : http://lnkd.in/_K65k5 From stephen at xemacs.org Wed Sep 30 19:25:24 2015 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Thu, 1 Oct 2015 02:25:24 +0900 Subject: [Mailman-Users] list-owner getting spammed In-Reply-To: <560BBFAD.7080703@bellsouth.net> References: <560A76C5.2080906@bellsouth.net> <560B887D.9040105@bluegrasspals.com> <560BBFAD.7080703@bellsouth.net> Message-ID: <22028.6916.473706.321715@turnbull.sk.tsukuba.ac.jp> Dennis Putnam writes: > Thanks for the reply. I am using fetchmail to retrieve each > mailbox. I am familiar with spamassassin but I don't think I can > integrate that with fetchmail. I'm not sure what I could use. Hi, Dennis -- I use fetchmail (for personal mail), but fetchmail normally delivers to a local MDA/LDA/MTA. Specifically, it can deliver using an SMTP protocol, or it can deliver over a pipe using the --mda option. So I invoke "fetchmail --mda maildrop" (maildrop is an MDA developed by the Courier MTA/IMAP project, I think). I don't currently use maildrop's filtering capabilities, but I would suppose that to access Spamassassin I would use the "xfilter" capability of Maildrop. I've also used procmail, but the fetchmail docs recommend maildrop, so you might want to use that program. You might also find that maildrop's built-in filtering is sufficient to your purposes. The advantage of SpamAssassin is that "crowd-sources" information about past spam -- if you were lucky, you update the SA rule set and automatically get protection from the most recent spam. Steve From dap1 at bellsouth.net Wed Sep 30 20:08:55 2015 From: dap1 at bellsouth.net (Dennis Putnam) Date: Wed, 30 Sep 2015 14:08:55 -0400 Subject: [Mailman-Users] list-owner getting spammed In-Reply-To: <22028.6916.473706.321715@turnbull.sk.tsukuba.ac.jp> References: <560A76C5.2080906@bellsouth.net> <560B887D.9040105@bluegrasspals.com> <560BBFAD.7080703@bellsouth.net> <22028.6916.473706.321715@turnbull.sk.tsukuba.ac.jp> Message-ID: <560C2537.1090600@bellsouth.net> On 9/30/2015 1:25 PM, Stephen J. Turnbull wrote: > Dennis Putnam writes: > > > Thanks for the reply. I am using fetchmail to retrieve each > > mailbox. I am familiar with spamassassin but I don't think I can > > integrate that with fetchmail. I'm not sure what I could use. > > Hi, Dennis -- I use fetchmail (for personal mail), but fetchmail > normally delivers to a local MDA/LDA/MTA. Specifically, it can > deliver using an SMTP protocol, or it can deliver over a pipe using > the --mda option. So I invoke "fetchmail --mda maildrop" (maildrop is > an MDA developed by the Courier MTA/IMAP project, I think). I don't > currently use maildrop's filtering capabilities, but I would suppose > that to access Spamassassin I would use the "xfilter" capability of > Maildrop. I've also used procmail, but the fetchmail docs recommend > maildrop, so you might want to use that program. > > You might also find that maildrop's built-in filtering is sufficient > to your purposes. The advantage of SpamAssassin is that > "crowd-sources" information about past spam -- if you were lucky, you > update the SA rule set and automatically get protection from the most > recent spam. > > Steve > Hi Steve, Thanks, I'll look into it. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 196 bytes Desc: OpenPGP digital signature URL: From mark at msapiro.net Wed Sep 30 20:49:41 2015 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 30 Sep 2015 11:49:41 -0700 Subject: [Mailman-Users] Fwd: BCC and bounces In-Reply-To: References: <8737yq2zw6.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <560C2EC5.3040004@msapiro.net> On 09/30/2015 04:36 AM, Borja Riesgo Juan wrote: > Thank you. i put something below: > The FAQ article at explains how to set > up such a list. > --> I did it. i want only two users to write to the list. how can i do > for set-reply_goes_to_list? how can i do to reply to the user that > write the mail? I understood that you wanted reply_goes_to_list to be "Explicit address" and reply_to_address to be your address so that replies to list posts go to you. You may also want first_strip_reply_to = Yes This is covered in the above FAQ under "How to set an announcement list to reply to a contact address:" If you want to reply to the poster who is unauthorized, that poster should be either a moderated member of the list or a non-member. If you set Privacy options... -> Sender filters -> member_moderation_action to Reject the moderated member gets a rejection notice containing the text in member_moderation_notice. This is covered in the above FAQ under "How to restrict the list so only authorized persons can post:" For non-members, the same is accomplished with generic_nonmember_action and nonmember_rejection_notice. Posting to the list is also covered in the above FAQ. ... > This address is used as the envelope sender and as the Sender: and > Errors-To: header addresses to enable bounced mail to be returned to the > listname-bounces address for Mailman's automated bounce processing. > --> i imagine that i cannot delete it. is there any possibility? I > don?t like this. i try to disable mailman's automated bounce > processing and the list is still there. The only way to do this is by modifying the source code and your isp does not give you sufficient access to do that. Note that it was your ISP that suggested you use Mailman for this. I think that a properly configured announcement list will do most if not all of what you need. If you don't think Mailman is a viable solution because of the exposure of the listname-bounces address by some mail clients, you need to negotiate with your ISP to install a later version which allows you to suppress the Sender: header or to provide some other solution. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan