-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 11 Nov 2004, Matt wrote:
> clamavsupport wrote: > > > > > 1. Client connects to CLAMav and sends auth info > > 2. CLAMav sets up a new ESMTP port 25 connection to the terminating MX > > and test user details for validity > > 3. Terminating MX that holds Authentication database (propriety > > database) sends response via ESMTP either authenticated or rejected > > 4. CLAMav based on response from terminating MX allows or denies the > > user the ability to relay thru the server. > > > Again, that is a Sendmail issue. Clamav in front of Sendmail, in this > fashion, should work as a transparent proxy, thereby passing all info to > Sendmail. > > Matt > _______________________________________________ > http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users > Maybe I'm missing something here but IMO some points :- 1) This is a sendmail issue. ClamAV scans for content it does not validate users nor does it deliver mail. clamav-milter scans mail. 2) To provide Auth-SMTP you need to validate the senders. You need a mechanism to do that. Why are you validating users for which the details are no available to you. 3) Why not have the terminating server do the scanning. It has the user info and could therefore both scan and validate. I actually do what you are wanting to do and my auth server uses SASL to validate from the main secure server. Jim :-) EMail : [EMAIL PROTECTED] GnuPG key : ftp://ftp.heartsine.co.uk/hst_gpg_public_keys/jim.allen.hst.gpg.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFBk5FFRdAZy0oJ0LwRAtbOAJ0bdZ86kWXLpAoZStNmKf0u9CD/wgCeNDIw sN0ua21XfU9NS5ueOX103cs= =wZV+ -----END PGP SIGNATURE----- _______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
