1.4.28 Released

Fixed bug in “reset settings to default” where the protocol wasn’t being retained.
More cleanup and clarification on settings screen.
Fixed bug where excerpts weren’t getting set if “Filter newlines” was set to “Yes”
Removed logic to increase memory size.

1.4.27 Released

Updated sample plugin for extending Postie.
Updated documentation for template variables.
Fixed a bug where text/plain attachments were not being treated as attachments.
Look for and include filterPostie.php in wp-content if it exists. (used for custom filters so they don’t get deleted on upgrades)
Cleanup of settings screen layout.
Added additional error logging for mail connections.

Forcing an Email Check

Postie relies on the built-in WordPress Cron process to fetch emails and turn them into posts. However, WordPress requires that there be traffic to your site in order to run the Cron process.

The first check you must do to be sure the WordPress Cron is enabled. Clicking Test Config on the Postie settings page will tell you if Cron is disabled. Look for

Cron: On

If you see Cron: off open your wp-config.php file and find a line like

define('DISABLE_WP_CRON', true);

if present, remove it. WordPress Cron should now work.

External Cron

If you would prefer to have more fine-grained control of how Postie checks for mail or you can’t get the WordPress Cron to work, you can setup a cron job.

From Wikipedia

The software utility Cron is a time-based job scheduler in Unix-like computer operating systems. People who set up and maintain software environments use cron to schedule jobs (commands or shell scripts) to run periodically at fixed times, dates, or intervals. It typically automates system maintenance or administration—though its general-purpose nature makes it useful for things like connecting to the Internet and downloading email at regular intervals. The name cron comes from the Greek word for time, χρόνος chronos.

The Easy Way

If you are using a hosting company that doesn’t allow you access to cron or you don’t want to mess with it you can use a service like SetCronJob to access http://<mysite>/?postie=get-mail

If your hosting company uses cPanel for managing your domain you can add a cron job through the cPanel interface. See the cron job docs then choose one of the commands listed below.

The Techie Way

Setup a cronjob to access http://<mysite>/?postie=get-mail Note that every time you access this page Postie will run – it is like clicking Run Postie on the Admin screen.

Note that before Postie 1.6 the URL was: http://<mysite>/wp-content/plugins/postie/get_mail.php This URL is no longer supported.

Linux

If your site runs on a UNIX/linux server, and you have shell access, you can enable mail checking using cron.

Examples:
This fetches the mail every five minutes with lynx

*/5 * * * * /usr/bin/lynx --source http://<mysite>/?postie=get-mail >/dev/null 2>&1

This fetches the mail every ten minutes with wget

*/10 * * * * /usr/bin/wget -O /dev/null http://<mysite>/?postie=get-mail >/dev/null 2>&1

Windows

You will need to install wget or curl.
Then use the Task Scheduler control panel to call wget or curl.
Examples:
wget example

wget http://<mysite>/?postie=get-mail

curl example

curl http://<mysite>/?postie=get-mail

Enabling Debug Output

As of version 1.5.5 you can click the “Run Postie (Debug)” button to have Postie check for emails and report debugging information to the screen.

Postie Options

To always log debug info to a log file you can still do the following:

In your wp-config.php file look for the following:

define(‘WP_DEBUG’, false);

Replace it with:

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('POSTIE_DEBUG', true);

Various errors, warning and informational will be written to the wp-content\debug.log file. There may also be all sorts of warnings and messages in your site as well depending on how well behaved your other plugins and themes are, so you will not want to leave these settings set to true all the time.

If the debug.log file doesn’t show up then create a file debug.log in the wp-content directory and then “chmod 666 debug.log” or use cpanel to do the same thing.

It is possible that the error log is in a different location. Running Postie or Test Config will tell you where it is located (as of 1.4.26).

1.4.24 Released

Fixed a bug where the original attachment name wasn’t being used.
Fixed a bug where the #eimg# tags in the excerpt were not getting expanded.

1.4.22 Released

Fixed a bug where the subject was not being properly decoded when Q-encoding was used.
Fixed a bug in #img# caption detection.
Fixed a bug where the tag command was picking up too much text.
Enhanced the date command to allow times as well.