> However, I've read that it is possible that all *outgoing emails* send > by qmail will be added to notspam folder of assp. What option should I
In your case, assuming all the emails either from external MTAs or from authenticated clients are hitting ASSP before being proxied to qMail your setup is already ok; I mean... external MTA -> ASSP (25) -> qMail (587) auth client -> ASSP (25) -> qMail (587) so even if an authenticated client or a host authorized to relay will send emails to an external address ASSP will see it and use them for auto whitelisting and for notspam collection; then qMail will route the message to the intended recipient (either local or remote) As for the setup; I'd suggest you to move qMail to a different port like (say) 9125 then setup ASSP this way listenPort 25 smtpDestination 127.0.0.1:9125 listenport2 587 smtpAuthServer 127.0.0.1:9125 EnforceAuth enabled the above means that all regular traffic will hit ASSP on port 25 and will be proxied to 127.0.0.1:9125 where qMail is running; also, authenticated traffic will be handled by ASSP on port 587, enforcing authentication for such connections and proxied (again) to 127.0.0.1:9125 At this point ensure to setup qMail to only allow authenticated clients to relay (along with whatever unauthenticated but trusted host IP which you want to allow to relay - if needed) and tell to your "customers" to use port 587 with authentication to send emails ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
