Re: [Declude.JunkMail] Razor
Do you need SA or something similar to invoke Razor or does it come into play more directly? As I was mentioning in my exchange with Bill, the Razor client portion is distributed as a few Perl apps (separate ones for checking, reporting, whitelisting, etc.) with numerous supporting .pm modules; the heavy-lifting is done in the .pms, which can also be called directly. As a clearly Perl-centric suite, it fits naturally into SpamAssassin, where it is, by far, most often deployed; SA users are assumed to be using Razor, or are told to do so before complaining about their catch rates! Under Unix variants, the apps such as razor-check can also be forked on their own, and wrapper scripts can be written to return results to a variety of calling MTAs. Unfortunately, it is not at all easy to get razor-check to work on Windows Perl interpreters; I think I'm one of the few to have gotten it working at all, but its reliability is still questionable (i.e. it frequently times out, though it does return correct results whenever it connects). I think this has to do with Perl's socket support, which is not equivalent on Windows and *nix (even though a vast number of other Perl areas work just as well on either platform). So the only reliable way that I know of to run Razor on Windows is to use one of the compiled (really, more like assembled) spamassassin.exe binaries that have the socket issues fixed up and Razor support inside. These exes, however, are necessarily bloated with Perl runtimes and the whole SpamAssassin enchilada, which means you are talking _major_ scan times per fork, even with all other SA tests turned off except for the Razor interface. Spamassassin.exe is simply a wrapped-up executable assembly of spamassassin.pl, and will not execute any faster than the .pl (it's just easier to roll out). Spamassassin.pl/.exe is the a standalone version of SA -- where a new spamassassin process is forked for every incoming mail -- which is not the way it should be run, even on Unix, though it appears to be even worse on Windows. Rather, SA should be launched via spamd, the client-server daemon, since that eliminates the huge overhead of Perl startup and module and rulebase loads; spamd is the only way to scale SA (okay, there are also third-party filtering daemons that support SA as well as other scanners, and replicate spamd's preloading functionality, but that's a whole other topic and completely on the *nix side). SPAMC32, a free Declude external test whose URL is in my sig, is a Windows client for spamd that was designed especially for Declude integration. It requires that you have a spamd running somewhere, and if you're going to need Razor support in your spamd, that somewhere is going to have to be a *nix box, as far as I know. OTOH, you could certainly demo Razor's accuracy by forking a bulky spamassassin.exe only against a corpus of false negatives. There are also a couple of (to my mind) dubious, low-adoption open-source SMTP proxies that claim to integrate Razor without SpamAssassin, but those are unproven in my book, and are likely too competitive to be appropriate on this list if they even work... but those might be another way to at least preview accuracy. HTH. --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] OT: Imail
Hi Mark, You could always modify the web templates so that they never see the link to the auto-responder page. I do this for other features that I don't want users to access. Hope this helps, Dean On 7/20/06, Mark Smith [EMAIL PROTECTED] wrote: I know this belongs on the IMAIL forum but I'm not subscribed there -- apologies in advance. Does anyone know of a way to globally disable the information manager so I can prevent users from setting up auto-responders? Thx --- 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. -- __ Dean Lawrence, CIO/Partner Internet Data Technology 888.GET.IDT1 ext. 701 * fax: 888.438.4381 http://www.idatatech.com/ Corporate Internet Development and Marketing Specialists --- 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] How to configure per-domain file for gateway domains
I am testing Declude acting as a gateway for domain on other server. The junkmail manual 4.0.8 says that global.cfg is the file used to configure the actions for outgoing email. But it also says To get around this, you can set up per-domain configuration files for the gateway domains.. I want to create a per-domain configuration file of actions for the outgoing e-mail. So I figured that creating a folder using the domain I am forwarding and a file global.cfg within that folder it will work. But it doesn't. Looking at at the debugged log file, Declude looks for the junkmail file at a per-user and per-domain basis (that is only use for incoming mail), but it doesn't look for for a global.cfg under a folder (domain) or user (global.cfg is used for outgoing e-mail) Bottom line: I don't know how to configure the outgoing actions as a per domain, per user. How does the configuration work? Could you please update the manual with that information? Thanks -Luis Arango --- 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] How to configure per-domain file for gateway domains
Add the following line to your global.cfg DOSENDERACTIONS ON Take the copy of your $default$.junkmail and rename it to $default$.sender (DOSENDERACTIONS ON uses the $default$.sender actions for OUTBOUND email rather than the OUTBOUND actions in the global.cfg) Likewise for per domain settings or per user setting ie. Alberti.sender David B www.declude.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Panda Consulting S.A. Luis Alberto Arango Sent: Friday, July 21, 2006 3:52 PM To: declude.junkmail@declude.com Subject: [Declude.JunkMail] How to configure per-domain file for gateway domains I am testing Declude acting as a gateway for domain on other server. The junkmail manual 4.0.8 says that global.cfg is the file used to configure the actions for outgoing email. But it also says To get around this, you can set up per-domain configuration files for the gateway domains.. I want to create a per-domain configuration file of actions for the outgoing e-mail. So I figured that creating a folder using the domain I am forwarding and a file global.cfg within that folder it will work. But it doesn't. Looking at at the debugged log file, Declude looks for the junkmail file at a per-user and per-domain basis (that is only use for incoming mail), but it doesn't look for for a global.cfg under a folder (domain) or user (global.cfg is used for outgoing e-mail) Bottom line: I don't know how to configure the outgoing actions as a per domain, per user. How does the configuration work? Could you please update the manual with that information? Thanks -Luis Arango --- 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] How to configure per-domain file for gateway domains
David, thank you very much. I tested it and now I understand how DOSENDRACTIONS work -I believe-. Finally I just used the default junkmail in the domain, something I thought it wasn't going to work, but it worked since I am using the box to domain forwarding (SM), so there is incoming email and declude looks for the default junmail file anyway., Definitely Declude has too many directives. I hope one day I can learn and fully use at least 20% of them. Problem solved. Declude is great. bye -Luis Arango -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Barker Sent: Viernes, 21 de Julio de 2006 02:57 p.m. To: declude.junkmail@declude.com Subject: RE: [Declude.JunkMail] How to configure per-domain file for gateway domains Add the following line to your global.cfg DOSENDERACTIONS ON Take the copy of your $default$.junkmail and rename it to $default$.sender (DOSENDERACTIONS ON uses the $default$.sender actions for OUTBOUND email rather than the OUTBOUND actions in the global.cfg) Likewise for per domain settings or per user setting ie. Alberti.sender David B www.declude.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Panda Consulting S.A. Luis Alberto Arango Sent: Friday, July 21, 2006 3:52 PM To: declude.junkmail@declude.com Subject: [Declude.JunkMail] How to configure per-domain file for gateway domains I am testing Declude acting as a gateway for domain on other server. The junkmail manual 4.0.8 says that global.cfg is the file used to configure the actions for outgoing email. But it also says To get around this, you can set up per-domain configuration files for the gateway domains.. I want to create a per-domain configuration file of actions for the outgoing e-mail. So I figured that creating a folder using the domain I am forwarding and a file global.cfg within that folder it will work. But it doesn't. Looking at at the debugged log file, Declude looks for the junkmail file at a per-user and per-domain basis (that is only use for incoming mail), but it doesn't look for for a global.cfg under a folder (domain) or user (global.cfg is used for outgoing e-mail) Bottom line: I don't know how to configure the outgoing actions as a per domain, per user. How does the configuration work? Could you please update the manual with that information? Thanks -Luis Arango --- 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. --- 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] How to configure per-domain file for gateway domains
I'm not sure why this would be the recommended method. I have always done this differently. If you create a folder under your Declude folder for the domain in question, and place a $Default$.junkmail file in it, that will handle the gatewayed domain's E-mail. So if this was example.com, you could create a file as C:\IMail\Declude\example.com\$Default$.junkmail Something did change somewhere in one of the versions where gatewayed E-mail stopped using the master $Default$.junkmail file and started using Global.cfg actions for gatewayed E-mail, but if you specify it with a per-domain config it will work. BTW, watch out for dictionary attacks. Those of us that have been doing this for more than a handful of domains have found that address validation is an absolute necessity. I'm sure that Sandy would recommend his free Exchange to Aliases scripting, but I would recommend either ORF, or Alligate Gateway for this, and Alligate Gateway is the easiest of all to configure to do validation since it can resolve in real-time off of the destination server and/or from an address flat file. Matt David Barker wrote: Add the following line to your global.cfg DOSENDERACTIONS ON Take the copy of your $default$.junkmail and rename it to $default$.sender (DOSENDERACTIONS ON uses the $default$.sender actions for OUTBOUND email rather than the OUTBOUND actions in the global.cfg) Likewise for per domain settings or per user setting ie. Alberti.sender David B www.declude.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Panda Consulting S.A. Luis Alberto Arango Sent: Friday, July 21, 2006 3:52 PM To: declude.junkmail@declude.com Subject: [Declude.JunkMail] How to configure per-domain file for gateway domains I am testing Declude acting as a gateway for domain on other server. The junkmail manual 4.0.8 says that global.cfg is the file used to configure the actions for outgoing email. But it also says To get around this, you can set up per-domain configuration files for the gateway domains.. I want to create a per-domain configuration file of actions for the outgoing e-mail. So I figured that creating a folder using the domain I am forwarding and a file global.cfg within that folder it will work. But it doesn't. Looking at at the debugged log file, Declude looks for the junkmail file at a per-user and per-domain basis (that is only use for incoming mail), but it doesn't look for for a global.cfg under a folder (domain) or user (global.cfg is used for outgoing e-mail) Bottom line: I don't know how to configure the outgoing actions as a per domain, per user. How does the configuration work? Could you please update the manual with that information? Thanks -Luis Arango --- 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. --- 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[2]: [Declude.JunkMail] How to configure per-domain file for gateway domains
I'm sure that Sandy would recommend his free Exchange to Aliases scripting, but I would recommend either ORF, or Alligate Gateway for this... But neither of your suggestions constitute adding address validation as a single function. They are standalone commercial products. Of course I would recommend using the *free* ldap2aliases, which couldn't be easier to run on an existing IMail server with absolutely zero overhead, or if one wanted to dip into rolling out a gateway, I would recommend the *free* 5XXSINK plug-in for IIS SMTP, rather than spending money on competitive products whose functions are well in excess of the address validation specification. --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] How to configure per-domain file for gateway domains
Matt, thank you very much for your answer and your suggestions regarding how to prevent dictionary attacks. They will be very useful. Btw: I used the default.junkmail file under the domain folder and it worked, just like you just wrote. -Luis Arango -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt Sent: Viernes, 21 de Julio de 2006 03:50 p.m. To: declude.junkmail@declude.com Subject: Re: [Declude.JunkMail] How to configure per-domain file for gateway domains I'm not sure why this would be the recommended method. I have always done this differently. If you create a folder under your Declude folder for the domain in question, and place a $Default$.junkmail file in it, that will handle the gatewayed domain's E-mail. So if this was example.com, you could create a file as C:\IMail\Declude\example.com\$Default$.junkmail Something did change somewhere in one of the versions where gatewayed E-mail stopped using the master $Default$.junkmail file and started using Global.cfg actions for gatewayed E-mail, but if you specify it with a per-domain config it will work. BTW, watch out for dictionary attacks. Those of us that have been doing this for more than a handful of domains have found that address validation is an absolute necessity. I'm sure that Sandy would recommend his free Exchange to Aliases scripting, but I would recommend either ORF, or Alligate Gateway for this, and Alligate Gateway is the easiest of all to configure to do validation since it can resolve in real-time off of the destination server and/or from an address flat file. Matt David Barker wrote: Add the following line to your global.cfg DOSENDERACTIONS ON Take the copy of your $default$.junkmail and rename it to $default$.sender (DOSENDERACTIONS ON uses the $default$.sender actions for OUTBOUND email rather than the OUTBOUND actions in the global.cfg) Likewise for per domain settings or per user setting ie. Alberti.sender David B www.declude.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Panda Consulting S.A. Luis Alberto Arango Sent: Friday, July 21, 2006 3:52 PM To: declude.junkmail@declude.com Subject: [Declude.JunkMail] How to configure per-domain file for gateway domains I am testing Declude acting as a gateway for domain on other server. The junkmail manual 4.0.8 says that global.cfg is the file used to configure the actions for outgoing email. But it also says To get around this, you can set up per-domain configuration files for the gateway domains.. I want to create a per-domain configuration file of actions for the outgoing e-mail. So I figured that creating a folder using the domain I am forwarding and a file global.cfg within that folder it will work. But it doesn't. Looking at at the debugged log file, Declude looks for the junkmail file at a per-user and per-domain basis (that is only use for incoming mail), but it doesn't look for for a global.cfg under a folder (domain) or user (global.cfg is used for outgoing e-mail) Bottom line: I don't know how to configure the outgoing actions as a per domain, per user. How does the configuration work? Could you please update the manual with that information? Thanks -Luis Arango --- 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. --- 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] Forged from local domains.
I am starting to see a lot of spam email that uses the recipient domain in the from address. So if the mail is going to [EMAIL PROTECTED] the from address may be something like [EMAIL PROTECTED] Is there any declude test to see if the sender is valid for local domains??? I thought I remembered something about the spammers using a wildcard to just fill in the recipient domain for the from address - seems like there should be a method to block this. Chuck Schick Warp 8, Inc. (303)-421-5140 www.warp8.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] Forged from local domains.
Chuck, Yes, you can make a version of SPAMDOMAINS that lists your own domains figuring that your own customers will be whitelisted for AUTH or IP and therefore not hit by that filter. IMO, even though they are forging addresses and their content may be spammy, those two things don't necessarily represent the best way to tag such guys. Gateways that tarpit or greylist like ORF and Alligate will block virtually zombie spammers with minimal effort, and if configured properly, without false positives. I only currently know of one zombie spammer that defeats greylisting, and a good number of them fail when tarpitted. Matt Chuck Schick wrote: I am starting to see a lot of spam email that uses the recipient domain in the from address. So if the mail is going to [EMAIL PROTECTED] the from address may be something like [EMAIL PROTECTED] Is there any declude test to see if the sender is valid for local domains??? I thought I remembered something about the spammers using a wildcard to just fill in the recipient domain for the from address - seems like there should be a method to block this. Chuck Schick Warp 8, Inc. (303)-421-5140 www.warp8.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 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] Forged from local domains.
This is the best use for SPF. If you can control or specify what machines can send mail for a domain, then you can set an SPF record in DNS and use SPF FAIL to block forged mail. Darin. - Original Message - From: Chuck Schick [EMAIL PROTECTED] To: Declude. JunkMail Declude.JunkMail@declude.com Sent: Friday, July 21, 2006 6:18 PM Subject: [Declude.JunkMail] Forged from local domains. I am starting to see a lot of spam email that uses the recipient domain in the from address. So if the mail is going to [EMAIL PROTECTED] the from address may be something like [EMAIL PROTECTED] Is there any declude test to see if the sender is valid for local domains??? I thought I remembered something about the spammers using a wildcard to just fill in the recipient domain for the from address - seems like there should be a method to block this. Chuck Schick Warp 8, Inc. (303)-421-5140 www.warp8.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 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] Forged from local domains.
Matt: Thanks. I have been looking at setting up a gateway filter. Thanks for your recommendations. Chuck Schick Warp 8, Inc. (303)-421-5140 www.warp8.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt Sent: Friday, July 21, 2006 4:42 PM To: declude.junkmail@declude.com Subject: Re: [Declude.JunkMail] Forged from local domains. Chuck, Yes, you can make a version of SPAMDOMAINS that lists your own domains figuring that your own customers will be whitelisted for AUTH or IP and therefore not hit by that filter. IMO, even though they are forging addresses and their content may be spammy, those two things don't necessarily represent the best way to tag such guys. Gateways that tarpit or greylist like ORF and Alligate will block virtually zombie spammers with minimal effort, and if configured properly, without false positives. I only currently know of one zombie spammer that defeats greylisting, and a good number of them fail when tarpitted. Matt Chuck Schick wrote: I am starting to see a lot of spam email that uses the recipient domain in the from address. So if the mail is going to [EMAIL PROTECTED] the from address may be something like [EMAIL PROTECTED] Is there any declude test to see if the sender is valid for local domains??? I thought I remembered something about the spammers using a wildcard to just fill in the recipient domain for the from address - seems like there should be a method to block this. Chuck Schick Warp 8, Inc. (303)-421-5140 www.warp8.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 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.
