Feature: SMTP sending of plain messages Background: Given there exists an account with username "[user:user]" and password "password" And there exists an account with username "[user:user2]" and password "password" Then it succeeds When bridge starts And the user logs in with username "[user:user]" and password "password" And user "[user:user]" finishes syncing And user "[user:user]" connects and authenticates SMTP client "1" Then it succeeds # black fails to get parent ID @skip-black Scenario: HTML message to external account When SMTP client "1" sends the following message from "[user:user]@[domain]" to "pm.bridge.qa@gmail.com": """ From: Bridge Test <[user:user]@[domain]> To: External Bridge Subject: HTML text external Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 In-Reply-To: This is body of HTML mail without attachment """ Then it succeeds When user "[user:user]" connects and authenticates IMAP client "1" Then IMAP client "1" eventually sees the following messages in "Sent": | from | to | subject | | [user:user]@[domain] | pm.bridge.qa@gmail.com | HTML text external | And the body in the "POST" request to "/mail/v4/messages" is: """ { "Message": { "Subject": "HTML text external", "Sender": { "Name": "Bridge Test" }, "ToList": [ { "Address": "pm.bridge.qa@gmail.com", "Name": "External Bridge" } ], "CCList": [], "BCCList": [], "MIMEType": "text/html" } } """ # black is changing order of attachments @skip-black Scenario: HTML message with inline image to external account When SMTP client "1" sends the following message from "[user:user]@[domain]" to "pm.bridge.qa@gmail.com": """ From: Bridge Test <[user:user]@[domain]> To: External Bridge Subject: Html Inline External Content-Disposition: inline User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0 MIME-Version: 1.0 Content-Language: en-US Content-Type: multipart/related; boundary="------------61FA22A41A3F46E8E90EF528" This is a multi-part message in MIME format. --------------61FA22A41A3F46E8E90EF528 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit

Behold! An inline

\r\n

Behold! An inline $3D\"\"\r\nwidth=3D\"24\"$
\r\n

\r\n\r\n" }, { "content-type": "image/gif", "content-type-name": "email-action-left.gif", "content-disposition": "inline", "content-disposition-filename": "email-action-left.gif", "transfer-encoding": "base64", "body-is": "R0lGODlhAQABAAAAADs=" } ] } ] } } """ Scenario: HTML message with alternative inline to internal account When SMTP client "1" sends the following message from "[user:user]@[domain]" to "[user:user2]@[domain]": """ From: Bridge Test <[user:user]@[domain]> To: Internal Bridge <[user:user2]@[domain]> Subject: Html Inline Alternative Internal Content-Disposition: inline User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------5A259F4DE164B5ADA313F644" Content-Language: en-US This is a multi-part message in MIME format. --------------5A259F4DE164B5ADA313F644 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Behold! An inline --------------5A259F4DE164B5ADA313F644 Content-Type: multipart/related; boundary="------------61FA22A41A3F46E8E90EF528" --------------61FA22A41A3F46E8E90EF528 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit

Behold! An inline

--------------61FA22A41A3F46E8E90EF528 Content-Type: image/gif; name="email-action-left.gif" Content-Transfer-Encoding: base64 Content-ID: Content-Disposition: inline; filename="email-action-left.gif" R0lGODlhAQABAAAAADs= --------------61FA22A41A3F46E8E90EF528-- --------------5A259F4DE164B5ADA313F644-- """ Then it succeeds When user "[user:user]" connects and authenticates IMAP client "1" Then IMAP client "1" eventually sees the following messages in "Sent": | from | to | subject | | [user:user]@[domain] | pm.bridge.qa@gmail.com | Html Inline Alternative External | And the body in the "POST" request to "/mail/v4/messages" is: """ { "Message": { "Subject": "Html Inline Alternative External", "Sender": { "Name": "Bridge Test" }, "ToList": [ { "Address": "pm.bridge.qa@gmail.com", "Name": "External Bridge" } ], "CCList": [], "BCCList": [], "MIMEType": "text/html" } } """ # black fails to get parent ID @skip-black Scenario: HTML message with extremely long line (greater than default 2000 line limit) to external account When SMTP client "1" sends the following message from "[user:user]@[domain]" to "pm.bridge.qa@gmail.com": """ From: Bridge Test <[user:user]@[domain]> To: External Bridge Subject: HTML text external Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 In-Reply-To: aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa """ Then it succeeds When user "[user:user]" connects and authenticates IMAP client "1" Then IMAP client "1" eventually sees the following messages in "Sent": | from | to | subject | | [user:user]@[domain] | pm.bridge.qa@gmail.com | HTML text external | And the body in the "POST" request to "/mail/v4/messages" is: """ { "Message": { "Subject": "HTML text external", "Sender": { "Name": "Bridge Test" }, "ToList": [ { "Address": "pm.bridge.qa@gmail.com", "Name": "External Bridge" } ], "CCList": [], "BCCList": [], "MIMEType": "text/html" } } """ Scenario: HTML message with Foreign/Nonascii chars in Subject and Body to external When user "[user:user]" connects and authenticates SMTP client "1" And SMTP client "1" sends the following EML "html/foreign_ascii_subject_body.template.eml" from "[user:user]@[domain]" to "pm.bridge.qa@gmail.com" Then it succeeds When user "[user:user]" connects and authenticates IMAP client "1" Then IMAP client "1" eventually sees the following messages in "Sent": | from | to | subject | | [user:user]@[domain] | pm.bridge.qa@gmail.com | Subjεέςτ ¶ Ä È | And the body in the "POST" request to "/mail/v4/messages" is: """ { "Message": { "Subject": "Subjεέςτ ¶ Ä È", "Sender": { "Name": "Bridge Test" }, "ToList": [ { "Address": "pm.bridge.qa@gmail.com", "Name": "External Bridge" } ], "CCList": [], "BCCList": [], "MIMEType": "text/html" } } """ # It is expected for the structure check to look a bit different. More info on GODT-3011 @regression # Black changes order of attachments @skip-black Scenario: HTML message with remote content in Body When SMTP client "1" sends the following message from "[user:user]@[domain]" to "[user:user2]@[domain]": """ Date: 01 Jan 1980 00:00:00 +0000 To: Internal Bridge Test <[user:user2]@[domain]> From: Bridge Test <[user:user]@[domain]> Subject: MESSAGE WITH REMOTE CONTENT SENT Content-Type: multipart/alternative; boundary="------------vUMV7TiM65KWBg30p6OgD3Vp" This is a multi-part message in MIME format. --------------vUMV7TiM65KWBg30p6OgD3Vp Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Remote content Bridge Remote content --------------vUMV7TiM65KWBg30p6OgD3Vp Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit

Remote content

Bridge

Remote content

--------------vUMV7TiM65KWBg30p6OgD3Vp-- """ Then it succeeds When user "[user:user]" connects and authenticates IMAP client "1" And IMAP client "1" eventually sees the following message in "Sent" with this structure: """ { "date": "01 Jan 01 00:00 +0000", "to": "Internal Bridge Test <[user:user2]@[domain]>", "from": "Bridge Test <[user:user]@[domain]>", "subject": "MESSAGE WITH REMOTE CONTENT SENT", "content": { "content-type": "text/html", "content-type-charset": "utf-8", "transfer-encoding": "quoted-printable", "body-is": "\r\n\r\n \r\n \r\n \r\n

Remote content

\r\n

\r\n

\r\n

$\"Bridge\"$

\r\n

Remote content
\r\n

\r\n
\r\n \r\n\r\n" } } """