[Mailman-Users] utf-8 subjects; extended "." regexp really necessary?

[Stephen J. Turnbull]

Adrian Pepper writes:
 > (Mailman 2.1.12, some local mods, but not around topics...)
 > 
 >  I had a utf-8 subject I was having difficulty matching with a topic regexp.
 > 
 >  Eventually I concluded the subject still had newlines in it when it was
 >  matched against the regexp.  (That is the continuation lines were not
 >  joined before matching).  And "." would not match the newline character(s)).

 >  Am I correct in my conclusion that .* won't match newline characters,
 >  but  will ?
 >  (And also, that that is the character class I created).

Yes.  Here are the docs for Python regular expressions as used in
Mailman: https://docs.python.org/2.7/library/re.html.

In general this problem would be addressed with the DOTALL flag:

The special characters are:

'.'
(Dot.) In the default mode, this matches any character except a
newline. If the DOTALL flag has been specified, this matches any
character including a newline.

Note that the definition of "newline" here is exactly "\n".

However, in your case I think there's a simpler method.

 >  For production I might need to put [\s\S\n\r]* between every pair of
 >  characters after a reasonable point in the expression.  Unless I can
 >  enumerate the possibilities more precisely.  (Which will probably
 >  result in an even longer looking character class).

Well, actually what you need is just "\s*" (or perhaps "\s+" or
"(\s|_)+") wherever a space might occur in the topic regexp, I think.
Line folding can only occur at whitespace (breaking this rule would be
noticed by everybody, and so is not likely to go unfixed), and "\s"
already includes "\n".

 >  Empirically I see  ?=\n =?utf-8?q?_ after "Weekly" and before "Ac".
 >  (And it seems the matching is done on the incoming subject, not the
 >  one formatted for resending, which, with my tag, and the utf-8
 >  of an incoming tag pushes the expression entirely onto the second
 >  line where I think the ".*" variant (or even [_ ]) would match.

That would explain your observations, but I am not familiar with the
topic code.  I don't have time to address that until the weekend, and
maybe not then as $DAYJOB is piling up work on me, and Mark is on
vacation in Croatia, so you may have to wait a bit for a final answer
on that.  I'm sorry about that, but I think at least for now the "\s*"
bandaid will get you most of the way to where you want to go.

--
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] utf-8 subjects; extended "." regexp really necessary?

[Adrian Pepper]

(Mailman 2.1.12, some local mods, but not around topics...)

 I had a utf-8 subject I was having difficulty matching with a topic regexp.

 Eventually I concluded the subject still had newlines in it when it was
 matched against the regexp.  (That is the continuation lines were not
 joined before matching).  And "." would not match the newline character(s)).

 So, for test purposes...

 Farmers[_ ]Weekly[\s\S\n\r]*Ac

 seemed to match my particular test subject.

 While the following did not.

 Farmers[_ ]Weekly.*Ac

 Am I correct in my conclusion that .* won't match newline characters,
 but  will ?
 (And also, that that is the character class I created).

 For production I might need to put [\s\S\n\r]* between every pair of
 characters after a reasonable point in the expression.  Unless I can
 enumerate the possibilities more precisely.  (Which will probably
 result in an even longer looking character class).

 Empirically I see  ?=\n =?utf-8?q?_ after "Weekly" and before "Ac".
 (And it seems the matching is done on the incoming subject, not the
 one formatted for resending, which, with my tag, and the utf-8
 of an incoming tag pushes the expression entirely onto the second
 line where I think the ".*" variant (or even [_ ]) would match.

 More generally, my question applies to any potentially long subject,
 but utf-8 subjects seem to get longer more easily.

 There is no header-equivalent line in the body (it's mime anyway).


Adrian Pepper

--
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] Installing Mailman

[Stephen J. Turnbull]

Dave Arndt writes:

 > Then... would the install and the "basics" be that different?

In a word ... "yes".  Mailman 2 is a monolithic system, with a fair
amount of attention given to "pluggability" of many features.
However, in practice, the vast majority of Mailman 2 systems just use
the default, bundled implementations of things like the archiver.

In Mailman 3, the mail reception and distribution system is one
subproject (dubbed "core"), the archiver ("HyperKitty") is another
subproject, and the web application ("Postorius") that users and list
owners use to configure their accounts and lists yet a third.  The
members overlap somewhat, but really, these are separate projects in
practice.  This isn't a problem for interoperability because the
design is good, but it does mean that installation questions have to
be directed to the right subgroup.  Pretty good progress has been made
on installing all subprojects as a bundle [1], but it's not anywhere
near as easy as "apt-get install mailman3" yet.

 > I had tried installing a different version of Mailman earlier (2)
 > and had the same issues I'm having now.

Ah, in that case maybe your issue is not in Mailman, but rather in
your system.  Then the generic experience with various OSes and MTAs
might be valuable to you.

Exactly what steps did you take to install Mailman 3 on your Centos
host?

FWIW, this:

 >>> http://domain.com/mailman/listinfo

 >>> I receive a "500 Internal Server Error".

looks like an Apache error rather than a Postorius error to me.  That
suggests that Apache is not configured to delegate to Postorius, or
perhaps Postorius isn't installed at all.  AFAICS, the typical install
instructions[1] have you set up Postorius and HyperKitty as standalone
Django apps (not recommended for production, and the instructions are
often not very specific about how to integrate these apps with "real"
webservers).

Footnotes: 
[1]  Eg, http://mailman-bundler.readthedocs.org/en/latest/.

--
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] Installing Mailman

