Can’t find what you’re looking for? Ask a question on the support forum.
When you click Test Config Postie tries to connect your your mail server to ensure everything is set up correctly. (Be sure to click Save first if you changed anything!). Unfortunately sometimes the error messages aren’t very clear and you need a way to verify things.
One common issue is that the port you are trying to use is blocked or your mail server isn’t listening on the port. You can verify these conditions by using the telnet command.
Note: You need shell access to the server Postie is installed on.
Connect to your server via RDP, VNC or SSH and open a command/terminal window and type something like the following:
telnet mail.examples.com 110
Substitute the server and port you are trying to verify. If successful you should see something like:
Type ‘Q’ and press return to tell the mail server you’re done.
For a IMAP (port 143) you should get something like:
Type ‘C logout’ and press return to tell the mail server you’re done.
For POP3-SSL or IMAP-SSL you need to use a different command. For example to test if you can get access to Gmail IMAP try:
echo "TAG LOGOUT" | openssl s_client -connect imap.gmail.com:993
For Gmail POP-SSL try:
echo quit | openssl s_client -connect pop.gmail.com:995
Yes. You can use either pop3-ssl or imap-ssl with a gmail account (including Google Apps). Before attempting to use with postie, make sure that you enable POP or IMAP in your Gmail preferences. See this for more info.
Yes, but you must use an email setup using the GoDaddy email service. See this page for more info.
WordPress cron (which Postie relies on) doesn’t run unless a page is accessed on the site. So if you send an email, but nobody accesses the site for 3 days Postie won’t be given the chance to fetch the email and publish the post.
To ensure that Postie runs smoothly on a low or no volume site you need to ensure that a page gets hit (any page is fine). Use something like cron + curl on Linux or install curl on Windows and use the Scheduled Tasks control panel or use one of the online cron services. See this page for more info.
It has been reported that enabling the “alternate” cron has worked for some people.
In your wp-config.php file add:
define('DISABLE_WP_CRON', true); define('ALTERNATE_WP_CRON', true);
add this before the line that says “That’s all, stop editing! Happy blogging.”
Postie works well with Gmail (and Google apps for business).
Please take a look at our Gmail settings page for details and prerequisites.
Postie works well with GoDaddy hosting, but you are required to use GoDaddy mail servers (rather than something like Gmail).
- Protocol: pop3
- Use Transport Layer Security: no
- Server: pop.secureserver.net
- Port: 110
- Userid: your full email address
- Password: your password
The answer is “you can’t do that directly”
However, what you can do is have each separate inbox forward their mail to a central mail account which you then configure Postie to check.
For example you have 2 email accounts that you want your users to send email to: firstname.lastname@example.org and email@example.com
You then create a third email account (firstname.lastname@example.org) that you don’t tell anyone about and your configure both askmeaquestion and news to forward every email to email@example.com
You then configure Postie to check the firstname.lastname@example.org email account.
Many people have this arrangement so that emails sent to each account get assigned different categories. To accomplish this you need to purchase the Category Per User AddOn and follow the directions for configuring Multiple Inboxes.
If you are using Gmail you have a simpler option. With Gmail it will ignore anything after the plus sign (+) so if your email is email@example.com emails to firstname.lastname@example.org and email@example.com will all show up in firstname.lastname@example.org and you can is the Category Per User AddOn to assign different categories.
If you get a message like:
Warning: stream_socket_enable_crypto(): Peer certificate did not match expected
And you are using DreamHost take a look at the following DreamHost support article: