On Thu, Sep 28, 2006 at 11:51:15AM -0400, Stephen Allen wrote: >Clive Menzies wrote: >> On (28/09/06 10:59), Stephen Allen wrote: >>> On Thu, Sep 28, 2006 at 10:34:14AM -0400 or thereabouts, celejar wrote: >>>> On 9/28/06, Stephen Allen <[EMAIL PROTECTED]> wrote: >>>>> Right. May have to. >>>>> >>>>> Thanks Clive. >>>> Have you tried 'exim -qff' ? >>> Hello Celejar: >>> >>> Yes, actually tried '-qf' prior as well -- No change in the 'q'. >>> >>> It seems strange that Exim4 would break, if the network to the SMARTHOST >>> is down. One would assume that it would carry on as usual once the >>> connection was restored. >> >> another thought: >> >> dpkg-reconfigure exim4-config > >Clive: > >Yeah I don't really want to resort to that -- If one has to do such a >draconian measure then I would think this is a bug in Exim4, no ? > >Surely one shouldn't have to do this to fix a mailq issue. >
You can look at the log for a particular message like so: # exim4 -Mvl <message-id> and if you want to retry delivery on a particular message, # exim4 -M <message-id> This will thaw a particular message id: # exim4 -Mt <message-id> that should be enough to get you going. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
