Topic: Newbie help please. 7.0rc3 POP3 email problem.. DNS?

[DevoDave]

Hi all..

I just upgraded my home server from 6.x to 7.0rc3.

Fresh install to brand new HDD, then restored from backup.  Server only mode.

Everything works fine, except my Outlook Express can't logon to retrieve mail.  

Your server has unexpectedly terminated the connection. Possible causes for this include server problems, network problems, or a long period of inactivity. Account: 'davidd@topgunamusements.com', Server: 'mail.downsmail.com', Protocol: POP3, Port: 110, Secure(SSL): No, Error Number: 0x800CCC0F

(Webmail (Hoarde) works as expected.)

I try to telnet to downsmail.com, or mail.downsmail.com, on port 110 and I get nothing from my Windows XP system.  If I telnet to the local IP address of my server (192.168.0.100) then it works OK.  I can't telnet to the 'real' IP though!  I changed my Outlook account to point to the local IP address and (surprise surprise) it works too.

I can ping the downsmail.com and mail.downsmail.com OK.  I can ping the IP as well as the local IP of the server too.

I swap the HDD back to the old 6.x installation and it works without a hitch so (I figure) the problem must be with 7.0rc3.

Any suggestions??

-David

[crazybob]

Mail is now secure, so you need to adjust your setting in outlook express. Enable ssl in the advanced settings for pop and smpt, and set the smtp port to 465.

That should fix it

Bob

[DevoDave]

Good.. I'm not going insane!

Bob, if I tick the 'SSL' box on incoming mail (POP3) in Outlook Express then the port number changes to 995.  Is this default value correct?  (It's still not working)

(SMTP mail is directed to my ISP)

[sonoracomm]

Yes.

However for those configuring secure SMTP (SSMTP, SSL) with Outlook (Express?), be sure to use port 465.

The port doesn't change automatically...probably assuming TLS

G

[DevoDave]

Sorry to be a bother, but still having problems.

I have ticked the Tools-Accounts-<account name>-Properties-Advanced 'This server requires a secure connection (SSL)' box and the port number is 995.  Good-o!

However is there anything else I need?  Outlook Express still can't connect..

The connection to the server has failed. Account: 'david@downsmail.com', Server: 'mail.downsmail.com', Protocol: POP3, Port: 995, Secure(SSL): Yes, Socket Error: 10060, Error Number: 0x800CCC0E

Thanks..

[crazybob]

Sorry to ask, but do you have pop and smtp enabled in server-manager?
Sometimes the obious trip us up.

[DevoDave]

Under the 'E-mail settings' tab I have the following.

E-mail settings

POP3 server access  Allow private and public (secure POP3S)
IMAP server access  Allow private and public (secure IMAPS)
Webmail access  Allow HTTPS (secure)

Virus scanning  Enabled
Spam filtering  Disabled
Executable content blocking  Disabled

E-mail retrieval mode  Standard (SMTP)
SMTP authentication  Allow SSMTP (secure)

Forwarding address for administrative notices  david@downsmail.com
E-mail to unknown users  Send to administrator
Address of internal mail server  
Address of Internet provider's mail server  mail-hub.bigpond.net.au

[sonoracomm]

OK, I'm assuming I have read correctly:

You have an Internet-connected mail server and everything is working fine from the internal (green) LAN.  You can also ping and use webmail from the outside (red, Internet).

You are in server-gateway mode.  If not, forward the proper mail ports from your firewall.

You are trying to connect a mail client from the outside (red, Internet).

You do not get a connection from that mail client PC if you

Code: [Select]

telnet <external_IP> 995

Out of curiosity, what happens when you try telnetting to other mail ports?  (25, 110, 143, 465, 993)

Try this command to see if the POP3S protocol is set to public access:

Code: [Select]

config show pop3s

If it isn't, try

Code: [Select]

config setprop pop3s access public
signal-event email-update
svc -t /service/pop3s

Frankly, I'm guessing on this...

Maybe the restore had a little baggage...hard to avoid.

G

[DevoDave]

Woohoo...

Thanks everyone!  sonoracomm prompted me in the right direction.

My bloody router was the problem.  It wasn't forwarding ports 995 to the server.

Case closed.  Thanks again!