> IMail uses it for several purposes, such as on the greeting (what you
first
> see when you telnet to port 25 on your mail server), and in the HELO/EHLO
> text. The RFCs require this to be a fully qualified domain name. That's
> just the way it is. It can't be an IP address or just "machinename" or
> whatever.
>
> You aren't supposed to use an unregistered domain name, but you likely
> could get away with it. But why would you want to?
We are proving mail services for various website that they will resell to
thier clients, so we were thinking it would be best to keep it generic, i.e.
"mailcenter.com" or something like that...
> >Our network security policy requires the mail server to be behind a
> >firewall. Is this going to be a problem, and why?
>
> That's not a problem, just so long as the firewall doesn't do anything it
> shouldn't. If it blocks port 25 access or blocks access to the mail
server
> in any other way, it would be a problem. Or, if it mucks with the SMTP
> protocol (as we've seen here recently, blocking EHLO and blocking some
> data), it would be a problem.
>
> > or is it just that the firewall has to support ESMTP?
>
> No, the firewall doesn't need to support any mail commands. The problem
> firewalls are the ones that BLOCK ESMTP.
>
> >Does ESMTP require a different port than 25 to send and recv SMTP AUTH
> >commands?
>
> No. ESMTP is just an enhancement to SMTP, and is all done on port 25.
>
> -Scott
>
> Declude: Anti-spam and Anti-virus solutions for IMail.
http://www.declude.com
Scott, thank you so much for your help. This will provide me some starting
points for troubleshooting.
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
An Archive of this list is available at:
http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
