Don't know how to connect to MS Exchange server via pop3 client

[colpaarm]

Hi guys

From what I understand, if you want to retrieve mail from a mail server you connect to a pop3 server. If you want to send mail, you connect to an smtp server. My boss has this pop3 software and wants to be able to connect to our exchange server. With this is a username and password. For the life of me, I see nothing with regards to setting a username and password on the server side so that clients can connect. And if they do connect, which mail box are they grabbing the info from? Any help/information would be greatly appreciated. Thanks in advance.

 

[jenlion]

You can use exchange to allow pop and smtp for your clients.

If your boss is always on the same network as the exchange server, and is only getting mail from the exchange server, then he doesn't need to configure pop. For example, if the exchange server handles yourdomain.com email, and your boss only needs mail for boss@yourdomain.com, and he has a computer that is only connected to the same network as Exchange, then you don't need anything else.

However, if he has a laptop he takes everywhere and insists on keeping his email with him and not on the server, or something like that, you can configure exchange to route messages in IMS. (Read up first so you don't accidentally open a relay). Then he can use his email client (outlook, eudora, whatever) to send and receive mail through the exchange server -- the exchage server is the pop/smtp server. He could sit at home and use mail.yourdomain.com (or whatever your server is publicly) and that will work fine. Exchange will happily support the local network users connected directly or the pop/smtp user, no problem. It should use his windows domain username and password, and only get mail from the recipient box you set up and associated with that windows server account.

Or perhaps you mean that he has another account that he wants to add to exchange? Maybe he has an address TheBoss@SomeOtherDomain.com that would like to add to his exchange account, and you would like to configure the server to get this mail and dump it to exchange appropriately. In that case you need a POP3 connector. There's a good one at

http://www.christensen-software.com/popcon.htm

You install this (I just put it right on the exchange server) and it will check any pop3 email account and move the messages to the specified Exchange account. So, if you have his SomeOtherDomain password, you can set it to move mail sent to TheBoss@SomeOtherDomain.com delivered to boss@yourdomain.com on the exchange server. Totally transparent to him.

As for your boss having some kind of pop3 software in particular, sounds like his SomeOtherDomain provider is giving him extra garbage you don't need. Find the appropriate username, password, and pop server associated with this account, and ignore the extra software, if this is the case.

 

[bchizary]

hi, quick one for jenlion- or anyone else who can help- i have a very similar problem- im new to exchange so this may be very easy.

We have a pop address with our isp which all mails for our domain (company name.co.uk) go to. we currently use an old ftgate server to pick up the mails and distribute them between all our users, how can i get exchange to do the same? i cant find anything in the options etc to input our username and password etc for our isp our the pop/smtp addresses to send and receive.

Thanks, and sorry for butting in colpaarm, hope answers to this may help maybe??

 

[FatesWebb]

if im not mistaken, and I most likely am, but ill guess and say that he answered that, when he said this...


Or perhaps you mean that he has another account that he wants to add to exchange? Maybe he has an address TheBoss@SomeOtherDomain.com that would like to add to his exchange account, and you would like to configure the server to get this mail and dump it to exchange appropriately. In that case you need a POP3 connector. There's a good one at

http://www.christensen-software.com/popc...

FW

FatesWebb

if you do what I suggested it is not my fault...