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

    (@wayneallen-1)

    Yes, 1.8.x will fix this issue. You can download the beta version at https://downloads.wordpress.org/plugin/postie.zip

    There are a few edge case features that haven’t been implemented, but should work for most people. The official release will be in a few weeks.

    If you run into any issue I would like to hear about them.

    Thread Starter JHGrove3

    (@jhgrove3)

    It is able to connect, but it doesn’t seem to be downloading any mail.

    I’m using cURL, POP3-SSL, Port 995. Here is the Debug feed:

    Starting mail fetch
    Postie Version: 1.8.1
    Wordpress Version: 4.5.3
    PHP Version: 5.5.9-1ubuntu4.19
    OS: Linux pod-42335 3.13.0-79-generic #123-Ubuntu SMP Fri Feb 19 14:27:58 UTC 2016 x86_64
    POSTIE_DEBUG: On
    Time: 2016-08-16 21:59:59 GMT
    Error log: /var/log/apache2/brasselerlink.error.log
    TMP dir: /tmp/
    Postie is in /nas/content/live/brasselerlink/wp-content/plugins/postie/
    WordPress cron is disabled. Postie will not run unless you have an external cron set up.
    Cron: Off
    Alternate Cron: Off
    wp_content_path: /nas/content/live/brasselerlink/wp-content
    MAKE SURE POP IS TURNED ON IN SETTING AT Gmail
    Connecting to pop.gmail.com:995 (pop3-ssl)
    Connecting via cURL
    Array
    (
    [version_number] => 467712
    [age] => 3
    [features] => 50877
    [ssl_version_number] => 0
    [version] => 7.35.0
    [host] => x86_64-pc-linux-gnu
    [ssl_version] => OpenSSL/1.0.1f
    [libz_version] => 1.2.8
    [protocols] => Array
    (
    [0] => dict
    [1] => file
    [2] => ftp
    [3] => ftps
    [4] => gopher
    [5] => http
    [6] => https
    [7] => imap
    [8] => imaps
    [9] => ldap
    [10] => ldaps
    [11] => pop3
    [12] => pop3s
    [13] => rtmp
    [14] => rtsp
    [15] => smtp
    [16] => smtps
    [17] => telnet
    [18] => tftp
    )

    )
    curl write: pop3s://pop.gmail.com – STAT
    curl read: matched expect
    curl read (13) :+OK 2 36568
    pop count: Array
    curl write: pop3s://pop.gmail.com – LIST
    curl read (13) :+OK 2 messages (36568 bytes)
    curl write: pop3s://pop.gmail.com – TOP 1 1
    curl read (13) :+OK message follows

    Plugin Author Wayne Allen

    (@wayneallen-1)

    Does IMAP work?

    Thread Starter JHGrove3

    (@jhgrove3)

    No, IMAP doesn’t work either. The Test Config button seems to work (it’s able to connect) but it doesn’t seem to be processing the emails.

    Settings: cURL, IMAP-SSL, port 993, imap.gmail.com

    Here is the debug trace:

    Starting mail fetch
    Postie Version: 1.8.1
    Wordpress Version: 4.5.3
    PHP Version: 5.5.9-1ubuntu4.19
    OS: Linux pod-42335 3.13.0-79-generic #123-Ubuntu SMP Fri Feb 19 14:27:58 UTC 2016 x86_64
    POSTIE_DEBUG: On
    Time: 2016-08-17 13:09:08 GMT
    Error log: /var/log/apache2/brasselerlink.error.log
    TMP dir: /tmp/
    Postie is in /nas/content/live/brasselerlink/wp-content/plugins/postie/
    WordPress cron is disabled. Postie will not run unless you have an external cron set up.
    Cron: Off
    Alternate Cron: Off
    wp_content_path: /nas/content/live/brasselerlink/wp-content
    Connecting to imap.gmail.com:993 (imap-ssl)
    Connecting via cURL
    Array
    (
    [version_number] => 467712
    [age] => 3
    [features] => 50877
    [ssl_version_number] => 0
    [version] => 7.35.0
    [host] => x86_64-pc-linux-gnu
    [ssl_version] => OpenSSL/1.0.1f
    [libz_version] => 1.2.8
    [protocols] => Array
    (
    [0] => dict
    [1] => file
    [2] => ftp
    [3] => ftps
    [4] => gopher
    [5] => http
    [6] => https
    [7] => imap
    [8] => imaps
    [9] => ldap
    [10] => ldaps
    [11] => pop3
    [12] => pop3s
    [13] => rtmp
    [14] => rtsp
    [15] => smtp
    [16] => smtps
    [17] => telnet
    [18] => tftp
    )

    )
    curl write: imaps://imap.gmail.com/INBOX – STATUS “INBOX” (MESSAGES)
    * STATUS “INBOX” (MESSAGES 4)
    curl read (14) :E004 OK Success
    curl write: imaps://imap.gmail.com/INBOX – FETCH 1:* (UID INTERNALDATE RFC822.SIZE ENVELOPE)
    * 1 FETCH (UID 2 RFC822.SIZE 9437 INTERNALDATE “16-Aug-2016 14:46:09 +0000” ENVELOPE (“Tue, 16 Aug 2016 07:46:08 -0700 (PDT)” “Thank you for joining our mailing list!” ((“Brasseler USA” NIL “marketing” “brasselerusa.com”)) ((“Brasseler USA” NIL “marketing” “brasselerusa.com”)) ((“Brasseler USA” NIL “marketing” “brasselerusa.com”)) ((“brasselerlinkinbox@gmail.com” NIL “brasselerlinkinbox” “gmail.com”)) NIL NIL NIL “”)) * 2 FETCH (UID 3 RFC822.SIZE 10207 INTERNALDATE “16-Aug-2016 14:55:12 +0000” ENVELOPE (“Tue, 16 Aug 2016 14:55:04 +0000 (UTC)” “Access for less secure apps has been turned on” ((“Google” NIL “no-reply” “accounts.google.com”)) ((“Google” NIL “no-reply” “accounts.google.com”)) ((“Google” NIL “no-reply” “accounts.google.com”)) ((NIL NIL “brasselerlinkinbox” “gmail.com”)) NIL NIL NIL “”)) * 3 FETCH (UID 4 RFC822.SIZE 29430 INTERNALDATE “16-Aug-2016 21:14:54 +0000” ENVELOPE (“Tue, 16 Aug 2016 14:14:53 -0700 (PDT)” “Brasseler Newsletter Archive” ((“Brasseler USA” NIL “marketing” “brasselerusa.com”)) ((“Brasseler USA” NIL “marketing” “brasselerusa.com”)) ((“Brasseler USA” NIL “marketing” “brasselerusa.com”)) ((“BrasselerLink Inbox” NIL “brasselerlinkinbox” “gmail.com”)) NIL NIL NIL “”)) * 4 FETCH (UID 6 RFC822.SIZE 7138 INTERNALDATE “16-Aug-2016 21:51:45 +0000” ENVELOPE (“Tue, 16 Aug 2016 21:51:42 +0000” “Post this Message” ((“James Grove” NIL “JamesGrove” “brasselerusa.com”)) ((“James Grove” NIL “JamesGrove” “brasselerusa.com”)) ((“James Grove” NIL “JamesGrove” “brasselerusa.com”)) ((“BrasselerLinkInbox@gmail.com” NIL “BrasselerLinkInbox” “gmail.com”)) NIL NIL NIL “<19C1924E09EF704892E2A036CA6905B256A1CFDE@SavMail02.savannah.brasselerusa.com>”))
    curl read (17) :F004 OK Success
    curl write: imaps://imap.gmail.com/INBOX – UID FETCH 2 (BODY[])
    * 1 FETCH (UID 2 BODY[] {9437}
    curl read (242) :G004 OK Success
    handlePart: type multipart/alternative
    handlePart: type text/plain
    handlePart: quoted-printable
    handlePart: charset utf-8 detected
    handlePart: converting utf-8 to UTF-8
    handlePart: disposition set to inline
    handlePart: inline un-named
    handlePart: type text/html
    handlePart: quoted-printable
    handlePart: charset utf-8 detected
    handlePart: converting utf-8 to UTF-8
    handlePart: fixing up html
    handlePart: disposition set to inline
    handlePart: inline un-named
    curl write: imaps://imap.gmail.com/INBOX – UID FETCH 2 (BODY[])
    * 1 FETCH (UID 2 BODY[] {9437}
    curl read (242) :H004 OK Success

    Plugin Author Wayne Allen

    (@wayneallen-1)

    Please contact me at help@postieplugin.com

    Plugin Author Wayne Allen

    (@wayneallen-1)

    A bug fix resolved this issue.
    https://downloads.wordpress.org/plugin/postie.zip

    Plugin Author Wayne Allen

    (@wayneallen-1)

    Fyi 1.8.2 beta has been released https://downloads.wordpress.org/plugin/postie.zip

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Version 1.8.1 to fix WPEngine Postie Conflict?’ is closed to new replies.