The MS email server used with MS servers is Exchange and it works SMTP only to get the mail.  I would expect that would be the same email  server functionality that they would provided with the home server.  There are some add-ons that allow for download via POP3 however they also simply download all the mail in the account expecting that the email client will get the email from the local server.

Hallo everybody, I'm new to this community and have just finished installing Mercury/32 on my Windows Home Server system. Installation was really a piece of cake and it works absolutely as expected, Mercury really is a great and mature product! 

Just one small problem is left open for me which I cannot solve, even after careful reading of all of the available help files. I'm using my internet providers POP3/SMTP email services. Previously I was able to configure in Outlook *not* to delete emails after downloading them via POP3 client access to my local system (I want to keep them for a certain time to be able to download again from a different site). In Outlook this is done simply by setting an option in the setup window for this specific connection. Obviously I cannot do that with the MercuryD POP3 client module? Whatever I tried, as soon as the email was downloaded to my windows home server systems with MercuryD it gets deleted on my ISPs mail server. The only option I found was in the setup for the POP3 *server* module, but this really is of no help for me. Do I miss something? Or is it simply impossible in Mercury?

Thanks for any hint or pointer to a reference.

Lothar

Sorry, this is not possible when using MercuryD - it's meant to retrieve all mail from the POP3 mailbox.

/Rolf 

It is really impossible in Mercury.  Mercury/32 is a mail server and as such will always download all if the mail for the server.  If anyone wants to get it via POP3 they go to this server and not the original source server.  It actually makes no sense to add in all of the other POP3 filtering and tools required to make this possible using MercuryD. 

Thank you very much for your comments, I appreciate that. It's too bad Mercury cannot do it. However, how comes Outlook can tell the ISPs POP3 server to keep the email data? Isn't this simply a protocol issue?

Normally I access my email from two locations and need to keep it for that reason during the first download.... Anyway, looks like I need to go back to "original Outlook" then, which is a shame.

Thanks again!

Lothar

[quote user="LH2312"]

Thank you very much for your comments, I appreciate that. It's too bad Mercury cannot do it. However, how comes Outlook can tell the ISPs POP3 server to keep the email data? Isn't this simply a protocol issue?

Normally I access my email from two locations and need to keep it for that reason during the first download.... Anyway, looks like I need to go back to "original Outlook" then, which is a shame.

Thanks again!

Lothar

[/quote]

Outlook and other POP3 clients are built with the ability to do things that are not built into the POP3 protocol.  One of these is to download only unread mail and to not delete the mail on the server.  When you are using a mail server to download mail from another server via POP3 this is not a function that is either required or desired.  The new server has the ability to serve up the downloaded mail via POP3.  Now if you are not wanting a server function then you probably do not want to download mail via MercuryD.

Well, as Thomas said, your option is to set Mercury as POP3 server (or IMAP if you prefer that) for the other location as well. To do this you will need a static IP address for your Internet connection, or some kind of DynDNS setup.

/Rolf
 

Well, I think I need to explain a bit why the functionality Outlook offers here is actually a very desired one, at least for me. I have setup a (small) home network, which is controlled by a machine running Windows Home Server. This offers me backup, central web services and other things, based on Win Server 2003 SP2 SBS. In parallel I have to collect0 email from different email accounts, all accessible by POP3/SMTP only (no IMAP funcs). Several of these accounts are for important incoming status emails from remote controlling systems, which are actually processed from two different locations, but without a possibility to implement a static server based on DynDNS or similar thing. In fact, why should I do this, if the ISP is offering this functionality already for free to me??

Besides that, I want to get rid of having to run two computer systems all the time, one being the windows home server (this is running 24/7 anyways) and in parallel another system to pull the POP3 emails from my ISP. As I said, I did this with Outlook in a very convenient way; just pull the email and keep it on the ISP server until the second system also downloaded it. It's just ticking an option box in the Outlook POP3 client setup.

It's no big thing that Mercury cant do it, as I said. At least for me this means simply continuing using Outlook 2007 directly and running two systems (which I was trying to avoid). Besides that I hope Microsoft will finally implement an email component add-in for their Windows Home Server. I expect it will offer the same functionality as Outlook nowadays by then.

Again, thanks for your suggestions!

Lothar

By using Mercury you are effectively replacing your ISP's mailserver with your own and all your clients should get their mail from Mercury.

The ISP server becomes just another link in the delivery chain that your clients (Outlook etc.) do not need to know about.