Re: Remote users cannot send e-mail through Outlook

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Mark Arnold [MVP] (mark_at_mvps.org)
Date: 07/29/04 

Date: Thu, 29 Jul 2004 15:36:18 +0100

Ooops, my bad there. Just re-read and noticed you're on W2K rather
than W2K3.
Yes, follow the lady's lazy bones "leverage the ISP relay" routine.

Just keep my post as something to consider for when you upgrade to
W2K3.

On Thu, 29 Jul 2004 15:24:28 +0100, "Mark Arnold [MVP]"
<mark@mvps.org> wrote:

>On Thu, 29 Jul 2004 06:44:13 -0700, "Jeff Gross"
><anonymous@discussions.microsoft.com> wrote:
>
>>I have a few users who do not work in our office. They
>>have Outlook installed on their home computers and then
>>dial up to the internet and do a send/receive.
>>
>>I have Exchange 2k3 on a Windows 2k server and the users
>>are configured to allow for SMTP/POP3. All was working
>>fine until earlier this week when they informed me that
>>they could no longer "send" mail. They get the
>>message "The TCP/IP connection was unexpectedly terminated
>>by your mail server. If this problem persists, contact
>>your LAN Administrator or Internet Provider".
>>
>>The users can still receive mail just fine. Also, I had
>>them log into OWA and they said they can send and receive
>>through OWA. Based on that, it appears that it's a relay
>>issue although the only thing that I've done in the past
>>few weeks is install the Microsoft Exchange Intelligent
>>Message Filter add-on. Does this change the relay
>>settings? Any help would be very much appreciated.
>>
>>Jeff
>
>If it was me I'd be completely changing the way of doing this.
>See:
>http://www.microsoft.com/technet/prodtechnol/exchange/2003/library/ex2k3rpc.mspx
>Basically. Outlook 2003 on the Home PC's (See guide for the hotfix
>required). Exchange 2003 with RPC over HTTPS. It's every bit as secure
>as a dial up link. Use a public (Verisign / BT etc) certificate. User
>uses their Internet connection to dial out / broadband to the net.
>
>The message they get isn't the one that they'd get if you'd locked
>them out of being able to relay, so it's probably not that (at first
>anyway)
>
>With the new technology in mind, have a look at smarter ways of doing
>things.

Relevant Pages

  • Re: Ouch! My SBS got hacked! Please help me not be a spammer
    ... With any mail server, the first thing to check is not a Windows virus. ... You should be checking your SMTP _relay_ settings. ... I have eTrust Anti Virus Version: 7.0.139 running with the latest signatures on SBS and all the other client computers. ...
    (microsoft.public.windows.server.sbs)
  • Re: DNS / ISA and Exchange issue
    ... This is neither ISA nor DNS. ... The key to this is the error message: ... The mail server is not configured to accept mail for smtp.ourdomain.com. ... to relay for mir@smtp.ourdomain.com (in reply to RCPT TO ...
    (microsoft.public.isa.configuration)
  • Re: Growing SMTP queue to random domains
    ... Spam Marshall. ... > The only knowledge base article I could find describes this problem ... > only if the mail server is open for relay or is on a black list of some ... The servers that are experiencing this issue are not open for relay ...
    (microsoft.public.exchange.admin)
  • Re: MX & A Records for Dual Domain Smtp Host
    ... Relay is for outgoing mail and doesn't require an MX record. ... outgoing email to another mail server. ... Here is a good article I found that discusses where to look in your config ...
    (microsoft.public.windows.server.dns)
  • Strange SMTP Garbage Flood
    ... Subject: Strange SMTP Garbage Flood ... I'm noticing an increasing amount of weird smtp relay attempts through my ... objective of discovering whether my mail server is an open relay) ...
    (Incidents)