Mailman-Users September 2015

mailman-users@python.org

45 participants
52 discussions

Re: [Mailman-Users] Forbidden Mailman Archive

by Kevin Nowaczyk

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 <beakerboy99(a)yahoo.com> wrote: Subject: Re: [Mailman-Users] Forbidden Mailman Archive To: "Mark Sapiro" <mark(a)msapiro.net> 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 <mark(a)msapiro.net> wrote: Subject: Re: [Mailman-Users] Forbidden Mailman Archive To: mailman-users(a)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/ > <Directory /var/lib/mailman/archives/public> > Options +FollowSymLinks > Order allow,deny > Allow from all > </Directory> needs to be Alias /pipermail/ /var/lib/mailman/archives/public/ <Directory /var/lib/mailman/archives/public> Options +FollowSymLinks Require all granted </Directory> If that isn't the answer, but the issue is 403 Forbidden, what's in /var/log/apache2/lists-error.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users(a)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.c…

5 years, 7 months

Forbidden Mailman Archive

by Kevin Nowaczyk

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: <VirtualHost *:80> 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/ <Directory /var/lib/mailman/archives/public> Options +FollowSymLinks Order allow,deny Allow from all </Directory> 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/ </VirtualHost> 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

5 years, 7 months

can any one help

by Mark Tyler

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

5 years, 7 months

strange postings to non-existant lists

by Bruce Harrison

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

5 years, 7 months

Error updating mailman Ubuntu 14.04.3

by billy noah

Tried running an update today and received this message: Setting up mailman (1:2.1.16-2ubuntu0.1) ... Looking for enabled languages (this may take some time) ... done. Removing unmodified files from /etc/mailman/eu done. Directory /etc/mailman/eu not empty, not removed. *... {repeat above message for each language} ...* Removing unmodified files from /etc/mailman/sv done. Directory /etc/mailman/sv not empty, not removed. Removing unmodified files from /etc/mailman/ast done. Directory /etc/mailman/ast not empty, not removed. Installing site language en ............................................ done. Downgrade detected, from version 0x20112f1 to version 0x20110f0 This is probably not safe. Exiting. dpkg: error processing package mailman (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: mailman E: Sub-process /usr/bin/dpkg returned an error code (1) Any ideas what I can do to remedy this?

5 years, 7 months

Re: [Mailman-Users] Fwd: BCC and bounces

by Stephen J. Turnbull

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.

5 years, 7 months

Re: [Mailman-Users] Does mailman care about mail aliases? (fwd)

by Laura Creighton

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(a)python.org References: <201509060915.t869FVVP015013(a)fido.openend.se> From: Mark Sapiro <mark(a)msapiro.net> Message-ID: <55EC5BA2.8060907(a)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(a)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(a)python.org > so I can unsubscribe us from this thing? The list should send the reminder if 'webmaster(a)python.org' is a member. The header below indicates that mail is being sent from the server to <webmaster(a)python.org> 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 <webmaster(a)python.org>; 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(a)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(a)python.org from guardasmailing(a)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 <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan - ------------------------------------------------------ Mailman-Users mailing list Mailman-Users(a)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

5 years, 7 months

Does mailman care about mail aliases?

by Laura Creighton

Somebody has subscribed 'webmaster(a)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(a)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(a)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: <guardasmailing-bounces(a)guardasmunicipais.com.br> 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 <lac(a)openend.se>; 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(a)mail.python.org Received: from albatross.python.org (localhost [127.0.0.1]) by mail.python.org (Postfix) with ESMTP id 3n7hc41gWmzMyg for <webmaster(a)python.org>; 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 <webmaster(a)python.org>; 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 <guardasmailing-bounces(a)guardasmunicipais.com.br>) 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 <borgesgmc(a)gmail.com>) id 1ZYGUf-0002sy-Q9 for guardasmailing(a)guardasmunicipais.com.br; Sat, 05 Sep 2015 13:39:10 -0300 Received: by igbni9 with SMTP id ni9so33685262igb.0 for <guardasmailing(a)guardasmunicipais.com.br>; 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: <GRUPR80MB073BF334FE5BF1A0D80627BA9570(a)GRUPR80MB073.lamprd80.prod.o utlook.com> References: <BLU176-W41CD84CB5BEE070D149707FE570(a)phx.gbl> <55E9CFA3.50204(a)terra.com.br> <SNT404-EAS153DC8FA6896B2BB2D26852BD570(a)phx.gbl> <GRUPR80MB073BF334FE5BF1A0D80627BA9570(a)GRUPR80MB073.lamprd80.prod.outloo k.com> Date: Sat, 5 Sep 2015 13:39:06 -0300 Message-ID: <CAGd8gSrzvUd3tyO50Vrpmq-fCNLjKnQEO3r6MEyNsZ10owTo-w(a)mail.gmail.com> From: Eduardo Borges <borgesgmc(a)gmail.com> To: Raquel Rosan Christino Gitahy <raquel(a)unoeste.br> Subject: Re: [Guardasmailing] =?utf-8?q?Urgente=3A_Solicita=C3=A7=C3=A3o_de_In?= =?utf-8?b?Zm9ybWHDp8O1ZXM=?= X-BeenThere: guardasmailing(a)guardasmunicipais.com.br X-Mailman-Version: 2.1.20 Precedence: list List-Id: <guardasmailing.guardasmunicipais.com.br> List-Unsubscribe: <http://guardasmunicipais.com.br/mailman/options/guardasmailin g_guardasmunicipais.com.br>, <mailto:guardasmailing-request@guardasmunicipais.com.br?subject=unsubscr ibe> List-Archive: <http://guardasmunicipais.com.br/pipermail/guardasmailing_guardasm unicipais.com.br/> List-Post: <mailto:guardasmailing@guardasmunicipais.com.br> List-Help: <mailto:guardasmailing-request@guardasmunicipais.com.br?subject=help> List-Subscribe: <http://guardasmunicipais.com.br/mailman/listinfo/guardasmailing _guardasmunicipais.com.br>, <mailto:guardasmailing-request@guardasmunicipais.com.br?subject=subscrib e> Cc: Joao Werner Falk <joaofalk(a)terra.com.br>, "guardasmailing(a)guardasmunicipais.com.br" <guardasmailing(a)guardasmunicipais.com.br> Content-Type: multipart/mixed; boundary="===============0204601574603855756==" Errors-To: guardasmailing-bounces(a)guardasmunicipais.com.br Sender: "Guardasmailing" <guardasmailing-bounces(a)guardasmunicipais.com.br> 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

5 years, 7 months

All confirmation emails going to SPAM on gmail

by Nitin Sharma

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#… 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+<vars>@domain , and this changes every time. Is there a way to make this consistent? Thanks Nitin

5 years, 7 months

creating a htdig global search

by Jason Fayre

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.

5 years, 7 months