> This of course brings up another question: Is there a way for
> Declude JunkMail to find out accurately if the sender is really a
> local user or not?
If by sender you mean the envelope sender, and not the username used
for SMTP AUTH, I don't see why not. If the domain is a local domain,
the IMail userbase is certainly available to applications running on
the server (with the exception of peering setups). So I'd say the
problem is not the _availability_ of the userbase per se, but the
resources utilized by such lookups against slow/remote userbases.
There've been a couple of threads on the IMail Forum about this, and
each time it comes up as if it were a brand-new function to be done by
IMail itself, I point out that the code is clearly already present:
this exact step is done by IMail when using the famously insecure
relay option 'Relay for Local Users,' but skipped when using the
mandatory AUTH/IP options, and of course skipped for non-relayed mail.
Just a little reshuffling on their end, and...:)
I think it might be better to start putting pressure on Ipswitch
through the IMail Forum than by trying to do the lookups using
Declude's process-per-message architecture.
--Sandy
------------------------------------
Sanford Whiteman, Chief Technologist
Broadleaf Systems, a division of
Cypress Integrated Systems, Inc.
e-mail: [EMAIL PROTECTED]
SpamAssassin plugs into Declude!
http://www.mailmage.com/download/software/freeutils/SPAMC32/Release/
---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". The archives can be found
at http://www.mail-archive.com.
