On Fri, 26 Nov 2004, Tony Finch wrote:
> The mua_wrapper feature was designed for machines which are permanently
> connected and which dual-boot between Windows and Linux. Therefore they
> must not have a local queue of any kind: after the user logs out of Linux
> the machine may not be booted into Linux again before it is reinstalled.
> Instead the queue lives on the central email systems, which are assumed to
> be permanently available. The error handling model is that the user must
> deal with any problems, so as you say the problems must be immediately
> visible to the user.
Precisely. And the name "mua_wrapper" was chosen because in effect it
converts an MUA that delivers only via a command-line call into one that
delivers using SMTP to a smarthost. Such MUAs do not normally have any
queueing. Either the message gets to the smarthost or it doesn't. If it
doesn't, the user has to deal with the problem manually.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
Get the Exim 4 book: http://www.uit.co.uk/exim-book
