Re: Setup an Exchange so everyone not in domain can send smtp mess

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



You can allow everyone to relay and that won't require them to authenticate. It's not a best practice, but if you understand the risks, you can configure it that way. If you have one network where they can't relay, while others can, then you have a network problem. Try a telnet to port 25 from the other site to your server, send a message manually, and see what happens.
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
..

"Bobson" <Bobson@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:758B9238-0D82-4EE9-8C57-ABEBCAC36F8C@xxxxxxxxxxxxxxxx
Hi Ed,

Thank you for your quick response. What about just a connector/hub? Does it
still need to authenticate?

Here is my real problem...

Our current production server is also working as a relay server. We setup a
"connector" or hub with port 25 so that can relay smtp messagse. However,
with the same accounts, people cannot just send smtp messages from one site
(running by vlan) but all other sites are fine. The accounts they use are all
the same. The error we got is 550 5.7.1.

That cofuse us little because why other sites can send smtp while all
settings are the same, but not from that specific site? the only way to make
that site work is to use an domain admin account to log on. Then we did not
get any errors. Again, why only to this site while other sites are fine?

Thank you!

Bobson

"Ed Crowley [MVP]" wrote:

Anyone who uses an Exchange mailbox must authenticate. You can allow SMTP
relay if you have a POP or IMAP client sending by SMTP to send via that
server, but I don't know whether that is what you're asking for.
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
..

"Bobson" <Bobson@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7A6D8288-E04C-4D30-86F2-970DD7A32B71@xxxxxxxxxxxxxxxx
> Hi Everyone,
>
> For testing purpose, I would like to set up an Exchange server so that
> everyone not in the domain can send SMTP messages.
>
> In order not to mess up our current domain network and our existing
> Exchange
> server, I did set up a new domain and install a new Exchange for that
> Domain.
> And I know I can only send messages out.
>
> Now... I would like to ask ... anyway I can setup that testing server > so
> everyone who does not have a domain account in that testing domain can
> still
> send smtp messagse out thru that testing Exchange server?
>
> Also, does this call "relay" as well -- just for my English purpose :)
>
> Thank you very much for your help.
>
> Bobson



.



Relevant Pages

  • RE: Exchange 2003 SMTP Queue
    ... Jorge, Thanks for the reply. ... I am pretty certain this is not a relay issue. ... >addresses of the Exchange server can relay through this ... If your Exchange server is blocked by the remote ...
    (microsoft.public.exchange.connectivity)
  • RE: error message in sbs reports
    ... kind of relay attempt through the server. ... Relay" for the SMTP Connections, this indicates that the relay has already ... off the Exchange server before you follow the steps. ...
    (microsoft.public.windows.server.sbs)
  • RE: Allowing Relay
    ... relay off your Exchange server. ... I agree with Lanwench that we should disable all relay options ... relay e-mail from your Exchange Server, we can query the SMTP log file, ... Microsoft Online Partner Support ...
    (microsoft.public.exchange2000.general)
  • Re: Relays Question
    ... If you allow relay, you ought to also require authentication. ... internal-only Windows 2003 server with the IIS SMTP service that does the ... the network can use the Exchange server as an open relay - do we have ...
    (microsoft.public.exchange.admin)
  • Re: Relay Question
    ... An open relay ... is an SMTP e-mail server that allows third-party relay of e-mail messages. ... Exchange 2003 is by default configured to prevent open relay. ... Microsoft does not control these sites ...
    (microsoft.public.windows.server.sbs)