[Mailman-Users] mailman 3 and freeipa

2019-03-18 Thread Stephen J. Turnbull 
Crossposting and redirecting replies to mailman-us...@mailman3.org.

Steven Jones writes:

 > I cant find anything on this so far but can Mailman3's webui use
 > freeipa as the authentication mechanism?

Hi Steve,

I don't have a complete answer offhand (and right now I'm just
reducing my inbox so a single google search is as much as I can do),
but searching for "freeipa django" indicates that there are
"connectors" for Django and FreeIPA.  The nicest option would be a
plugin for Django's socialauth application.

If that doesn't seem to exist, perhaps you can just add a FreeIPA
application to the Django configuration.  You would need to add it to
both Postorius and HyperKitty configurations.

Steve


-- 
Associate Professor  Division of Policy and Planning Science
http://turnbull.sk.tsukuba.ac.jp/ Faculty of Systems and Information
Email: turnb...@sk.tsukuba.ac.jp   University of Tsukuba
Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Fwd: Uncaught runner exception

2019-03-18 Thread Lothar Schilling 

Mit herzlichem Dank und freundlichen Grüßen!

Lothar Schilling

Förderverein Pro Asyl e.V.
Postfach 160624
60069 Frankfurt
Tel. 069 242314-40

Am 15.03.2019 um 17:25 schrieb Mark Sapiro:
> On 3/15/19 4:27 AM, Lothar Schilling wrote:
>> Am 14.03.2019 um 18:55 schrieb Mark Sapiro:
>>> On 3/14/19 2:39 AM, Lothar Schilling wrote:
> ...
 string
 
> ...
>> Sadly not:
>>
>> import string
>> string.lowercase
>>     'abcdefghijklmnopqrstuvwxyz'
>> string  
>>     
>
> This is interesting. Here you get 
> and before (above) you got  '/usr/lib64/python2.6/string.pyc'>.
>
> I wonder why the difference.
>
> In the message at
> 
> I suggested this patch
>
> === modified file 'Mailman/Archiver/pipermail.py'
> --- Mailman/Archiver/pipermail.py 2018-05-03 21:23:47 +
> +++ Mailman/Archiver/pipermail.py 2019-03-02 04:51:23 +
> @@ -60,9 +60,12 @@
>  else:
>  # Mixed case; assume that small parts of the last name will be
>  # in lowercase, and check them against the list.
> -while i>0 and (L[i-1][0] in lowercase or
> -   L[i-1].lower() in smallNameParts):
> -i = i - 1
> +try:
> +while i>0 and (L[i-1][0] in lowercase or
> +   L[i-1].lower() in smallNameParts):
> +i = i - 1
> +except:
> +syslog('error', 'Exception in fixAuthor: %s', author)
>  author = SPACE.join(L[-1:] + L[i:-1]) + ', ' + SPACE.join(L[:i])
>  return author
>
>
>
> I assume you still have that installed. In any case, if you add a second
> syslog line after the first
>
> syslog('error', 'lowercase value: %r', lowercase)
>
> What do you then get in Mailman's error log
>
>

Exception in fixAuthor: D▒rthe Hinz - Fl▒chtlingsrat Nds.
Mar 18 08:33:51 2019 (23745) lowercase value:
'abcdefghijklmnopqrstuvwxyz\xb5\xdf\xe0\xe1\xe2\xe3\xe4\xe5\xe6\xe7\xe8\xe9\xea\xeb\xec\xed\xee\xef\xf0\xf1\xf2\xf3\xf4\xf5\xf6\xf8\xf9\xfa\xfb\xfc\xfd\xfe\xff'
Mar 18 10:06:50 2019 (23745) Exception in fixAuthor: Philipp Millius
(Fl▒chtlingsrat THR e.V.)
Mar 18 10:06:50 2019 (23745) lowercase value:
'abcdefghijklmnopqrstuvwxyz\xb5\xdf\xe0\xe1\xe2\xe3\xe4\xe5\xe6\xe7\xe8\xe9\xea\xeb\xec\xed\xee\xef\xf0\xf1\xf2\xf3\xf4\xf5\xf6\xf8\xf9\xfa\xfb\xfc\xfd\xfe\xff'
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Delivery errors and spam grading

2019-03-18 Thread Davide Marchi 

