Re: [Exim] exim + sophos ...

Top Page
Delete this message
Reply to this message
Author: Odhiambo Washington
Date:  
To: Andrew D
CC: Exim Users
Subject: Re: [Exim] exim + sophos ...
* Andrew D <awd@???> [20010518 16:14]: writing on the subject 'Re: [Exim] exim + sophos ...'
Andrew> ----- Original Message -----
Andrew> Sent: Friday, May 18, 2001 9:18 PM
Andrew> Subject: [Exim] exim + sophos ...
Andrew>
Andrew>
Andrew> > I'm looking for customers, which use exim as MailRelay and
Andrew> > the sophos mailchecker package for virus checking...
Andrew> >
Andrew> I don't use sophos, but I do use virus scanning using a script/app called
Andrew> amavis ( www.amavis.org ) which does have support for it as well as many
Andrew> other *nix virus scanners. (you can even pass each email through multiple
Andrew> scanners (I think))
Andrew> HTH
Andrew> cya
Andrew> Andrew


Hi Andrew,

I am having a problem in the Amavis - Exim axis. Hopefully you can help
me out. I added the lines from README.exim to my configure file and the
end result is that no deliveries were taking place at all!!
I posted to this list and got 'a few bones thrown at me' - but not in a
bad way though. I posted to the list because I saw the problem was my
(inexperience) with exim. May I kindly attach my e-mail so that you may
take a look and advise. So far the amavis director causes deliveries to
stop. If I disable it things do work but I want to scan both ways.
I installed the amavis-perl-11


MTIA

[attachment]

* Philip Hazel <ph10@???> [20010517 12:14]: writing on the subject 'Re: [Exim] Problem After AMAVIS'
Philip> On Thu, 17 May 2001, Odhiambo Washington wrote:
Philip>
Philip> > wash:~$ exim -d9 -bt root
Philip> > Exim version 3.22 debug level 9 uid=3D1000 gid=0
Philip> > probably Berkeley DB version 1.8x (native mode)
Philip> > Actual local interface address is 62.8.64.108 (xl0)
Philip> > Actual local interface address is 212.49.74.108 (xl0)
Philip> > Actual local interface address is 127.0.0.1 (lo0)
Philip> > root@???
Philip> >   deliver to root in domain alligator.wananchi.com
Philip> >   director = amavis_director, transport = amavis
Philip> > wash:~$
Philip> >
Philip> > Under normal circumstance, that is in the absence of the Amavis d=
irector,
Philip> > the scenario would be like this:
Philip> >
Philip> > alligator# exim -bt root
Philip> > admin@???
Philip> >     <-- root@???
Philip> >   deliver to admin in domain alligator.wananchi.com
Philip> >   director = localuser, transport = local_delivery
Philip> >
Philip> > So there seems to be an issue with the amavis director which I am
Philip> > not able to see???
Philip>
Philip> Well, it is going to deliver the message to amavis using the "amavis"
Philip> transport. Is this what you want or not? After all, you have set up your
Philip> first director as
Philip>
Philip> amavis_director:
Philip>   condition = "${if eq {$received_protocol}{scanned-ok} {0}{1}}"
Philip>   driver = smartuser
Philip>   transport = amavis
Philip>
Philip> so it will always do that unless the received protocol is "scanned-ok".
Philip> When amavis sends the message back, it should set the protocol value to
Philip> "scanned-ok". You can test what will happen then with
Philip>
Philip> exim -oMr scanned-ok -bt root



Hello Philip,

Please allow me to revisit the amavis issue. I wrote back to you yesterday
that the test above gave desired results while testing for the
aliases. What I did not notice at that time is that with this director in
place, not even local deliveries were taking place! All the mail for any
local account got stuck.=20
I was in communication with the maintainer for the amavis-perl port on
FreeBSD and he says he explicitly disabled the port from building with
support for exim because, and I beg to quote his e-mail:

[quote]

"From: Roman Shterenzon <roman@???>
To: Odhiambo Washington <wash@???>
In-Reply-To: <20010518160711.E18179@???>
Organization: Xpert UNIX Systems Ltd.
Subject: Re: [Exim] Problem After AMAVIS

The reason qmail, exim and postfix were disabled is that I didn't have
clear instructions about how to configure them as a relay with scanning.
The port aim was to set up a system where all mail, and not just local
will be scanned.

--Roman Shterenzon, UNIX System Administrator and Consultant
[ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ]

[/quote]

May I humbly request your assistance on this one. I am not an expert coder
to handle this situation.
He says that he'll be happy to give maximum support for Exim if he can be
given the directions on how scanning in both directions can be achieved.

MTIA

Have a fabulous weekend.


-Wash

--
Odhiambo Washington Wananchi Online Ltd.,
wash@??? 1st Flr Loita Hse
Tel: 254 2 313985 Loita Street.,
Fax: 254 2 313922 PO Box 10286, 00100-NAIROBI,KE.


[/attachment]

Andrew>
Andrew>
Andrew>
Andrew> --
Andrew> Of course there's no reason for it,
Andrew> it's just our policy.
Andrew>
Andrew>
Andrew> --
Andrew> ## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at http://www.exim.org/ ##

-Wash

--
Odhiambo Washington Wananchi Online Ltd.,
wash@??? 1st Flr Loita Hse
Tel: 254 2 313985 Loita Street.,
Fax: 254 2 313922 PO Box 10286, 00100-NAIROBI,KE.

Connector Conspiracy, n:
    [probably came into prominence with the appearance of the
KL-10, none of whose connectors match anything else] The tendency of
manufacturers (or, by extension, programmers or purveyors of anything)
to come up with new products which don't fit together with the old
stuff, thereby making you buy either all new stuff or expensive
interface devices.