On 12/05/2014 02:45 PM, Andrew Stuart wrote:
>
> It sounds like there’s no built in way so I’ll probably just modify the
> source so that a message to BCC results in a silent post. I’d be interested
> to hear if anyone thinks that approach is likely to cause problems.
An alternative way would be to create a new address
LISTNAME-archive@hostname which would just queue the message in the in
queue with an abbreviated pipeline consisting perhaps of just Moderate
(to ensure the sender is authorized to post) and ToArchive.
You would need to create scripts/archive which could be a copy of
scripts/owner with a few occurrences of 'owner' changed to 'archive' and
the final enqueue changed to something like:
inq.enqueue(sys.stdin.read(),
listname=listname,
_plaintext=1,
pipeline=['Moderate', 'ToArchive'],
toarchive=1)
The toarchive=1 in the metadata is meaningless, but it would allow
different treatment in any handler in the pipeline.
You would also need to modify and recompile src/mail-wrapper.c to add
"archive" to the valid commands and add the LISTNAME-archive alias(es)
or whatever to the MTA (you could modify Mailman/MTA/Manual.py and/or
Mailman/MTA/Postfix.py to generate these).
--
Mark Sapiro <m...@msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
------------------------------------------------------
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
