SBS2003 POP3 connector and Outlook 2003 - message date/time stamp

Discussion in 'Windows Small Business Server' started by GM1, Oct 11, 2006.

  1. GM1

    GM1 Guest

    I have SBS 2003 SP1 and am using the in-built POP3 connector with Outlook
    2003 clients. All works fine except that when clients access their e-mail
    messages in Outlook they see the date the message was downloaded to the
    server not the actual date / time that the sender sent the message. I have
    tried changing the outlook fields but have been unable to find a way of
    displaying the correct info. I am using POP3 rather than SMTP because my
    server is not running 24/7 and not really suited therefore to SMTP delivery.
    I hope I am missing something very simple here. Any help would be much
    GM1, Oct 11, 2006
    1. Advertisements

  2. In
    I beliee this is normal behavior. The POP connector is really not

    Why is your server not running all the time?

    Even if it isn't, note, you can still use SMTP. Most, if not all, of your
    senders SMTP servers will retry delivery - or you can get someone else's
    server specified in a lower-priority MX record (see, MailHop
    BackupMX for one) so they will queue/spool the mail for you.
    Lanwench [MVP - Exchange], Oct 11, 2006
    1. Advertisements

  3. GM1

    xxx Guest

    Can I just ask, Lanwench (cute name :) ) why the POP connector is not recommended?

    I am looking at a possible installation in central Europe for a new client
    branch office and cannot find ISP's who do direct MX mail - so I may well have
    to do the whole thing using POP for inbound mail.

    Would appreciate any comments.

    Thanks again.

    xxx, Oct 11, 2006
  4. In
    Cute? Awww, and there I was, going for "Stern and Forbidding."

    You can host your own mail even if you don't have a static IP address...or
    an always-on connection.
    They don't need their ISP to do anything - just their DNS host. If the
    people hosting the DNS won't change their client's MX records as the client
    requests, find someone else to host the DNS.
    Lanwench [MVP - Exchange], Oct 12, 2006
  5. GM1

    xxx Guest

    Thank you very much for that information. It really helps.

    Another question?? If there are problems with the ISP etc and we keep make the
    DNS MX record changes directly - what happens with Outbound emails?

    Does the ISP see them as originating from 'within' their network or is there a
    danger that we might be regarded as 'relaying' off their SMTP server and
    therefore potentially liable to be classed as SPAM?

    I might be barking up the wrong tree here but, as you can guess, I want to get
    my planning right!

    Thanks again.

    xxx, Oct 12, 2006
  6. In
    Such as.... ?
    Your MX records & your inbound mail really have no direct bearing on your
    outbound mail.
    You have two choices for outbound mail (and you configure this in the

    1. Send out all mail directly to the recipients' servers, resolving names
    via DNS
    2. Forwarding all mail to your ISP's SMTP server as a smarthost so *they*
    deal with the delivery.

    If you have a dynamic public IP, #2 is the way to go.
    You would be relaying through them - but either they will allow
    unauthenticated relay because you are on their network, or they'd ask you to
    authenticate (which you would set up in your SMTP connector's properties).

    If your ISP won't let you use their SMTP server, find someone who will -
    dyndns has a MailHop Outbound service that doesn't cost too much, or you can
    find plenty of others.
    Planning is good. :)
    Lanwench [MVP - Exchange], Oct 12, 2006
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.