• Hello —
    After struggling mightily with getting my client’s GoDaddy/Office365 (Outlook) and Postie configuration to work (short answer, I gave up…), I figured out a 100% solution!

    I created a subdomain and set up a cPanel email for that, which worked half way. Postie would connect to it, but to I had to add a DNS A record to get it to accept the email separately from the main domain. Now it’s working flawlessly (well save for the nasty markup that Outlook adds to its html mail, but that’s a topic for a different thread). And… most importantly, didn’t mess up my clients Office365.

    To illustrate:

    1) domain.com is the master domain
    2) post.domain.com is the subdomain
    by default, these two records were among those created when the subdomain was created:
    CNAME webmail.post post.domain.com
    A post.medstarnw.com (IP of main domain)

    3) Needed to separate out and create a new A record for the post.domain.com that points to the IP for the main domain. That looks like :
    A mail.post (IP#)
    (note, no .com added here)

    Hope this works for others!

    • This topic was modified 6 years, 7 months ago by flowergirl.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Just curious, I posted a similar solution right below your post. As you said Office 365 doesn’t work with Postie. I didn’t have to create a sub domain, just created a Cpanel email.
    It could send email but not receive. Then I made the change below to fix it.

    The Cpanel email can but not receive email until you :
    Check your Cpanel – Email – MX Entry Routing setting. It should be set to Routing, not remote. This allows the email to receive too.

    • This reply was modified 6 years, 7 months ago by LesTexas60.
    • This reply was modified 6 years, 7 months ago by LesTexas60.

    To Flowergirl: Some more specifics to add a Cpanel email to Godaddy for Postie use:
    SOLVED FINALLY;
    As someone else suggested, I created a new email address through the Cpanel functions in GoDaddy. After the email is created I went to the Configure button that showed multiple ways to auto configure the email for many other hosts.
    At the bottom of the page it shows Manual Setup. This is for Postie.
    Here is the key; The incoming server was not just pop.secureserver.net,
    When you enter the MailServer in Postie be sure to use the full server name: a2plcpnlxxxx.prod.iad2.secureserver.net (The xxxx will vary depending on your account)
    I used Pop3, no TLS with port 110 and everything works great now.
    So easy once you know what to look for.
    Hope this helps others..

    Thread Starter flowergirl

    (@flowergirl)

    I wasn’t able to just create a cPanel email as it wasn’t found when I tried sending a test email to it… because the Office365 intercepted it to say there was no such address, so I had to go with the subdomain to completely separate it out.

    I didn’t know to use a Routing vs Remote setting (that might have solved it? I don’t deal with name records much at all), and since I’m fearful of messing up their Office365, the subdomain solution is a good solution in my case.

    And, yes, I did have to do the full server name just as you described above.

    I was able to set up the server using IMAP-SSL port 993.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Workaround for GoDaddy / Office365 / Postie’ is closed to new replies.