Public bug reported:
Hi,
the following test case resulted in: HTTP/1.0 500 Internal Server Error
Username: MyTest
e-mail: MyTest(a)domain.invalid
1. Create user
curl -v -H "Accept: application/json" -H "Content-type: application/x-www-form-urlencoded" -X POST -d 'email=MyTest@domain.invalid&display_name=MyTest@domain.invalid' http://localhost:8001/3.0/users
-> 201 Created
DB address contains email "mytest(a)domain.invalid" and _original "MyTest(a)domain.invalid"
curl -v -H "Accept: application/json" -H "Content-type: application/x
-www-form-urlencoded" -X POST -d
'list_id=some_list.domain.invalid&role=member&subscriber=MyTest(a)domain.invalid'
http://localhost:8001/3.0/members
-> 500 Internal Server Error
No log file contain any exception or error message
Workaround available: Using lower-case letters result in a success
curl -v -H "Accept: application/json" -H "Content-type: application/x-www-form-urlencoded" -X POST -d 'list_id=some_list.domain.invalid&role=member&subscriber=mymest(a)domain.invalid' http://localhost:8001/3.0/members
** Affects: mailman
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1332922
Title:
Mailman 3.0 REST API does not support e-mails with uppercase letters
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1332922/+subscriptions
Public bug reported:
This attribute is obsolete and should be removed.
** Affects: mailman
Importance: Undecided
Assignee: Barry Warsaw (barry)
Status: New
** Tags: mailman3
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1307644
Title:
Remove IMailingList.moderator_password
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1307644/+subscriptions
Public bug reported:
The Invalid email addresses section in the doctests in
src/mailman/model/docs/registration.rst attempts to register various
invalid email addresses and checks that they are rejected.
In particular, the test
>>> registrar.register(mlist, '\xa0(a)example.com')
Traceback (most recent call last):
...
InvalidEmailAddressError: \xa0(a)example.com
will fail if python's sys.getdefaultencoding() returns 'UTF-8' because
the invalid address is reported with the UTF-8 encoding of nonbreaking
space rather than \xa0.
** Affects: mailman
Importance: Undecided
Status: New
** Tags: mailman3
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1285496
Title:
A test in src/mailman/model/docs/registration.rst fails if Python
default encoding is UTF-8
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1285496/+subscriptions
Public bug reported:
Messages gated to a list from usenet bypass all the checks in
Moderate.py. It is appropriate to bypass generic_nonmember_action
because many usenet posts will be from nonmembers of the list, but if
the sender is a moderated member or a nonmember matching one of the
*_these_nonmembers filters, those things should be honored.
** Affects: mailman
Importance: Medium
Assignee: Mark Sapiro (msapiro)
Status: In Progress
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1252575
Title:
The Mail<->News gateway doesn't honor moderation or *_these_nonmembers
for messages gated from usnet.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1252575/+subscriptions
Public bug reported:
In http://www.mail-archive.com/mailman-users%40python.org/msg62889.html,
I explained the (very strong) desirability of having posts made from
Usenet to Mailman be subject to normal moderation rules instead of
automatically and unconditionally approved. (In short, to not let
Usenet spam through to the mailing lists without any checking.)
In his reply, http://www.mail-archive.com/mailman-users%40python.org/msg62890.html, Mark gave a simple one-line change
(that is working fine so far as we can tell).
When I asked, Mark told me that the change couldn't be made for mailman
2.1, since it would need to be a user option and thus have i18n impact,
so suggested that I post it here, tagged mailman3, which I hope I've
done here.
Happy hacking,
Karl
** Affects: mailman
Importance: Undecided
Status: New
** Tags: mailman3
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1197473
Title:
moderating usenet->mailman posts
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1197473/+subscriptions
Public bug reported:
When Postorius GETs a collection of lists from the REST API, it will in
most situations only use a subset (the ones that are set to "advertise
in list index"). This is a minor issue as long as the request isn't
paginated, but can lead to incorrect item counts when it is.
Example:
GET /lists/test(a)example.com?page=1&count=10
will return all lists within the range [:10] from the database. If there
are x unadvertised lists in the result, the page will only show 10 - x
results.
I guess the most common way to solve this is for the REST API to accept
a number of common filter params which are used in the WHERE clause of
the database query. In this case:
GET /lists/test(a)example.com?page=1&count=10&advertised=(0|1|2)
0 - only non-advertised
1 - only advertised
2 - both
** Affects: mailman
Importance: Undecided
Status: New
** Tags: mailman3 rest
** Description changed:
When Postorius GETs a collection of lists from the REST API, it will in
most situations only use a subset (the ones that are set to "advertise
in list index"). This is a minor issue as long as the request isn't
paginated, but can lead to incorrect item counts when it is.
Example:
GET /lists/test(a)example.com?page=1&count=10
will return all lists within the range [:10] from the database. If there
are x unadvertised list in the result, the page will only show 10 - x
results.
I guess the most common way to solve this is for the REST API to accept
- a number of common filter params which are used for the WHERE clause of
+ a number of common filter params which are used in the WHERE clause of
the database query. In this case:
GET /lists/test(a)example.com?page=1&count=10&advertised=(0|1|2)
0 - only non-advertised
1 - only advertised
2 - both
** Description changed:
When Postorius GETs a collection of lists from the REST API, it will in
most situations only use a subset (the ones that are set to "advertise
in list index"). This is a minor issue as long as the request isn't
paginated, but can lead to incorrect item counts when it is.
Example:
GET /lists/test(a)example.com?page=1&count=10
will return all lists within the range [:10] from the database. If there
- are x unadvertised list in the result, the page will only show 10 - x
+ are x unadvertised lists in the result, the page will only show 10 - x
results.
I guess the most common way to solve this is for the REST API to accept
a number of common filter params which are used in the WHERE clause of
the database query. In this case:
GET /lists/test(a)example.com?page=1&count=10&advertised=(0|1|2)
0 - only non-advertised
1 - only advertised
2 - both
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1190582
Title:
Add some common filters to REST API resources that expose collections
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1190582/+subscriptions
Public bug reported:
The LMTP server currently does a sanity check on the To field of the
incoming message, to ensure that it is addressed to a valid mailing
list. This check ignores acceptable aliases, but it should honor them.
** Affects: mailman
Importance: Undecided
Status: New
** Tags: mailman3
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1170726
Title:
The LMTP server needs to check acceptable aliases
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1170726/+subscriptions
Public bug reported:
searching all the code (mailman-3.0.0b3) (with ack) for "tomoderators" returns this:
$ ack -ai tomoderators
src/mailman/bin/checkdbs.py
202: msg.send(mlist, **{'tomoderators': True})
src/mailman/chains/hold.py
241: nmsg.send(mlist, **dict(tomoderators=True))
src/mailman/app/moderator.py
228: msg.send(mlist, tomoderators=True)
299: msg.send(mlist, tomoderators=True)
I can't see where this option is actually used. In practice, the
moderation notification sent from hold.py in line 241 just goes to
everyone in the mailing list, not the moderators.
** Affects: mailman
Importance: Undecided
Status: New
** Tags: mailman3
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1170388
Title:
the tomoderators argument to "send" is ignored
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1170388/+subscriptions
Public bug reported:
There should be an interface for posting to a list from the Web UI
** Affects: mailman
Importance: Undecided
Status: New
** Tags: wishlist
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1104505
Title:
Web posting interface
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1104505/+subscriptions