Viewing 15 replies - 16 through 30 (of 43 total)
  • UPDATE

    After a bit of searching around, I found out what my problem was and why it was saying there was no new mail.

    I had my password off by 1 character… /sigh

    Also, make sure you configure Authorized Addresses for the email account you’ll be sending emails from to the posting account.

    My final thoughts: Great plug-in (now that it’s working), very handy, saves time.

    Ah. Glad you got it working!

    doug

    hi guys, in particular coldmoonrising – I’m in exactly the same situation, I am using Bluehost too and it’s proving to be a bit of a problem. I’ve done as you have, setting up the same email in Bluehost as in Gmail and have got it connecting, but only when I use Bluehost’s details in the mailserver option. As a result, any emails I send to the email address make their way to Gmail nicely, but not to Bluehost… so I’d like to know if you ran into this problem, and how you worked it out? what settings are you using?

    Thanks!

    Munyin,

    When you write you initial post via the email, which email account are you sending it too first, your bluehost email or gmail?

    If you have all of your settings configured for bluehost POP3 (do not use SSL) and you’ve also added the email address you are posting from to the USER -> Authorized Addresses, you should be able to get your auto-posts going no problem.

    The thing is you will need to email your posts directly your bluehost email account rather then gmail.

    Let me know if you’re still having any issues and be descriptive as posssible with any errors you’re facing.

    Hi Coldmoonrising – thanks for replying.

    Tough one to answer, as the email addresses are the same. But it arrives to the gmail apps account rather than the bluehost one, I’m guessing this is because I did the Bluehost Google Apps wizard and it changed the MX settings. As a result, the Bluehost inbox is always empty. I tried setting up an email account just in Bluehost, but it didn’t work at all, I got failed delivery messages.

    My current settings in Postie:

    Mail Protocol: pop3
    Port: 110
    Postie Time Correction: 8 hours
    Mail Server: boxXXX.bluehost.com
    Mail Userid/password: the same one as Gmail Apps

    That’s as much as I have I’m afraid. I tried fetching the email from Bluehost’s webmail using Horde, and it managed to work that way, but there’s no way of auto fetching without logging in it seems. If you have any advice/suggestions, I’d be very grateful.

    Thanks.

    Munyin,

    That’s very interesting that both email addresses are the same. Not sure how that is possible since your bluehost email should be (for example) [email protected] and google could be [email protected]. I don’t mean to be digging but why would you be pointing your MX records to google?

    If this persists, the only thing I can suggest would be to point your MX records back to bluehost, create a new email via your cPanel and setup your Mail Server in Postie to mail.yourdomain.com.

    Oh, it’s because I’m using Gmail to access and manage the domain accounts, hence I’m able to set up email addresses that are exactly the same.

    Yeah, I came to the same conclusion… but if I do that, then I won’t be able to use Gmail to manage the email accounts! I’m just going to have to find a different way.

    Just a thought… Postie does not require that the POP account you check be in any particular domain. If you are having MX record issues because the email account you are trying to use is conflated with Gmail, can’t you just create another email account in another domain you host at Bluehost and use that?

    Maybe I’m assuming that like me everybody has extra domains lying around?

    doug

    My only main issue is that it doesn’t check on its own, so have to figure out how to set a cron job to do it :(…

    Anyone have a easy explanation on how to do that?

    Postie doesn’t require you setting up a cron job. There is a Postie setting for checking every so-many minutes. I have it set to check every 10 minutes and it does it by itself without me having to set up a cron job.

    doug

    Doug,

    I’ve just started to try using Postie, and came across this group of posts. I have a bluehost account. After some trial and error, I was able to get Postie to connect to my host, with the help of bluehost’s support. Testing the configuration works fine.

    However, when running Postie manually (for testing purposes), I get the message that there is now new mail. Others in this forum say they’re having the same problem, but you’re not.

    What version of WordPress are you using? Based on some things I’ve seen about Postie support, I wonder if it’s working in older versions of WordPress, but not the current one (versions 3.4).

    Thanks,
    Marcia

    Doug, sorry, a typo changed the intent of my email. Postie says there is “no new email”, not “now new email”.

    Thanks,
    Marcia

    Hi. I am using version 3.4.1, the latest version.

    Can you check your mail account independently (with a mail client) and see if there really is mail there or not?

    doug

    Yes, I have checked the email with a mail client, and see there the three emails I sent as tests. So Postie is connecting, email exists, but Postie sends back a message saying there is no new email.

    I’m thinking that the “no new mail” message is misleading me, and that something else is going on.

    One thing I noticed, the postie/get_mail.php puts outs the message “no new mail” when it finds no “unread” mail. So I need to find out what constitutes “unread” mail on my mail server. I’m using the Pop3 setting. This may be a clue, so I’ll pursue it.

    Marcia

    Yes, I think for sure Postie only checks unread messages. When you check using a mail client the messages get marked as “read.”

    So I think you should do the test with a new message and make sure NOT to check the see if the message is there with a mail client before running Postie.

    doug

Viewing 15 replies - 16 through 30 (of 43 total)
  • The topic ‘Has Postie been killed?’ is closed to new replies.