Re[2]: [Declude.JunkMail] Valid Senders - Best Declude Practices
> 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.
RE: [Declude.JunkMail] Valid Senders - Best Declude Practices
About a year ago, I wrote a C++ (no external dependencies) external-plus (whitelist/blacklist) add-in for Declude that supports the following: 1. Whitelist / Blacklist at company level. 2. Whitelist / Blacklist at user level (has support for aliases via redirection) 3. Whitelist / Blacklist at a group level (supported by redirection) 4. Includes validating recipients (If there is one valid recipient, then the message is allowed) The program supports filtering the to, from and subject fields, as well as, IP addresses in the headers. For the to, from and subject fields, the software supports matching using StartsWith, EndsWith, Contains, is (equal), NotStartsWith, NotEndsWith, NotContains, IsNot and Regex For IP addresses, it supports the following formats: single address (192.168.1.3) and multiple addresses (192.168.1.3\255.255.255.255 [single address], 192.168.1.3\32 [single address], 192.168.1\255.255.255.0 [single class "C"] or 192.168.1.5\24 [single class "C"] or 192.168.1.5\255.255.255.254 [two class "C" ranges] or 192.168.1.5\25 [two class "C" ranges] and so on. It also has a valid recipient list for the domain and has full logging capabilities. Like others we are also preprocessing our email and we are using "xWall". Using xWall, it blocks in over 90% of our incoming email. If any one is interested in the software, please let me know and I would be glad to share it. David Cornerstone Computer Solutions, Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Cummins Sent: Saturday, December 30, 2006 2:35 PM To: declude.junkmail@declude.com Subject: RE: [Declude.JunkMail] Valid Senders - Best Declude Practices > 5XXSink is a connection-time event sink for MS SMTP This sounds like an interesting tool. What if I can only apply it to some domains though? If I set this up on the same box as SmarterMail, and used the MS SMTP to forward to SmarterMail (what, on a different port I guess?) then am I correct in guessing that I have to have a comprehensive list of all recipients? I don't think I'll be able to get all the Exchange Servers I service to play nice right away. > OTOH, if you were using IMail as the MTA wrapper for Declude, it > would be possible to do all this stuff natively within IMail by using > a "smart store-and-forward" setup and some sync scripts for your S&F > domains. > > The same logic seems possible for SM, and would certainly be the "best > way" in theory; but if you've already probed their forums, I assume > there's no established "cookbook" from that side. 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. :) In iMail you set up Store and Forward by entering the IP in the SMTP security, and then making an entry in the Windows Host file. In SmarterMail you just enter the IP/domain name in "Domain Forwarding" - no place to really put any e-mail addresses for either product, that I know of anyway. :( You know, Declude Pro handles a whitelist.txt and a blacklist.txt on a per domain config. It might be nice to have a validRecipients.txt file too. Yeah, it's sort of useless for POP/IMAP domains but it would sure be handy for store and forward relay. It would really cut down on my resource load if that could be one of the first tests processed, so all the other little engines don't have to waste their time. > --Sandy Thanks for your input, Sandy! You too, Markus, Mark and Herb. Alligate looks like an impressive gateway product, I'll keep it in mind - and I'm thinking of upgrading the hardware on that box now as well. It wasn't all that shabby to begin with though. -- Michael Cummins 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/rel ease / Defuse Dictionary Attacks: Turn Exchange or IMail mailboxes into IMail Aliases! http://www.imprimia.com/products/software/freeutils/exchange2aliases/dow nloa d/release/ http://www.imprimia.com/products/software/freeutils/ldap2aliases/downloa d/re lease/ --- 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
RE: [Declude.JunkMail] Valid Senders - Best Declude Practices
> 5XXSink is a connection-time event sink for MS SMTP This sounds like an interesting tool. What if I can only apply it to some domains though? If I set this up on the same box as SmarterMail, and used the MS SMTP to forward to SmarterMail (what, on a different port I guess?) then am I correct in guessing that I have to have a comprehensive list of all recipients? I don't think I'll be able to get all the Exchange Servers I service to play nice right away. > OTOH, if you were using IMail as the MTA wrapper for Declude, it > would be possible to do all this stuff natively within IMail by using > a "smart store-and-forward" setup and some sync scripts for your > S&F domains. > > The same logic seems possible for SM, and would certainly be the "best > way" in theory; but if you've already probed their forums, I assume > there's no established "cookbook" from that side. 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. :) In iMail you set up Store and Forward by entering the IP in the SMTP security, and then making an entry in the Windows Host file. In SmarterMail you just enter the IP/domain name in "Domain Forwarding" - no place to really put any e-mail addresses for either product, that I know of anyway. :( You know, Declude Pro handles a whitelist.txt and a blacklist.txt on a per domain config. It might be nice to have a validRecipients.txt file too. Yeah, it's sort of useless for POP/IMAP domains but it would sure be handy for store and forward relay. It would really cut down on my resource load if that could be one of the first tests processed, so all the other little engines don't have to waste their time. > --Sandy Thanks for your input, Sandy! You too, Markus, Mark and Herb. Alligate looks like an impressive gateway product, I'll keep it in mind - and I'm thinking of upgrading the hardware on that box now as well. It wasn't all that shabby to begin with though. -- Michael Cummins 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/downloa d/release/ http://www.imprimia.com/products/software/freeutils/ldap2aliases/download/re lease/ --- 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 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.
Re: [Declude.JunkMail] Valid Senders - Best Declude Practices
> I wrote a Cold Fusion script that looks for these silly text files > every so many minutes and then parses the crappy, cluttered thing > into a nice clean CSV for me, and now I can do anything I want with > it. I imagine that someday I'll use it in conjunction with the > gateway, but hey, I have this information right now. > What would be the best way to use this information with Declude? I'll answer your query without padding your stated needs. 5XXSink is a connection-time event sink for MS SMTP (that is, a plug-in written to the MS API) expressly designed for high-performance recipient validation against a text file, with changes taking effect immediately. Simple to operate: you maintain lists of valid recipient domains and users, it rejects anything not on that list. You can set up an MS SMTP instance as your MX, same-box, forwarding to SmarterMail. Whatever else you do with MS SMTP is up to you, 5XXSINK is just built for it because it's a highly reliable and OS-bundled MTA. 5XXSINK is free. It is in prod at numerous sites with no reported problems. (I'm the primary developer of this tool, and all of our downloadable tools are free software.) http://www.imprimia.com/products/software/freeutils/5xxsink/download/release Later, when it comes to building your gateway, you know you'll have a plethora of options across OSs and vendors/communities. For now, 5XXSINK is the fastest existing method I know of directly. OTOH, if you were using IMail as the MTA wrapper for Declude, it would be possible to do all this stuff natively within IMail by using a "smart store-and-forward" setup and some sync scripts for your S&F domains. The same logic seems possible for SM, and would certainly be the "best way" in theory; but if you've already probed their forums, I assume there's no established "cookbook" from that side. Note that there are many other products basically equivalent to MS SMTP + 5XXSINK insofar as this need is concerned: they're easy-to-maintain, lightweight Windows-based MTAs that perform recipient validation from text files and thus can serve the same purpose as an MX running on the same box as your mailbox server. Mind you, their *additional* features, footprint, and scaleability vary enormously, but here they would all fill the bill. Mercury/32's SMTP module is one I can def'ly vouch for. --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.
Re: [Declude.JunkMail] Valid Senders - Best Declude Practices
Yes, we do it to filter for some customers that want to run their own mail server but not have to deal with managing virus and spam filters. We use the same smartermail server to host about 80 domains/1400 mailboxes and do domain forwarding for another 10 or so domains with about 500 addl mailboxes. Herb John T (Lists) wrote: Does SmarterMail allow you to create aliases for a domain, such as [EMAIL PROTECTED] is an alias for [EMAIL PROTECTED]? John T eServices For You "Life is a succession of lessons which must be lived to be understood." Ralph Waldo Emerson (1802-1882) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Michael Cummins Sent: Thursday, December 28, 2006 1:44 PM To: declude.junkmail@declude.com Subject: [Declude.JunkMail] Valid Senders - Best Declude Practices OK. I have a box that I use as an incoming relay for about 30 or so Exchange servers that all live out in the wild. I run Smarter Mail, Declude, Message Sniffer, INVURIBL, F-Prot and all kinds of good stuff before I pass it along to the Exchange server with SmarterMail domain forwarding. I am getting my ass kicked by volume because the mail server accepts any address and forwards it along; most of which of course are addresses that don't exist. I'm building a gateway box in the near future, which will help keep the incoming fluff down a bit, I'm sure, but what I really need to do is to implement some kind of valid recipient list. I doubt that I'll be able to LDAP all over God's green earth with any kind of reliability or speed. Since the gateway won't be implemented for a few weeks, I'm been playing with things to get ready for it, namely, how to get valid sender lists from such a disparate group of Exchange servers. So. I patched together this _vbscript_ that exports a list of exchange addresses using LDAP into a text file. It runs as a WinCron job. I created a batch file that uploads it to one of my Cold Fusion servers. That runs as a WinCron job, too. I wrote a Cold Fusion script that looks for these silly text files every so many minutes and then parses the crappy, cluttered thing into a nice clean CSV for me, and now I can do anything I want with it. I imagine that someday I'll use it in conjunction with the gateway, but hey, I have this information right now. What would be the best way to use this information with Declude? Ideally, it should be implemented on a per domain basis, in case I can't get some Exchange servers to play nice with me. Eventually I suppose it will be mandatory, I'm sure, but not right now when I am coming up with best practices, eh? So do I set up each text file for each domain as a separate filter? And then only use it in the applicable per domain junkmail file? Is that the best way to do it? Or am I making Declude work too hard? I would really love any suggestions you might have. Thanks! -- Michael Cummins --- 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 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. -- Herb Guenther Lanex, LLC www.lanex.com (262)789-0966x102 Office (262)780-0424 Direct This e-mail is confidential and is for the use of the intended recipient(s)only. If you are not an intended recipient please advise us of our error by return e-mail then delete this e-mail and any attached files. You may not copy, disclose or use the contents in any way. ---This E-mail came from the Declude.JunkMail mailing list. Tounsubscribe, just send an E-mail to [EMAIL PROTECTED], andtype "unsubscribe Declude.JunkMail". The archives can be foundat http://www.mail-archive.com.
Re: [Declude.JunkMail] Valid Senders - Best Declude Practices
Hi Mike; I feel your pain, processing 200,000 messages a day for about 15K good ones. It sounds to me like your server may just be underpowered. We just upgraded our server to a new unit moving from Windows 2000 to 2003 R2 and to Dual, Dual core Opterons, even with only one CPU on the mobo now I can tell that we would be able to handle a number like 1M messages a day with Declued/sniffer/smartermail just fine. The better hardware gives you more licensing bang for the buck. Herb Michael Cummins wrote: I can strongly consider Alligate in front of Declude. So let's say I build a dedicated Alligate box to live in front of my two Declude enabled servers. How much of a load would it be able to handle? I would need it to handle close to 250k messages per day (current combined load) with room to grow, and it looks like Alligate is yet-another-thousand-dollar-thing-that-will-need-yearly-subscriptions-of-hun dreds-of-dollars. I'd be happier if I could just send my money to one company. So would Declude, I'm sure. But hey. If that's what you gotta do. I was thinking of using a home built postfix gateway to go in front of the boxen, and if I need more I was just going to add more identical postfix boxen a la round robin DNS. Bad idea? Good idea? But my customers could use some help today, which is why I was thinking of using Declude to do some recipient verification. Conceptually, that would cut down the work load considerably, right? I've been having trouble with my Message Sniffer (in persistent mode) going into a cascading failure during peak periods because of the volume; so I leave it off most of the time, which is a huge waste. I'm just wondering how to go about using Declude to do this. Thanks for all the feedback! I've got an open mind. -- Michael Cummins --- 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. -- Herb Guenther Lanex, LLC www.lanex.com (262)789-0966x102 Office (262)780-0424 Direct This e-mail is confidential and is for the use of the intended recipient(s)only. If you are not an intended recipient please advise us of our error by return e-mail then delete this e-mail and any attached files. You may not copy, disclose or use the contents in any way. ---This E-mail came from the Declude.JunkMail mailing list. Tounsubscribe, just send an E-mail to [EMAIL PROTECTED], andtype "unsubscribe Declude.JunkMail". The archives can be foundat http://www.mail-archive.com.
Re: [Declude.JunkMail] Valid Senders - Best Declude Practices
Mike, You are making your life more difficult by approaching it this way. Since you gateway, you need recipient validation, and that alone will drop your utilization by at least half if not much more. You would also benefit from pre-scanning. Alligate does both things painlessly. Just ask them for a trial license and read their manual pages. It's not that expensive either. Matt Michael Cummins wrote: I can strongly consider Alligate in front of Declude. So let's say I build a dedicated Alligate box to live in front of my two Declude enabled servers. How much of a load would it be able to handle? I would need it to handle close to 250k messages per day (current combined load) with room to grow, and it looks like Alligate is yet-another-thousand-dollar-thing-that-will-need-yearly-subscriptions-of-hun dreds-of-dollars. I'd be happier if I could just send my money to one company. So would Declude, I'm sure. But hey. If that's what you gotta do. I was thinking of using a home built postfix gateway to go in front of the boxen, and if I need more I was just going to add more identical postfix boxen a la round robin DNS. Bad idea? Good idea? But my customers could use some help today, which is why I was thinking of using Declude to do some recipient verification. Conceptually, that would cut down the work load considerably, right? I've been having trouble with my Message Sniffer (in persistent mode) going into a cascading failure during peak periods because of the volume; so I leave it off most of the time, which is a huge waste. I'm just wondering how to go about using Declude to do this. Thanks for all the feedback! I've got an open mind. -- Michael Cummins --- 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 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.
RE: [Declude.JunkMail] Valid Senders - Best Declude Practices
> I can strongly consider Alligate in front of Declude. So let's say I build a dedicated Alligate box to live in front of my two Declude enabled servers. How much of a load would it be able to handle? I would need it to handle close to 250k messages per day (current combined load) with room to grow, and it looks like Alligate is yet-another-thousand-dollar-thing-that-will-need-yearly-subscriptions-of-hun dreds-of-dollars. I'd be happier if I could just send my money to one company. So would Declude, I'm sure. But hey. If that's what you gotta do. I was thinking of using a home built postfix gateway to go in front of the boxen, and if I need more I was just going to add more identical postfix boxen a la round robin DNS. Bad idea? Good idea? But my customers could use some help today, which is why I was thinking of using Declude to do some recipient verification. Conceptually, that would cut down the work load considerably, right? I've been having trouble with my Message Sniffer (in persistent mode) going into a cascading failure during peak periods because of the volume; so I leave it off most of the time, which is a huge waste. I'm just wondering how to go about using Declude to do this. Thanks for all the feedback! I've got an open mind. -- Michael Cummins --- 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.
RE: [Declude.JunkMail] Valid Senders - Best Declude Practices
In this case, all of the domains are simply listed in the "Domain Forwarding" portion of the SmarterMail config, and Declude operates with Outbound Scanning on. The SmarterMail server is not actually the hosting server, it is just forwarding the mail to the Exchange servers, so no domains or e-mail addresses are set up there. I run an IMail 2006.1 server for my POP/IMAP needs, but I am taking a closer and closer look at SmarterMail for that, too. Since I haven't used SmarterMail for POP/IMAP, I can only guess that it handles Aliases like any other POP/IMAP server. -- Michael Cummins -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John T (Lists) Sent: Thursday, December 28, 2006 5:27 PM To: declude.junkmail@declude.com Subject: RE: [Declude.JunkMail] Valid Senders - Best Declude Practices Does SmarterMail allow you to create aliases for a domain, such as [EMAIL PROTECTED] is an alias for [EMAIL PROTECTED] John T eServices For You "Life is a succession of lessons which must be lived to be understood." Ralph Waldo Emerson (1802-1882) --- 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.
RE: [Declude.JunkMail] Valid Senders - Best Declude Practices
Does SmarterMail allow you to create aliases for a domain, such as [EMAIL PROTECTED] is an alias for [EMAIL PROTECTED] John T eServices For You "Life is a succession of lessons which must be lived to be understood." Ralph Waldo Emerson (1802-1882) > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael > Cummins > Sent: Thursday, December 28, 2006 1:44 PM > To: declude.junkmail@declude.com > Subject: [Declude.JunkMail] Valid Senders - Best Declude Practices > > OK. > > I have a box that I use as an incoming relay for about 30 or so Exchange > servers that all live out in the wild. I run Smarter Mail, Declude, Message > Sniffer, INVURIBL, F-Prot and all kinds of good stuff before I pass it along > to the Exchange server with SmarterMail domain forwarding. > > I am getting my ass kicked by volume because the mail server accepts any > address and forwards it along; most of which of course are addresses that > don't exist. > > I'm building a gateway box in the near future, which will help keep the > incoming fluff down a bit, I'm sure, but what I really need to do is to > implement some kind of valid recipient list. I doubt that I'll be able to > LDAP all over God's green earth with any kind of reliability or speed. > > Since the gateway won't be implemented for a few weeks, I'm been playing > with things to get ready for it, namely, how to get valid sender lists from > such a disparate group of Exchange servers. > > So. > > I patched together this VBscript that exports a list of exchange addresses > using LDAP into a text file. > > It runs as a WinCron job. > > I created a batch file that uploads it to one of my Cold Fusion servers. > > That runs as a WinCron job, too. > > I wrote a Cold Fusion script that looks for these silly text files every so > many minutes and then parses the crappy, cluttered thing into a nice clean > CSV for me, and now I can do anything I want with it. I imagine that > someday I'll use it in conjunction with the gateway, but hey, I have this > information right now. > > What would be the best way to use this information with Declude? > > Ideally, it should be implemented on a per domain basis, in case I can't get > some Exchange servers to play nice with me. Eventually I suppose it will be > mandatory, I'm sure, but not right now when I am coming up with best > practices, eh? > > So do I set up each text file for each domain as a separate filter? And > then only use it in the applicable per domain junkmail file? > > Is that the best way to do it? > > Or am I making Declude work too hard? > > I would really love any suggestions you might have. Thanks! > > -- Michael Cummins > > > > --- > 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 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.
[Declude.JunkMail] Valid Senders - Best Declude Practices
OK. I have a box that I use as an incoming relay for about 30 or so Exchange servers that all live out in the wild. I run Smarter Mail, Declude, Message Sniffer, INVURIBL, F-Prot and all kinds of good stuff before I pass it along to the Exchange server with SmarterMail domain forwarding. I am getting my ass kicked by volume because the mail server accepts any address and forwards it along; most of which of course are addresses that don't exist. I'm building a gateway box in the near future, which will help keep the incoming fluff down a bit, I'm sure, but what I really need to do is to implement some kind of valid recipient list. I doubt that I'll be able to LDAP all over God's green earth with any kind of reliability or speed. Since the gateway won't be implemented for a few weeks, I'm been playing with things to get ready for it, namely, how to get valid sender lists from such a disparate group of Exchange servers. So. I patched together this VBscript that exports a list of exchange addresses using LDAP into a text file. It runs as a WinCron job. I created a batch file that uploads it to one of my Cold Fusion servers. That runs as a WinCron job, too. I wrote a Cold Fusion script that looks for these silly text files every so many minutes and then parses the crappy, cluttered thing into a nice clean CSV for me, and now I can do anything I want with it. I imagine that someday I'll use it in conjunction with the gateway, but hey, I have this information right now. What would be the best way to use this information with Declude? Ideally, it should be implemented on a per domain basis, in case I can't get some Exchange servers to play nice with me. Eventually I suppose it will be mandatory, I'm sure, but not right now when I am coming up with best practices, eh? So do I set up each text file for each domain as a separate filter? And then only use it in the applicable per domain junkmail file? Is that the best way to do it? Or am I making Declude work too hard? I would really love any suggestions you might have. Thanks! -- Michael Cummins --- 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.