> This sounds like an interesting tool. What if I can only apply it to
> some domains though?
That's totally fine. You're not required to have a complete recipient
list for all domains from the get-go. You simply enter wildcard-type
domain names like so, alongside the e-mail addresses:
@example.com
[EMAIL PROTECTED]
@example.net
[EMAIL PROTECTED]
The wildcard domain names function like your standard/existing
store-and-forward setup, with all the attendant backscatter and
scanning overhead... you won't get anything special out of them, but
you'll be able to pass the traffic with no probs.
> I'm pretty sure that Declude processes the traffic before the IMail
> product, so I need to nab it before it gets to Declude if I'm going
> to trim my resources. I'm not sure about SmarterMail, but I suspect
> the same. MSG gets handed to Declude, which calls up Sniffer and
> invURIBL, and then tosses it back into the MTA queue for mail
> handling.
> Unless I'm wrong, in which case I'll get tapped back in line. :)
It's not that you're wrong, that's just the "dumb" -- albeit
traditional, and advised by Ipswitch -- way to do it. The "smart" way
to do it, avoiding all the processing overhead and backscatter, is to
use true domains in your MTA, rather than non-recipient-aware
forwarding domains, creating a user alias forwarding to each user on
the remote mailbox server.
My exchange2aliases and ldap2aliases scripts (see my sig) are intended
for the above setup, though both use LDAP to get the addresses from
the mailbox server (either Active Directory LDAP or IMail's bundled
OpenLDAP) and therefore are better suited to a controlled environment
where the IMail MX and the mailbox server are on the same company LAN.
If you're forwarding for a bunch of remote servers, and can only count
on plain text files, you could either (a) use 5XXSink; (b) toss
together your own version of ldap2aliases using ASCII input instead of
LDAP; or (c) my preference before (b): import your ASCII files into an
OpenLDAP install and run ldap2aliases against it. The reason I prefer
(c) to (b) is that having your recipient list served up by a proper
LDAP directory service allows you to access that same service in
future from any LDAP client, such as Postfix, et al. MXs, and with
LDAP, caching and indexing are all built-in.
--Sandy
------------------------------------
Sanford Whiteman, Chief Technologist
Broadleaf Systems, a division of
Cypress Integrated Systems, Inc.
e-mail: [EMAIL PROTECTED]
SpamAssassin plugs into Declude!
http://www.imprimia.com/products/software/freeutils/SPAMC32/download/release/
Defuse Dictionary Attacks: Turn Exchange or IMail mailboxes into IMail Aliases!
http://www.imprimia.com/products/software/freeutils/exchange2aliases/download/release/
http://www.imprimia.com/products/software/freeutils/ldap2aliases/download/release/
---
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.
