Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: clanger on February 25, 2004, 11:14:51 PM
-
Here I am again. Same problem can't get email it conects but when authorising it says this error message:
Your server has unexpectedly terminated the connection. Possible causes for this include server problems, network problems, or a long period of inactivity. Account: 'c allen5000', Server: '127.0.0.1', Protocol: POP3, Port: 110, Secure(SSL): No, Error Number: 0x800CCC0F
Been having this problem for a while but by taking off and putting on mail protection sa few times it seems to have sorted it out but, not this time. Mine is not the only one having this problem.
Please help again. :-[
-
Before you ask, and I forgot to mention I have just downloaded mirc. But the problem started before then. I have had updates but it didn't seem to bother it til now. I hate to keep bothering you but it is driving me mad. Trying to remember all you asked me before to save time.
-
Clanger, I did not remember your computer configuration:
1. email client (program: Outlook Express for instance)?
2. firewall?
3. the way you connect Internet (dial-up or DSL)?
4. your operational system?
Could be simpler if you give us some more information... :-\
-
Sorry I use dsl, run Windows XP, and use Outlook Express. Stupid I now but never thought of that information. It seems to have righted itself for know but, all of a sudden it goes off again and, then I have to keep changing mail protection on and off till it settles. When its like that I can't receive mail either with mail protection on or off.
-
I forgot to say no firewall used.
-
Clanger, let's go step by step:
You can configure your email account in Outlook Express like this:
1. pop server: 127.0.0.1
2. smpt server: 127.0.0.1
3. user name: your_user_name#your_pop_server_address
4. password
5. authentication: your password could be left blank, choose to remember it and for the smtp server write: #your_smtp_server_address.
If you want, send me an email or IM asking more information ;)
-
Done all that had a good lesson of Techie 101 and for ages worked fine, even did another computer which had the same problem. It works fine for a while then goes off.
No matter what I do it doesn't work, seems to right itself after a while but its frustrating to keep having to mess about.
-
Hmm... it also doesn't work for me :(.
I'm using Windows XP SP1, Outlook Express, have a ADSL connection and use a firewall.
My settings are:
Outlook Express
POP3 & SMTP server: 127.0.0.1
Account name: my-username#my-POP3-server
And the password.
Remember password is checked.
Also 'My server requires authentication' is checked.
Account name is the same as described above, just with my-SMTP-server instead.
Password is blank, and remeber password is checked.
Firewall
ASHMAISV.EXE has the following rules:
TCP Outbound on port: SMTP, NNTP, POP3, POP3S & IMAP
About Outlook Express I haven't touched any settings and it's been working perfectly before with e-mail and newsgroups.
More is that I've set my firewall to let me know if any more rules should be applies, but nothing happens about that.
Anyone who can give me some advice.
Btw - the error I get is the exact same as posted in the first post of this thread.
I've tried disabling my firewall but the result is the same.
-
I am having the same problem. If you close OE take mail protection off and then set it up as it where with Pop3 and SMTP your server. Then close the program and put mail protection back on it sometimes works. Not the ideal solution. But until someone gets back to me from here its all I know what to advise you to do, it works for me although it drives me mad.
One of the techies will sort you out properly when they come on line.
-
Thanx - will try it out - and hope the techies will take over when they see the post ;)
-
I wonder what's so special about Tiscali... I've heard about people having specific problems with avast and Tiscali accounts... ???
Are you talking about UK Tiscali or which one?
Is it the free email service (so that we can do the tests under the same conditions) or a paid one?
Thanks
-
Its tiscali.co.uk. I had these problems earlier and one of your guys sorted me out, then it all started again. I am on ADSL 512 connection, windows XP and OE.
Really it so frustrating. Get your messages in Tiscali but not to OE were I would sooner have them
-
Hmm... I'm not a tiscali user - I just get the same error.
-
Wait til the techies come on line they are really good. If it can be sorted out they will do it. Give good clear instructions even I can follow.
-
See my post below.
Lost reply and had to resubmit.
techie.....
-
I wonder what's so special about Tiscali...
Vlk,
It really doesn't matter whether it is the free or pay Tiscali.
Tiscali UK is tricky to configure with Avast.
Firstly, it does not simply use a short form "username". The username is the full email address apended by the #pop.tiscali.co.uk or #smtp.tiscali.co.uk respectively.
Secondly, configuration of the SMTP server login depends on whether SMTP authentication was ON or OFF when Avast was installed.
which means that "username@tiscali.co.uk#smtp.tiscali.co.uk
or simply "#smtp.tiscali.co.uk" might be the correct format to use.
If the user followed the manual configuration instructions as per the example provided and eliminated the correct username format, then the MPW would configure
Avast to "username@tiscali.co.uk#127.0.0.1"
The MPW could add #127.0.0.1 only if the user had deleted #popserver string from their username. If they had previously checked 'Automatically protect all accounts that I create in the future', then avast periodically sets the protection to all accounts that it finds. Thus if the account is set like
POP server: 127.0.0.1
username: NAME
Avast considers the account as unprotected and modifies it to POP server: 127.0.0.1
username: NAME#127.0.0.1
after this periodical search, which is wrong.
...........................................................Quoted from Vojtech
This has been the problem in the past and I have been in contact with Vojtech about this. My suggestion would be to re-write the manual configuration instructions and clarify the relevant section.
Hope this helps everyone.
techie
-
So if I changed the line where it says user@tiscali.co.uk#pop3.tiscali.co.uk to user@tiscali.co.uk#127.0.0.1 it would solve all my problems or, have I got the wrong end of the stick. ???
-
clanger,
I don't know if it will solve your problem without going it to more research.
But, if you check your OE settings, the Incoming Mail Server (Pop) name should be "username@tiscali.co.uk#pop.tiscali.co.uk" and the Outgoing Mail Server (Smtp) name MIGHT work with one of these formats:
SMTP authentication must be set to "on" in the OE/Tools/Accounts/Properties/Servers menu.
1. "username@tiscali.co.uk#smtp.tiscali.co.uk"
or
2. "#smtp.tiscali.co.uk
If these do not fix things, then we will need to do more Q and A.
techie
-
So if I changed the line where it says user@tiscali.co.uk#pop3.tiscali.co.uk to user@tiscali.co.uk#127.0.0.1 it would solve all my problems
No, absolutely not. This setting is wrong that's vojtech was trying to say. The only way it can work is username#realpopserver.
Firstly, it does not simply use a short form "username". The username is the full email address apended by the #pop.tiscali.co.uk or #smtp.tiscali.co.uk respectively.
There should be no difference - there are no special checks for @'s or .'s...
Secondly, configuration of the SMTP server login depends on whether SMTP authentication was ON or OFF when Avast was installed.
which means that "username@tiscali.co.uk#smtp.tiscali.co.uk
or simply "#smtp.tiscali.co.uk" might be the correct format to use.
Well that's trues but that's the case with any ISP (not only Tiscali), isn't it?
If the user followed the manual configuration instructions as per the example provided and eliminated the correct username format, then the MPW would configure
Avast to "username@tiscali.co.uk#127.0.0.1"
Hmm, that seems like a bug we should fix... I was not aware of that. I wonder how the MPW is detecting whether an account is 'covered' or not... I'll have this checked.
clanger, have you checked the 'Automatically protect all accounts that I create in the future' box in the Mail Protection Wiz?
Thanks
Vlk
-
No, absolutely not. This setting is wrong that's vojtech was trying to say. The only way it can work is username#realpopserver
Then again, as I have said. It depends on WHEN the Smtp authentication was set to ON.
There should be no difference - there are no special checks for @'s or .'s...
The problem has been that in the past the MPW has not responded always correctly to @ and "." in the username format. We had a severe problem with Pegasus (remember Walker?). His setup was never resolved successfully.
Well that's trues but that's the case with any ISP (not only Tiscali), isn't it?
No it is not. The US Isp format is usually just the username such as "techie". Therefore the format would look like "techie#pop.av.com" and the Smtp would be either "techie#smtp.av.com" or simply "#smtp.av.com"
Hmm, that seems like a bug we should fix... I was not aware of that. I wonder how the MPW is detecting whether an account is 'covered' or not... I'll have this checked.
Yes indeed. Check with Voj to see if he is looking into this further.
clanger, have you checked the 'Automatically protect all accounts that I create in the future' box in the Mail Protection Wiz?
Checking this box could cause the problem above if the user does not cofigure the username format correctly. Avast will then stick in 127.0.0.1 after the cross hatch # when it periodically scans for new accounts.
For some reason, and maybe it is because of the longer than usual formatting, Tiscali users have had more problems than others, so I think maybe a clearer Help file is needed or a 'bug fix" on the MPW.
Techie