[rt-users] shut down without losing mail?

[Jorn Hass]

Well, if you had Postfix, you could issue a temporary code, i.e. 451 based
on recipient...

Postfix makes controlling mail a lot easier. We use separate access files
for client (ip/host/net), sender (from) and recipient (to) fields, which
makes it easier to control. We also filter on helo parameters, but that's
another chapter... 

Still would like to see a combo setup though, where one could say: if from
x, sent to y, block...

Sigh, the dreams...

Regards, Jörn Hass
Senior Systems Engineer, Infrastructure.
Internet Solutions
E-mail:		jorn.hass at is.co.za
WWW:		http://www.is.co.za
 

-> -----Original Message-----
-> From: Lorens Kockum [mailto:rt-id-45 at lists.lorens.org]
-> Sent: 01 April 2003 13:36 PM
-> To: Les Mikesell
-> Cc: rt-users at lists.fsck.com
-> Subject: Re: [rt-users] shut down without losing mail?
-> 
-> On Mon, Mar 31, 2003 at 11:48:07AM -0600, Les Mikesell wrote:
-> > Is there a clean way to stop RT (to upgrade versions for
-> > example...) without dropping any inbound email?  Does
-> > sendmail take some magic return value from a pipe delivery
-> > as a temporary failure and retry later?
-> 
-> Not by default, no. See 3).
-> 
-> 1) Shutdown the mailserver, or just disable incoming mail if
->    it's a mailserver dedicated to RT.
-> 
-> 2) Use MTA-specific magic to defer mails addressed to RT alias
->    instead of giving them to RT.
-> 
-> 3) Permanently use MTA-specific magic to defer mails addressed
->    to RT alias if giving them to RT results in an error (not
->    quite off-the-cuff certain how to do this but pretty sure
->    it's possible with exim, otherwise writing a wrapper should
->    be very simple, could be incorporated into procmailrc below)
-> 
-> 4) Never needed previous solutions because I send my incoming RT
->    mail through procmail, to handle the REALLY big attachments,
->    the most blatant spam, etc. Promail either sends to RT or to
->    a spoolfile. Mutt reads the spoolfile, and I have a macro to
->    send to RT directly, bypassing procmail.
-> 
->    That's nice in itself, so once you have that, it's just a
->    matter of putting a comment in a strategic place in the
->    procmailrc, and everything goes to the spoolfile until you
->    macro it onwards.
-> 
->    (OK this is for an old RT install but I don't see that RT3
->    should be different)
-> 




"This e-mail may contain confidential information and may be legally
privileged and is intended only for the person to whom it is addressed. If
you are not the intended recipient, you are notified that you may not use,
distribute or copy this document in any manner whatsoever. Kindly also
notify the sender immediately by telephone, and delete the e-mail. When
addressed to clients of the company from where this e-mail originates ("the
sending company ") any opinion or advice contained in this e-mail is subject
to the terms and conditions expressed in any applicable terms of business or
client engagement letter . The sending company does not accept liability for
any damage, loss or expense arising from this e-mail and/or from the
accessing of any files attached to this e-mail."