> I'm not dumping on LDAP, I think it can be very useful, however in
> this case, is it really necessary? Why not just support loading a
> text file into memory and using that?
Because it's poor architecture that I wouldn't trust on my mailserver.
> It's the lowest common denominator...
Yep, that's the problem, all right. :)
> The only reason not to use text files would be a technical
> limitation, but I'm not suggesting that it be accessed once per
> message, so that isn't at issue.
Then you clearly don't see the _other_ technical problems involved.
Disk I/O is not the primary problem.
> I would certainly look to VAMsoft for this application if they
> supported text files...
Well, you _can_ use ORF for this! Just use their "everybody but"
recipient blacklist, whose addresses are stored in the .INI file and
read once at service start (ORF service, not SMTP service). Every time
you update the file, net restart ORF. It's _already_ there for you in
ORF if this is the way you want to swing it.
I believe that if you have a single domain, AD via LDAP is the better
way to go. As a longtime LDAP user, I believe your concerns about the
complexity of having a built-in LDAP service running with the sole
purpose of MX user lookup are unfounded.
--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.
