Inbound Email not being recieved via ADSL Router using POP3 Connector 1

[bdavidso]

Hopefully sonmebody can shed some light!!
I have an NT PDC with Exchange 5.5 connected to an ADSL Netopia Router. They are providing internet and supposedly email transfer to the registered domain I have. They are telling me they are forwarding the mail to the router via an MX record and then the router is forwarding the mail to my server see below for background info. I have setup the IMC for SMTP and this works with no problems as far as sending mail out. I have then setup a POP3 connector and added all of the Exchange email accounts that exist on the Exchange server. Each account has the proper exchange account selected. I do have a descrepancy with the password with the ISP. They are telling me what the password is but none of the Exchange users can receive email. I know I have missed something either in the setup or what, that is the question. HELP !!


Background:
Running SBServer 4.5. with Exchange 5.5 NT SP6a.
Server IP 192.168.1.2 private network
LAN IP 192.168.1.1 private network
WAN IP 216.199.31.198
Clients are using Outlook 2000 with Static Private network IPs
DNS provided by ISP

Thanks for the assistance!

 

[PRW2000]

First thing i would try is to make sure that your mx record / alias records are working at the isp by doing an NSLOOKUP on the domain eg "nslookup

http://www.fredsmith.com"

and it should resolve this and tell you what your DNS server is what your allias is and what your ip address is.

Other than that i would ask them to change the password for you account.

Have you had any reports of people getting messages returnd as undeliverable?

 

[bdavidso]

The below is information based on the NSlookup tables. I had to remove the DNS server names since I am at work.
>

http://www.southernarchitect.com

Non-authoritative answer:
Name: fp2k-1.fdn.com
Address: 216.199.2.163
Aliases:

http://www.southernarchitect.com

> mail.southernarchitect.com
Name: mail.southernarchitect.com
Address: 216.199.12.42
I have had them change the password and still answering your second question, getting messages returned undeliverable via the below message. The ?? are actually user names.
----- The following addresses had transient non-fatal errors -----
> <??@southernarchitect.com>
> <??@southernarchitect.com>
>
> ----- Transcript of session follows -----
> <??@southernarchitect.com>,<??@southernarchitect.com>... Deferred:
Connection timed out with mail.southernarchitect.com.
It almost appears that the ISP is not forwarding properly or I do not have Exchange setup to grab the incoming email properly? I am just not sure why exchange is not pulling in the mail. Do I need a some type of 3rd party program to grab the email ?

Thanks for all the assistance!

 

[bdavidso]

My next question to all the Experts!!
Is it possible that I do not even need the POP connector on Exchange since it appears that the POP connector is looking for specific mailboxes on the ISP versus the ISP should be simply routing all inbound email to southernarchitect.com via the WAN port to the LAN port on the router. If this is to be true then the IMC would be set for inbound & outbound for all mail delivery and then Exchange would simply receive all mail for the above domain and route it to the appropriate mailbox.
Any thoughts comments on this being the problem that I have.

Thanks again for the help !!

 

[PRW2000]

Well looks like all the DNS is correct then and no you don't have to have a 3rd party piece of software SBS 4.5 should come with the pop3 conector!

Do you have server setup to dump all mail into a specific mailbox(s) or have you left the server to work out where the mail has to go by looking what comes before the @ symbol?

If it's the later then you need to make sure that your clients all have those aliases otherwise server will return them as undiliverable.

Only other reason i can think of is incorect user name / password or port 110 blocked!

 

[PRW2000]

if all your mail is for the domain southernarchitect.com then the pop3 conector should be set to pick up mail for *@southernarchitect.com this usually already exists there is no need to specify individual names @southernarchitect.com

Then as long as all your alias are corect exchange should be able to work out which mailbox the message is for and dump it straight in there.

So all you need to do is enter the main user account and password and tell server how often to collect mail and it should go do it!

 

[bdavidso]

PWR2000 and to All...

I thought I had it setup to work out where the mail has to go by looking what comes before the @ symbol. But now that you have raised that question, I am not sure that it is setup that way at all. I have missed something if it is not setup that way.

Now as far as the aliases, can the exchange users address have the same name as the aliases or do they have to be different, if I am asking that question correctly ? If I look at users properties in exchange and the user has a defined SMTP address would that have to be different than the defined email address in POP3 connector address? Or do I not need the POP3 connector at all and by it running it is causing more headaches and undeliverables since the POP3 is going out and looking for specific mailbox addresses versus the IMC going out and looking for all mail @southernarchitect.com and then resolving the email address by the SMTP address in each users mailbox ?

Thanks again for all the assistance!!

 

[PRW2000]

You don't need to specify each individual users email address in the pop conector beacuse all your mail is for anything@southernarchitect.com so you just need to configure one address to pick up from that being *@southernarchitect.com then when the server goes out and picks the mail up it will sort the mail into the correct mail boxes by looking at the first part of the address eg bob.smith it will then compare that to the users email addresses within your system (there aliases) an providing it can find an entry it will put that in there mail store.

So if a person has an email address of bob.smith@southernarchitect.com and that is what you have configured his address to be then if some one sends a message to bob.smith@southernarchitect.com it goes to you main account when exchange connects to your isp it just asks for all mail for domain southernarchitect.com so will pick up bob.smiths mail as well it should then determin what mail box to put that in by it self by looking at the first part of the address there is no need to configure the pop conector to go and check every mailbox you have created.

 

[chifu]

I have not been able to get a pop3 incoming feed to work with Exchange. I believe it does not work, unless some one has managed this.

Ask your ISP to give you a SMTP feed. They will give you a IP address which you need to set your Exchange server to. Then set up your Exchange Internet Connector with the addressing details provided by your ISP and away you go. Remember to set the DNS server addresses in Networking.

The idea is that any one sending Mail to your E-mail address has a DNS entry which points directly to your server.

 

[chifu]

One further thing about the IP address of your Exchange server. Because you have a Internal IP address for it, you will need to find some way of mapping this to the Real internet address that your ISP will provide. This very much depends on how your network is set up.

I assume your router is running NAT, in which case you could set up a one-one NAT link between the Real address and the internal address eg. If the address supplied by the ISP is 234.324.56.12 and your Exchange server is 192.168.4.32 then create a one to one link between the two. This will allow E-mail sent to 234.324.56.12 to be forwarded to 192.168.4.32

 

[yizhar]

HI!

I haven't yet read all the messages here, but one more thing:

ADSL uses a different MTU (maximum packet size) then Ethernet.
Some problems like these can be solved by modifying registry values on your NT server (which transfers large files through the ADSL link).

I think it is this one but I'm not sure -
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\<AdapterName>\Parameters\Tcpip
Value Name: MTU
Value Data: 1462 (DWORD)

You can try and see if it helps.
Ofcourse you should write down previous values and have a backup.


Bye
Yizhar Hurwitz

http://come.to/yizhar

http://teachers.sivan.co.il/yizhar

 

[bdavidso]

I would like to thank everyone for all of the responses on this issue that I had and would like to let everyone now that it ended up being the ISP that had typed in the wrong IP address for the incoming SMTP mail. Shame on them...

Thanks again for all the support I have received on this trying issue.

It is nice to know that when you set something correctly and try and second guess yourself that I actually did right the first time...

Thanks Again to ALL the experts !!!!!