Exim+MailScanner - not always queuing mail on "in" side

Tim Bishop tim-lists at BISHNET.NET
Tue Jun 3 08:25:30 IST 2003

On Mon, Jun 02, 2003 at 04:01:59PM +0100, Tim Bishop wrote:
> On Mon, Jun 02, 2003 at 02:01:07PM +0100, Tony Finch wrote:
> > Tim Bishop <tim-lists at BISHNET.NET> wrote:
> >
> > >The problem is that occasionally (but not always) locally generated
> > >messages such as cron output don't get deferred by the incoming exim.
> > >From my understanding of Exim it seems that it's ignored the queue_only,
> > >then tried to defer it. Then, for some reason, it's decided to fail
> > >the message.
> >
> > This is probably because the hints database for the incoming exim says
> > that addresses have been failing for such a long time that they bounce
> > immediately. You need to check that the spool directory configurations
> > for the incoming and outgoing exims are correct and that they are being
> > run with the correct commands, and check that /var/spool/exim_incoming/db
> > is empty (as it should be if the queue_only option is working).
> I did have a retry file in the exim.in/db directory - which was
> causing the bouncing. However, I think I know how this got there.

And this morning it has magically returned. :/

I suppose a cron job could deal with this, but I'd prefer a tidier
solution really.


Tim Bishop
PGP Key: 0x5AE7D984

More information about the MailScanner mailing list