[Bug 500695] [NEW] Some sendmail bounces not detected

[Matt Selsky]

Public bug reported:

Some bounces from sendmail are not detected by the current bounce code.

A regression was introduced in svn commit r4486:

http://mailman.svn.sourceforge.net/viewvc/mailman/trunk/mailman/Mailman/Bouncers/SimpleMatch.py?view=diff&r1=4485&r2=4486

When ?P was changed to ?P, the code in the process()
function was not updated to match.

** Affects: mailman
 Importance: Undecided
 Status: New

-- 
Some sendmail bounces not detected
https://bugs.launchpad.net/bugs/500695
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
___
Mailman-coders mailing list
Mailman-coders@python.org
http://mail.python.org/mailman/listinfo/mailman-coders

[Bug 500695] Re: Some sendmail bounces not detected

[Matt Selsky]

** Attachment added: "sendmail bounce message not grokked by current code"
   http://launchpadlibrarian.net/37219852/sendmail_02.txt

-- 
Some sendmail bounces not detected
https://bugs.launchpad.net/bugs/500695
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
___
Mailman-coders mailing list
Mailman-coders@python.org
http://mail.python.org/mailman/listinfo/mailman-coders

[Bug 500695] Re: Some sendmail bounces not detected

[Matt Selsky]

** Attachment added: "Add test to test_bounces.py"
   http://launchpadlibrarian.net/37219843/test_bounces.patch

-- 
Some sendmail bounces not detected
https://bugs.launchpad.net/bugs/500695
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
___
Mailman-coders mailing list
Mailman-coders@python.org
http://mail.python.org/mailman/listinfo/mailman-coders

[Bug 500695] Re: Some sendmail bounces not detected

[Matt Selsky]

** Attachment added: "Update SimpleMatch bouncer to check both addr and 
fulladdr regexes"
   http://launchpadlibrarian.net/37219816/SimpleMatch.patch

-- 
Some sendmail bounces not detected
https://bugs.launchpad.net/bugs/500695
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
___
Mailman-coders mailing list
Mailman-coders@python.org
http://mail.python.org/mailman/listinfo/mailman-coders

[Bug 500695] Re: Some sendmail bounces not detected

[Matt Selsky]

Hmm, I wonder why these bounces were not caught by my 2.1.12
installation.  I'll recheck against uncaught bounces on January 1st.

In the meantime, this patch removes the useless fulladdr part of the
regex since the process function doesn't reference it.

** Attachment added: "SimpleMatch.py.patch"
   http://launchpadlibrarian.net/37237387/SimpleMatch.py.patch

-- 
Some sendmail bounces not detected
https://bugs.launchpad.net/bugs/500695
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
___
Mailman-coders mailing list
Mailman-coders@python.org
http://mail.python.org/mailman/listinfo/mailman-coders

[Bug 500952] [NEW] Extra escape characters in DOCTYPE

[Matt Selsky]

Public bug reported:

The DOCTYPE header for 2 files in the sk templates contain extra escape
characters around the quote marks.

** Affects: mailman
 Importance: Undecided
 Status: New

-- 
Extra escape characters in DOCTYPE
https://bugs.launchpad.net/bugs/500952
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
___
Mailman-coders mailing list
Mailman-coders@python.org
http://mail.python.org/mailman/listinfo/mailman-coders

[Bug 500952] Re: Extra escape characters in DOCTYPE

[Matt Selsky]

** Attachment added: "extra-escape-chars.patch"
   http://launchpadlibrarian.net/37239175/extra-escape-chars.patch

-- 
Extra escape characters in DOCTYPE
https://bugs.launchpad.net/bugs/500952
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
___
Mailman-coders mailing list
Mailman-coders@python.org
http://mail.python.org/mailman/listinfo/mailman-coders

[Bug 500955] [NEW] Templates for AST use inconsistent DOCTYPE

[Matt Selsky]

Public bug reported:

