• Resolved teammeta

    (@teammeta)


    I have recently updated to WordPress 4.7. Since then, Postie has stopped automatically checking for emails. I have also updated Postie to version 1.8.22 with no improvement. If I use the “Process Email” button within the plugin it will check and pull the email. It just wont check on its own automatically. Is this a known issue? And is there a fix?

Viewing 15 replies - 1 through 15 (of 19 total)
  • Plugin Author Wayne Allen

    (@wayneallen-1)

    There is no known issue. If you disable all other plugins does Postie start working?

    Thread Starter teammeta

    (@teammeta)

    I have disabled all other plugins and I am still experiencing the issue. Postie will only grab emails if done manually with the “Process Emails” or “Debug” button.

    Plugin Author Wayne Allen

    (@wayneallen-1)

    I just tested this with WP 4.7 and Postie 1.8.22 and it worked without issue.

    Please click the Test Config button and post it here.

    You can also install WPX Cron Manager Light to see if the cron is set up correctly.

    Hello. I have the same problem. Manually it works. Automatic writing a plugin does not take away from the mailbox. Established WPX Cron Manager Light, showing that all is well. What to do?

    Plugin no longer accept mail after updating to version 4.7 engine.

    Postie Configuration Test
    Postie Version: 1.8.22
    Wordpress Version: 4.7
    PHP Version: 5.6.27
    OS: Linux srv134-h-st.jino.ru 2.6.18-406.el5 #1 SMP Tue Jun 2 17:25:57 EDT 2015 x86_64
    POSTIE_DEBUG: On
    Time: 2016-12-22 05:51:51 GMT
    Error log:
    TMP dir: /tmp/
    Postie is in /home/users1/a/alexsibmail/domains/idmyself.ru/wp-content/plugins/postie/
    cURL version: 7.47.2
    Cron: On
    Alternate Cron: Off
    Clock Tests

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

    tag_Delay:
    tag_Delay: pre: 1482385911
    tag_Delay: post: 1482385911
    tag_Delay: post date: 2016-12-22 12:51:51 / 2016-12-22 05:51:51 (gmt) / 0
    Post time: 2016-12-22 12:51:51
    Encoding

    default_charset: UTF-8
    DB_CHARSET: utf8mb4
    DB_COLLATE:
    WordPress encoding: UTF-8
    Postie encoding: UTF-8
    Connect to Mail Host

    Postie connection: sockets
    Postie protocol: pop3
    Postie server: mail.alexsibmail.myjino.ru
    Postie port: 110
    checking
    Connecting via Socket
    Socket: mail.alexsibmail.myjino.ru:110
    Socket error: 0 –
    checkOS: Linux
    socket read (1) :+OK Hello there.
    socket write: ‘USER [email protected]

    checkOS: Linux
    socket read (1) :+OK Password required.
    socket write: ‘PASS w[poq][p

    checkOS: Linux
    socket read (1) :+OK logged in.
    socket write: ‘STAT

    checkOS: Linux
    socket read (1) :+OK 2 3019992
    pop count: Array
    Successful POP3 connection on port 110
    # of waiting messages: 2
    socket write: ‘QUIT

    checkOS: Linux
    socket read (1) :+OK Bye-bye.

    • This reply was modified 7 years, 11 months ago by alexsibmail.
    Plugin Author Wayne Allen

    (@wayneallen-1)

    Please take a look in your web server logs for any errors.

    I’m having the same problem….. I have 11 unprocessed emails.
    We’re using Postie to manage a sailing blog as we travel around the world over the next year.

    We’ve been wondering why none of our posts have made out of the gmail account.

    When I run the debug…. I get an “oops that page does not exist” as a result. Then there is a stub post that is processed.

    Also – where should I look for the debug log? I have it on.

    Here is my config test:

    Postie Configuration Test
    Postie Version: 1.8.22
    Wordpress Version: 4.7
    PHP Version: 5.4.45
    OS: Linux p3plcpnl0576.prod.phx3.secureserver.net 2.6.32-673.26.1.lve1.4.18.el6.x86_64 #1 SMP Fri Oct 21 11:58:14 EDT 2016 x86_64
    POSTIE_DEBUG: On
    Time: 2016-12-25 21:24:05 GMT
    Error log:
    TMP dir: /home/samoorelex/public_html/XXXXXXXXXXXX/wp-content/uploads/
    Postie is in /home/samoorelex/public_html/XXXXXXXXX/wp-content/plugins/postie/
    cURL version: 7.36.0
    Cron: On
    Alternate Cron: Off
    Clock Tests
    This shows what time it would be if you posted right now
    tag_Delay:
    tag_Delay: pre: 1482701045
    tag_Delay: post: 1482701045
    tag_Delay: post date: 2016-12-25 21:24:05 / 2016-12-25 21:24:05 (gmt) / 0
    Post time: 2016-12-25 21:24:05
    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: imap-ssl
    Postie server: imap.gmail.com
    Postie port: 993
    checking
    Connecting via Socket
    Socket: tls://imap.gmail.com:993
    Socket error: 0 –
    socket write: ‘A0001 CAPABILITY

    checkOS: Linux
    socket read (3) :* OK Gimap ready for requests from 50.62.176.103 u203mb475091988oig
    socket write: ‘A0002 LOGIN [email protected] Lex1ng+0n

    checkOS: Linux
    socket read (2) :* CAPABILITY IMAP4rev1 UNSELECT IDLE NAMESPACE QUOTA ID XLIST CHILDREN X-GM-EXT-1 UIDPLUS COMPRESS=DEFLATE ENABLE MOVE CONDSTORE ESEARCH UTF8=ACCEPT LIST-EXTENDED LIST-STATUS LITERAL- APPENDLIMIT=35651584
    socket write: ‘A0003 SELECT “INBOX”

    checkOS: Linux
    socket read (8) :* FLAGS (\Answered \Flagged \Draft \Deleted \Seen $NotPhishing $Phishing)
    socket write: ‘A0004 STATUS “INBOX” (MESSAGES)

    checkOS: Linux
    socket read (2) :* STATUS “INBOX” (MESSAGES 11)
    Successful IMAP-SSL connection on port 993
    # of waiting messages: 11
    socket write: ‘A0005 LOGOUT

    checkOS: Linux
    socket read (2) :* BYE LOGOUT Requested
    —————–

    Hoping you can help us out!

    This morning I enabled debug, replacing the debug false statement in wp-config.php with the three lines of new instructions from your support note. I also created a debug.log file.

    I’ve run the get manual email (have 11 in queue) several times. The debug log is still 0 bytes. permissions are 666

    One other thing that happens, when I run manual email check or debug, the retun I get is the “oops, cant find that page on the blog. Plus a new temp post shows up on the blog.
    name is tmptitle
    contents are tmpPost
    it is saved as a draft.

    I hope that helps.

    Plugin Author Wayne Allen

    (@wayneallen-1)

    >when I run manual email check or debug, the retun I get is the oops, cant find that page

    That seems very strange. Have you tried reinstalling Postie? All your settings will be retained.

    >The debug log is still 0 bytes

    Sound like the log location is being overridden. You can use one of the phpinfo plugins to find out where the error log really is.

    So, I should remove postie then re-install?

    Plugin Author Wayne Allen

    (@wayneallen-1)

    Worth a try.

    Hi Wayne,

    I uninstalled and reinstalled. Still not picking up posts……

    I have some new info but I’m afraid the text is pretty long and I’d like to send it to you privately.
    What’s the best way to do that?

    Here is a summary:
    Warning: stream_select(): unable to select [4]: Interrupted system call (max_fd=5) in /home/samoorelex/public_html/svlexington.net/wp-content/plugins/postie/lib/pSocketConnection.php on line 185
    socket read (0) :
    handlePart: type text/plain
    handlePart: no encoding
    handlePart: converting iso-8859-1 to UTF-8
    handlePart: no disposition set
    handlePart: text extracted
    socket write: ‘A0019 UID FETCH 126 (BODY[])

    checkOS: Linux
    socket read (604095) :* 1 FETCH (UID 126 FLAGS (\Seen) BODY[] {23546642}

    Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 13107160 bytes) in /home/samoorelex/public_html/svlexington.net/wp-content/plugins/postie/lib/pImapMailServer.php on line 102

    Thanks – Sam

    Plugin Author Wayne Allen

    (@wayneallen-1)

    You can send a full log to [email protected]

    However, it looks like you are running out of memory. See this https://postieplugin.com/faq/fatal-error-memory/

    You might check the email account Postie is looking at, I suspect there is a message with a very large attachment.

    Hello ,
    POSTIE would be a nice asset for one of my website and i Installed it recently on line. I am faced with same issue as mentioned in this topic: mail autocheck does not work correctly. Only manually check is working.
    Any help or suggestion from the plugin author will be appreciated.
    Many thanks in advance.
    Below is my Postie configuration

    Postie Configuration Test
    Postie Version: 1.8.22
    Wordpress Version: 4.7
    PHP Version: 5.3.29-1~dotdeb.0
    OS: Linux web02 3.10-0.bpo.2-amd64 #1 SMP Debian 3.10.5-1~bpo70+1 (2013-08-11) x86_64
    POSTIE_DEBUG: Off
    Time: 2016-12-26 18:45:47 GMT
    Error log:
    TMP dir: /tmp/
    Postie is in /var/www/vhosts/sncgrandvalence.free-h.fr/httpdocs/wp-content/plugins/postie/
    cURL version: 7.26.0
    Cron: On
    Alternate Cron: Off
    Clock Tests

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

    Post time: 2016-12-26 19:45:47
    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-ssl
    Postie server: pop.free.fr
    Postie port: 995
    checking
    Successful POP3-SSL connection on port 995
    # of waiting messages: 0

    Plugin Author Wayne Allen

    (@wayneallen-1)

    @gegevalence please check your web server logs for error messages.

Viewing 15 replies - 1 through 15 (of 19 total)
  • The topic ‘Postie does not auto check emails after WordPress Update’ is closed to new replies.