SMTP debug log

Description

When mail is not delivered successfully, the first order of business is to look for errors that prevent mail library from working properly.

To help you diagnose the email communication issues MyBackup logs all failed and successful deliveries to a logfile.

If you are using the native email back-end then the log will contain an entry for each email that is sent with a brief information about when, who, what.

If you are using the Pear Mail back-end with debug option set ON then the Pear Mail library provides extended debug information like the example below:

Recv: 220 mx.google.com ESMTP c11sm22982907wib.1 - gsmtp
Send: EHLO localhost
Recv: 250-mx.google.com at your service, [x.x.x.x]
Recv: 250-SIZE 35882577
Recv: 250-8BITMIME
Recv: 250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN XOAUTH
Recv: 250-ENHANCEDSTATUSCODES
Recv: 250-PIPELINING
Recv: 250-CHUNKING
Recv: 250 SMTPUTF8
Send: AUTH LOGIN
Recv: 334 bWFpbHVzZXI
Send: bWFpbHVzZXJAZG9tYWluLm9yZw
Recv: 334 UGFzc3dvcmQ6
Send: cGFzc3dvcmQ=
Recv: 235 2.7.0 Accepted
Send: MAIL FROM:<mailuser@domain.org>
Recv: 250 2.1.0 OK c11sm22982907wib.1 - gsmtp
Send: RCPT TO:<whatever@younameit.info>
Recv: 250 2.1.5 OK c11sm22982907wib.1 - gsmtp
Send: DATA
Recv: 354  Go ahead c11sm22982907wib.1 - gsmtp
Send: MIME-Version: 1.0
Send: --=_f29f431eb8f4144cb810444e297bec5e
Send: 7XAmjtaRZ
Send: 
Recv: 250 2.0.0 OK 1435074337 c11sm22982907wib.1 - gsmtp
Send: QUIT
Recv: 221 2.0.0 closing connection c11sm22982907wib.1 - gsmtp