[Dave Arndt]

On Tue, Nov 24, 2015 at 12:41 PM, Stephen J. Turnbull 
wrote:

> Dave Arndt writes:
>
>  > So this list is version specific?  I though it was a mailman users
>  > list (in general).
>
> No, and yes.  People are welcome to discuss Mailman 3 here.  But
> Mailman 3 is not yet widely deployed, so there is little experience
> with it on this list.  Eventually Mailman 3 will be user-supported...
>

Then... would the install and the "basics" be that different?

I had tried installing a different version of Mailman earlier (2) and had
the same issues I'm having now.
--
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] Installing Mailman

[Stephen J. Turnbull]

Dave Arndt writes:

 > So this list is version specific?  I though it was a mailman users
 > list (in general).

No, and yes.  People are welcome to discuss Mailman 3 here.  But
Mailman 3 is not yet widely deployed, so there is little experience
with it on this list.  Eventually Mailman 3 will be user-supported, as
Mailman 2 is, but for now almost all expertise is in the developers,
and they don't hang out here (with the exception of myself and Mark,
and neither of us has global knowledge of Mailman 3).  So Mark is
saying, if you've got a specific question, you're *welcome* to ask the
developers directly.  Or you can ask here and hope to get lucky. ;-)

--
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] spam coming through a moderated list after a shunt

[Mark Sapiro]

Mark Sapiro wrote:

> 1) The skipping of the handler throwing the exception upon unshunting
> seems to be a bug.


This bug has been reported at
 and a fix committed
for the next release.

-- 
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] Installing Mailman

[Dave Arndt]

On Tue, Nov 24, 2015 at 2:59 AM, Mark Sapiro  wrote:

> On 11/23/15 1:34 PM, Dave Arndt wrote:
> > I'm trying to install Mailman 3.0 on CentOS 7.1
>
>
> Questions about Mailman 3 and particularly Postorius and Hyperkitty are
> better posted to the mailman-develop...@python.org list
> . Please
> join that list if you are not already a member and post there.
>
> The people working most closely with MM 3 are much more likely to read
> your post on mailman-developers. We will soon have a
> mailman3-us...@mailman3.org list (running on MM 3 of course), but there
> are still infrastructure issues to work out before that list will be
> operational.
>
>
So this list is version specific?  I though it was a mailman users list (in
general).

Thanks for the info.  I'll look elsewhere.

- da
--
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] Problem pgp signed messages

[Stephen J. Turnbull]

Mark Sapiro writes:

 > Perhaps the sigs being stripped are another protocol, e.g.
 > application/pkcs7-signature or ??

That was the first thing that occurred to me, although I was thinking
S-MIME.

--
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] Installing Mailman

[Mark Sapiro]

On 11/23/15 1:34 PM, Dave Arndt wrote:
> I'm trying to install Mailman 3.0 on CentOS 7.1


Questions about Mailman 3 and particularly Postorius and Hyperkitty are
better posted to the mailman-develop...@python.org list
. Please
join that list if you are not already a member and post there.

The people working most closely with MM 3 are much more likely to read
your post on mailman-developers. We will soon have a
mailman3-us...@mailman3.org list (running on MM 3 of course), but there
are still infrastructure issues to work out before that list will be
operational.


> checking Mailman status, it shows that its "running".
> 
> To test the installation, I'm trying to access
> 
> http://domain.com/mailman/listinfo
> 
> I receive a "500 Internal Server Error".
> 
> How do I determine what's wrong?  Which logs should I look at?


/var/log/http/error_log or whatever the relevant Apache error log is on
your server. Also possibly Mailman's Error log.


> Where can I find truly comprehensive documentation?  All the installation
> docs  I've found online seem to be just a little bit different - and none
> of them provide insight on troubleshooting problems like the one above.


MM 3 docs are at 

-- 
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