** Description changed: When a new mailman subscriber is created with the email of an already existing mailman subscriber or user a `409` code with a message `user already exists` is returned by the postorius but when the same email but now case sensitive is used a `500` code with message `server error code` is returned. The latter should also return a `409` instead of `500` as it is misleading. + + Although the mailman core is giving `AssertionError: User should have + had linked address` in both the cases`. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1425359 Title: 500 error code shown by postorius instead of 409 error code To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1425359/+subscriptions

** Description changed: When a new mailman subscriber is created with the email of an already existing mailman subscriber or user a `409` code with a message `user already exists` is returned by the postorius but when the same email but now case sensitive is used a `500` code with message `server error code` is returned. The latter should also return a `409` instead of `500` as it is misleading. + + Bug discussed in detail at : https://mail.python.org/pipermail/mailman- + developers/2015-March/024474.html ** Description changed: + Bug discussed in detail at : https://mail.python.org/pipermail/mailman- + developers/2015-March/024474.html + When a new mailman subscriber is created with the email of an already existing mailman subscriber or user a `409` code with a message `user - already exists` is returned by the postorius but when the same email but - now case sensitive is used a `500` code with message `server error code` - is returned. + already exists` is returned by the Mailman REST API but when the same + email but now case sensitive is used a `500` code with message `server + error code` is returned. The latter should also return a `409` instead of `500` as it is misleading. - - Bug discussed in detail at : https://mail.python.org/pipermail/mailman- - developers/2015-March/024474.html -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1425359 Title: 500 error code shown by postorius instead of 409 error code To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1425359/+subscriptions

** Tags added: postorius -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1425359 Title: 500 error code shown by postorius instead of 409 error code To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1425359/+subscriptions

This Bug was result of treating case sensitive and case insensitive addresses differently which in both cases mailman treats as identical. So always comparing the strings by making the cases identical (lower case here) , will solve the bug. The solution thus provided to make the cases similar seems apt. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1425359 Title: 500 error code shown by postorius instead of 409 error code To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1425359/+subscriptions

** Changed in: mailman Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1425359 Title: 500 error code shown by postorius instead of 409 error code To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1425359/+subscriptions