Auto or Manual processing fails

  • Resolved Rick Hellewell

    (@rhellewellgmailcom)


    7 years, 1 month ago

    This is debug output. Automatic processing stopped on this subsite; other subsites working OK. Test config is OK. Manual processing doesn’t process mail. Changed settings from ‘all” to ‘2’ (number of mails to get), no joy.

    Starting mail fetch

    WordPress datetime: 2017-10-24 19:11:49

    doing postie_session_start

    OS: Linux just184.justhost.com 3.10.0-614.10.2.lve1.4.50.el6h.x86_64 #1 SMP Mon May 22 17:31:11 EDT 2017 x86_64

    PHP Version: 5.4.43

    PHP error_log: error_log

    PHP log_errors: On

    PHP get_temp_dir: /tmp/

    PHP cURL version: 7.24.0

    WordPress Version: 4.8.2

    WordPress Multisite

    network_home_url(): https://www.missionaryletters.com/

    WP_TEMP_DIR: (none)

    WP_HOME: (none)

    home_url(): https://www.missionaryletters.com/elderparkerhardy

    WP_SITEURL: (none)

    site_url(): https://www.missionaryletters.com/elderparkerhardy

    WP_DEBUG: Off

    WP_DEBUG_DISPLAY: On

    WP_DEBUG_LOG: Off

    WP_MAX_MEMORY_LIMIT: 256M (default)

    WP_MEMORY_LIMIT: 64M

    DISABLE_WP_CRON: Off

    ALTERNATE_WP_CRON: Off

    WP_CRON_LOCK_TIMEOUT: 60

    iconv: present

    Active plugins

    Array
    (
    [0] => akismet/akismet.php
    [1] => contact-form-7-success-page-redirects/cf7-success-page-redirects.php
    [2] => email-subscribers/email-subscribers.php
    [3] => iwp-client/init.php
    [4] => simple-css/simple-css.php
    )

    Postie is in /home2/cellarw1/public_html/missionaryletters/wp-content/plugins/postie/

    Postie Version: 1.9.8

    POSTIE_DEBUG: On

    wp_content_path: /home2/cellarw1/public_html/missionaryletters/wp-content

    memory at start of email processing: 61164728

    getemails: Connecting to mail.missionaryletters.com:143 (imap)

    getemails: procol: imap

    pConnection: mailbox: INBOX

    Connecting via Socket

    Socket: mail.missionaryletters.com:143

    Socket error: 0 –

    Socket: IMAP

    socket write: (login) LOGIN/APOP/PASS

    socket read (2) :* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready.

    socket write: A0002 SELECT “INBOX”

    socket read (9) :* FLAGS (\Answered \Flagged \Deleted \Seen \Draft)

    getemails: listing messages

    socket write: A0003 STATUS “INBOX” (MESSAGES)

    socket read (2) :* STATUS INBOX (MESSAGES 6)

    socket write: A0004 FETCH 1:2 (UID INTERNALDATE RFC822.SIZE)

    socket read (3) :* 1 FETCH (UID 18 INTERNALDATE “23-Oct-2017 20:43:25 -0600” RFC822.SIZE 47641328)

    listMessages: line: ‘* 1 FETCH (UID 18 INTERNALDATE “23-Oct-2017 20:43:25 -0600” RFC822.SIZE 47641328)’

    listMessages: found: UID 18 INTERNALDATE “23-Oct-2017 20:43:25 -0600” RFC822.SIZE 47641328

    listMessages: line: ‘* 2 FETCH (UID 19 INTERNALDATE “23-Oct-2017 22:30:50 -0600” RFC822.SIZE 49922936)’

    listMessages: found: UID 19 INTERNALDATE “23-Oct-2017 22:30:50 -0600” RFC822.SIZE 49922936

    listMessages: line: ‘A0004 OK Fetch completed (0.001 + 0.000 secs).’

    getemails: fetch 18

    socket write: A0005 UID FETCH 18 (BODY[])

    socket read (611035) :* 1 FETCH (UID 18 BODY[] {47641328)

    — (end of debug output) (also sent via email)

    Ideas?

    THanks…Rick…

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

    (@wayneallen-1)

    Since it is ending on a FETCH I suspect the email it is trying to get has a very large attachment and it is timing out or running out of memory.

    Thread Starter Rick Hellewell

    (@rhellewellgmailcom)

    Turned out it was a memory problem. Even there was no error message shown; processing just died. Suggestion: if a particular email is timing out, skip that one and go on to the next email.

    (Note for lurkers:) The fix was to put this line in the wp-config.php file

    define( 'WP_MEMORY_LIMIT', '3000M' );

    Note that you need to put that line before the

    /* That's all, stop editing! Happy blogging. */

    Or the change will not be put into effect.

    Thanks…Rick..

    Plugin Author Wayne Allen

    (@wayneallen-1)

    Glad you were able to resolve it.

    Unfortunately many themes get in the way of error messages.

    Also timeouts waiting for the mail server are handed as you describe. Php time-outs kill the script which means they can’t be handled gracefully.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Auto or Manual processing fails’ is closed to new replies.