Hi Friends,

I have a few doubts, I write you in the hope of a hint.
For Mailman 2.1.23 on Debian Stretch:

1) How is it possible from Mailman monitor the delivery errors? Only 
sysadmin mail server from the logs?
2) Is it possible avoid spam grading, increasing the number of sending 
sessions/decreasing individual emails sent per session? And eventually 
your hint? :-)





Many thanks!

Davide




--
cosmogoniA
n o p r o v a r e n o f a r e o n o n f a r e n o n c e p r o v a r e

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Delivery errors and spam grading

2019-03-18 Thread David Gibbs via Mailman-Users 

On 3/18/2019 4:51 AM, Davide Marchi wrote:
1) How is it possible from Mailman monitor the delivery errors? Only 
sysadmin mail server from the logs?


This is what VERP deliveries are for. The FROM address is tagged so that 
bounces can be clearly identified.

https://wiki.list.org/DOC/So%20what%20is%20this%20VERP%20stuff

david



--
IBM i on Power Systems: For when you can't afford to be out of business!

I'm riding 615 miles (Yes, you read that right) 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 https://mideml.diabetessucks.net.

You can see where my donations come from by visiting my interactive donation 
map ... https://mideml.diabetessucks.net/map (it's a geeky thing).

I may have diabetes, but diabetes doesn't have me!
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Delivery errors and spam grading

2019-03-18 Thread Stephen J. Turnbull 
Davide Marchi writes:

 > 1) How is it possible from Mailman monitor the delivery errors? Only 
 > sysadmin mail server from the logs?

That depends on what you mean by "monitor" and "delivery errors".  If
you mean mail refused by some system (typically the final recipient)
and returned to Mailman, that is what we call "bounces".  Mailman can
be configured on the [Bounce processing] screen to send mail to the
list owner (only, not moderators or the site administrator) four types
of notifications about bounces.  The default is usually appropriate.

In some cases recipient systems don't identify the bounced recipient.
In that case you can use VERP as described below, which arranges that
Mailman receives all bounces in such a way that the recipient can be
identified (a special-purpose return address is allocated per
recipient).

There is no web-based monitor in Mailman 2.  These notifications are
sent by email to the list owner.  However, if your email provider uses
a web-based manager like cPanel, you may have some access to this
information (I don't use cPanel, so I don't know what features it
provides for monitoring system health).

If you mean any other kind of delivery failure that is detected by the
Mailman host, but is not returned to Mailman, then it is simply
impossible for Mailman to even be aware of them, and you would have to
check the MTA (mail server) logs.  And of course there are delivery
errors that happen and never are returned to the Mailman host at all
(you find out about these because subscribers tell you).  There's
nothing that can be done about those by Mailman, either.

 > 2) Is it possible avoid spam grading

You should set DMARC Moderation Action to Munge From in the [Privacy
options -- Sender filters] screen.  (Strictly speaking this isn't spam
filtering, it's mitigating breakage induced by incompetent email
providers.)  And of course you should filter incoming mail for spam
(and if you have any human users besides root on the Mailman host,
outgoing mail too -- this is why it's a good idea to have a dedicated
host for Mailman!)  The MTA should be set up to use DKIM and SPF.

 > increasing the number of sending sessions/decreasing individual
 > emails sent per session?

It's not obvious to me that this is very useful: most of the big
providers count the number of times a message is received by any
method.  They don't care if you do it one at a time (although they may
shut you down before any mail is delivered if they are counting the
recipients per session).  The usual reason for throttling is because
Mailman's provider doesn't like accepting huge numbers of addressees
from Mailman, not because you have tons of subscribers at one
provider.

Only very crudely, in a site-wide way or very drastically per-list.
The site-wide option works with Mailman's internal "SMTPDirect"
DELIVERY_MODULE (which is the default).  Set SMTP_MAX_RCPTS to some
"reasonable" figure in mm_cfg.py.  This applies to all outgoing
connections.

