Re: [Mailman-Users] Recipient field at webui

2016-03-25 Thread Mark Sapiro
On 03/25/2016 01:30 PM, Boris Samorodov wrote: > > And there is no details link. My webui site looks the same. Should the > detailed link be enabled somewhere? The web admindb summary page has a Held Messages table. The right hand column in this table has entries like: Click on the message numbe

Re: [Mailman-Users] Recipient field at webui

2016-03-25 Thread Boris Samorodov
25.03.16 23:13, Mark Sapiro пишет: > On 03/25/2016 12:47 PM, Boris Samorodov wrote: >> >> Here is an example. Original e-mail: >> ... >> From: sen...@domain.tld >> To: recipi...@another.tld[*] >> BCC: l...@maillist.tld >> Subject: E-mail subject >> >> >> ... >> >> Here is a WEBUI: >> ... >> E-

Re: [Mailman-Users] Recipient field at webui

2016-03-25 Thread Mark Sapiro
On 03/25/2016 12:47 PM, Boris Samorodov wrote: > > Here is an example. Original e-mail: > ... > From: sen...@domain.tld > To: recipi...@another.tld[*] > BCC: l...@maillist.tld > Subject: E-mail subject > > > ... > > Here is a WEBUI: > ... > E-mail subject > Sender data here > Recipient data

Re: [Mailman-Users] Recipient field at webui

2016-03-25 Thread Boris Samorodov
25.03.16 21:34, Mark Sapiro пишет: > I don't understand. If you are asking is it possible to find out what > was in the original Bcc: list from the received message, the answer is > No except you can know from the Received: headers how it got to you, but > not to any other potential recipient. >

Re: [Mailman-Users] Recipient field at webui

2016-03-25 Thread Mark Sapiro
On 03/25/2016 10:23 AM, Boris Samorodov wrote: > > I've got a mailman-2.1.15 list which is BCC'ed by an original e-mail > message. Is it possible to get/view the original recipient at WEBUI > (along with Subject and Sender)? I don't understand. If you are asking is it possible to find out what w

Re: [Mailman-Users] Spam through my mailman?

2016-03-25 Thread Mark Sapiro
On 03/25/2016 09:17 AM, Michael Shulman wrote: > > The SPF and DKIM passes make it seem like this spam is actually being > sent from my server, not just from somewhere else with a spoofed > sender. Is there some way that my mailman may be misconfigured that > could be allowing the spammer to spa

[Mailman-Users] Recipient field at webui

2016-03-25 Thread Boris Samorodov
Hi All! I've got a mailman-2.1.15 list which is BCC'ed by an original e-mail message. Is it possible to get/view the original recipient at WEBUI (along with Subject and Sender)? Any help is appreciated. Thank you. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power

[Mailman-Users] Spam through my mailman?

2016-03-25 Thread Michael Shulman
Hi, I am receiving spam to my list-owner address that appears to be sent from the same list-owner address. Here are some of the headers, anonymized a bit (google is there because my email is forwarded to my gmail address). Received-SPF: pass (google.com: domain of mailman-boun...@my.server.com d

Re: [Mailman-Users] Mailman Web interface disappeared after upgrade to Jessie

2016-03-25 Thread Andrew Hodgson
Hi, In the upgrade to Jessie you got Apache 2.4, so you need to enable the CGI support by running a2enmod cgi then restart Apache. Hope this helps, Andrew. -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/l

Re: [Mailman-Users] Mailman Web interface disappeared after upgrade to Jessie

2016-03-25 Thread Mark Sapiro
On 03/24/2016 11:54 PM, Hedy Dargère wrote: > >>> >>> I followed your suggestions but nothing change. >>> I always have in my apache log : >>> >>> 78.xx.yyy.zzz - - [24/Mar/2016:14:17:36 +0100] "GET /listinfo HTTP/1.1" 404 >>> 504 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 >>>

Re: [Mailman-Users] Mailman Web interface disappeared after upgrade to Jessie

2016-03-25 Thread Hedy Dargère
>> >> I followed your suggestions but nothing change. >> I always have in my apache log : >> >> 78.xx.yyy.zzz - - [24/Mar/2016:14:17:36 +0100] "GET /listinfo HTTP/1.1" 404 >> 504 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 >> Firefox/45.0" > > And what is in Apache's error log a