summaryrefslogtreecommitdiff
path: root/src/mailman/rest/docs/addresses.rst (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Complete the port to Falcon 1.0.Barry Warsaw2016-04-021-0/+9
|
* Members and nonmembers moderation action fallbackAurélien Bompard2016-03-311-5/+0
| | | | | | | | Members and nonmember's moderation action should be None by default, and in that case the moderation rule should fallback to the mailing list's default action. Fixes: #189
* Major push for completing issue #121. Now in API 3.1, all UUIDs must be theBarry Warsaw2015-12-301-2/+2
| | | | | | | | | hex representations of a UUID, not the int representation. Also: * Some general code cleanup. * Fix issue 185 (REST server crash when subscribing a user without a preferred address).
* Allow a Member's moderation_action to be changed by the REST API.Aurélien Bompard2015-12-081-0/+5
| | | | Cleanups by Barry. Closes !67
* add tests, fix docs, remove contact_addressAbhilash Raj2015-03-281-0/+1
|
* * Member resource JSON now include the ``member_id`` as a separate key.Barry Warsaw2015-02-131-0/+5
|
* * You can now DELETE an address. If the address is linked to a user, theBarry Warsaw2015-02-051-0/+61
| | | | user is not delete, it is just unlinked.
* Trunk merge.Barry Warsaw2014-12-221-6/+124
|\
| * /user sub-resource of the address documented by Aurélien Bompard.Barry Warsaw2014-12-091-11/+124
| |\
| | * Document the new /addresses/<email>/user resourceAurélien Bompard2014-12-091-10/+120
| |/ | | | | | | Fixes LP bug #1400520
| * REST feature: create a user from an existing addressAurélien Bompard2014-12-081-0/+5
| | | | | | | | Fixes LP bug #1312884
* | All the REST tests pass.Barry Warsaw2014-12-151-7/+0
|/
* * Fixed a crash in the REST server when searching for nonmembers viaBarry Warsaw2014-04-151-5/+10
| | | | | | | | ``/find`` which we've never seen before, because those members only have an address record, not a user record. This requires a small change in the API where the JSON response's ``address`` key now contains the URL to the address resource, the new ``email`` key contains the email address as a string, and the ``user`` key is optional.
* Add an email address to an existing user via the REST API.Barry Warsaw2014-04-141-0/+53
|\
| * * Added an API endpoint to POST new email addresses to a user resource.Florian Fuchs2014-04-131-0/+34
|/ | | | * Updated docs.
* * You can now verify and unverify an email address through the REST API.Barry Warsaw2012-09-221-1/+41
| | | | | | | POST to .../addresses/<email>/verify and .../addresses/<email>/unverify respectively. The POST data is ignored. It is not an error to verify or unverify an address more than once, but verifying an already verified address does not change its `.verified_on` date. (LP: #1054730)
* * The link between members and the mailing lists they are subscribed to, isBarry Warsaw2012-09-041-5/+5
| | | | | | | | | | | | | | | now via the RFC 2369 `list_id` instead of the fqdn listname (i.e. posting address). This is because while the posting address can change if the mailing list is moved to a new server, the list id is fixed. (LP: #1024509) + IListManager.get_by_list_id() added. + IListManager.list_ids added. + IMailingList.list_id added. + Several internal APIs that accepted fqdn list names now require list ids, e.g. ISubscriptionService.join() and .find_members(). + IMember.list_id attribute added; .mailing_list is now an alias that retrieves and returns the IMailingList. - list_id added (LP: #1024509)
* Schema change. After discussion at Pycon, we decided to change "real_name" toBarry Warsaw2012-03-151-3/+3
| | | | | | | | | | | "display_name" across the board. * `IMailingList.real_name` -> `IMailingList.display_name` * `IUser.real_name` -> `IUser.display_name` * `IAddress.real_name` -> `IAddress.display_name` * Schema changes: - real_name -> display_name (mailinglist, user, address)
* * You can now query or change a member's `delivery_mode` attribute throughBarry Warsaw2011-09-011-0/+239
the REST API (LP: #833132). Given by Stephen A. Goss.