Hi,
On Mon, 24.01.2005 at 10:15:23 -0300, Nicolas Lopez <[EMAIL PROTECTED]> wrote: > That's a very nice approach. > May be I'll get on it on my spare time. > Mensaje citado por raymond <[EMAIL PROTECTED]>: > > What might be a more useful approach to this sort of thing is to allow > > setting > > alternate rcpthosts and locals hashes via an environmental variable similar > > to what's done with QMAILQUE. This would allow you to run any number of > > SMTP > > daemons with different mail handling policies for subsets of domains. (ie > > spam scanning, dnsrbl options etc. might differ to satisfy different > > customers.) It would also allow you to do what your doing with qmail-verify > > for non-local domains. I've also thought about this various times, but didn't yet get around doing it. Imho several pieces are needed, so the "easiest" way to do it would be to just say something like QCONTROL="/var/qmail/control/1" for the settings to smtpd #1, and so on for the other smtpds (also being able to ask different LDAP servers etc). The only piece to keep in mind would be to have only _one_ qmail-send running... ;-) And, I'm not really convinced if this effort is worth the effect, since individual spam & virus filtering options could also easily be achieved w/o resorting to hacking qmail-smtpd. Eg. clone your instance of qmail-scanner-queue.pl and tweak them. Afterwards, just run several qmail-smtpds with individual settings for QMAILQUEUE. Or, one could make the schema somewhat bigger, having fields for this kind of stuff, thus eliminating the need to set these items on a per-daemon-basis (since you then could do it on a per-user basis). Eg. these optional fields could be queried from third-party programs like spam filters, too (eg. SpamAssassin has recently aquired an LDAP backend module, and I'm about sure that something similar could be hacked directly into qmail-scanner). Best, --Toni++
