RE: [Declude.JunkMail] Declude gone whacky?
Great! Do you think you can get it to work on aliases rather than just intended recipients like you mentioned? Dan -Original Message- From: [EMAIL PROTECTED] [mailto:Declude.JunkMail-owner;declude.com]On Behalf Of R. Scott Perry Sent: Tuesday, November 12, 2002 6:15 PM To: [EMAIL PROTECTED] Subject: RE: [Declude.JunkMail] Declude gone whacky? The test email that I sent only had one recipient. The problem started when I sent the test message to [EMAIL PROTECTED] to test the filter setup. There was not a valid imail account or alias for muji. I waited a minute for it to process and then checked the declude logs to see what had occurred. That is when I noticed that the server was acting loaded. I checked the mailboxes where the muji message would have gone and it wasn't there yet, so it was still processing. We've found the cause for this; there is a bug in the handling of the new ALLRECIP filter option that is causing this. It will be fixed in the next release. -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. --- [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.
RE: [Declude.JunkMail] Declude gone whacky?
Great! Do you think you can get it to work on aliases rather than just intended recipients like you mentioned? Yes, in the next release, the ALLRECIPS filter option will work on both the intended recipient and actual recipient, so you won't have to have the account created on the server. -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.
RE: [Declude.JunkMail] Declude gone whacky?
I resent an email and declude has now gone somewhat wacky. The imail server was acting loaded, so I checked the task man and there are 6 or 8 instances of declude running - taking up all of the cpu cycles. Ther are also about 15-20 .~md and .smd files in the spool dir and three or 4 .vir directories. It is busy doing something! Any ideas what happened? It looks like there was a problem with the code that could have potentially caused this, if there were large numbers of recipients for the E-mail. This will be fixed in the next release. However, with the 4 .vir directories as well (which are from Declude Virus), it may just be that you had a large amount of incoming traffic, that was being scanned normally. Does declude normally run multiple instances? Yes -- the IMail architecture will have either one Declude.exe process or one SMTP32.exe process for each E-mail that is being processed (after it is received by the SMTPD32.exe process). So it obviously doesn't like something with the filter. I did not create those accounts; muji and ddd. I was hoping the filters would work without a valid account as that was my inital goal. I have now deactivated the filter test line and all is running well. Tomorrow I'll try it with valid accounts, althought that doesn't do me much good, even if it works. I'll see if we can get the ALLRECIPS filter option to work with aliases as well. Although the aliases in IMail are very useful, they do come with their drawbacks. -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.
RE: [Declude.JunkMail] Declude gone whacky?
I resent an email and declude has now gone somewhat wacky. The imail server was acting loaded, so I checked the task man and there are 6 or 8 instances of declude running - taking up all of the cpu cycles. Ther are also about 15-20 .~md and .smd files in the spool dir and three or 4 .vir directories. It is busy doing something! Any ideas what happened? It looks like there was a problem with the code that could have potentially caused this, if there were large numbers of recipients for the E-mail. This will be fixed in the next release. However, with the 4 .vir directories as well (which are from Declude Virus), it may just be that you had a large amount of incoming traffic, that was being scanned normally. The test email that I sent only had one recipient. The problem started when I sent the test message to [EMAIL PROTECTED] to test the filter setup. There was not a valid imail account or alias for muji. I waited a minute for it to process and then checked the declude logs to see what had occurred. That is when I noticed that the server was acting loaded. I checked the mailboxes where the muji message would have gone and it wasn't there yet, so it was still processing. At this point I don't think there was any .vir directories. I waited 2-3 minutes and started to see multiple instances of declude.exe in taskman/processes. These were no doubt additional messages that were coming in while the test message was still processing. I waited another few minutes but none of the declude processes would ever finish and nothing was getting written to the logs. So that is when I killed it with a rename of global.cfg and a reboot. I believe it somehow chocked on the test message and the filter, possibly because there wasn't a valid imail account. I tried this two times with basically the same results. I will try it again but with a valid user account. Does declude normally run multiple instances? Yes -- the IMail architecture will have either one Declude.exe process or one SMTP32.exe process for each E-mail that is being processed (after it is received by the SMTPD32.exe process). So it obviously doesn't like something with the filter. I did not create those accounts; muji and ddd. I was hoping the filters would work without a valid account as that was my inital goal. I have now deactivated the filter test line and all is running well. Tomorrow I'll try it with valid accounts, althought that doesn't do me much good, even if it works. I'll see if we can get the ALLRECIPS filter option to work with aliases as well. Although the aliases in IMail are very useful, they do come with their drawbacks. How do you mean to work with aliases as well? Are you referring to the imail aliases? I guess it would be OK to still have an alias for old users, but where would it point to? I would like it just be able to delete a user when they are gone, aliases and all and then put their name in another file to have all their future mail dumped. It just makes imail more confusing to manage when there are many old unused users that should have been just deleted. I appreciate your help in figuring out a way to do this. Dan --- [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.
RE: [Declude.JunkMail] Declude gone whacky?
The test email that I sent only had one recipient. The problem started when I sent the test message to [EMAIL PROTECTED] to test the filter setup. There was not a valid imail account or alias for muji. I waited a minute for it to process and then checked the declude logs to see what had occurred. That is when I noticed that the server was acting loaded. I checked the mailboxes where the muji message would have gone and it wasn't there yet, so it was still processing. At this point I don't think there was any .vir directories. I waited 2-3 minutes and started to see multiple instances of declude.exe in taskman/processes. These were no doubt additional messages that were coming in while the test message was still processing. I waited another few minutes but none of the declude processes would ever finish and nothing was getting written to the logs. Since there will only be one Declude.exe process for each E-mail, if there was a problem with the E-mail to [EMAIL PROTECTED], it couldn't have affected the other Declude.exe processes. My guess in this case is that there was a mail loop of some sort, which is the only way that extra Declude.exe processes could have been created (although the new ones would only appear after Declude processed the E-mail, so that doesn't make a lot of sense either). So that is when I killed it with a rename of global.cfg and a reboot. I believe it somehow chocked on the test message and the filter, possibly because there wasn't a valid imail account. I tried this two times with basically the same results. I will try it again but with a valid user account. Without the valid IMail account, the E-mail would be processed with the nobody alias as the recipient, rather than the actual account (so per-user settings would be based on the nobody alias, and the ALLRECIPS filter option would be based on the nobody alias). I'll see if we can get the ALLRECIPS filter option to work with aliases as well. Although the aliases in IMail are very useful, they do come with their drawbacks. How do you mean to work with aliases as well? The ALLRECIPS filter option (which was added to the v1.62 beta) only looks at the actual recipients, not the intended recipients (the address that the sender tried to send to). So in the case of the nobody alias, the ALLRECIPS filter option doesn't look at the intended recipient (which is what we are going to see if we can change). Are you referring to the imail aliases? I guess it would be OK to still have an alias for old users, but where would it point to? No -- the idea is just that you could still use the old nobody alias, and still have Declude JunkMail filter based on the intended recipient (muji), even though the mail is going to the nobody alias. -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.
RE: [Declude.JunkMail] Declude gone whacky?
The test email that I sent only had one recipient. The problem started when I sent the test message to [EMAIL PROTECTED] to test the filter setup. There was not a valid imail account or alias for muji. I waited a minute for it to process and then checked the declude logs to see what had occurred. That is when I noticed that the server was acting loaded. I checked the mailboxes where the muji message would have gone and it wasn't there yet, so it was still processing. We've found the cause for this; there is a bug in the handling of the new ALLRECIP filter option that is causing this. It will be fixed in the next release. -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.
RE: [Declude.JunkMail] Declude gone whacky?
I renamed global.cfg go global.bak and rebooted. Everything started OK, so I renamed it bak to global.cfg and now declude is doing the same thing. It clearly doesn't like something with the filters. Here is what I have in the global.cfg WEIGHT10weight x x 10 0 WEIGHT20weight x x 20 0 WEIGHT100 weight x x 100 0 SNIFFER external nonzero f:\imail\sniffer\sniffer.exe 10 0 BLACKLIST fromfile f:\IMail\kill\fromfile.txt x 5 0 CATCHALLMAILS catchallmails x x 0 0 OLDEMPLOYEE filter f:\IMail\Declude\oldemployee1.txt x 100 0 and this is the content of the employee1.txt file: ALLRECIPS 0 CONTAINS [EMAIL PROTECTED] ALLRECIPS 0 CONTAINS [EMAIL PROTECTED] The junkmail file only has: WEIGHT100 HOLD Any ideas? --- [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.
RE: [Declude.JunkMail] Declude gone whacky?
I renamed global.cfg go global.bak and rebooted. Everything started OK, so I renamed it bak to global.cfg and now declude is doing the same thing. What exactly is happening? WEIGHT100 weight x x 100 0 OLDEMPLOYEE filter f:\IMail\Declude\oldemployee1.txt x 100 0 That's good. and this is the content of the employee1.txt file: ALLRECIPS 0 CONTAINS [EMAIL PROTECTED] ALLRECIPS 0 CONTAINS [EMAIL PROTECTED] That's good (assuming that you are running v1.62 or higher, which is needed for the ALLRECIPS option). The junkmail file only has: WEIGHT100 HOLD And that looks good too. Did you add the [EMAIL PROTECTED] and [EMAIL PROTECTED] accounts? -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.
RE: [Declude.JunkMail] Declude gone whacky?
OLDEMPLOYEE filter f:\IMail\Declude\oldemployee1.txt x 100 0 and this is the content of the employee1.txt file: This may be a typo, but it does not appear here that the actual file name employee1.txt and the config option in the Global.cfg oldemployee1.txt are the same. Just something to look at... Bill --- [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.
RE: [Declude.JunkMail] Declude gone whacky?
It doesn't look like you got the earlier message. Here it is: I was in the middle of testing the filters, and initially go a couple of errors in the log that said it could not open my filter file. I rechecked the configuration for a typo and everything looked OK. I sent a couple more emails and nothing showed in the log that it was even looking at the filter file. So, I created a new filter file with a new name and renamed it in the global.cfg. I resent an email and declude has now gone somewhat wacky. The imail server was acting loaded, so I checked the task man and there are 6 or 8 instances of declude running - taking up all of the cpu cycles. Ther are also about 15-20 .~md and .smd files in the spool dir and three or 4 .vir directories. It is busy doing something! Any ideas what happened? Does declude normally run multiple instances? I am going to rename the global.cfg and try a reboot. It won't let me kill any of the declude processes. So it obviously doesn't like something with the filter. I did not create those accounts; muji and ddd. I was hoping the filters would work without a valid account as that was my inital goal. I have now deactivated the filter test line and all is running well. Tomorrow I'll try it with valid accounts, althought that doesn't do me much good, even if it works. I am on version 1.62 Thanks Dan -Original Message- From: [EMAIL PROTECTED] [mailto:Declude.JunkMail-owner;declude.com]On Behalf Of R. Scott Perry Sent: Monday, November 11, 2002 6:50 PM To: [EMAIL PROTECTED] Subject: RE: [Declude.JunkMail] Declude gone whacky? I renamed global.cfg go global.bak and rebooted. Everything started OK, so I renamed it bak to global.cfg and now declude is doing the same thing. What exactly is happening? WEIGHT100 weight x x 100 0 OLDEMPLOYEE filter f:\IMail\Declude\oldemployee1.txt x 100 0 That's good. and this is the content of the employee1.txt file: ALLRECIPS 0 CONTAINS [EMAIL PROTECTED] ALLRECIPS 0 CONTAINS [EMAIL PROTECTED] That's good (assuming that you are running v1.62 or higher, which is needed for the ALLRECIPS option). The junkmail file only has: WEIGHT100 HOLD And that looks good too. Did you add the [EMAIL PROTECTED] and [EMAIL PROTECTED] accounts? -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. --- [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.
RE: [Declude.JunkMail] Declude gone whacky?
Sorry, yes a typo. The filename did match the global.cfg line. -Original Message- From: [EMAIL PROTECTED] [mailto:Declude.JunkMail-owner;declude.com]On Behalf Of Bill Landry Sent: Monday, November 11, 2002 6:57 PM To: '[EMAIL PROTECTED]' Subject: RE: [Declude.JunkMail] Declude gone whacky? OLDEMPLOYEE filter f:\IMail\Declude\oldemployee1.txt x 100 0 and this is the content of the employee1.txt file: This may be a typo, but it does not appear here that the actual file name employee1.txt and the config option in the Global.cfg oldemployee1.txt are the same. Just something to look at... Bill --- [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. --- [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.