Most of the templates use a DOCTYPE of HTML 4.01 Transitional, but the
AST templates use HTML 3.2.

The patch updates the DOCTYPES for the AST templates.

** Affects: mailman
 Importance: Undecided
 Status: New

-- 
Templates for AST use inconsistent DOCTYPE
https://bugs.launchpad.net/bugs/500955
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
___
Mailman-coders mailing list
Mailman-coders@python.org
http://mail.python.org/mailman/listinfo/mailman-coders

[Bug 500955] Re: Templates for AST use inconsistent DOCTYPE

[Matt Selsky]

** Attachment added: "ast-html401.patch"
   http://launchpadlibrarian.net/37239212/ast-html401.patch

-- 
Templates for AST use inconsistent DOCTYPE
https://bugs.launchpad.net/bugs/500955
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
___
Mailman-coders mailing list
Mailman-coders@python.org
http://mail.python.org/mailman/listinfo/mailman-coders

[Bug 490602] [NEW] sourcecode/mailman/configure.in does not support group names with spaces

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

conftest.py created in sourcecode/mailman/configure.in  gets passed a
partial group name when the group name has a space, such as "domain
users".

It appears to be passed at line 382 where it is assigned to mailmangroup
and that MM_FIND_GROUP_NAME takes a list of space separated groups.

** Affects: mailman
 Importance: Undecided
 Status: New

-- 
sourcecode/mailman/configure.in does not support group names with spaces
https://bugs.edge.launchpad.net/bugs/490602
You received this bug notification because you are a member of Mailman Coders, 
which is subscribed to GNU Mailman.
___
Mailman-coders mailing list
Mailman-coders@python.org
http://mail.python.org/mailman/listinfo/mailman-coders

[Bug 490602] Re: sourcecode/mailman/configure.in does not support group names with spaces

[Curtis Hovey]

** Project changed: launchpad => mailman

** Changed in: mailman
   Status: New => Confirmed

** Changed in: mailman
   Importance: Undecided => Low

-- 
sourcecode/mailman/configure.in does not support group names with spaces
https://bugs.launchpad.net/bugs/490602
You received this bug notification because you are a member of Mailman
Coders, which is a direct subscriber.
___
Mailman-coders mailing list
Mailman-coders@python.org
http://mail.python.org/mailman/listinfo/mailman-coders

[Bug 502022] [NEW] RFE: provide option to email displayed message to email address

[Aaron Whitehouse]

Public bug reported:

Very often, I will come across a new piece of information on a topic
that has previously been discussed on the list.  I will then search
through my email accounts to try and find a copy of an email in that
thread and reply to it, so that the message is correctly archived in the
list manager etc.

Quite a lot of times, I will have deleted the relevant message.  I then
have to find it on the list, which is not a problem.  Because I don't
have a copy of the email to reply to, I can't reply to the thread and
make it come up as part of the thread.  At best, I can create a new
email and add a permalink to the original thread.  This would not,
however, allow people browsing the old thread in the archives to see the
newer information.

What would be ideal (and which I have seen implemented in other list
managers, but cannot remember where) would be if, after finding a post
in the archives, one could click a button and enter an email address to
have that message (with all thread headers etc.) emailed to that email
address again.  Then the user could simply reply to the new email to
have the threading properly maintained.

A second, related use-case is for people who aren't on the list and find
a "hanging" thread in the archives.  I often Google and find threads
that end with something like "I will provide an update on this soon"
with no following update.  It would be nice, even if I wasn't on the
mailing list, to have that one email sent to me so that I could reply
and maintain threads.

** Affects: mailman
 Importance: Undecided
 Status: New

-- 
RFE: provide option to email displayed message to email address
https://bugs.launchpad.net/bugs/502022
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
___
Mailman-coders mailing list
Mailman-coders@python.org
http://mail.python.org/mailman/listinfo/mailman-coders

Re: [Bug 502022] Re: RFE: provide option to email displayed message to email address

[Aaron Whitehouse]

