Re: 553 sorry, relaying denied from your location

Correct. The default SMTP Server uses (myIP), port 25. The added SMTP server
uses (myIP), port 465. The client connects fine when set up for secure
connection on port 465. The relay won't go through.

"Ed Crowley [MVP]" wrote:

In the client you specify the SMTP port number that is to be used.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"ScottB" <ScottB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9BBDEEB9-C7A2-461D-8DAD-FD0DE98BC416@xxxxxxxxxxxxxxxx
Yes, client contacts Exchange Server. Here are some parameters that might
be
a problem, but I don't know how to fix:

1. Default SMTP Server is on port 25.
2. Newly created server is on port 465, Same IP. I have tried various
iterations of secure, always secure, 128 bit encryption, etc.
3. Messages to relay go out on same SMTP server as they come in, and
corresponding error messages in the log refer to that server.
4. There is one SMTP Connector with Default Server as Bridgehead

So: Relayed messages would go out as secure on port 465? If so, perhaps
that's the issue. And, if so, is there a way to make them relay through
the
Default Virtual Server instead, which would be on Port 25?

Thanks for keeping with me on this. There must be a way...

"Ed Crowley [MVP]" wrote:

Are you contacting an Exchange server with the client? I may be wrong,
but
that doesn't appear to be an Exchange response.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"ScottB" <ScottB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C36B33AA-47C3-4BC4-B19A-383CC5A47DB2@xxxxxxxxxxxxxxxx
Hmm. I had used username@xxxxxxxxxxxxx I changed to
domain.local\username\alias and it wouldn't authenticate.
domain.local\username (or domain.com) still gives me this:

Your message did not reach some or all of the intended recipients.

Subject: test
Sent: 7/18/2007 9:21 AM

The following recipient(s) could not be reached:

scottsails@xxxxxxxxxxx on 7/18/2007 9:21 AM
There was a SMTP communication problem with the recipient's
email server. Please contact your system administrator.
<slonet.water-law.local #5.5.0 smtp;553 sorry, relaying
denied
from your location [64.122.12.225] (#5.7.1)>


"Ed Crowley [MVP]" wrote:

Did you enter the account in the format:

Domain\User_ID\Alias

or Domain\User_ID if User_ID = Alias? Or using forward slashes
instead
of
backslashes (some clients don't like backslashes)?
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"ScottB" <ScottB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:19F61574-2E8F-4549-953F-73F75EE134C4@xxxxxxxxxxxxxxxx
I'm using Treos and the SnapperMail email application, IMAP4, and
SMTP
for
send email. I have set up a dedicated secure SMTP Virtual Server for
this
purpose using port 465. As to authentication, I've tried every
combination
I
can imagine. For email within the domain all is well. But sending
mail
to
an
external domain from the Treo (always?) gets the 553 error.

Previously, I used the default virtual server, not secured, and
relaying
worked fine. But I've been having spam problems.

Ideas?









.

Relevant Pages

  • RE: DNS and Exchange issues
    ... with the Exchange Server after you have installed the patch 888619. ... XFOR: Telnet to Port 25 of IMC to Test IMC Communication: ... Start Exchange System Manager. ... Port 21 enables external and internal file transfer ...
    (microsoft.public.windows.server.sbs)
  • Re: MSADC 8355 LDAP Result failed
    ... I receive 2 when the server restarts. ... Event Category: LDAP Operations ... Opening LDAP session to directory xxx on port 389. ... If you put Exchange on one, ...
    (microsoft.public.exchange.setup)
  • Re: Exchange 2003 - POP3 only delivers email to Administrator
    ... Server to allow internet users access Exchange through POP3 services, ... Port 21 enables external and internal file transfer ...
    (microsoft.public.windows.server.sbs)
  • Re: Created on Access 2003, but.......................
    ... But that's not secure under any scenario, as any port scanner ... Well, you still need a userid, password and database name. ... You're assuming the server remains in a secured configuration. ...
    (comp.databases.ms-access)
  • Re: ConfigDSInteg error
    ... Agreement to point to the new Exchange 2003 server is so that it will have ... You would also change the port ... Any ADC connection agreements configured to point to the SRS would need to ...
    (microsoft.public.exchange.setup)