Re: [Declude.JunkMail] [Declude.Junkmail] MS SMTP LDAP Routing

[Matt]

John, Thanks for the info.  It appears that if this tool is to be used in a high volume environment, then the process of validating will need to be very efficient.  I'm guessing that AD is pretty quick to query, similar to both LDAP and DNS.  Access on the other hand is something that is currently causing me some issues in my hosting environment where someone has an ecommerce store that has outgrown their Access solution despite it only being a moderately trafficked site and the database only being 15 MB.  Just a simple page load on that site will hit almost 100% of dual PIII 1 GHz processors.  That will have to change :) I've been digging into this and it's apparent that there is some sort of MS SMTP SDK or resources provided so that a different application could be designed, possibly one that took a list from something as simple as a text file and loaded it into memory for use like this.  It might not even be all that hard to accomplish.  I've also found that you can in fact control the outgoing port on MS SMTP in the MetaBase, which means that you could have this sit on the same server as an IMail Gateway running on something besides port 25.  Looks like there might be a lot of possibilities here in using this as a pre-filter. Naturally though, things would be a whole lot easier if IMail could just simply be configured so that it doesn't take over every IP on the server.  Maybe we should all start a letter writing campaign to Ipswitch asking that they do this.  It would seem to be a simple enough change. Matt John Tolmachoff (Lists) wrote: The AD schema can be extended to include custom fields and such. One such item that comes to mind is contacts, which are not users but rather addressable objects in AD. Since AD is a database, you would not create a database within a database, but rather extend the schema of the database. However, warning. Extending and/or changing the schema is permanent and must be thoroughly tested to ensure there are no repercussions. For gateway domains not in AD, you might want to consider, if possible, a separate LDAP querry to a simple Access database. John Tolmachoff Engineer/Consultant/Owner eServices For You -----Original Message----- From: [EMAIL PROTECTED] [mailto:Declude.JunkMail- [EMAIL PROTECTED]] On Behalf Of Matt Sent: Monday, February 09, 2004 11:06 AM To: [EMAIL PROTECTED] Subject: Re: [Declude.JunkMail] [Declude.Junkmail] MS SMTP LDAP Routing Sandy, I recall checking this out once before when it was mentioned, probably by you. Somehow I figured that you would probably be the one that would know :) I do see the piece about ActiveDirectory integration. I'm not an AD expert by any means, and I'm wondering if it's plausible to create a database of sorts within AD that isn't the equivalent of your accounts. This would be a great place to store such information if possible. I could then create an application that essentially dumped the IMail users to a file, and users from a separate database for gatewayed domains, and then imported it into AD for use with something like this. Also, now that it's clear that MS SMTP can be used for envelope rejection, I'm wondering how easy it would be to write an application that pulled this information from any number of sources (IMail's LDAP for instance). I've got a programmer buddy that I'm sure could handle this if I gave him the right pointers. It's not that ORF is expensive, it's quite cheap, but I'm really only looking for envelope rejection of bad accounts and also potentially for dictionary attacks through some mechanism designed to detect them. Any idea about what is used to tap into the MS SMTP service to make these extensions? Right now I have no legitimate need for this due to my traffic, however my business is growing and I would like to stay ahead of the game and make plans for the future. Envelope rejection for gatewayed domains would be a big bandwidth and processor saver, and it doesn't look like IMail is headed in the direction of providing such a tool beyond their own accounts. Thanks, Matt Sanford Whiteman wrote: LDAP routing cannot be used for (and isn't designed for) that purpose. If you're looking to integrate MS SMTP with your userbase, the best bet is ORF from Vamsoft, which offers AD-integrated envelope rejection. --Sandy -- ------------------------------------ Sanford Whiteman, Chief Technologist Broadleaf Systems, a division of Cypress Integrated Systems, Inc. mailto:[EMAIL PROTECTED] ------------------------------------ -- --- [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. -- ===================================================== MailPure custom filters for Declude JunkMail Pro. http://www.mailpure.com/software/ ===================================================== --- [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. --- [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. -- ===================================================== MailPure custom filters for Declude JunkMail Pro. http://www.mailpure.com/software/ =====================================================