I would try this option: put in an alias-like file the list of to_be_deferred users; alised to an address such [EMAIL PROTECTED]; in your /etc/hosts to.defer.host point to a non-responsive-host (for example 172.31.30.29 assuming your local net do not use one of such addresses); When the message arrive it is accepted but then stay in queue; When you want back to deliver. remove the entries that forward the user to the non-responding-host; then add to.defer.hosts to local domain and some roputer that rerout domain to.defer.host to standar domain. give temporarily the address 172.31.30.29 to your computer e force the queue to exaust.
On Tue, 14 Oct 2008, Graeme Fowler wrote: > On Tue, 2008-10-14 at 13:46 -0700, Jeroen van Aart wrote: > > This means the MTA which attempted delivery will retry again. > > But the issue here is that Jason is talking about MUAs, not MTAs... > > > When I added the line to my aliases file, and tried to send a message > > to the account with Thunderbird, the message that I added to my > > aliases file was displayed in Thunderbird, but the message was not > > queued for delivery on the mail server. I'd be fine if the sending > > user got a message that their message was queued for delivery. Is > > this the correct behaviour? or am I misunderstanding? > > What Jason needs is an ACL that accepts MUA submissions (which are > authenticated, aren't they?), but a router/transport pair that > subsequently defers according to the contents of the "temporary stop > delivery" file. > > Now how he'd get to that state I'm not about to work out, > unfortunately... rather too much else to do before sleeping tonight! > > Graeme > > > -- > ## List details at http://lists.exim.org/mailman/listinfo/exim-users > ## Exim details at http://www.exim.org/ > ## Please use the Wiki with this list - http://wiki.exim.org/ > > -- ## List details at http://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
