Re: [Exim] Changed behavior of -Mg and -M in exim-3

Top Page
Delete this message
Reply to this message
Author: Philip Hazel
Date:  
To: Hans Morten Kind
CC: exim-users
Subject: Re: [Exim] Changed behavior of -Mg and -M in exim-3
On Tue, 26 Oct 1999, Hans Morten Kind wrote:

> I finally upgraded to exim-3.03, it seems nice but there are some
> details changed from exim-2 I dont understand.
>
> Some messages which get frozen I would like to "give up", ie returning
> the message to the originator with the message "delivery cancelled by
> administrator". "exim -v -Mg <msgid>" used to do the trick, however as
> far as I can se the deliver_force_thaw never gets set so exim refuses,
> only telling me "Message is frozen".


I'm surprised nobody has noticed this before! That was not an intended
change. It seems natural to me that -Mg should imply a forced thaw, and
I will fix this in the next release.

> On a server running some mailinglists I have been using the
> queue_smtp option to speed up remote deliveries. However when
> using queue_smtp_domains or queue_remote_domains under exim-3
> there seems to be no way of forcing delivery on a specific message.
>
> When running "exim -v -M <msgid>" no delivery is attempted.
> exim says remote delivery skipped (queue_remote_domains) or
> domain matches queue_smtp_domains, or -odqs set (queue_smtp_domains).


Again, this isn't an intended change. The -M option should always
override all queuing options. I will fix this one too.

The process of "freezing" the code for the next release should start in
a couple of weeks. At that time testing code will be available.

Thanks for reporting these anomalies.

Philip

-- 
Philip Hazel            University of Cambridge Computing Service,
ph10@???      Cambridge, England. Phone: +44 1223 334714.
Government Policy: If it ain't broke, fix it till it is.