Author Topic: Scan Inbound Mail incompatibility problem  (Read 10995 times)

0 Members and 1 Guest are viewing this topic.

Alistair

  • Guest
Scan Inbound Mail incompatibility problem
« on: July 02, 2005, 02:44:59 AM »
Just thought I would mention that the incoming scanner seems to be a bit invasive in that it blocks out the service wanting to use. EG I am a programmer, and have written a program called 'spamdel' when spamdel wants to read the message it firstly gets the message number (GetUIDLList) then reads the desired text. Similarly to delete a message it GetUIDLList then delete desired message. Problem is when GetUIDLList, Avast blocks the port and program hangs. Without incoming scanning programs work fine. I expect this issue to be a common one with any program wanting the POP3 port, and would be hard to overcome, as many servers only have one port dedicated to POP3. Maybe there is a method around it, but not apparent to me.
Alistair+

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67235
Re: Scan Inbound Mail incompatibility problem
« Reply #1 on: July 02, 2005, 02:51:20 AM »
Yes, there is a workaround.
Just add the name of the GetUIDLList process to be excluded from scanning.
Click 'Settings' in my signature than browse for the [MailScanner] section. You'll find there how to exclude it.
Another possibility is redirecting avast to scan other port number than the spam killer application (Redirection tab of Internet Mail provider settings).
Welcome to the most configurable antivirus round  8)
The best things in life are free.

Alistair

  • Guest
Re: Scan Inbound Mail incompatibility problem
« Reply #2 on: July 02, 2005, 05:48:45 AM »
Yes, there is a workaround.
Just add the name of the GetUIDLList process to be excluded from scanning.
Click 'Settings' in my signature than browse for the [MailScanner] section. You'll find there how to exclude it.
Another possibility is redirecting avast to scan other port number than the spam killer application (Redirection tab of Internet Mail provider settings).
Welcome to the most configurable antivirus round  8)

Superb, just one problem. Most users would not be aware of these settings, and could not be bothered changing them. I believe Norton anti-virus has an 'ask the user to allow' method. If u are the programmer, could you please consider adding this feature in to a future release. I suspect you have one of the most popular freeware antiv progs, and it would be nice if it would help, not hinder other programs in their use of the net. IMHO ;-)

Alistair

  • Guest
Re: Scan Inbound Mail incompatibility problem
« Reply #3 on: July 02, 2005, 07:01:00 AM »
Yes, there is a workaround.
Just add the name of the GetUIDLList process to be excluded from scanning.
Click 'Settings' in my signature than browse for the [MailScanner] section. You'll find there how to exclude it.
Another possibility is redirecting avast to scan other port number than the spam killer application (Redirection tab of Internet Mail provider settings).
Welcome to the most configurable antivirus round  8)

Sorry, cannot for the life of me find any string entry in the [Mailscanner] section which is similar to you describe. Could you enlighten me with an example? The only thing vaguely like the job looked to be PassThrough=1 which is not suitable.
Al+

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 86946
  • No support PMs thanks
Re: Scan Inbound Mail incompatibility problem
« Reply #4 on: July 02, 2005, 01:46:48 PM »
Add a new line IgnoreProcess if it doesn't exist in the [Mailscanner] section. I have done this to exclude/ignore MailWasher.exe and I added the line directly below the [Mailscanner] section start.

IgnoreProcess=GetUIDLList (or what ever the executable filename is)
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 22.9.6034 (build 22.9.7554.734) UI 1.0.728/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67235
Re: Scan Inbound Mail incompatibility problem
« Reply #5 on: July 02, 2005, 01:55:45 PM »
Superb, just one problem. Most users would not be aware of these settings, and could not be bothered changing them. I believe Norton anti-virus has an 'ask the user to allow' method. If u are the programmer, could you please consider adding this feature in to a future release. I suspect you have one of the most popular freeware antiv progs, and it would be nice if it would help, not hinder other programs in their use of the net. IMHO ;-)
I'm not a programmer... I do not work for Alwil company... I'm just an user like you.
They're adding GUI for changing settings little by little by users' ask.
Anyway, please, never compare our beloved avast! with Norton. Norton is not the minimal part configurable as avast...
Norton is a big black closed box...  :P

Sorry, cannot for the life of me find any string entry in the [Mailscanner] section which is similar to you describe.
Follow David  ;)
In the first post of that thread I've wrote that you must add the lines that you don't have...
The best things in life are free.

Offline lukor

  • Administrator
  • Super Poster
  • ***
  • Posts: 1885
    • AVAST Software
Re: Scan Inbound Mail incompatibility problem
« Reply #6 on: July 03, 2005, 12:08:34 AM »
Alistair, the problem probably lies in the way your program communicates via POP3 protocol. The IgnoreProcess trick would probably work, but it should NOT be necessary.

Mail Scanner redirect your communication with server and scans the communication. If you just get the UIDList, you probably would not transmit any data that might be scanned. Anyway your program spamdel speaks with Internet Mail scanner instead of the destination server.

How does the communication looks like? Do you login, getUIDList and logout? Or do you send the command and block until the result is returned? Enable logging in Mail Scanner and decipher from the log what does Mail Scanner receive and how does it understand the commands.

