I haven't had much experience with the finer details of email services, so bear with me.
I have a user who sets up temporary field offices all over the place on a frequent basis. He wants to use Outlook 2003 no matter which ISP he's using. We both want to configure his Outlook so that neither one of us has to change his settings each time he moves to another location and that his mail always appears to be from user@domain.com.
His normal account settings look something like this:
Account: user@domain.com
Outgoing Mail: smtpserver.domain.com
Incoming Mail: pop3server.domain.com
Unless I'm mistaken, if he has to use a different ISP (otherdomain.com) that blocks mail relaying, he would need to change his outgoing mail server to something like smtpserver.otherdomain.com. I think we've also had occasion where he could only send mail through smtpserver.otherdomain.com if he used an email address of user@otherdomain.com. As I mentioned before, I don't want that. His mail always needs to arrive at the recipient as being from his user@domain.com address.
If I were able to set Outlook to connect to our mail server via HTTP, wouldn't this solve my problem? From what I've been able to determine without having my hands on a system using Outlook 2003, I could send and receive user@domain.com mail via httpserver.domain.com even if he was using otherdomain.com for internet service. He wouldn't even need to bother with SMTP, POP3, and/or IMAP, correct?
I'm considering setting up an in-house mail server. Any recommendations regarding a mail server app that supports HTTP access (as well as SMTP and POP3) and runs on Windows Server 2003? Our ISP's current mail server only supports SMTP and POP3.
I have a user who sets up temporary field offices all over the place on a frequent basis. He wants to use Outlook 2003 no matter which ISP he's using. We both want to configure his Outlook so that neither one of us has to change his settings each time he moves to another location and that his mail always appears to be from user@domain.com.
His normal account settings look something like this:
Account: user@domain.com
Outgoing Mail: smtpserver.domain.com
Incoming Mail: pop3server.domain.com
Unless I'm mistaken, if he has to use a different ISP (otherdomain.com) that blocks mail relaying, he would need to change his outgoing mail server to something like smtpserver.otherdomain.com. I think we've also had occasion where he could only send mail through smtpserver.otherdomain.com if he used an email address of user@otherdomain.com. As I mentioned before, I don't want that. His mail always needs to arrive at the recipient as being from his user@domain.com address.
If I were able to set Outlook to connect to our mail server via HTTP, wouldn't this solve my problem? From what I've been able to determine without having my hands on a system using Outlook 2003, I could send and receive user@domain.com mail via httpserver.domain.com even if he was using otherdomain.com for internet service. He wouldn't even need to bother with SMTP, POP3, and/or IMAP, correct?
I'm considering setting up an in-house mail server. Any recommendations regarding a mail server app that supports HTTP access (as well as SMTP and POP3) and runs on Windows Server 2003? Our ISP's current mail server only supports SMTP and POP3.