Situation: Server rebuild

OS: WinXP Pro
HTTP Server: IIS5.1
SQL 2005
.NET Framework 2.0, 3.0, 3.5

Symptoms:
1) Can only logon to primary account on default domain group in webmail. Can maintain all settings in default account. All other accounts result in:
“Your logon attempt was not successful. Please try again.”

2) When sending mail from webmail on default domain, the error is returned:
“Error sending mail: Error receiving data – empty string received”

3) When connecting to Argo Mail Server via mail client Outlook Express, a successful POP3 interrogation occurs, but the following SMTP error occurs:
“550 5.7.1 Unable to relay ...”
indicating a winsock error 10061

4) When sending from an external mail server to Argo Mail server, a message is returned to the external mail server:
“550 5.7.1 Unable to relay ...”

Configuration:
Server firewall is off, router firewall is on, but open to ports 80, 25, 110, 587, 6060, 443, 143, and a few other ports.
IIS5.1 uses ports 80, 443, 21, 587, all successfully in a multi-domain format
Argo Mail uses 25, 110, 6060, 143, using only 110 successfully, have not tested 143
Argo Webmail successfully implements a multi-domain format with the proper login loading for each domain.
An external telnet cannot establish a connection on port 25 at this IP address.

All suggestions in this forum have been re-checked without finding the cause, eg. DNS stuff, SMTPServerList.xml, firewalls, etc)

I use the WAN [address] for the local host on the server options, and I use the LAN address for binding, and I use the mail.domain.org address for the local host for each of 3 mail domains. Before I alter all of the parameters, could this be the source of trouble?

Any ideas for a solution?

Altering the server local host from the WAN IP address to the LAN IP address allows the default account to send and receive messages as normal. I haven't done that for the past few years of operating the Argo Sever, but thats okay, I can live with it.

When an SMTP connection is made from a mail server on the WAN, the Argo server log indicates that legitimate RCPT TO email addresses I have established on the Argo server are not local (status 551) and therefore the SMTP connection needs authentication before relaying the message. This can't happen so the end result is an authentication error, hence the 550 error observations in the post above.

With the alteration described above the Argo server doesn't recognize my 2nd and 3rd domains. Have I structured my domain groups wrong? I can't see any other way to structure the domain groups in the server that would make any sense and operate the way I have operated the server for the past few years.

With a little help from Archie and a little experimentation on my part, I found the elusive solution to the problem described above.

First, new domains were not being added to the server. I did add them through the 'new domain' button and they would appear on the server console, but they would disappear when I closed the console and re-opened it.

The solution was to right click on the domain group and select 'new' instead of using the 'new domain' button. Don't ask me why, but on this specific server the 'new domain' button does NOT work the same as the right click 'new' method.

Thanks for sharing. I am glad to see that you were able to get the issue resolved.