Alternatively, you can set VERP_INTERVAL=1 in mm_cfg.py, which ensures
that every message is a one-subscriber-per-SMTP-session sitewide, or
for each list you can enable Personalization in the [Non-digest
options] which has the same effect for one list.  (You probably should
also disable the Digestable option in [Digest options].

Steve

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Fwd: Uncaught runner exception

2019-03-18 Thread Mark Sapiro 
On 3/18/19 2:29 AM, Lothar Schilling wrote:
> 
> Exception in fixAuthor: D▒rthe Hinz - Fl▒chtlingsrat Nds.
> Mar 18 08:33:51 2019 (23745) lowercase value:
> 'abcdefghijklmnopqrstuvwxyz\xb5\xdf\xe0\xe1\xe2\xe3\xe4\xe5\xe6\xe7\xe8\xe9\xea\xeb\xec\xed\xee\xef\xf0\xf1\xf2\xf3\xf4\xf5\xf6\xf8\xf9\xfa\xfb\xfc\xfd\xfe\xff'
> Mar 18 10:06:50 2019 (23745) Exception in fixAuthor: Philipp Millius
> (Fl▒chtlingsrat THR e.V.)
> Mar 18 10:06:50 2019 (23745) lowercase value:
> 'abcdefghijklmnopqrstuvwxyz\xb5\xdf\xe0\xe1\xe2\xe3\xe4\xe5\xe6\xe7\xe8\xe9\xea\xeb\xec\xed\xee\xef\xf0\xf1\xf2\xf3\xf4\xf5\xf6\xf8\xf9\xfa\xfb\xfc\xfd\xfe\xff'


which is iso-8859-1 encoding of
'abcdefghijklmnopqrstuvwxyzµßàáâãäåæçèéêëìíîïðñòóôõöøùúûüýþÿ' and which
is the problem.

I don't know why in testing string.lowercase does not return the above
string, but in the Python that's running ArchRunner, and presumably the
rest of mailman, string.lowercase has that value. This is what needs to
be fixed. The first step is possibly to do

locate string.py

And then look at all the ones you find to see which defines lowercase
that way and then figure out why the Python that runs Mailman uses that
one rather that the ones you see in testing.

Also,

which -a python

may help find things.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Delivery errors and spam grading

2019-03-18 Thread Mark Sapiro 
On 3/18/19 5:39 AM, Stephen J. Turnbull wrote:
> 
> If you mean any other kind of delivery failure that is detected by the
> Mailman host, but is not returned to Mailman, then it is simply
> impossible for Mailman to even be aware of them, and you would have to
> check the MTA (mail server) logs.


However errors that occur during SMTP from Mailman to the outgoing MTA
are returned to Mailman. Mailman sees the SMTP status return and if it
is a 5xx status, scores that as a bounce and if it is a 4xx status
retries sending the message to the failed recipient(s) at configurable
intervals for a configurable time.

The retry interval is DELIVERY_RETRY_WAIT with a default of one hour,
but in MM 2.1.23, DELIVERY_RETRY_WAIT is ignored and the interval is 15
minutes.

The duration of retries is DELIVERY_RETRY_PERIOD with a default of 5
days, after which Mailman gives up without scoring a bounce.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Delivery errors and spam grading

2019-03-18 Thread Jim Dory 
On Mon, Mar 18, 2019 at 4:39 AM Stephen J. Turnbull <
turnbull.stephen...@u.tsukuba.ac.jp> wrote:

>
>   (You probably should
> also disable the Digestable option in [Digest options]
>

I'm also receiving several bounces back for errors such as:
 "SMTP error from remote mail server after end of data:
554 Failed: Malformed MIME field: X-Ham-Report:"

Or:
 "SMTP error from remote mail server after end of data:
554 5.7.1 [P4] Message blocked due to spam content in the message."

Mostly associated with the digest. Curious about the statement  above from
Steve: is disabling the digest option something people do regularly to
prevent issues like this? and if so - if I were to disable it now, what
happens to those members who are using that option? I assume they just
start automatically receiving non-digest messages, but figured I should ask.

thanks, JD
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Delivery errors and spam grading

2019-03-18 Thread Barry S. Finkel 

On 3/18/2019 8:44 PM, Jim Dory wrote:

On Mon, Mar 18, 2019 at 4:39 AM Stephen J. Turnbull <
turnbull.stephen...@u.tsukuba.ac.jp> wrote:



   (You probably should
also disable the Digestable option in [Digest options]



I'm also receiving several bounces back for errors such as:
  "SMTP error from remote mail server after end of data:
 554 Failed: Malformed MIME field: X-Ham-Report:"

Or:
  "SMTP error from remote mail server after end of data:
 554 5.7.1 [P4] Message blocked due to spam content in the message."

Mostly associated with the digest. Curious about the statement  above from
Steve: is disabling the digest option something people do regularly to
prevent issues like this? and if so - if I were to disable it now, what
happens to those members who are using that option? I assume they just
start automatically receiving non-digest messages, but figured I should ask.

thanks, JD


The second "error" message is one over which you have little control.
The recipient's mail system detected content in the digest that it
considered spam.  I assume that if the messages in the digest had been
sent individually in non-digest mode, then the message that had the
objectionable content would have been similarly flagged.

As for the first "error" - A quick Google search showed that the

 X-Ham-Report:

header line is written by Cpanel when it detects that the message is
not spam.  I do not know if any other software writes this line.
I am not an expert in MIME, but I do not see how any "X-" header
line could be treated as a malformed MIME header.

If you have users who are using digest mode, then removing that option
will cause consternation with those users.  And I doubt that the digest
mode has anything to do with this error message.

--Barry Finkel

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Delivery errors and spam grading

2019-03-18 Thread Mark Sapiro 
On 3/18/19 6:44 PM, Jim Dory wrote:
> On Mon, Mar 18, 2019 at 4:39 AM Stephen J. Turnbull <
> turnbull.stephen...@u.tsukuba.ac.jp> wrote:
> 
>>
>>   (You probably should
>> also disable the Digestable option in [Digest options]
>>
> 
> I'm also receiving several bounces back for errors such as:
>  "SMTP error from remote mail server after end of data:
> 554 Failed: Malformed MIME field: X-Ham-Report:"


Does your outgoing MTA add an X-Ham-Report: header? Perhaps it does so
in a non-compliant way.


> Or:
>  "SMTP error from remote mail server after end of data:
> 554 5.7.1 [P4] Message blocked due to spam content in the message."


This one you can't do much about. The recipient thinks it's spammy, but
you'll never know why without a lot of trial and error.

If your problems are mostly with digests, you can subscribe yourself (at
alternate addresses) to both MIME and plain digests and then when you're
looking at a bounce, at least you'll have your copy of the message that
was sent for analysis.


> Mostly associated with the digest. Curious about the statement  above from
> Steve: is disabling the digest option something people do regularly to
> prevent issues like this? and if so - if I were to disable it now, what
> happens to those members who are using that option? I assume they just
> start automatically receiving non-digest messages, but figured I should ask.


Good thing you asked, although if you set digestable to No, at that
point and on every web admin access after you will get a big, bold

Warning: You have digest members, but digests are turned off. Those
people will not receive mail. Affected member(s) [list of digest members]

You will need to set those members to non-digest either manually or via
a script like 
-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Delivery errors and spam grading

2019-03-18 Thread Jim Dory 
On Mon, Mar 18, 2019 at 6:19 PM Mark Sapiro  wrote:

>
> Does your outgoing MTA add an X-Ham-Report: header? Perhaps it does so
> in a non-compliant way.
>
>
> > is disabling the digest option something people do regularly to
> > prevent issues like this? and if so - if I were to disable it now, what
> > happens to those members who are using that option?
>
> Good thing you asked, although if you set digestable to No, at that
> point and on every web admin access after you will get a big, bold
>
> Warning: You have digest members, but digests are turned off. Those
> people will not receive mail. Affected member(s) [list of digest members]
>
> You will need to set those members to non-digest either manually or via
> a script like 
> --
>
>
Thanks very much Mark and Barry. I'll look into the errors further on my
own. Don't know that much about this stuff.. I'm on a VPS with root
access.. it uses Exim and Apache SpamAssassin. I can log in via WHM or
CPanel. So I'll poke around. Things were pretty quiet for awhile, but our
VPS was just migrated to another server by our host, so I think a few
things may have gotten changed.

As for disabling Digest, I have a fair number of users that would probably
be upset. Just tonight at a social event in town, one user mentioned our
mailing list (comparing it to a local facebook group) saying how he enjoyed
having the digest so it didn't ping his phone for every message rolling in.
(Some of us know how to filter that, but most users may not). So I probably
will not disable it.

/jim
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org