Recent Posts

Tags

News

  • Search

    <input class="BlogSearch" type="text" name="searchBox" id="blogSearchText" value="" onkeypress="return blogSearch(event, this);"> <input type="button" value="Search" onclick="return blogSearch2('blogSearchText');" class="BlogSearchButton"> <script type="text/javascript"> function blogSearch(event, oInput) { var keyCode = (event) ? event.keyCode : keyStroke.which; if (keyCode == 13) { top.location = 'http://www.google.com/search?q=' + escape(oInput.value) + '+inurl%3Ajavier+site%3Amsmvps.com'; return false; } return true; } function blogSearch2(oInputId) { var oInput = document.getElementById(oInputId); top.location = 'http://www.google.com/search?q=' + escape(oInput.value) + '+inurl%3Ajavier+site%3Amsmvps.com'; return false; } </script>

Community

Email Notifications

SBS Blogs

Helpful Sites

Archives

Javier's SBS Wonderland

Take the red pill and see how far down the rabbit hole goes...

Email problems when using the POP3 connector

If you are using the POP3 connector to receive mail, but you have some accounts (like a remote user) that are not collected by the SBS box you will find that it’s not possible to send mail to those accounts from inside the SBS domain.

As soon as you try to send mail to that account, Exchange will send you and NDR back saying "The email account does not exist at the organization this message was sent to.  Check the email address, or contact the recipient directly to find out the correct address."

This happens because by default Exchange is setup to be authoritative for the domain, any address that doesn't exist on you server will appear as undeliverable. The best way to workaround this is to collect all mail on your SBS box and then make the remote user connect to the SBS box instead of your ISP (you could use OWA, RPC over HTTP or even POP3/IMAP).

Another workaround to this problem is to open Exchange System Manager-> right-click Virtual SMTP server-> Properties-> Messages tab-> Specify your ISP's SMTP mail server on the field “Forward all mail with unresolved recipients to host".

Note: If you are using SMTP to receive mail you should not do this (there is no need anyway)... you could cause a mail loop because of this.

Posted: Feb 23 2005, 12:28 PM by Javier | with 11 comment(s)
Filed under:

Comments

Javier said:

SBS 2003 has an option, on the 'pop3 connector manager properties' dialog box, which allows you to 'specify the mailbox where undeliverable mails are sent'. This can be found on the troubleshooting tab. I have tried this but it does not work. Please advice.
# April 12, 2005 11:47 AM

Javier said:

Hi,

I have problems with setting up pop3 connector.
Server is running SBS 2000 with SP4, and Exchange with SP3. I have
configured pop3 email clients to relay emails in SBServer. Emails are
downloaded successfully from ISP but didn`t relay to recipient on SBServer.
In the Event Viewer doesn`t appear any error event rather then only
information event:


Event Type: Information
Event Source: POP3 Connector
Event Category: Download
Event ID: 4023
Date: 4/21/2005
Time: 4:58:53 PM
User: N/A
Computer: SERVER
Description:
The POP3 session transcript was:
<G>: +OK POP3 server ready (7.1.005)
<134D7E5112512B5EF1F3960DA559C26B111DE05D@mail.domain.net.>
<C>: USER cad
<S>: +OK Password required
<C>: PASS <secret password>
<S>: +OK 1 messages
<C>: STAT
<S>: +OK 1 1445
<C> { Downloaded and deleted messages if neccessary. }
<C>: QUIT
<S>: +OK POP3 server closing connection

And after that appears this information event:

Event Type: Information
Event Source: POP3 Connector
Event Category: Delivery
Event ID: 4032
Date: 4/21/2005
Time: 4:58:57 PM
User: N/A
Computer: SERVER
Description:
A recipient has been processed. Recipient information:
NDR Status Code: 600
Error Code: 00002745
SMTP Reply:
SMTP Name: cad@domain.net
SMTP Host: server.domain.local


Can anyone realize where is the problem?

Thanks
# April 22, 2005 3:26 AM

Javier said:

If you've installed anything *(including Virus Scan Enterprise) which blocks Port 25 to protect from Mass Mailing Worms - this will cause this error.

# June 21, 2005 12:41 PM

TrackBack said:

Email problems when using the POP3 connectorooeess
# July 22, 2005 12:10 AM

TrackBack said:

Email problems when using the POP3 connectorooeess
# August 2, 2005 7:56 PM

Javier said:

Solution might be here, http://www.experts-exchange.com/Networking/Email_Groupware/Exchange_Server/Q_21061241.html
# August 4, 2005 6:41 PM

Javier said:

I would start with modifying the primary SMTP address on the user accounts to use the email address of what is used publicly. For example, if a user bill has an email account on from the isp of bill@ispsevice.net, then make that his primary SMTP address and the default internal address such as bill@company.local as a secondary. If that doesn't work, you may have to use a smart host on the Virtual SMTP Connector and point to the ISP's smtp server in addition to modifying the primary smtp addresses. If the ISP required authentication for smtp, you may have to confiure that as well on the Virtual SMTP Connector.
# August 22, 2005 5:28 PM

TrackBack said:

# November 7, 2005 10:11 PM

TrackBack said:

# November 7, 2005 10:47 PM

Javier said:

I responded to Susan's article about this situation with a word of caution. Here is the support article from Microsoft that discusses how to properly share an SMTP name space with more than one mail server:

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

Here is where I described the mail loop that Javier mentions in his note at the end of his article:

http://msmvps.com/bradley/archive/2005/11/07/74848.aspx#74885
# November 8, 2005 12:14 PM

Javier said:

I just want to emphasize two things:

1) You only need to do this when using the POP3 connector. If you are using SMTP mail... DO NOT use it.

2) KB311721 is basically a different (and more complex) way of doing the same thing (although it gives you more options). But again, there is no "proper way" to do this if you are using SMTP... just don't do it.
# November 8, 2005 12:40 PM
Leave a Comment

(required) 

(required) 

(optional)

(required)