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.
