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
** 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 i
** 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 M
** 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 Mailm
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"
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
** 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 GN
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:
** 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 Mail
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
** 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 notific
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 th
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 b
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
--
so
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 8
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)
16 matches
Mail list logo
