David Lemson's WebLog

Product Unit Manager, Exchange

Blogs

How are you using the Windows 2003 POP Server, Part II

  • Comments 23
  • Likes

In a previous post, I asked people how they are using the Win2K3 POP server and what features they wish it had.  One thing I'd like to get, especially from people who posted that they do use it today, is some more details on why and how they are using it. 

1) It seems to me that a Windows Server license is pretty expensive, so are you buying Windows Server for other reasons and just happen to use the POP server because it's free, or did the POP server play a role in choosing Windows Server?  Do you have other dedicated servers already?

2) What kind of scenario are you running it in?  Are you an ISP, are you running it for your home/family? Are you running it for a business? 

3) What other options did you look at and why did you or did you not settle on using the Windows POP server?

If you would like to send me a response via private mail or feedback, please feel free to do so.

Comments
  • PS - if you want to email me directly, my address is dlemson@microsoft.com. I do appreciate people giving me their email addresses in their feedback so I can ask follow-up questions. No, I won't send you spam!.

  • I didn't realize that Win2k3 had a POP server until reading your post. I'm currently in the initial phases of setting up a business and was dreading having to pick up an exchange licence. Now instead of Win2k I'll definitely pick up 2k3 on one machine to handle my email, since I'm starting a small ISV i have no reason for a full blown exchange server and this would definitely suit my needs. Thanks for the info, I'll let you know how it goes!

    [paul@paultyng.net]

  • Dammit now you went and lost a sale.

  • Well, Ferris, I don't really consider the Windows POP server to be a real competitor to Exchange. Exchange offers so much more: OWA, MAPI (full support for Outlook), antivirus and antispam hooks/features, mobile access from phones, full-text indexing and thousands of more things.

    I have an idea of what I think the competitors to Windows 2003 POP server are, but I'd love to hear from real people what they consider to be the real competitors.

    And, finally, why would you buy a Windows 2003 Server license and use POP, when you could buy a Windows Small Business Server Edition 2003 license, which comes with Exchange?

  • We've (small ISP) been using XMail (http://www.xmailserver.org) for quite some time. It's certainly not as friendly as Win2k3's POP server, but allows multiple domains, filters, custom authentication, etc. and isn't too difficult for someone competent to set up. And it runs just fine on Win2K so no need for upgrading to Win2K3 :).

  • Currently we are looking to utilize Exchange for calendaring, but when meetings are POP'ed through W2K3's server, it strips any meaningful data and makes it just a text message. It has a neat feature to provide a link to OWA, but would be ideal is if users that POP'd email could have an attachment that would be digestable by Outlook as an external viewer. Our users have choice in their email client, but would like to use Outlook for calendaring.

  • One side effect of allowing users to POP their email is that it removes it from the Exchange Information store. Which then breaks access to OWA and Outlook. One thing would be nice is to allow IT to enforce at the server level a "Leave on Server for X Days" of messages.

  • 1. Yes, the licenses are expensive. I'd have server running anyway, the POP is just a plus. If it weren't in the product, I'd have to buy something else and that would be expensive as well.
    2. Running it for my family and friends.
    3. I've run some other mail systems on Windows. Most of them are as pricey as Exchange, and aren't really geared towards small companies. *nix OS requires getting too intimate with SendMail. PostFix is easier, but not as up to date as far as RFCs. Running SBS would likely require more RAM. Exchange is just too hungry for small 10-25 user systems. Yes, it's feature rich.

  • I'm hosting some Domains and Websites (Frontpage, ASP.NET) and every customer wants an E-Mail Address for his Domain. With NT4 I did use Exchange 5.5 but it's to expensive and not developed for Internet use on a standalone Webserver. (I need a Domain only for authenticating a Mail User..)

    The POP3 Service works good, the Mailbox Quota also. My Problem may be on SMTP Service. Incoming Mail that is over the Mailbox Quota or undeliverable (no Mailbox found) goes in the Drop Directory. The Quota of the Drop Directory:

    "When Enable drop directory quota is selected, the SMTP service limits the size of your drop directory to 10 times the size specified by the Limit message size to (KB) setting.
    Exceeding this quota will generate a 452 4.2.2 Mailbox Full entry in the protocol log."

    does not stop receiving more Mails.

    How can I set up to reject undeliverable Mails (no Mailbox or Mailbox full) and send an Error Message back to the Sender? Such Messages should be not received to make no Traffic and the Drop Directory remains blank.

    elssner@interdev.de

  • TJ: I don't exactly understand the scenario you're in. Exchange does offer the feature you're asking for. If you set on the POP service that users are using "rich text", then it will encapsulate calendaring items within a TNEF attachment, which Outlook can use to turn it back into a meeting request or whatever.
    And yes it would be nice to enforce "leave mail on server for X days" on the server, but I'm afraid that even if we did add a new extension to communicate that to the client, there are no clients that would understand it.

    Sethalon: interesting point about the RAM requirement.

    Lutz: that is a good question. I would expect that the SMTP drop directory quota would have no effect on POP mailboxes, because they are entirely different things. When mail is delivered to a POP mailbox, it never reaches the SMTP drop directory, the POP service "intercepts" it. (well to be honest it installs a hook into the SMTP service to make the SMTP service deliver it to the mailbox instead of putting it in the drop directory, but the effect is the same) Is there a quota setting on the mailbox from within the POP admin? I don't have a Windows Server machine available to me at the moment so I can't check myself, but if there are no quota settings in the POP service admin, then I suspect that feature is just missing.

  • I would love to see a catch all mailbox facility built in.... You know... if it doesn't match the usernames that are configured... stick it in the unknown@domain.com mailbox.

  • Paul: Yes, that seems especially important given that SMTP doesn't give an error in session when a mailbox doesn't exist. So I get spam (to a non-existent account), and SMTP accepts it. Tries to deliver it. Can't. Generates an NDR. Can deliver that, because either the sender domain must exist (as configured), or the mailbox is invalid. My BadMail and queue fill up with messages that can't be handled. Maintenance is very poor. I could write you a script to move any messages in Drop and put them in a specific folder. :-)

    I'm just about to pull the plug on this, and use one of my linux boxes to do mail. This is a very much 1.0 solution, and waiting for Longhorn is out of the question. My job requires that I'm well versed in non-MS mail services, but I would really like to see Windows able to compete with *nix on this part. They've got a lot of lead time. Exchange is a great product, but I'm not up for the money/overhead for what it gets me.

  • Hi,

    I found this set of scripts that creates a single catch all account across all the domains that you run but its not exactly what I'm looking for as there is no capability of a catch all per domain....

    http://isorecorder.alexfeinman.com/catchall.htm

    Someone may find it useful though!

  • I tried to use Windows Server 2003's POP3/SMTP servers for an Extranet. We have a number of partners partners, etc, that we want to provide email for, but we do not want to use an Exchange license. The 3 different authentication methods were great, but we wanted the ability to choose which method per user. In other words, we had reason to allow internal users "extranet" email accounts, as well as partners. However, the server determined which method would be used, rather than the user.

    Also, POP3 and SMTP did not use the same authentication methods, so when we secured the SMTP server, we blew apart security since it was no longer the same between POP3 (which we were running in password mode) and SMTP.

    I really liked the fact that messages were individual files, rather than stored in a database. It made it much easier to backup. It also allowed me to double click on a message in Windows Explorer and read it with Outlook Express.

  • Hi David:
    So what are Microsoft's plans for the POP3 service? Will it be developed any more? Is it just there for marketing or does MS really plan to offer it as a real alternative to free SMTP/POP3 on Linux?
    Thanks, and thanks for having this blog!
    J.