Thanks Mark for the very quick and helpful response!

I hadn't realised that.  Perhaps this could be made clearer with an
identical link next to the email address saying "(reply to this
message)", or something.

I also hadn't realised that the threading was limited to single
months.  That seems a bit of a limitation to me and I hadn't realised
it.  Perhaps there are a few threads that I haven't seen the end of
for this reason and hadn't thought to look at the next month's threads
(as there were no more "next in this thread"s).  It would be excellent
if this could be kept in mind through the MM3 enhancements.  If
nothing else, having complete threads (including those in following
months) prevents threads being reopened by people finding them in the
archives.

The one use-case that the current method does not work for, and an
"email this to me" link would, is actually one that I face at the
moment: I am away (and so don't have the originals of the emails) and
am using webmail to clear my messages.  The machine is set up for
somebody else's email (the people I am staying with), so "mailto"
links don't work.  If it emailed me the message, I could reply to it
with webmail.  Probably not an uncommon use-case when so many people
are using GMail etc. instead of an email client.

Please feel free to alter the subject etc. to better fit what remains
to be enhanced.

-- 
RFE: provide option to email displayed message to email address
https://bugs.launchpad.net/bugs/502022
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
___
Mailman-coders mailing list
Mailman-coders@python.org
http://mail.python.org/mailman/listinfo/mailman-coders

[Bug 490602] Re: sourcecode/mailman/configure.in does not support group names with spaces

[Barry Warsaw]

This is not worth fixing.  Mailman 3 doesn't use the same mechanism, and
in all the years of MM2 development, this is the first such complaint
about this I've seen.  I didn't even know spaces in group names on *nix
was allowed .


** Changed in: mailman
   Status: Confirmed => Won't Fix

-- 
sourcecode/mailman/configure.in does not support group names with spaces
https://bugs.launchpad.net/bugs/490602
You received this bug notification because you are a member of Mailman
Coders, which is a direct subscriber.
___
Mailman-coders mailing list
Mailman-coders@python.org
http://mail.python.org/mailman/listinfo/mailman-coders

[Bug 265965] Re: url parse (probably) cannot handle port number

[Raphael Mankin]

In particular, all mails sent from mailman have the port number on the
end of the reply address. This causes certain mail servers to reject the
messagges.

A workaround is to have two web listeners, one on port 80 and one on the
real port e.g. 8080. One then redirects all mailman requests on port 80
to the other port. I do this because I have to have my main web server
and my mailman web server running as different users.

The problem is current in 2.1.12

-- 
url parse (probably) cannot handle port number
https://bugs.launchpad.net/bugs/265965
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
___
Mailman-coders mailing list
Mailman-coders@python.org
http://mail.python.org/mailman/listinfo/mailman-coders

[Bug 265965] Re: url parse (probably) cannot handle port number

[Mark Sapiro]

The original bug is invalid. If the site is properly configured with the
appropriate port in DEFAULT_URL_PATTERN and PUBLIC_ARCHIVE_URL in
mm_cfg.py the web interface works fine. E.g.

DEFAULT_URL_PATTERN = 'http://%s:8080/mailman
PUBLIC_ARCHIVE_URL = 'http://%(hostname)s:8080/pipermail/%(listname)s'

After making such a change in mm_cfg.py, you need to run fix_url to
update existing lists. See the FAQs at  and
.

The issue in the comment from Raphael Mankin is probably because the
list's host_name attribute has a port. It should not. This in turn
probably results from having a port appended to DEFAULT_EMAIL_HOST or
the host in an add_virtualhost() directive. This is a misconfiguration.
Note that the list's host_name is exposed and can be changed on the
list's General Options admin page.

** Changed in: mailman
   Status: New => Invalid

-- 
url parse (probably) cannot handle port number
https://bugs.launchpad.net/bugs/265965
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
___
Mailman-coders mailing list
Mailman-coders@python.org
http://mail.python.org/mailman/listinfo/mailman-coders