Fixed bug in new category logic
Fixed bug where non-category taxonomy was being selected as the post category.
Added option to force categories to match exactly.
Added logic to skip text attachments named “ATT00001.txt” where the numbers can be any sequence. This improves the previous fix by detecting all attachments added, not just the first one.
Fixed bug in detecting need for imap extension.
Added additional selections for “Maximum number of emails to process”
Added logic to skip text attachments named “ATT00001.txt” which are added by MS Exchange virus scanning.
Added option to check for email every 5 minutes.
Fixed bug that caused activation to fail or show a blank page.
Fixed bug where WP media upload rejects a file.
Added a check for mbstring.
Fixed bug when attachment names were only supplied via d_parameters.
Fixed bug where manually running Postie worked, but calling get_mail.php directly did not.
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.
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.
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
If you see
Cron: off open your wp-config.php file and find a line like
if present, remove it. WordPress Cron should now work.
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.
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.
If your site runs on a UNIX/linux server, and you have shell access, you can enable mail checking using cron.
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
Fixed a bug where signatures were not removed in html emails.
Added support for text attachments such as text/calendar.
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.
To always log debug info to a log file you can still do the following:
wp-config.php file look for the following:
Replace it with:
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).