d_baron at 012.net.il
Mon Jul 16 11:54:25 UTC 2007
On Monday 16 July 2007, Marc Haber wrote:
> On Mon, Jul 16, 2007 at 02:28:17PM +0300, David Baron wrote:
> > I am running the latest and greatest of Debian Sid and all seems fine.
> > The DEBCONFitemDEBONF is now a non-issue and I placed the macro
> > attempting to surpress "false positive" warnings. See and next boot
> > because that is when I get them.
> Why do you still need to have DEBCONFsomethingDEBCONF strings in your
> config? If you don't, remove them and the warning suppression macro.
The warnings are false. An fgrep yielded only .old and .save files which were
saved by the installation or by me. I have since deleted them.
> > The error logs I had might have been a "fluke" caused by the way
> > apt-get/kpackage handled the error after not accepting the new
> > configuration file. They way they were reproduced indicates this type of
> > thing.
> > My config is
> > fetchmail --> exim4 ---->
> > / \
> > procmail pipe running spamassassin and "clamassassin"
> > One thing I have noticed, every bootup: A bunch of spam messages do get
> > by and this is stuff most certainly caught by spamassassin so somehow,
> > they may be a delay in that procmail pipe coming into effect? Seems to
> > work fine afterwards.
> I do not have any idea how this complex setup behaves. Why don't you
> use exim's built-in interfaces to spamassassin and the virus scanner?
Documentation (maybe now long long outdated) recommended doing it this way, at
least for spamassassin.
More information about the Pkg-exim4-users