Re: SMTP Relay....Driving me crazy....

As far as I know Exchange will only listen on one port. This client needed
it to listen on 25 for general functionality. In order to accommodate the
"workaround" for those traveling users, I added another small app listening
on port 80 and forwarding to 25 on the Exchange server. This was back when
RPC over HTTP wasn't available.

I hope this is less confusing.

--
Claus
"SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message
news:uGTs4GEoHHA.1220@xxxxxxxxxxxxxxxxxxxxxxx
I find your comments a little confusing.

Yes, RPC over HTTPS is the best answer, for domain member machines. My
users on non-domain members whinge about having to put in their
credentials each time they open Outlook. I give the smallest part of a
Rat's Heiney about this inconvenience because I know it is a secure method
of access requiring one thing, the user to type their password, they can
live with it because I say 'that's the way it is, live with it'.

The confusing part is the 'free little mail server' and why you would run
this on port 80. If you want to 'obfuscate' SMTP Exchange will happily
listen to whatever port you desire.

"Claus" <cjobes@xxxxxxxxxxxxx> wrote in message
news:uA8nxV$nHHA.5052@xxxxxxxxxxxxxxxxxxxxxxx
SG,

You are totally right. That's why RPC over HTTP is a real good solution.
I had some clients that insisted on a POP3 solution. In those cases I
installed a free little mail server on the SBS, configured it to listen
on port 80 and then forwarded all email internally on port 25 to the
exchange server. Worked fine but I'm not a big fan of it since Outlook
over the Internet has made possible.

--
Claus
"SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message
news:ehTx8L%23nHHA.4552@xxxxxxxxxxxxxxxxxxxxxxx
I'm curious about your experience with SMTP blocking.

Is it similar to AU? eg. Anyone can connect direct to me on port 25 (ie.
I can receive by SMTP) but I must relay out through the ISP's (BigPond)
server (I cannot connect to a remote :25, except ISP mail server). If I
pay an additional monthly fee, $10/mth for static IP, I can do direct
SMTP.

I ask mainly because I have travellers using various internet
connections while away. We allow them auth'd SMTP to the 'home' server
but as similar restrictions come into play around the world I'm actually
thinking of closing off authSMTP m'self (on the basis that often the
person _we want_ to use it can't anyway).

"Claus" <cjobes@xxxxxxxxxxxxx> wrote in message
news:OKIPKnynHHA.4900@xxxxxxxxxxxxxxxxxxxxxxx
One question, one observation:
When you test the account in OE, does it find the SMTP server and
sending testmail fails or is it failing on finding the server?
You should tell your client that the remote user will only be able to
relay mail if he/she is connected to the same ISP. Most ISPs are
blocking 25 on their perimeter except for their own mail servers and
the clients that purchased business connections with static IPs.

--
Claus
"Mark Greene" <notvalid@xxxxxxxxxxx> wrote in message
news:92pe535g6be05amr3i5shncf4n2soprlk7@xxxxxxxxxx

I have a customer that requires a remote user to relay messages
through the Exchange SMTP Server. I've tried to talk them into using
Outlook over the Internet (RPC over HTTPS), but they insist on
relaying through the SMTP Server....

The "Allow all computers which successfully authenticate to relay,
regardless of the list above." box is checked, but the user still
cannot relay messages through the SMTP server. The Outlook Express
client is is set to use SMTP authentication, and I've tried using the
several different iterations of username (username, domain\username,
username@domain, etc.) but still cannot get the mail to send from the
Outlook Exprerss client. The user can use POP3 to check their
messages without any issues using just their username and password....

What gives??

Thanks for any help....










.

Relevant Pages

  • Re: Unable to print to networked printer - get access denied messa
    ... Check the permissions on the server assuming the client has a true RPC ... How is the Standard TCP/IP port configured for the device? ...
    (microsoft.public.windowsxp.print_fax)
  • Re: interfaces lo:1 lo:2 lo:3? (for remote ssh tunnels)
    ... That's the problem tunneling (port forwarding) solves. ... >>can't get past the client firewall. ... > I don't understand why the server would be making the ... server initiates another connection to the client -- in this ...
    (Debian-User)
  • Re: RealVNC
    ... I recently upgraded a client to SBS 2003 Premium with ISA. ... This server was so full of trojans, spyware, ... the vendor complained because I would not let pcAnywhere ... Then there is default Java listening port on port 5800 on the ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Connection Issue
    ... through port number 3389 and a workstation on the LAN through port number ... I understand that you want to allow a LAN client ... and you have configured server publishing rule ... > By default Terminal Server and Windows 2000 Terminal Services uses TCP ...
    (microsoft.public.windows.server.sbs)
  • Re: RealVNC
    ... I use VNC behind server ... Default listening port for RealVNC server that runs on the machine ... And then "other"party - not the client can run RealVNC Viewer in ...
    (microsoft.public.windows.server.sbs)
Loading