Just to preface this a bit...do you think that it is possible that there was a locked file issue that was keeping Declude from accessing this file?
No (if so, that should be reflected in the log file).
In other words, I might have been updating that particular $Default$.junkmail at that very instant in time with a save over the old copy. I've always wondered how systems would handle such an issue.
If this happens, Declude JunkMail will treat it as if the file doesn't exist. So if it is a per-user setting, Declude JunkMail will try the per-domain settings; if it is a per-domain settings, Declude JunkMail will try the \IMail\Declude\$default$.JunkMail file. If it can't use any, then a message will appear in the log file (and the IGNORE action will be used for all tests).
I believe this is the loop that we were trying to prevent by not scanning .GSE files (bounces).
I'm still on 8.05 H1 or H2, and Declude 1.79i4. I thought this came into play in 8.10.
I'm thinking that IMail might be getting polluted when this happens.
Instead of looking in the HOSTS file for the IP, it goes to the DNS which points back to itself. That would explain how it sends to itself at least, just not why it ignores the normal routine.
That does sound plausible.
Are those your outgoing actions (in the global.cfg file)? The original E-mail was an outgoing E-mail (or gateway E-mail). It looks like the IGNORE action is being used for all tests.
There are no actions listed in my global.cfg file, just tests now. This came from the $Default$.junkmail file that all of their other E-mail uses, and generally uses properly.
Ah -- that's why the IGNORE action was used for all the tests. Declude JunkMail detected that it was an outgoing E-mail, in which case the outgoing actions from the \IMail\Declude\global.cfg file are used.
It looks to me like IMail is looping on its own. It has the correct recipient, yet keeps sending the E-mail back to itself.
Looks like that to me too, however it's strange that it chose a Declude skipped E-mail to do this on. I've seen this several times before in dead spool files, and there generally aren't too many of them outside of SMTP restarts. Maybe I should turn off IMail's DNS cache???
Declude isn't skipping it (you're seeing the headers in there); it's just using the \IMail\Declude\global.cfg file instead of one of the other config files.
-Scott
--- [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.