There are two possibilities:
1) your program is BAD - meaning it does not speak proper POP3
2) Mail Scanner does not understand the commands used by your program even though they are correct

If 2) is the case and your are speaking correct POP3 according to POP3 RFC we should probably modify Mail Scanner to understand your commands. If 1) is the case, well you know what to do...  :P  Fix it. For example do you use \r\n to terminate the line (just like RFC requests) or just plain \n (WRONG) ?
 

Anyway, post here the transcript of the communication (e.g. when simulated in telnet), and send me or vojtech the logfile from Mail Scanner and we will find out where the problem is.

« Last Edit: July 03, 2005, 12:12:37 AM by lukor »

Alistair

  • Guest
Re: Scan Inbound Mail incompatibility problem
« Reply #7 on: July 03, 2005, 01:41:34 AM »
How does the communication looks like? Do you login, getUIDList and logout? Or do you send the command and block until the result is returned? Enable logging in Mail Scanner and decipher from the log what does Mail Scanner receive and how does it understand the commands.
Appreciate. Can u send me a PIM with your email adds and I will return findings.
Re above, I log in then get the UID list. I also log in and read headers and that part works OK through the mail scanner so there is something different in the outgoing protocol with some operations like UID and delete message that MScanner does not like there.

BTW just a thought, you have a nice help file, but pressing F1 in On-Access protection control, and other interfaces does not restore it.

Offline lukor

  • Administrator
  • Super Poster
  • ***
  • Posts: 1885
    • AVAST Software
Re: Scan Inbound Mail incompatibility problem
« Reply #8 on: July 03, 2005, 01:57:21 AM »
use the email from my public profile.

Alistair

  • Guest
Re: Scan Inbound Mail incompatibility problem
« Reply #9 on: July 03, 2005, 03:10:09 AM »
With the log, I cannot get any i/o information. EG when the scanner is activated by my email program, nothing is logged even in debug or info. Am I missing something, or are standard i/o ignored, but problems are posted to the log. If the latter that is a pity, as debug would have shown me the difference between a working I/O from my program to the opposite.
Alistair+
PS keeping this thread public as others might be wanting to work with Avast similarly.

Offline lukor

  • Administrator
  • Super Poster
  • ***
  • Posts: 1885
    • AVAST Software
Re: Scan Inbound Mail incompatibility problem
« Reply #10 on: July 03, 2005, 09:27:27 AM »
Have you enabled logging in the Mail Scanner (by adding the line log=20 into the Mailscanner section of avast4.ini) ???

[MailScanner]
Log=20

Edit: BTW you can post your spamdel, I can check what does it send...

Edit2: Of course you need to restart Mail Scanner before and then terminate Mail Scanner after your trial - in order to flush the log on disk a make it available for reading.
« Last Edit: July 03, 2005, 09:36:53 AM by lukor »

Alistair

  • Guest
Re: Scan Inbound Mail incompatibility problem
« Reply #11 on: July 03, 2005, 09:38:06 PM »
=>Have you enabled logging in the Mail Scanner (by adding the line log=20 into the Mailscanner section of avast4.ini) ???
No will do; I had assumed it was in the log interface setup :-(
=> BTW you can post your spamdel, I can check what does it send...
OK, its url is
http://www.spamdel.com
or download
http://www.spamdel.com/spamdel.exe
Does not put anything into registry (uses INI files) so you can install & Uninstall clean.

Cheers,
Al+

Alistair

  • Guest
Re: Scan Inbound Mail incompatibility problem
« Reply #12 on: July 03, 2005, 10:54:43 PM »
Still no log of all coms events generated, or is that particular log not visible in the log viewer? I changed the [mailscanner] log=20 , saved, Stop access protection, then Start access protection right?

Interesting, I have two pop email accounts free.net.nz and orcon.net.nz if I use my default Avast scanner locks spamdel out, but if I use the secondary spamdel works OK. Would be good to see the log to see what is happening.
Alistair+
« Last Edit: July 03, 2005, 10:56:19 PM by Alistair »

Offline lukor

  • Administrator
  • Super Poster
  • ***
  • Posts: 1885
    • AVAST Software
Re: Scan Inbound Mail incompatibility problem
« Reply #13 on: July 03, 2005, 10:59:01 PM »
Alistair, search the forum for Log=20 !!!

the log file is generated in the <avast4>\data\log folder in the file ashMaisv.log, will be accessible only when Internet Mail provider is terminated.

Anyway, I have downloaded your program, filled up the introductory wizard, let it download my messages. It marked 5 of them as spam (well, missed my spams and marked the regular mails, but that does not matter for now), I've chosen one, clicked spamDel/Del, it redownloaded again and the message was deleted. All this was scanned by avast mail scanner...hmm, nothing wrong here.

Alistair

  • Guest
Re: Scan Inbound Mail incompatibility problem
« Reply #14 on: July 04, 2005, 07:05:35 AM »
Hi again. I can see the error on mailserver Orcon here; you can see mailserver Freenet is OK. I am not sure where the anomaly is, but it appears the UIDL list is not being provided correctly for some reason from Orcon when it parses via Avast.
Will put more time into it in next days when I can.
Alistair+