SMTP Mail error

[Gerhard]

Hi,

I some asp.net beta 2 code that works fine on an XP Pro machine, but on a
Windows 2003 Server gets the following error:

System.Net.Mail.SmtpFailedRecipientException {"Mailbox unavailable. The
server response was: 5.7.1 <ve****@quixnet.net>... Relaying denied. IP name
possibly forged [208.179.189.145]"}
System.Net.Mail.SmtpFailedRecipientException

Any idea what would cause that?

[Mikael Östberg]

You have to allow relaying in your SMTP server.

Check security settings in IIS.

This is dine by right-clicking Default SMTP Virtual Server and choosing
properties.

Then go to the Access tab. Click on the Relay button at the bottom of the
dialog.

Add the IPs you want to grant access. By default this is turned of
completely and since your web server is on the same machine, you could add
127.0.0.1 as the only entry in the list.

You can also open it up completely by checking the radio button All except
the list below and leave the list blank. However, if it is a public server
that is not a recommended setting.

That should solve that issue.

Mikael Östberg
"Gerhard" <Ge*****@discussions.microsoft.com> wrote in message
news:3D**********************************@microsof t.com...

Hi,

I some asp.net beta 2 code that works fine on an XP Pro machine, but on a
Windows 2003 Server gets the following error:

System.Net.Mail.SmtpFailedRecipientException {"Mailbox unavailable. The
server response was: 5.7.1 <ve****@quixnet.net>... Relaying denied. IP name possibly forged [208.179.189.145]"}
System.Net.Mail.SmtpFailedRecipientException

Any idea what would cause that?

[Gerhard]

Here is the reply I got from the system administrator at for that computer:

"I had already set this setting to relay everything and you still got the
message.

"I now set it to 127.0.0.1 and for the whole domain. I can easily use the
SMTP server with Outlook express, it forwards just fine.

"You only get the error message with ASp.net.

"It is not the SMTP setting."

The code works fine on a Windows XP Pro Machine (which is where I am
developing), so any other ideas where I should look on this? I did change
the web.config settings to match the server settings on the new machine.

Windows 2003 Server is not a product I have dealt with personally.

Thanks.

Bob
"Mikael Östberg" wrote:

You have to allow relaying in your SMTP server.

Check security settings in IIS.

This is dine by right-clicking Default SMTP Virtual Server and choosing
properties.

Then go to the Access tab. Click on the Relay button at the bottom of the
dialog.

Add the IPs you want to grant access. By default this is turned of
completely and since your web server is on the same machine, you could add
127.0.0.1 as the only entry in the list.

You can also open it up completely by checking the radio button All except
the list below and leave the list blank. However, if it is a public server
that is not a recommended setting.

That should solve that issue.

Mikael Östberg
"Gerhard" <Ge*****@discussions.microsoft.com> wrote in message
news:3D**********************************@microsof t.com...

Hi,

I some asp.net beta 2 code that works fine on an XP Pro machine, but on a
Windows 2003 Server gets the following error:

System.Net.Mail.SmtpFailedRecipientException {"Mailbox unavailable. The
server response was: 5.7.1 <ve****@quixnet.net>... Relaying denied. IP

name

possibly forged [208.179.189.145]"}
System.Net.Mail.SmtpFailedRecipientException

Any idea what would cause that?

[Gerhard]

Found the problem, so this is resolved. Thanks for your help.

"Mikael Östberg" wrote:

You have to allow relaying in your SMTP server.

Check security settings in IIS.

This is dine by right-clicking Default SMTP Virtual Server and choosing
properties.

Then go to the Access tab. Click on the Relay button at the bottom of the
dialog.

Add the IPs you want to grant access. By default this is turned of
completely and since your web server is on the same machine, you could add
127.0.0.1 as the only entry in the list.

You can also open it up completely by checking the radio button All except
the list below and leave the list blank. However, if it is a public server
that is not a recommended setting.

That should solve that issue.

Mikael Östberg
"Gerhard" <Ge*****@discussions.microsoft.com> wrote in message
news:3D**********************************@microsof t.com...

Hi,

I some asp.net beta 2 code that works fine on an XP Pro machine, but on a
Windows 2003 Server gets the following error:

System.Net.Mail.SmtpFailedRecipientException {"Mailbox unavailable. The
server response was: 5.7.1 <ve****@quixnet.net>... Relaying denied. IP

name

possibly forged [208.179.189.145]"}
System.Net.Mail.SmtpFailedRecipientException

Any idea what would cause that?

[dp]

I have the same problem, can you please share the solution with me ?

dimitris

"Gerhard" wrote:

Found the problem, so this is resolved. Thanks for your help.

"Mikael Östberg" wrote:

You have to allow relaying in your SMTP server.

Check security settings in IIS.

This is dine by right-clicking Default SMTP Virtual Server and choosing
properties.

Then go to the Access tab. Click on the Relay button at the bottom of the
dialog.

Add the IPs you want to grant access. By default this is turned of
completely and since your web server is on the same machine, you could add
127.0.0.1 as the only entry in the list.

You can also open it up completely by checking the radio button All except
the list below and leave the list blank. However, if it is a public server
that is not a recommended setting.

That should solve that issue.

Mikael Östberg
"Gerhard" <Ge*****@discussions.microsoft.com> wrote in message
news:3D**********************************@microsof t.com...

Hi,

I some asp.net beta 2 code that works fine on an XP Pro machine, but on a
Windows 2003 Server gets the following error:

System.Net.Mail.SmtpFailedRecipientException {"Mailbox unavailable. The
server response was: 5.7.1 <ve****@quixnet.net>... Relaying denied. IP

name

possibly forged [208.179.189.145]"}
System.Net.Mail.SmtpFailedRecipientException

Any idea what would cause that?