[Mailman-Users] Mailman 2.1.12 and issues with TLS 1.2 and DMARC

Hello I wonder if you can help. My organisation represents and supports GPs across most of London. We have elected representatives and we use Mailman mailing lists to provide listservers to elected representatives. We currently use version 2.1.12 (http://lists.lmc.org.uk/mailman/admin) but I

Re: [Mailman-Users] Mailman 2.1.12 confirm.py works fine with http but does not work with https

On 11/5/19 8:02 AM, jimw...@attglobal.net wrote: > > To make my website more secure, my website is configured to only work > with https and not with http. > > Please let me know how I can use confirm.py with https. > > confirm.py works fine with http, but not with https. As I said in a prior r

[Mailman-Users] Mailman 2.1.12 confirm.py works fine with http but does not work with https

Hi, I have mailman 2.1.12 installed on Centos 6.5 using Apache 2.2.15 and python 2.6.6. The mailman web page "Confirm Subscription Request" generated by confirm.py works fine with http, but does not work with https. Please let me know if there is a modification that I can make for confirm.

Re: [Mailman-Users] Mailman 2.1.12

Frank Murphy wrote: > >looking through the Admin Interface. >I'm trying to work out where >to place following: > >Subject must contain: "from" (the word) In Privacy opyions... -> Spam filters -> header_filter_rules use a regexp along the lines of ^Subject:.*\Wfrom\W with an action of Accept fol

[Mailman-Users] Mailman 2.1.12

Mailman 2.1.12 New to Mailman, and indeed python. looking through the Admin Interface. I'm trying to work out where to place following: Subject must contain: "from" (the word) Mail Body must contain: "Reporter: @ (word Reporter: + @ symbol) Even http://wiki.list.org/display/DOC/3+List+administ

Re: [Mailman-Users] Mailman 2.1.12 can't accept email fromThunerbird3.1.4 help!

Mark Sapiro-3 wrote: > > wilby wrote: >>> >>> The message is sent back to me (and only to me). >>> It starts with the rejection message under "privacy Options", "rejection >>> to moderated members". >>> >>> Then it presents me with a .eml file that contains me original message >>> to >>> MM.

Re: [Mailman-Users] Mailman 2.1.12 can't accept email fromThunerbird3.1.4 help!

wilby wrote: >> >> The message is sent back to me (and only to me). >> It starts with the rejection message under "privacy Options", "rejection >> to moderated members". >> >> Then it presents me with a .eml file that contains me original message to >> MM. >> >> At the end is an attachment of m

Re: [Mailman-Users] Mailman 2.1.12 can't accept email from Thunerbird3.1.4 help!

Mark Sapiro-3 wrote: > > wilby wrote: >> >>For some reason a very recent update to Thunderbird 3.1.4 email has suddenly >>stopped the Mailman 2.1.12 account, that I administer, from accepting my >>messages. > > > Exactly what happens when you send a post from T-bird. If it bounces or > if Mai

Re: [Mailman-Users] Mailman 2.1.12 can't accept email from Thunerbird3.1.4 help!

wilby wrote: > >For some reason a very recent update to Thunderbird 3.1.4 email has suddenly >stopped the Mailman 2.1.12 account, that I administer, from accepting my >messages. Exactly what happens when you send a post from T-bird. If it bounces or if Mailman rejects it, what does the bounce/rej

[Mailman-Users] Mailman 2.1.12 can't accept email from Thunerbird 3.1.4 help!

For some reason a very recent update to Thunderbird 3.1.4 email has suddenly stopped the Mailman 2.1.12 account, that I administer, from accepting my messages. I can send to this Mailman account from non-Tbird email software. Help needed badly. Thanks, Wilby -- View this message in context:

Re: [Mailman-Users] Mailman 2.1.12 and htDig integration patches

* Hank van Cleef : > I'm wondering what is the situation with Mailman 2.1.12 integration > with the htDig search engine. In the past, I've relied on Richard > Barrett's excellent support at openinfo.co.uk and have a 2.1.11 build > with his patches. However, I don't see anything listed there for >

[Mailman-Users] Mailman 2.1.12 and htDig integration patches

I'm wondering what is the situation with Mailman 2.1.12 integration with the htDig search engine. In the past, I've relied on Richard Barrett's excellent support at openinfo.co.uk and have a 2.1.11 build with his patches. However, I don't see anything listed there for 2.1.12. While I can work

Re: [Mailman-Users] Mailman 2.1.12 - Python 2.4.[456]incompatibility

Barry Finkel wrote: > >My Python version is 2.4.3, and I ran a modified conftest.py program >from the configure script to determine that the email package is 3.0.1. >I could not determine the package version number from looking at the >.py modules in /usr/lib/python2.4/email on my Ubuntu Mailman m

Re: [Mailman-Users] Mailman 2.1.12 - Python 2.4.[456]incompatibility

I wrote, in part: >>Or do I have to specify something to get the Mailman-supplied >>e-mail package untarred? Thanks. and Mark Sapiro replied: >That would be another approach. After running ./configure and before >running any make commands, you could edit misc/Makefile to replace the >line > >

Re: [Mailman-Users] Mailman 2.1.12 - Python 2.4.[456]incompatibility

Barry Finkel wrote: >On Mon, 16 Mar 2009 10:52:05 Mark Sapiro wrote: > >>There is an internal inconsistency in the 3.0.2 email package that >>shipped with Python 2.4.4 through 2.4.6. This has to do with the >>Charset.Charset() constructor setting input_charset to a unicode which >>then causes Type

Re: [Mailman-Users] Mailman 2.1.12 - Python 2.4.[456] incompatibility

On Mon, 16 Mar 2009 10:52:05 Mark Sapiro wrote: >There is an internal inconsistency in the 3.0.2 email package that >shipped with Python 2.4.4 through 2.4.6. This has to do with the >Charset.Charset() constructor setting input_charset to a unicode which >then causes TypeError: decoding Unicode is

[Mailman-Users] Mailman 2.1.12 - Python 2.4.[456] incompatibility

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 There is an internal inconsistency in the 3.0.2 email package that shipped with Python 2.4.4 through 2.4.6. This has to do with the Charset.Charset() constructor setting input_charset to a unicode which then causes TypeError: decoding Unicode is not su

Re: [Mailman-Users] Mailman 2.1.12 final released.

A HUGE THANK YOU! On 23 Feb 2009 at 15:25, Mark Sapiro wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > I am happy to announce the final release of Mailman 2.1.12. > > Since 2.1.12rc2 there have been a few bug fixes, the Polish > translation has been updated and a couple of

Re: [Mailman-Users] Mailman 2.1.12 final released.

S/U/N wrote: >Champagne! > >* > * >* * [] > _**_ || >|*||*| |* | >|_||_| |__| >\*/\*/ | *| >_|__|_ |__| > Merci! -- Mark Sapiro The high

Re: [Mailman-Users] Mailman 2.1.12 final released.

S/U/N wrote: Champagne! I prefer Château d'Yquem. Vintage 1811, SVP. -- Brad Knowles If you like Jazz/R&B guitar, check out LinkedIn Profile: my friend bigsbytracks on YouTube at http://preview.tinyurl.com/bigsbytracks --

Re: [Mailman-Users] Mailman 2.1.12 final released.

Champagne! * * * * [] _**_ || |*||*| |* | |_||_| |__| \*/\*/ | *| _|__|_ |__| Mark Sapiro a écrit : > I am happy to announce the final relea

[Mailman-Users] Mailman 2.1.12 final released.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I am happy to announce the final release of Mailman 2.1.12. Since 2.1.12rc2 there have been a few bug fixes, the Polish translation has been updated and a couple of items have been added to the contrib directory. Mailman 2.1.12 is a minor bug fix and