Public bug reported:
Setting localhost in postfix_lmtp works against Postfix defaults and
breaks delivery.
Reason: The Postfix lmtp client only uses dns queries by default to
search for hostnames. If the DNS server does not provide an answer for
"localhost" delivery from the lmtp client to mailman fails.
Solution: Provide "127.0.0.1" instead of "localhost". This does not
require DNS and is even faster because it saves DNS lookups.
Example:
hey2(a)mailman.state-of-mind.de
lmtp:[localhost.localdomain]:8024
** Affects: mailman
Importance: Undecided
Status: New
** Tags: 3.0 mailman
--
setting localhost in postfix_lmtp breaks delivery
https://bugs.launchpad.net/bugs/544477
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
Public bug reported:
Collapsing multipart/alternative parts to just the first alternative
only works if the message itself is multipart/alternative, or the
multipart/alternative part is at the first sub-level.
For example, given this structure:
multipart/mixed
| multipart/related
| | multipart/alternative
| | | text/plain
| | | text/html
| | image/jpeg
| application/msword
The multipart/alternative part will not be collapsed.
** Affects: mailman
Importance: Medium
Assignee: Mark Sapiro (msapiro)
Status: In Progress
** Changed in: mailman
Importance: Undecided => Medium
** Changed in: mailman
Status: New => In Progress
** Changed in: mailman
Milestone: None => 2.1.14
** Changed in: mailman
Assignee: (unassigned) => Mark Sapiro (msapiro)
--
Content filtering fails to collapse alternatives.
https://bugs.launchpad.net/bugs/576675
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
Public bug reported:
Feature request
Mailman 3 should try to fuzzily match unknown author addresses against
the member database. For example, if "turnbull(a)sk.domain.tld" is
subscribed, then "turnbull(a)shako.sk.domain.tld" probably is the same
person. This could probably be efficiently implemented by storing
domains in bigendian order, and testing for prefixes. Bonus points for
matching on full name. For example, for me personally
firstname(a)xemacs.org and lastname(a)xemacs.org both resolve to me, which
could not be reasonably associated by algorithm, but I always use the
same full name, which would be strong indication that it's me. Possibly
matching on mailbox would also be useful, but only as an optimization to
be confirmed by one of the other two (or maybe if the match is unique?)
Note that for the first example, the second "turnbull@shako" variant is
today used only by spammers; I haven't sent a message with that "From"
since 1995, and I doubt it's been used as "Sender" more than a very
small handful of times since 2000. For this reason, the feature should
*never* be automated. Instead, it should be part of the moderation
interface. If a match is detected, then an option should appear saying
something like "This address appears to be an alias for <member name and
address>. [ ] Add <unknown address> as an alias for <member>."
** Affects: mailman
Importance: Undecided
Status: New
** Description changed:
Feature request
Mailman 3 should try to fuzzily match unknown author addresses against
the member database. For example, if "turnbull(a)sk.tsukuba.ac.jp" is
subscribed, then "turnbull(a)shako.sk.tsukuba.ac.jp" probably is the same
person. This could probably be efficiently implemented by storing
domains in bigendian order, and testing for prefixes. Bonus points for
matching on full name. For example, for me personally
firstname(a)xemacs.org and lastname(a)xemacs.org both resolve to me, which
could not be reasonably associated by algorithm, but I always use the
same full name, which would be strong indication that it's me. Possibly
matching on mailbox would also be useful, but only as an optimization to
be confirmed by one of the other two (or maybe if the match is unique?)
Note that for the first example, the second "turnbull@shako" variant is
today used only by spammers; I haven't sent a message with that "From"
since 1995, and I doubt it's been used as "Sender" more than a very
small handful of times since 2000. For this reason, the feature should
*never* be automated. Instead, it should be part of the moderation
interface. If a match is detected, then an option should appear saying
something like "This address appears to be an alias for <member name and
- address>. [ ] Add <unknown> address as an alias for <member>."
+ address>. [ ] Add <unknown address> as an alias for <member>."
** Description changed:
Feature request
Mailman 3 should try to fuzzily match unknown author addresses against
- the member database. For example, if "turnbull(a)sk.tsukuba.ac.jp" is
- subscribed, then "turnbull(a)shako.sk.tsukuba.ac.jp" probably is the same
+ the member database. For example, if "turnbull(a)sk.domain.tld" is
+ subscribed, then "turnbull(a)shako.sk.domain.tld" probably is the same
person. This could probably be efficiently implemented by storing
domains in bigendian order, and testing for prefixes. Bonus points for
matching on full name. For example, for me personally
firstname(a)xemacs.org and lastname(a)xemacs.org both resolve to me, which
could not be reasonably associated by algorithm, but I always use the
same full name, which would be strong indication that it's me. Possibly
matching on mailbox would also be useful, but only as an optimization to
be confirmed by one of the other two (or maybe if the match is unique?)
Note that for the first example, the second "turnbull@shako" variant is
today used only by spammers; I haven't sent a message with that "From"
since 1995, and I doubt it's been used as "Sender" more than a very
small handful of times since 2000. For this reason, the feature should
*never* be automated. Instead, it should be part of the moderation
interface. If a match is detected, then an option should appear saying
something like "This address appears to be an alias for <member name and
address>. [ ] Add <unknown address> as an alias for <member>."
--
Mailman 3 member functions should "guess" address membership
https://bugs.launchpad.net/bugs/514625
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
Public bug reported:
The test program reports an error if it detects an existing mailman.cfg:
Failure in test test_current_working_directory (mailman.tests.test_configfile.TestConfigFileSearch)
Traceback (most recent call last):
File "/usr/lib/python2.6/unittest.py", line 279, in run
testMethod()
File "/root/mailman/src/mailman/tests/test_configfile.py", line 107, in test_current_working_directory
self.assertEqual(found, config_file)
File "/usr/lib/python2.6/unittest.py", line 350, in failUnlessEqual
(msg or '%r != %r' % (first, second))
AssertionError: '/etc/mailman.cfg' != u'/tmp/tmpVfAIyB/home/alex/mailman/hacking/mailman.cfg'
I believe it should not do this. It should either silently ignore the
difference or use the test mailman.cfg or ... but not break.
** Affects: mailman
Importance: Undecided
Status: New
** Tags: 3.0 mailman
--
test breaks if existing mailman.cfg is found
https://bugs.launchpad.net/bugs/543618
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
Public bug reported:
Postfix has a very handy command called postconf(1) which lets you dump
all or one Postfix configuration variable. It would be very handy for
Mailman 3 to have something similar.
** Affects: mailman
Importance: Medium
Assignee: Barry Warsaw (barry)
Status: Triaged
** Affects: mailman/3.0
Importance: Medium
Assignee: Barry Warsaw (barry)
Status: Triaged
** Also affects: mailman/3.0
Importance: Medium
Assignee: Barry Warsaw (barry)
Status: Triaged
--
Add the equivalent of postconf(1)
https://bugs.launchpad.net/bugs/518517
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
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.
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.
Public bug reported:
For a good, working Mailman 3.0 UI we have to handle the passwords for each user (needed when they subscribe/unsubscribe/want to access their settings page but also for the admins and listowners). Hence, we need to implement the possibility to check for passwords in the rest-client (I believe these are saved in the user table in the core DB) and/or a login function.
We should probably use https for the psw authentication.
** Affects: mailman
Importance: Undecided
Status: New
** Tags: mailman3 rest-api
--
Login function needed in rest-client
https://bugs.launchpad.net/bugs/600780
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
florianfuchs has proposed merging lp:~flo-fuchs/mailman/restclient into lp:mailman.
Requested reviews:
Mailman Coders (mailman-coders)
I added a rest client in src/mailmanclient as well as a doctest in src/mailman/rest/docs/restclient.txt.
--
https://code.launchpad.net/~flo-fuchs/mailman/restclient/+merge/28522
Your team Mailman Coders is requested to review the proposed merge of lp:~flo-fuchs/mailman/restclient into lp:mailman.
Public bug reported:
Trying to retrieve a list of all mailing lists in the system (using the
rest client) MM3 crashes with the traceback below. It seems to be a
regression issue but I think it might also be a general bug since a non
existing column in the DB is called.
About the lock mentioned in the traceback: gallia is my wireless network
and the processes I have running are Mailman 3 core and a Django app for
the MM3 UI which should work together.
anna@athena:~/Documents/Programmering/mailman3/mailman$ Traceback (most recent call last):
File "/usr/lib/python2.6/wsgiref/handlers.py", line 93, in run
self.result = application(self.environ, self.start_response)
File "/home/anna/Documents/Programmering/mailman3/mailman/src/mailman/rest/wsgiapp.py", line 58, in __call__
environ, start_response)
File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/restish-0.11-py2.6.egg/restish/app.py", line 18, in __call__
response = self.get_response(request, resource_or_response)
File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/restish-0.11-py2.6.egg/restish/app.py", line 65, in get_response
resource_or_response = resource_or_response(request)
File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/restish-0.11-py2.6.egg/restish/resource.py", line 211, in __call__
return _dispatch(request, match, lambda r: callable(self, r))
File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/restish-0.11-py2.6.egg/restish/resource.py", line 239, in _dispatch
response = func(request)
File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/restish-0.11-py2.6.egg/restish/resource.py", line 211, in <lambda>
return _dispatch(request, match, lambda r: callable(self, r))
File "/home/anna/Documents/Programmering/mailman3/mailman/src/mailman/rest/lists.py", line 215, in collection
resource = self._make_collection(request)
File "/home/anna/Documents/Programmering/mailman3/mailman/src/mailman/rest/helpers.py", line 140, in _make_collection
collection = self._get_collection(request)
File "/home/anna/Documents/Programmering/mailman3/mailman/src/mailman/rest/lists.py", line 134, in _get_collection
return list(getUtility(IListManager))
File "/home/anna/Documents/Programmering/mailman3/mailman/src/mailman/model/listmanager.py", line 84, in __iter__
for fqdn_listname in self.names:
File "/home/anna/Documents/Programmering/mailman3/mailman/src/mailman/model/listmanager.py", line 90, in names
for mlist in config.db.store.find(MailingList):
File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/storm-0.16.0-py2.6-linux-i686.egg/storm/store.py", line 968, in __iter__
result = self._store._connection.execute(self._get_select())
File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/storm-0.16.0-py2.6-linux-i686.egg/storm/database.py", line 217, in execute
raw_cursor = self.raw_execute(statement, params)
File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/storm-0.16.0-py2.6-linux-i686.egg/storm/databases/sqlite.py", line 153, in raw_execute
return Connection.raw_execute(self, statement, params)
File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/storm-0.16.0-py2.6-linux-i686.egg/storm/database.py", line 299, in raw_execute
self._check_disconnect(raw_cursor.execute, *args)
File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/storm-0.16.0-py2.6-linux-i686.egg/storm/database.py", line 342, in _check_disconnect
return function(*args, **kwargs)
OperationalError: no such column: mailinglist.last_post_at
Aug 13 10:52:47 2010 (2982) timed out
Usage: master [options]
Master sub-process watcher.
Start and watch the configured queue runners and ensure that they stay alive
and kicking. Each are fork and exec'd in turn, with the master waiting on
their process ids. When it detects a child queue runner has exited, it may
restart it.
The queue runners respond to SIGINT, SIGTERM, SIGUSR1 and SIGHUP. SIGINT,
SIGTERM and SIGUSR1 all cause the qrunners to exit cleanly. The master will
restart qrunners that have exited due to a SIGUSR1 or some kind of other exit
condition (say because of an exception). SIGHUP causes the master and the
qrunners to close their log files, and reopen then upon the next printed
message.
The master also responds to SIGINT, SIGTERM, SIGUSR1 and SIGHUP, which it
simply passes on to the qrunners. Note that the master will close and reopen
its own log files on receipt of a SIGHUP. The master also leaves its own
process id in the file `data/master-qrunner.pid` but you normally don't need
to use this pid directly.
master: error: The master qrunner lock could not be acquired, because it
appears as if some process on some other host may have acquired it. We can't
test for stale locks across host boundaries, so you'll have to clean this up
manually.
Lock file: /home/anna/Documents/Programmering/mailman3/mailman/var/locks/master-qrunner.lck
Lock host: gallia
Exiting.
Traceback (most recent call last):
File "/usr/lib/python2.6/wsgiref/handlers.py", line 93, in run
self.result = application(self.environ, self.start_response)
File "/home/anna/Documents/Programmering/mailman3/mailman/src/mailman/rest/wsgiapp.py", line 58, in __call__
environ, start_response)
File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/restish-0.11-py2.6.egg/restish/app.py", line 18, in __call__
response = self.get_response(request, resource_or_response)
File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/restish-0.11-py2.6.egg/restish/app.py", line 65, in get_response
resource_or_response = resource_or_response(request)
File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/restish-0.11-py2.6.egg/restish/resource.py", line 211, in __call__
return _dispatch(request, match, lambda r: callable(self, r))
File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/restish-0.11-py2.6.egg/restish/resource.py", line 239, in _dispatch
response = func(request)
File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/restish-0.11-py2.6.egg/restish/resource.py", line 211, in <lambda>
return _dispatch(request, match, lambda r: callable(self, r))
File "/home/anna/Documents/Programmering/mailman3/mailman/src/mailman/rest/lists.py", line 215, in collection
resource = self._make_collection(request)
File "/home/anna/Documents/Programmering/mailman3/mailman/src/mailman/rest/helpers.py", line 140, in _make_collection
collection = self._get_collection(request)
File "/home/anna/Documents/Programmering/mailman3/mailman/src/mailman/rest/lists.py", line 134, in _get_collection
return list(getUtility(IListManager))
File "/home/anna/Documents/Programmering/mailman3/mailman/src/mailman/model/listmanager.py", line 84, in __iter__
for fqdn_listname in self.names:
File "/home/anna/Documents/Programmering/mailman3/mailman/src/mailman/model/listmanager.py", line 90, in names
for mlist in config.db.store.find(MailingList):
File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/storm-0.16.0-py2.6-linux-i686.egg/storm/store.py", line 968, in __iter__
result = self._store._connection.execute(self._get_select())
File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/storm-0.16.0-py2.6-linux-i686.egg/storm/database.py", line 217, in execute
raw_cursor = self.raw_execute(statement, params)
File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/storm-0.16.0-py2.6-linux-i686.egg/storm/databases/sqlite.py", line 153, in raw_execute
return Connection.raw_execute(self, statement, params)
File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/storm-0.16.0-py2.6-linux-i686.egg/storm/database.py", line 299, in raw_execute
self._check_disconnect(raw_cursor.execute, *args)
File "/home/anna/Documents/Programmering/mailman3/mailman/eggs/storm-0.16.0-py2.6-linux-i686.egg/storm/database.py", line 342, in _check_disconnect
return function(*args, **kwargs)
OperationalError: no such column: mailinglist.last_post_at
** Affects: mailman
Importance: Undecided
Status: New
** Tags: mailman3 rest-api
--
Possible regression issue in MM3
https://bugs.launchpad.net/bugs/617285
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.