MS SMTP Provider Attachment blocking bug

I have a separate resident task setup for the server in the DMZ zone. Its an SMTP server so I have the MS SMTP 2000/2003 provider. In that provider’s properties I go to Blocking and enable attachment blocking by name. Then I list the following:
*.ade
*.adp
*.asx
*.bas
*.bat
*.chm
*.cmd
*.com
*.cpl
*.crt
*.exe
*.hlp
*.inf
*.ins
*.isp
*.js
*.jse
*.lnk
*.mdb
*.mde
*.mdt
*.mdw
*.mdz
*.msc
*.msi
*.msp
*.mst
*.pcd
*.pif
*.reg
*.scf
*.scr
*.sct
*.shb
*.shs
*.url
*.vb
*.vbe
*.vbs
*.wsc
*.wsf
*.wsh

This works well. The problem is that just now for the 5 time over the course of 3 months we suddenly recieve NO attachments. When I go in and look where I have this list the list begins with * and is cut off right around *.mdt. So I go in and delete the * and then re-add the bottom half. I don’t know why this is continuing to happen but it would be helpful if it could stop changing this list on me. It seems to happen if I modify or update the computer that is in the group that has this particular resident task defined but I can’t really narrow that down.

Please try the following:

  • insert the list the way you want it to have it
  • confirm with OK, OK etc untill all the config windows are closed
  • go to Administrative Tools → Services
  • restart the “avast antivirus” service
  • now check the the list. is it truncated?

Thanks
Vlk

no, list is still good. even after a reboot of the server list is good.

Is this a managed version of avast?
Are you making the changes locally on the SMTP server or in the console?

yes managed. I’m running the ADNM console from my laptop (connecting to my ADNM server) and modifying the DMZ servers resident task from there.

OK, and when the truncation occurs, it occurs in both the on-server Resident Protection task (in the console), or only directly on the machine running the SMTP provider (the “client” - although technically probably a server machine)?

hmmm, not clear what you mean on this one? In the adnm console when I go to the dmz resident task properties, the smtp provider has it truncated. I never locally touch the server.

OK, I see. I thought you were also changing it locally.
So it gets truncated in the database. Very strange indeed.
Couldn’t it be somehow connected e.g. to a run of the “DB Cleanup” task? Maybe it cleans up little too much? :slight_smile:

That’s quite possible that task did run today. Though it ran on the 14th and this didn’t happen. ???

So if you run the task now, manually, does it happen?

I don’t want to mess with it while i’m not physically there, and we won’t be in monday cause of the hurricane so I’ll have to let you know on tuesday.

Oh my, you’re in Florida…? :-X
BTW I’ll try to simulate it in our lab as well.

Thanks
Vlk

yea but at least this time its hitting the west coast first. last year sucked. Actually if power is out for a day or two I might not get to it until wed, thurs.
so don’t hold your breath.

ok just got power back tonight. will be in office tomorrow and let you know.

FYI I tried to simulate the problem but couldn’t find a way to reproduce it here…

This just happened again today. The DB cleanup task ran this morning as well as the DB backup task. Then the attachment blocking area in the smtp provider was clipped off at .mdt and a “*” was added to the front of the list effectively blocking every attachment.
I fixed the list and manually ran the backup and cleanup task but the list remained intact. Plus it says clean records older than 3 months so I would think if the cleanup task was doing it, it would happen every 3 months but last time it happened was 2 months ago.

The bug has finally been found. It will be fixed in the next update.

BTW it had nothing to do with the “Clean DB” task. Instead, the settings weren’t surviving server restart (or restart of the “avast! Manamagement Server” service). I.e. until the service was restarted, the settings were saved (cached) correctly. But when the restart occured, they were clipped (in fact, they were correctly saved to the DB, but then incorrectly READ from the DB).

Thanks for pointing this out!

Cheers
Vlk

Glad this was found! This was my last little issue with avast and soon it will be gone.