>I was a little confused because the Junkmail page said v1.21a was the
>latest version
>but was a BETA.
Don't worry about that. Our beta/release cycle is very different from
IMail and most other companies. Rather than come out with a new version
one or twice a year, and then beta test all the new features, we usually
come out with quite a few betas that both fix problems and add new
features. So we may end up with a public release, then release a beta with
a couple new features, another beta that fixes a problem with one of those
new features, and then another beta that adds a couple more features and
then a public release.
>2. It would be nice if the sample config contained all of the options with
>the default option(s) uncommented. For example, the LOGLEVEL is set to LOW
>in the default GLOBAL.CFG. The documentation wasn't exactly clear what the
>options were LOGLEVEL except in the Testing section of the document. When
>I set LOGLEVEL to MEDIUM, the Declude log file stated: "Warning: Log Level
>in CFG file invalid; setting to debug level." Did I miss something?
It's actually "MID" instead of MEDIUM (I'm not sure why). You can find
those hidden under "Log file location" in the "Advanced Configuration"
section of the manual. That does sound like a good idea to have all the
options listed in the config file (but commented out), though.
>3. My wife subscribes to a listserv through EGROUPS.COM (now part of Yahoo
>I believe). The list is very active and the messages come in logged as
>SPAMHEADERS and that's all. These are legit e-mails which is a bit shocking
>to me.
Unfortunately, Egroups sends out its E-mail without a "Message-ID:"
header. This header is automatically added by all legitimate mail clients,
but it seems like Egroups had their own programmers write their own code to
send E-mail, and missed the Message-ID: header. That header isn't required
by the RFCs, but since lots of spam is missing it, and almost all
legitimate mail contains it, the lack of the Message-ID: header causes the
SPAMHEADERS test to fail.
One option would be to add a line anywhere in \IMail\Declude\global.cfg
that says "WHITELIST FROM @returns.onelist.com". The WHITELIST feature
(which hasn't yet been documented, but has been well tested) will let you
automatically whitelist E-mails based on certain criteria. Here, we are
whitelisting based on a return address (technically the "MAIL FROM" address
in the SMTP envelope, or where the E-mail would go if it bounced) that
contains "@returns.onelist.com". It seems that Egroups sends out their
E-mails with a return address at that domain. The only side-effect of
doing this is that a spammer could send you mail by using any made-up
address at "@returns.onelist.com", but it is unlikely that a spammer would
do this.
>4. Is there a way to block messages on multiple failed tests? For example,
>is there a way to specify if a messages fails the SPAMHEADERS *AND* the
>REVDNS test to hold/delete the message?
No. This is something that we would like to add at some point, but have
not yet determined how difficult it would be to add this.
-Scott
---
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". You can E-mail
[EMAIL PROTECTED] for assistance. You can visit our web
site at http://www.declude.com .
