summaryrefslogtreecommitdiff
path: root/src/mailman/docs/mlist-addresses.txt
diff options
context:
space:
mode:
Diffstat (limited to 'src/mailman/docs/mlist-addresses.txt')
-rw-r--r--src/mailman/docs/mlist-addresses.txt54
1 files changed, 27 insertions, 27 deletions
diff --git a/src/mailman/docs/mlist-addresses.txt b/src/mailman/docs/mlist-addresses.txt
index 75ec3df37..48d25a8f3 100644
--- a/src/mailman/docs/mlist-addresses.txt
+++ b/src/mailman/docs/mlist-addresses.txt
@@ -4,54 +4,54 @@ Mailing list addresses
Every mailing list has a number of addresses which are publicly available.
These are defined in the IMailingListAddresses interface.
- >>> mlist = config.db.list_manager.create(u'_xtest@example.com')
+ >>> mlist = config.db.list_manager.create('_xtest@example.com')
The posting address is where people send messages to be posted to the mailing
list. This is exactly the same as the fully qualified list name.
- >>> mlist.fqdn_listname
- u'_xtest@example.com'
- >>> mlist.posting_address
- u'_xtest@example.com'
+ >>> print mlist.fqdn_listname
+ _xtest@example.com
+ >>> print mlist.posting_address
+ _xtest@example.com
Messages to the mailing list's 'no reply' address always get discarded without
prejudice.
- >>> mlist.no_reply_address
- u'noreply@example.com'
+ >>> print mlist.no_reply_address
+ noreply@example.com
The mailing list's owner address reaches the human moderators.
- >>> mlist.owner_address
- u'_xtest-owner@example.com'
+ >>> print mlist.owner_address
+ _xtest-owner@example.com
The request address goes to the list's email command robot.
- >>> mlist.request_address
- u'_xtest-request@example.com'
+ >>> print mlist.request_address
+ _xtest-request@example.com
The bounces address accepts and processes all potential bounces.
- >>> mlist.bounces_address
- u'_xtest-bounces@example.com'
+ >>> print mlist.bounces_address
+ _xtest-bounces@example.com
The join (a.k.a. subscribe) address is where someone can email to get added to
the mailing list. The subscribe alias is a synonym for join, but it's
deprecated.
- >>> mlist.join_address
- u'_xtest-join@example.com'
- >>> mlist.subscribe_address
- u'_xtest-subscribe@example.com'
+ >>> print mlist.join_address
+ _xtest-join@example.com
+ >>> print mlist.subscribe_address
+ _xtest-subscribe@example.com
The leave (a.k.a. unsubscribe) address is where someone can email to get added
to the mailing list. The unsubscribe alias is a synonym for leave, but it's
deprecated.
- >>> mlist.leave_address
- u'_xtest-leave@example.com'
- >>> mlist.unsubscribe_address
- u'_xtest-unsubscribe@example.com'
+ >>> print mlist.leave_address
+ _xtest-leave@example.com
+ >>> print mlist.unsubscribe_address
+ _xtest-unsubscribe@example.com
Email confirmations
@@ -62,15 +62,15 @@ to be confirmed. It requires that a cookie be provided, which will be
included in the local part of the email address. The exact format of this is
dependent on the VERP_CONFIRM_FORMAT configuration variable.
- >>> mlist.confirm_address('cookie')
- u'_xtest-confirm+cookie@example.com'
- >>> mlist.confirm_address('wookie')
- u'_xtest-confirm+wookie@example.com'
+ >>> print mlist.confirm_address('cookie')
+ _xtest-confirm+cookie@example.com
+ >>> print mlist.confirm_address('wookie')
+ _xtest-confirm+wookie@example.com
>>> config.push('test config', """
... [mta]
... verp_confirm_format: $address---$cookie
... """)
- >>> mlist.confirm_address('cookie')
- u'_xtest-confirm---cookie@example.com'
+ >>> print mlist.confirm_address('cookie')
+ _xtest-confirm---cookie@example.com
>>> config.pop('test config')