Your server has unexpectedly terminated the connection. Possible causes for this include server problems, network problems, or a long period of inactivity. Account: ‘Fabiano Ribeiro’, Server: ‘mail.prohost.com.br’, Protocol: SMTP, Port: 25, Secure(SSL): No, Error Number: 0x800CCC0F"
Your server has unexpectedly terminated the connection. Possible causes for this include server problems, network problems, or a long period of inactivity. Account: ‘Fabiano Ribeiro’, Server: ‘mail.prohost.com.br’, Protocol: IMAP, Port: 143, Secure(SSL): No, Error Number: 0x800CCC0F"
This is a error message and i don’t know how can fix it.
What email program are you using?
What Operating System are you using?
Are you using a firewall, if so which one?
Does this happen for only outbound (sending) connections (smtp and imap are for sending)?
Does it only happen if you are sending emails with attachments?
I assume that you don’t have any problem with inbound email (pop3)?
As a start point you can try increasing the time out delay in your email program.
when Avast was running i could not connect to our IMAP server at work. Not just when retrieving mail, but I could not even log in … there was no connection at all and I had to disable Avast to connect & get my mail.
Eventually I changed the config. file to disable IMAP mail checking ; StartIMAP=0 or something …
there must be some old threads here with my problem.
well, every single application and protocol works, except IMAP … so I’m pretty sure that my firewall allows Avast to do what it wants/needs. When i try to connect to the IMAP server, my firewall (Outpost Pro 2.5) doesn’t block anything … when i disable IMAP checking in Avast, it works !
There’s something wrong in Avast’s handling of IMAP and it started with 4.5 … before that : no problem at all.
Please insert the line
Log=20
to file C:\Program Files\ALWIL Software\Avast4\Data\avast4.ini under [MailScanner] for detailed logging.
Then send one mail (or retrive mail if incoming mail is the problem), which will generate the log file. After that, post the last lines of the log file C:\Program Files\ALWIL Software\Avast4\Data\log\aswMaiSv.log. Thanks.
I noticed that when using StartImap=1, by default Ashmaisv.exe listens for IMAP on localhost:loopback port 12143 (!?!) …
So I put a line under [MailScanner] : ImapListen=192.168.1.2:143 (local IP address).
And now it works ; Avast listens on local:192.168.1.2 port 143 and when I connect to the IMAP server at work through dial-back it redirects (?) to the IP of the mailserver and asks for my password …
It’s probably very simple and logical, but if anybody here can explain what happens ; I’m listening …
yes.
but the IMAP server is on a different IP address (at work) ; not 192.168.1.2 or 127.0.0.1 … ??
and when i’m connecting thru dial-up to the server, I get a different IP address every time … so why do my local addresses have to be trusted to connect to an IMAP server on another network ??
but reading your ‘understanding avast.ini’ thread, the ‘Trust=’ is ignored anyway, now that i specified an ‘ImapListen=’ …
“If you set the Listen items in the form of: 127.0.0.1:Port, the Trust item has no effect, because only connections from the local address (127.0.0.1) are accepted”
yes.
but the IMAP server is on a different IP address (at work) ; not 192.168.1.2 or 127.0.0.1 ... ??
and when i'm connecting thru dial-up to the server, I get a different IP address every time ... so why do my local addresses have to be trusted to connect to an IMAP server on another network ??
‘Trust’ setting is not related to the mail servers that you use, but rather from where a connection is accepted. And it is from a mail client running on your computer.
"If you set the Listen items in the form of: 127.0.0.1:Port, the Trust item has no effect, because only connections from the local address (127.0.0.1) are accepted"
Well, this sentence from the help is not quite precise. It tries to say that changing the default ‘Trust’ when ‘Listen’ is set to 127.0.0.1:Port, has no additional security effect, because this ‘Listen’ value implies that only 127.0.0.1 is trusted. Thus if you define your ‘Trust’ and omit 127.0.0.1, it won’t accept any connection.
: