Link to home
Start Free TrialLog in
Avatar of BuildingITC
BuildingITC

asked on

Outlook POP SMTP - Sending reported error 0x80040201

Exchange works fine from within the office.  From home when we try to POP/SMTP into the server we get the error message in the subject line when sending email to an domain.  We receive fine but cannot send, reply or forward.  I have searched high and low for a meaning of this error and am stumped.  We have Outlook 2000 and 2003 on the home PC's and Small Business Server 2000 on the office server.  It is behind a WatchGuard Firebox 700.  Any help would be appreciated.
Avatar of David Wilhoit
David Wilhoit
Flag of United States of America image

So you are connecting to POP from outside? Hopefully, different profiles for Outlook? give more details of how you're set up, please.

D
Avatar of BuildingITC
BuildingITC

ASKER

Home PC only has one profile for POP3 SMTP to server.  Office PC just has exchange setup - no POP.  Hope this helps.   Clean setup.
OK. the internet email setup has to authenticate on the Exchange server. Do you have that checkbox set up on the profile?

d
Hi BuildingITC

Has sending email from the home PC connecting to the SBS 2000 worked in the past?  Is the error just on OL 2000 or OL 2003?

If Kidego's comments are not working to resolve your issue, It may be that you need to do a detect and repair on both or either/or depending on which program the error originates from.
Here is the email I get back from the system...

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

      Subject:      RE: Update
      Sent:      12/30/2003 12:59 PM

The following recipient(s) could not be reached:

      'Tom McCarthy' on 12/30/2003 12:59 PM
            550 Requested action not taken: mailbox unavailable
hmmm. sounds like you have a contact in your profile at home, that may be old. If so, delete the contact, and recreate or send an email to his smtp address, as you know it to be. Second, the NDR you get, is it from your Exchange server? what is the POP3/SMTP server you have specified in your home profile?

d
That message is coming from my Exchange box.  This happens to anyone outside our own domain so it is not contact specific.  Our mail server is mail.buildingitc.com for both POP and SMTP.  Hope this helps.
OK, just so I'm clear, other domains can send mail to your server from the outside world, yes or no? your own users, have no problems internally, but externally, they can receive but not send, yes?

D
Other domains can send email to us no problem.  Inside the office (through exchange not POP/SMTP) we have no problem.  Outside the office we can receive via POP but not send.  That is all correct.
OK, did you check what I asked you to check? Is the box checked in your Outlook profile that says, My server requires authentication? Please verify this for me, let me know...

D
Yes I did.  Same effect.

It is funny that when I click Test Account Settings it sends and I receive the test message no problem.

When I send to a user in my domain it sits in my outbox but when I send to a user outside my domain it clears the outbox goes into my sent items by then I get the NDR report.
OK, so you're not able to send to anyone at all. Is both incoming and outgoing mail server set to the exchange box? What version of Outlook, BTW?

D

I am using Outlook 2003 and my partner uses 2000.  We both have the same problem.  Incoming and outgoing set to mail.buildingitc.com
Strange - If I REPLY to someone in our domain it sends right away even though I have email in my outbox sitting.  If I create a new email to someone in my domain it fails.  Very odd.
No other internet email accounts tied up in this profile? When you create a new email, where do you choose the "To" field, from a contact list, a PAB, or what?  And what ISP are you using?

D
Only email account setup.  Only one profile.  I mostly reply to messages so the T0 field is auto populated.  I am on BellSouth.net and our server is on InterNAP.
Reading this again, just noticed something... when you telnet to port 25 on your mailserver, does watchguard answer for it, or does Exchange? Could be that Watchguard is acting as the SMTP gateway, and not allowing you to authenticate.

D
I think I may have found the problem.  I searched the MS KB for the 550 error and found a issue specifically related to the firewall.

http://support.microsoft.com/default.aspx?scid=kb;en-us;305007

I am checking my SMTP proxy settings now and will let you know.
LOL, ha!! I beat you to it :)

D
Too funny.  I am installing the firewall configuration utility on my server so I can check the policy and make the changes.  Only getting 8Kbps for some reason so this may take a couple of hours.
I'm East coast time, you're not :) I'm gonna eat, you let me know how it goes.

D
Well, I tried what the KB article said and no luck.  I even went as far to turn on full logging and added every header type to the allowed list.  I finally just deleted the SMTP proxy and created a manual rule for SMTP to act as a simple filter.  When I did that the NDR message I am receiving in my inbox changed to the following.  I changed the user to xxx to avoid spiders sending my buddy spam.  Anyway, I wend in and looked over my SMTP Virtual Server settings and everything looks fine.  It is locked down to just allow its own internal IP to forward to prevent it from being used as an open relay.  I am stumped... again.

550 5.7.1 Unable to relay for xxx@anewbroadband.net
ASKER CERTIFIED SOLUTION
Avatar of David Wilhoit
David Wilhoit
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial