Timing issues: posts go to scheduled and post after 7 hour delay

What is displayed when you click the Test Config button?

The data below.
Postie time correction is set at 0
The server is set at UTC according to company
The mails are sent from a PC set at GMT+2 (Brussels)
My PC showed a time of 21:33 when I printed the config test
Posts were retrieved by Postie around 17:50 GMT+2 and are in Scheduled by wordpress to be posted at 17:54 but are still in there. I estimate they will be posted In 4 to 5 hours based on experience which squares with the time of 13:38 below in the config test. I have no idea where that time comes from.

Strangely in my “General settings” of WordPress I see. The setting there is “Brussels”
Universal time (UTC) is 2017-01-03 13:39:53. Local time is 2017-01-03 14:39:53.
Wordpress is wrong the time should be 20:39 something for UTC.

Postie Configuration Test

Postie Version: 1.8.22

Wordpress Version: 4.7

PHP Version: 5.4.45

OS: Linux server1035.mylogin.co 4.4.39-opteron-hst #4 SMP Wed Dec 28 11:19:01 UTC 2016 x86_64

POSTIE_DEBUG: Off

Time: 2017-01-03 13:31:58 GMT

Error log:

TMP dir: /tmp/

Postie is in /home/www/econocuba.impela.net/wp-content/plugins/postie/

cURL version: 7.46.0

Cron: On

Alternate Cron: Off

Clock Tests

This shows what time it would be if you posted right now

Post time: 2017-01-03 13:31:58

Encoding

default_charset:

DB_CHARSET: utf8

DB_COLLATE:

WordPress encoding: UTF-8

Postie encoding: UTF-8

Connect to Mail Host

Postie connection: sockets

Postie protocol: pop3

Postie server: ssl://pop.gmail.com

Postie port: 995

checking

Successful POP3 connection on port 995

# of waiting messages: 0

Try adjusting the “Postie Time Correction” setting, click save, then click Test Config until “Post time” is correct.

OK

Were you able to fix the issue?

Nope. but it is a server issue as far as I can see.

I Just noticed this same issue on a email/post sent today. The post was set as scheduled, I think 2 hours in the future (when I looked at it).

If the General, Read time zone setting is set to “Los Angeles” (-7 UTC, I think), and the Postie Time Correction value is set to 0, is that a correct setting?

I note that the ‘scheduled post’ problem just cropped up after the latest update (this last weekend).

Thanks…

Assuming you updated your blog timezone to -7 just recently you will need to change the Postie Time Correction value to the same value.

There has been no change to the blog time zone. The scheduled posts problem is new; I haven’t noticed the problem prior to the last update.

Not sure why there even needs to be that setting in Postie, though. Seems to me that Postie should grab/use the WP setting.

But, again, posts published immediately before the last Postie version update. It is only since the last update that a customer (they own the sub-site on a multisite install) noticed that a post wasn’t getting published immediately (they use Postie processes to publish all posts; they do not go into the Admin Editor).

I mis-spoke a bit. Postie does now use the blog timezone, if it was already set.

Maybe a better question is – do you care about the date/time in the email? Currently Postie uses the date/time from the email as the post date/time. There could be a setting to ignore that and just use the current time.

Thanks. For my particular multi-site ‘focus’, the date/time of the post is not a significant factor. The current date/time (when the email is processed by Postie) is sufficient for our needs.

I suppose for others that a ‘delay publishing’ setting might be useful. I’d see this as a shortcode/parameter thing in the email, that would allow specifying when the post should be published (x hours from now, or a specific date/time).

Nice to know that Postie uses the blog timezone. But it is still puzzling to me what a post on one of the sub-sites was set to publish in the future. I will try some testing on a test sub-site to see if I can duplicate. I will post the results of testing in a new thread, if that is OK.

…Rick…

Sounds good.

We reviewed all data and it turns out that the server time was not correctly set to UTC. Within Postie correction did nothing. Now the server time is set correctly to UTC feedwordpress and Postie with correction 0 work fine. The timing difference also works in postie since the last update.