Topic: webmail and external email access

[Shackleton]

hello,

From inside our network, the email is working flawlessly.  We can send and receive emails using thunderbird without problems.  External users can send emails using the smtp relay we set up with godaddy, however they cannot access our in house sme email server (imap), nor can they access webmail.  External webmail displays "web page cannot be displayed" and the external clients thunderbird attempt at accessing the sme server times out.  We can access and succesfully log into the webmail page from inside the network.

The following are current settings on our system.

webmail: allow HTTPS
IMAP server access: Allow private and public (secure IMAPS)

Thunderbird on the external clients are set to SSL port 993 (tried it with secure auth checked and unchecked)

ports 25, 80, 993 & 995 are open on the linksys router between the server (set in server only mode) and the internet.

sme 7.1

the website we host can be viewed from outside the network.

I know some of this information was not in a sensible order.  Are there any other specs needed to help diagnose this problem?

Thanks,

Shackleton

[pfloor]

You need port 443 for webmail to work.

995 is for pop3s and you won't need that if you are not using pop3s.

You may also need to forward 465 for TB to work but I'm not quite sure.

[TrevorB]

webmail: allow HTTPS

ports 25, 80, 993 & 995 are open on the linksys router between the server (set in server only mode) and the internet.

HTTPS (for webmail) requires that you use the https prefix in your url (eg. https://<your domain>/webmail) and that port 81 is available (the standard https port).

Open up port 81 on the linksys as well and you may have more luck.

Trevor B

[skydivers]

Open up port 81 on the linksys as well and you may have more luck.

Trevor B

You need port 443 for webmail to work.

pfloor

Quite confusing, opening up port 443 will do the job. (Which is https)

[TrevorB]

Quite confusing, opening up port 443 will do the job. (Which is https)

You're quite right....

Don't know what I was thinking of at the time.....

[jfarschman]

Trevor you must have worked with the ols Cobalt RaQs and Qubes.  They put https on port 81 for some odd reason.
 

[Shackleton]

Hi, Thank you for the replies.  I've opened up port 443 as suggested, however, the web page cannot displayed screen still comes up on the external client.  Any other ideas?


I have been able to fix the other problem.  The external TB client can now send and receive email, however, an ugly security certificate screen window pops up.  Once clicking past it, everything works, but the security certificate screen comes up at each new restart of TB.  

The webmail issue is the one we're most interested in at this point.

Thanks,

Shackleton

[Shackleton]

Ok, we're dumb.  Found the problem with the webmail, it's working now, but it is also giving us the security certificate issue mentioned earlier for TB.  Something about the security certificate is for "blah.blahblah.com and you are signing on to blahblah.com"

Thanks,

Shackleton

[TrevorB]

Something about the security certificate is for "blah.blahblah.com and you are signing on to blahblah.com"

Do some searching of the forum and you'll find that it is associated with the fact that you have a certificate generated for your server(eg. e-smith.yourdomain.com) rather than your domain (eg. yourdomain.com).

There is a way to generate your own key for the domain (rather than just the server) and to also use an external key. The 'Custom CA Certificate' HowTo is in the wiki, but I'm not sure where the other one is anymore.

Good Luck