Doug Traylor ([EMAIL PROTECTED]) wrote: > Whitelisting has nothing to do with Internal->Internal or local->local mail, > it is only for External->Internal mail. Communications between internal > employees is different then business comunication from the world to us so > the added non-spam generated email is not very pertinent in a bayesian > standpoint. All outgoing email auto-whitelists the external recipients as > it should.
I'm aware of all this and certainly don't route our local-to-local mail via ASSP by choice - it's just that I currently don't seem to have a choice, read on. > It has been done for some that manage multiple domains, but for me there is > no need. There is no need for ASSP to handle any internal email period. > Even if we had external users(not physically connected to our internal > network), we would have their email clients connect directly to our MTA on > auth port 587 that wuold then send from the MTA through ASSP the same way > for outgoing only. All outgoing email is routed from our MTA->ASSP->SMTP > delivery service->Internet. This also works with our MTA's webmail > application where there is no client app to connect to ASSP. Let me explain our setup and then ask you for ideas on how to improve the situation: We're running eGroupWare as MUA (webmail), it lives on a qmail server, and uses Courier IMAP as MDA. We have a separate server for mail scanning, ASSP receives Inbound mail here, and passes it on to Vexira (VAMS) which does virus and spam (now disabled) filtering, and then passes mail on to the qmail server. Prior to installing ASSP, eGroupWare was configured to deliver locally to the qmail server, which would then either deliver to a local mailbox (for local mail), or directly (without passing through the scanning server) to the intended recipient's (for external mail) mail server. eGroupWare can only be configured for a single SMTP destination server for sent mail - it can't sent local mail one way and external mail another way. So when I installed ASSP, I had to direct all mail being sent by eGroupWare to ASSP (in order to utilise auto-whitelisting), which would still pass all this on to Vexira, and then on to qmail, which would again deliver either locally or externally depending on the recipient. Apart from installing a separate ASSP instance that handles only the mail sent by eGroupWare, the only other solution I can think of is to install yet another daemon on the qmail/eGroupWare server. This daemon's purpose would be to do just one thing: split local mail from external mail, local mail gets delivered to the qmail daemon, and external mail is passed on to ASSP. I then point eGroupWare to this daemon instead of to ASSP. Does this seem like a workable idea, any other (simpler) ideas? > > Doug Thanx for bearing with me, Francois. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Assp-user mailing list Assp-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-user
