On Wed, 05 Mar 2008 18:27:28 +0100 Manuel Molina Cuberos
<[EMAIL PROTECTED]> wrote:

> I'm configuring (or trying to, due to the lack of documentation) Exim 4 
> to use DSPAM.
> The configuration I'm trying, after several failures, is :
> 
> Exim 4 receives the message from Internet --> dspamc -> dspam (daemon 
> mode, MySQL backend) --> Exim thru 127.0.0.1 port 2525 (instead of -oMr 
> spam-scanned approach)

Just out of curiosity: why not use dspamc as a filter for a
pipe-delivery to something like "[...]exim -oMr spam-scanned -bS", but
instead chose this approach? I fail to see the gaining...

> It seems that I have to provide something in ClientIdent, that is used 
> to identify DSPAM itself to the MTA, but I have :
> 
> 2008-03-05 18:10:31 H=(localhost) [127.0.0.1] sender verify fail for 
> <[EMAIL PROTECTED]>: Unrouteable address
> 2008-03-05 18:10:31 H=(localhost) [127.0.0.1] F=<[EMAIL PROTECTED]> 
> rejected RCPT <[EMAIL PROTECTED]>: Sender verify failed

The message "[EMAIL PROTECTED]" should be enough hint I think. It's
unroutable, of course. But without your actual exim-configuration, it's
hard to tell what's really happening, because I'm afraid you might have
changed some email-addresses in your e-mail, so you don't get
spammed ;o) Let's see your config. Or... chose the pipe-approach -
which should be less overhead anyway.

Cheers

        - Mark

-- 
Fortune cookie of the hour:

You have not converted a man because you have silenced him.
                -- John Viscount Morley

Attachment: signature.asc
Description: PGP signature

Reply via email to