Update of /cvsroot/mailman/mailman3/doc
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv31133/doc
Added Files:
Tag: 3.0
ALIASES.txt Issues.txt Running.txt
Log Message:
Initial checkin of Mailman3 source
--- NEW FILE: ALIASES.txt ---
A typical Mailman list exposes nine aliases which point to seven different
wrapped scripts. E.g. for a list named `mylist', you'd have:
mylist-bounces -> bounces
mylist-confirm -> confirm
mylist-join -> join (-subscribe is an alias)
mylist-leave -> leave (-unsubscribe is an alias)
mylist-owner -> owner
mylist -> post
mylist-request -> request
-request, -join, and -leave are robot addresses; their sole purpose is
to process emailed commands. -bounces is the automated bounce
processor, and all messages to list members have their return address
set to -bounces. If the bounce processor fails to extract a bouncing
member address, it can optionally forward the message on to the list
owners.
-owner is for reaching a human operator with minimal list interaction
(i.e. no bounce processing). -confirm is another robot address which
processes replies to VERP-like confirmation notices.
So delivery flow of messages look like this:
joerandom ---> mylist ---> list members
| |
| |[bounces]
| mylist-bounces <---+ <-------------------------------+
| | |
| +--->[internal bounce processing] |
| ^ | |
| | | [bounce found] |
| [bounces *] +--->[register and discard] |
| | | | |
| | | |[*] |
| [list owners] |[no bounce found] | |
| ^ | | |
| | | | |
+-------> mylist-owner <--------+ | |
| | |
| data/owner-bounces.mbox <--[site list] <---+ |
| |
+-------> mylist-join--+ |
| | |
+------> mylist-leave--+ |
| | |
| v |
+-------> mylist-request |
| | |
| +---> [command processor] |
| | |
+-----> mylist-confirm ----> +---> joerandom |
| |
|[bounces] |
+----------------------+
A person can send an email to the list address (for posting), the
-owner address (to reach the human operator), or the -confirm, -join,
-leave, and -request mailbots. Messages to the list address are then
forwarded on to the list membership, with bounces directed to the
-bounces address.
[*] Messages sent to the -owner address are forwarded on to the list
owner/moderators. All -owner destined messages have their bounces
directed to the site list -bounces address, regardless of whether a
human sent the message or the message was crafted internally. The
intention here is that the site owners want to be notified when one of
their list owners' addresses starts bouncing.
Any messages to site owners has their bounces directed to a special
"loop-killer" address, which just dumps the message into the
data/owners-bounces.mbox file.
Finally, message to any of the mailbots causes the requested action to
be performed. Results notifications are sent to the author of the
message, which all bounces pointing back to the -bounces address.
--- NEW FILE: Issues.txt ---
- What should SMTP_MAX_RCPT default be? JC Lawrence argues for 5
- Should we munge Message-ID on incoming messages?
- pro: we can guarantee uniqueness and use it as a key to the message store
- con: it breaks correlation with the non-list copy, and usenet threading
--- NEW FILE: Running.txt ---
To run Mailman3 from the checkout, you currently need Twisted, PyProtocols,
and Zope Page Templates. To get all the required stuff, run ./getstuff.sh
Next, build everything with this command:
% make inplace
_______________________________________________
Mailman-checkins mailing list
[EMAIL PROTECTED]
Unsubscribe: http://mail.python.org/mailman/options/mailman-checkins/archive%40jab.org
