From e1531c200c2f672c96ab23318d7aaf04a43a60e0 Mon Sep 17 00:00:00 2001 From: Leander Beernaert Date: Fri, 6 Jan 2023 14:38:06 +0100 Subject: [PATCH] GODT-1817: Delete old smtp send feature tests All these tests have already been ported. --- tests/_features/smtp/send/bcc.feature | 69 ---- .../smtp/send/embedded_message.feature | 38 -- tests/_features/smtp/send/failures.feature | 52 --- tests/_features/smtp/send/html.feature | 335 ------------------ tests/_features/smtp/send/html_att.feature | 210 ----------- tests/_features/smtp/send/mixed_case.feature | 38 -- tests/_features/smtp/send/plain.feature | 324 ----------------- tests/_features/smtp/send/plain_att.feature | 187 ---------- .../_features/smtp/send/same_message.feature | 45 --- tests/_features/smtp/send/send_append.feature | 50 --- .../_features/smtp/send/two_messages.feature | 71 ---- 11 files changed, 1419 deletions(-) delete mode 100644 tests/_features/smtp/send/bcc.feature delete mode 100644 tests/_features/smtp/send/embedded_message.feature delete mode 100644 tests/_features/smtp/send/failures.feature delete mode 100644 tests/_features/smtp/send/html.feature delete mode 100644 tests/_features/smtp/send/html_att.feature delete mode 100644 tests/_features/smtp/send/mixed_case.feature delete mode 100644 tests/_features/smtp/send/plain.feature delete mode 100644 tests/_features/smtp/send/plain_att.feature delete mode 100644 tests/_features/smtp/send/same_message.feature delete mode 100644 tests/_features/smtp/send/send_append.feature delete mode 100644 tests/_features/smtp/send/two_messages.feature diff --git a/tests/_features/smtp/send/bcc.feature b/tests/_features/smtp/send/bcc.feature deleted file mode 100644 index 790f1dda..00000000 --- a/tests/_features/smtp/send/bcc.feature +++ /dev/null @@ -1,69 +0,0 @@ -Feature: SMTP with bcc - Background: - Given there is connected user "user" - And there is SMTP client logged in as "user" - - Scenario: Send message to address in to and bcc - When SMTP client sends message with bcc "bridgetest2@protonmail.com" - """ - Subject: hello - From: Bridge Test <[userAddress]> - To: Internal Bridge - - hello - - """ - Then SMTP response is "OK" - And mailbox "Sent" for "user" has messages - | from | to | subject | - | [userAddress] | bridgetest@protonmail.com | hello | - And message is sent with API call - """ - { - "Message": { - "Subject": "hello", - "ToList": [ - { - "Address": "bridgetest@protonmail.com", - "Name": "Internal Bridge" - } - ], - "CCList": [], - "BCCList": [ - { - "Address": "bridgetest2@protonmail.com" - } - ] - } - } - """ - - - Scenario: Send message only to bcc - When SMTP client sends message with bcc "bridgetest@protonmail.com" - """ - Subject: hello - From: Bridge Test <[userAddress]> - - hello - - """ - Then SMTP response is "OK" - And mailbox "Sent" for "user" has messages - | from | to | subject | - | [userAddress] | | hello | - And message is sent with API call - """ - { - "Message": { - "Subject": "hello", - "ToList": [], - "CCList": [], - "BCCList": [ - { - "Address": "bridgetest@protonmail.com" - } - ] - } - } - """ diff --git a/tests/_features/smtp/send/embedded_message.feature b/tests/_features/smtp/send/embedded_message.feature deleted file mode 100644 index 843e5124..00000000 --- a/tests/_features/smtp/send/embedded_message.feature +++ /dev/null @@ -1,38 +0,0 @@ -Feature: SMTP sending embedded message - Scenario: Send it - Given there is connected user "user" - And there is SMTP client logged in as "user" - When SMTP client sends message - """ - From: Bridge Test <[userAddress]> - To: Internal Bridge - Subject: Embedded message - Content-Type: multipart/mixed; boundary="boundary" - - This is a multi-part message in MIME format. - --boundary - Content-Type: text/plain; charset=utf-8 - Content-Transfer-Encoding: 7bit - - - --boundary - Content-Type: message/rfc822; name="embedded.eml" - Content-Transfer-Encoding: 7bit - Content-Disposition: attachment; filename="embedded.eml" - - From: Bar - To: Bridge Test - Subject: (No Subject) - Content-Type: text/plain; charset=utf-8 - Content-Transfer-Encoding: quoted-printable - - hello - - --boundary-- - - - """ - Then SMTP response is "OK" - And mailbox "Sent" for "user" has messages - | from | to | subject | - | [userAddress] | bridgetest@protonmail.com | Embedded message | diff --git a/tests/_features/smtp/send/failures.feature b/tests/_features/smtp/send/failures.feature deleted file mode 100644 index c9a87652..00000000 --- a/tests/_features/smtp/send/failures.feature +++ /dev/null @@ -1,52 +0,0 @@ -Feature: SMTP wrong messages - Background: - Given there is connected user "user" - And there is SMTP client logged in as "user" - - Scenario: Message with attachment and wrong boundaries - When SMTP client sends message - """ - From: Bridge Test <[userAddress]> - To: Internal Bridge - Subject: With attachment (wrong boundaries) - Content-Type: multipart/related; boundary=bc5bd30245232f31b6c976adcd59bb0069c9b13f986f9e40c2571bb80aa16606 - - --bc5bd30245232f31b6c976adcd59bb0069c9b13f986f9e40c2571bb80aa16606 - Content-Disposition: inline - Content-Transfer-Encoding: quoted-printable - Content-Type: text/plain; charset=utf-8 - - This is body of mail with attachment - - --bc5bd30245232f31b6c976adcd59bb0069c9b13f986f9e40c2571bb80aa16606 - Content-Disposition: attachment; filename=outline-light-instagram-48.png - Content-Id: <9114fe6f0adfaf7fdf7a@protonmail.com> - Content-Transfer-Encoding: base64 - Content-Type: image/png - - iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAALVBMVEUAAAD///////////////// - //////////////////////////////////////+hSKubAAAADnRSTlMAgO8QQM+/IJ9gj1AwcIQd - OXUAAAGdSURBVDjLXJC9SgNBFIVPXDURTYhgIQghINgowyLYCAYtRFAIgtYhpAjYhC0srCRW6YIg - WNpoHVSsg/gEii+Qnfxq4DyDc3cyMfrBwl2+O+fOHTi8p7LS5RUf/9gpMKL7iT9sK47Q95ggpkzv - 1cvRcsGYNMYsmP+zKN27NR2vcDyTNVdfkOuuniNPMWafvIbljt+YoMEvW8y7lt+ARwhvrgPjhA0I - BTng7S1GLPlypBvtIBPidY4YBDJFdtnkscQ5JGaGqxC9i7jSDwcwnB8qHWBaQjw1ABI8wYgtVoG6 - 9pFkH8iZIiJeulFt4JLvJq8I5N2GMWYbHWDWzM3JZTMdeSWla0kW86FcuI0mfStiNKQ/AhEeh8h0 - YUTffFwrMTT5oSwdojIQ0UKcocgAKRH1HiqhFQmmJa5qRaYHNbRiSsOgslY0NdixItUTUWlZkedP - HXVyAgAIA1F0wP5btQZPIyTwvAqa/Fl4oacuP+e4XHAjSYpkQkxSiMX+T7FPoZJToSStzED70HCy - KE3NGCg4jJrC6Ti7AFwZLhnW0gMbzFZc0RmmeAAAAABJRU5ErkJggg== - --bc5bd30245232f31b6c976adcd59bb0069c9b13f986f9e40c2571bb80aa16606 - - - """ - Then SMTP response is "SMTP error: 554 5.0.0 Error: transaction failed, blame it on the weather: failed to create new parser: unexpected EOF" - - Scenario: Invalid from - When SMTP client sends message - """ - From: Bridge Test - To: Internal Bridge - - hello - - """ - Then SMTP response is "SMTP error: 554 5.0.0 Error: transaction failed, blame it on the weather: backend: invalid email address: not owned by user" diff --git a/tests/_features/smtp/send/html.feature b/tests/_features/smtp/send/html.feature deleted file mode 100644 index 2db43075..00000000 --- a/tests/_features/smtp/send/html.feature +++ /dev/null @@ -1,335 +0,0 @@ -Feature: SMTP sending of HTML messages - Background: - Given there is connected user "user" - And there is SMTP client logged in as "user" - - Scenario: HTML message to external account - When SMTP client sends message - """ - From: Bridge Test <[userAddress]> - 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 SMTP response is "OK" - And mailbox "Sent" for "user" has messages - | from | to | subject | - | [userAddress] | pm.bridge.qa@gmail.com | HTML text external | - And message is sent with API call - """ - { - "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 inline image to external account - When SMTP client sends message - """ - From: Bridge Test <[userAddress]> - 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
-

- - - - --------------61FA22A41A3F46E8E90EF528 - Content-Type: image/gif; name="email-action-left.gif" - Content-Transfer-Encoding: base64 - Content-ID: - Content-Disposition: inline; filename="email-action-left.gif" - - R0lGODlhGAAYANUAACcsKOHs4kppTH6tgYWxiIq0jTVENpG5lDI/M7bRuEaJSkqOTk2RUU+P - U16lYl+lY2iva262cXS6d3rDfYLNhWeeamKTZGSVZkNbRGqhbOPt4////+7u7qioqFZWVlNT - UyIiIgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA - AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACwAAAAAGAAYAAAG - /8CNcLjRJAqVRqNSSGiI0GFgoKhar4NAdHioMhyRCYUyiTgY1cOWUH1ILgIDAGAQXCSPKgHa - XUAyGCCCg4IYGRALCmpCAVUQFgiEkiAIFhBVWhtUDxmRk5IIGXkDRQoMEoGfHpIYEmhGCg4X - nyAdHB+SFw4KRwoRArQdG7eEAhEKSAoTBoIdzs/Cw7iCBhMKSQoUAIJbQ8QgABQKStnbIN1C - 3+HjFcrMtdDO6dMg1dcFvsCfwt+CxsgJYs3a10+QLl4aTKGitYpQq1eaFHDyREtQqFGMHEGq - SMkSJi4K/ACiZQiRIihsJL6JM6fOnTwK9kTpYgqMGDJm0JzsNuWKTw0FWdANMYJECRMnW4IA - ADs= - --------------61FA22A41A3F46E8E90EF528-- - - """ - Then SMTP response is "OK" - And mailbox "Sent" for "user" has messages - | from | to | subject | - | [userAddress] | pm.bridge.qa@gmail.com | Html Inline External | - And message is sent with API call - """ - { - "Message": { - "Subject": "Html Inline External", - "Sender": { - "Name": "Bridge Test" - }, - "ToList": [ - { - "Address": "pm.bridge.qa@gmail.com", - "Name": "External Bridge" - } - ], - "CCList": [], - "BCCList": [], - "MIMEType": "text/html" - } - } - """ - - Scenario: HTML message with alternative inline to internal account - When SMTP client sends message - """ - From: Bridge Test <[userAddress]> - To: Internal Bridge - 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" - - R0lGODlhGAAYANUAACcsKOHs4kppTH6tgYWxiIq0jTVENpG5lDI/M7bRuEaJSkqOTk2RUU+P - U16lYl+lY2iva262cXS6d3rDfYLNhWeeamKTZGSVZkNbRGqhbOPt4////+7u7qioqFZWVlNT - UyIiIgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA - AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACwAAAAAGAAYAAAG - /8CNcLjRJAqVRqNSSGiI0GFgoKhar4NAdHioMhyRCYUyiTgY1cOWUH1ILgIDAGAQXCSPKgHa - XUAyGCCCg4IYGRALCmpCAVUQFgiEkiAIFhBVWhtUDxmRk5IIGXkDRQoMEoGfHpIYEmhGCg4X - nyAdHB+SFw4KRwoRArQdG7eEAhEKSAoTBoIdzs/Cw7iCBhMKSQoUAIJbQ8QgABQKStnbIN1C - 3+HjFcrMtdDO6dMg1dcFvsCfwt+CxsgJYs3a10+QLl4aTKGitYpQq1eaFHDyREtQqFGMHEGq - SMkSJi4K/ACiZQiRIihsJL6JM6fOnTwK9kTpYgqMGDJm0JzsNuWKTw0FWdANMYJECRMnW4IA - ADs= - --------------61FA22A41A3F46E8E90EF528-- - - --------------5A259F4DE164B5ADA313F644-- - - """ - Then SMTP response is "OK" - And mailbox "Sent" for "user" has messages - | from | to | subject | - | [userAddress] | bridgetest@protonmail.com | Html Inline Alternative Internal | - And message is sent with API call - """ - { - "Message": { - "Subject": "Html Inline Alternative Internal", - "Sender": { - "Name": "Bridge Test" - }, - "ToList": [ - { - "Address": "bridgetest@protonmail.com", - "Name": "Internal Bridge" - } - ], - "CCList": [], - "BCCList": [], - "MIMEType": "text/html" - } - } - """ - - Scenario: HTML message with alternative inline to external account - When SMTP client sends message - """ - From: Bridge Test <[userAddress]> - To: External Bridge - Subject: Html Inline Alternative 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-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" - - R0lGODlhGAAYANUAACcsKOHs4kppTH6tgYWxiIq0jTVENpG5lDI/M7bRuEaJSkqOTk2RUU+P - U16lYl+lY2iva262cXS6d3rDfYLNhWeeamKTZGSVZkNbRGqhbOPt4////+7u7qioqFZWVlNT - UyIiIgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA - AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACwAAAAAGAAYAAAG - /8CNcLjRJAqVRqNSSGiI0GFgoKhar4NAdHioMhyRCYUyiTgY1cOWUH1ILgIDAGAQXCSPKgHa - XUAyGCCCg4IYGRALCmpCAVUQFgiEkiAIFhBVWhtUDxmRk5IIGXkDRQoMEoGfHpIYEmhGCg4X - nyAdHB+SFw4KRwoRArQdG7eEAhEKSAoTBoIdzs/Cw7iCBhMKSQoUAIJbQ8QgABQKStnbIN1C - 3+HjFcrMtdDO6dMg1dcFvsCfwt+CxsgJYs3a10+QLl4aTKGitYpQq1eaFHDyREtQqFGMHEGq - SMkSJi4K/ACiZQiRIihsJL6JM6fOnTwK9kTpYgqMGDJm0JzsNuWKTw0FWdANMYJECRMnW4IA - ADs= - --------------61FA22A41A3F46E8E90EF528-- - - --------------5A259F4DE164B5ADA313F644-- - - """ - Then SMTP response is "OK" - And mailbox "Sent" for "user" has messages - | from | to | subject | - | [userAddress] | pm.bridge.qa@gmail.com | Html Inline Alternative External | - And message is sent with API call - """ - { - "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" - } - } - """ - - Scenario: HTML message with extremely long line (greater than default 2000 line limit) to external account - When SMTP client sends message - """ - From: Bridge Test <[userAddress]> - 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 SMTP response is "OK" - And mailbox "Sent" for "user" has messages - | from | to | subject | - | [userAddress] | pm.bridge.qa@gmail.com | HTML text external | - And message is sent with API call - """ - { - "Message": { - "Subject": "HTML text external", - "Sender": { - "Name": "Bridge Test" - }, - "ToList": [ - { - "Address": "pm.bridge.qa@gmail.com", - "Name": "External Bridge" - } - ], - "CCList": [], - "BCCList": [], - "MIMEType": "text/html" - } - } - """ diff --git a/tests/_features/smtp/send/html_att.feature b/tests/_features/smtp/send/html_att.feature deleted file mode 100644 index be140b0e..00000000 --- a/tests/_features/smtp/send/html_att.feature +++ /dev/null @@ -1,210 +0,0 @@ -Feature: SMTP sending of HTML messages with attachments - Background: - Given there is connected user "user" - And there is SMTP client logged in as "user" - - Scenario: HTML message with attachment to internal account - When SMTP client sends message - """ - From: Bridge Test <[userAddress]> - To: Internal Bridge - Subject: HTML with attachment internal - Content-Type: multipart/related; boundary=bc5bd30245232f31b6c976adcd59bb0069c9b13f986f9e40c2571bb80aa16606 - - --bc5bd30245232f31b6c976adcd59bb0069c9b13f986f9e40c2571bb80aa16606 - Content-Disposition: inline - Content-Transfer-Encoding: quoted-printable - Content-Type: text/html; charset=utf-8 - - This is body of HTML mail with attachment - - --bc5bd30245232f31b6c976adcd59bb0069c9b13f986f9e40c2571bb80aa16606 - Content-Disposition: attachment; filename=outline-light-instagram-48.png - Content-Id: <9114fe6f0adfaf7fdf7a@protonmail.com> - Content-Transfer-Encoding: base64 - Content-Type: image/png - - iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAALVBMVEUAAAD///////////////// - //////////////////////////////////////+hSKubAAAADnRSTlMAgO8QQM+/IJ9gj1AwcIQd - OXUAAAGdSURBVDjLXJC9SgNBFIVPXDURTYhgIQghINgowyLYCAYtRFAIgtYhpAjYhC0srCRW6YIg - WNpoHVSsg/gEii+Qnfxq4DyDc3cyMfrBwl2+O+fOHTi8p7LS5RUf/9gpMKL7iT9sK47Q95ggpkzv - 1cvRcsGYNMYsmP+zKN27NR2vcDyTNVdfkOuuniNPMWafvIbljt+YoMEvW8y7lt+ARwhvrgPjhA0I - BTng7S1GLPlypBvtIBPidY4YBDJFdtnkscQ5JGaGqxC9i7jSDwcwnB8qHWBaQjw1ABI8wYgtVoG6 - 9pFkH8iZIiJeulFt4JLvJq8I5N2GMWYbHWDWzM3JZTMdeSWla0kW86FcuI0mfStiNKQ/AhEeh8h0 - YUTffFwrMTT5oSwdojIQ0UKcocgAKRH1HiqhFQmmJa5qRaYHNbRiSsOgslY0NdixItUTUWlZkedP - HXVyAgAIA1F0wP5btQZPIyTwvAqa/Fl4oacuP+e4XHAjSYpkQkxSiMX+T7FPoZJToSStzED70HCy - KE3NGCg4jJrC6Ti7AFwZLhnW0gMbzFZc0RmmeAAAAABJRU5ErkJggg== - --bc5bd30245232f31b6c976adcd59bb0069c9b13f986f9e40c2571bb80aa16606-- - - """ - Then SMTP response is "OK" - And mailbox "Sent" for "user" has messages - | from | to | subject | - | [userAddress] | bridgetest@protonmail.com | HTML with attachment internal | - And message is sent with API call - """ - { - "Message": { - "Subject": "HTML with attachment internal", - "Sender": { - "Name": "Bridge Test" - }, - "ToList": [ - { - "Address": "bridgetest@protonmail.com", - "Name": "Internal Bridge" - } - ], - "CCList": [], - "BCCList": [], - "MIMEType": "text/html" - } - } - """ - - Scenario: HTML message with attachment to external account - When SMTP client sends message - """ - From: Bridge Test <[userAddress]> - To: External Bridge - Subject: HTML with attachment external PGP - Content-Type: multipart/mixed; boundary=bc5bd30245232f31b6c976adcd59bb0069c9b13f986f9e40c2571bb80aa16606 - - --bc5bd30245232f31b6c976adcd59bb0069c9b13f986f9e40c2571bb80aa16606 - Content-Disposition: inline - Content-Transfer-Encoding: quoted-printable - Content-Type: text/html; charset=utf-8 - - This is body of HTML mail with attachment - - --bc5bd30245232f31b6c976adcd59bb0069c9b13f986f9e40c2571bb80aa16606 - Content-Disposition: attachment; filename=outline-light-instagram-48.png - Content-Id: <9114fe6f0adfaf7fdf7a@protonmail.com> - Content-Transfer-Encoding: base64 - Content-Type: image/png - - iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAALVBMVEUAAAD///////////////// - //////////////////////////////////////+hSKubAAAADnRSTlMAgO8QQM+/IJ9gj1AwcIQd - OXUAAAGdSURBVDjLXJC9SgNBFIVPXDURTYhgIQghINgowyLYCAYtRFAIgtYhpAjYhC0srCRW6YIg - WNpoHVSsg/gEii+Qnfxq4DyDc3cyMfrBwl2+O+fOHTi8p7LS5RUf/9gpMKL7iT9sK47Q95ggpkzv - 1cvRcsGYNMYsmP+zKN27NR2vcDyTNVdfkOuuniNPMWafvIbljt+YoMEvW8y7lt+ARwhvrgPjhA0I - BTng7S1GLPlypBvtIBPidY4YBDJFdtnkscQ5JGaGqxC9i7jSDwcwnB8qHWBaQjw1ABI8wYgtVoG6 - 9pFkH8iZIiJeulFt4JLvJq8I5N2GMWYbHWDWzM3JZTMdeSWla0kW86FcuI0mfStiNKQ/AhEeh8h0 - YUTffFwrMTT5oSwdojIQ0UKcocgAKRH1HiqhFQmmJa5qRaYHNbRiSsOgslY0NdixItUTUWlZkedP - HXVyAgAIA1F0wP5btQZPIyTwvAqa/Fl4oacuP+e4XHAjSYpkQkxSiMX+T7FPoZJToSStzED70HCy - KE3NGCg4jJrC6Ti7AFwZLhnW0gMbzFZc0RmmeAAAAABJRU5ErkJggg== - --bc5bd30245232f31b6c976adcd59bb0069c9b13f986f9e40c2571bb80aa16606-- - - """ - Then SMTP response is "OK" - And mailbox "Sent" for "user" has messages - | from | to | subject | - | [userAddress] | pm.bridge.qa@gmail.com | HTML with attachment external PGP | - And message is sent with API call - """ - { - "Message": { - "Subject": "HTML with attachment external PGP", - "Sender": { - "Name": "Bridge Test" - }, - "ToList": [ - { - "Address": "pm.bridge.qa@gmail.com", - "Name": "External Bridge" - } - ], - "CCList": [], - "BCCList": [], - "MIMEType": "text/html" - } - } - """ - - Scenario: Alternative plain and HTML message with rfc822 attachment - When SMTP client sends message - """ - From: Bridge Test <[userAddress]> - To: External Bridge - Subject: Alternative plain and HTML with rfc822 attachment - Content-Type: multipart/mixed; boundary=main-parts - - This is a multipart message in MIME format - - --main-parts - Content-Type: multipart/alternative; boundary=alternatives - - --alternatives - Content-Type: text/plain - - There is an attachment - - - --alternatives - Content-Type: text/html - - There is an attachment - - - --alternatives-- - - --main-parts - Content-Type: message/rfc822 - Content-Transfer-Encoding: 7bit - Content-Disposition: attachment - - Received: from mx1.opensuse.org (mx1.infra.opensuse.org [192.168.47.95]) by - mailman3.infra.opensuse.org (Postfix) with ESMTP id 38BE2AC3 for - ; Sun, 11 Jul 2021 19:50:34 +0000 (UTC) - From: "Bob " - Sender: "Bob" - To: "opensuse-factory" - Cc: "Bob" - References: - Subject: VirtualBox problems with kernel 5.13 - Date: Sun, 11 Jul 2021 21:50:25 +0200 - Message-ID: <71672e5f-24a2-c79f-03cc-4c923eb1790b@lwfinger.net> - MIME-Version: 1.0 - Content-Type: text/plain; charset="utf-8" - Content-Transfer-Encoding: quoted-printable - X-Mailer: Microsoft Outlook 16.0 - List-Unsubscribe: - Content-Language: en-us - List-Help: - List-Subscribe: - Thread-Index: AQFWvbNSAqFOch49YPlLU4eJWPObaQK2iKDq - - I am writing this message as openSUSE's maintainer of VirtualBox. - - Nearly every update of the Linux kernel to a new 5.X version breaks = - VirtualBox. - - Bob - - --main-parts-- - - """ - Then SMTP response is "OK" - And mailbox "Sent" for "user" has messages - | from | to | subject | - | [userAddress] | pm.bridge.qa@gmail.com | Alternative plain and HTML with rfc822 attachment | - And message is sent with API call - """ - { - "Message": { - "Subject": "Alternative plain and HTML with rfc822 attachment", - "Sender": { - "Name": "Bridge Test" - }, - "ToList": [ - { - "Address": "pm.bridge.qa@gmail.com", - "Name": "External Bridge" - } - ], - "CCList": [], - "BCCList": [], - "MIMEType": "text/html" - } - } - """ diff --git a/tests/_features/smtp/send/mixed_case.feature b/tests/_features/smtp/send/mixed_case.feature deleted file mode 100644 index 747a6720..00000000 --- a/tests/_features/smtp/send/mixed_case.feature +++ /dev/null @@ -1,38 +0,0 @@ -Feature: SMTP sending with mixed case address - Background: - Given there is connected user "user" - And there is SMTP client logged in as "user" - - Scenario: Mixed sender case in sender address - When SMTP client sends message - """ - From: Bridge Test <[userAddress|capitalize]> - To: Internal Bridge - - hello - - """ - Then SMTP response is "OK" - And mailbox "Sent" for "user" has messages - | from | to | subject | - | [userAddress] | bridgetest@protonmail.com | | - And message is sent with API call - """ - { - "Message": { - "Subject": "", - "Sender": { - "Name": "Bridge Test" - }, - "ToList": [ - { - "Address": "bridgetest@protonmail.com", - "Name": "Internal Bridge" - } - ], - "CCList": [], - "BCCList": [], - "MIMEType": "text/plain" - } - } - """ diff --git a/tests/_features/smtp/send/plain.feature b/tests/_features/smtp/send/plain.feature deleted file mode 100644 index 483090a3..00000000 --- a/tests/_features/smtp/send/plain.feature +++ /dev/null @@ -1,324 +0,0 @@ -Feature: SMTP sending of plain messages - Background: - Given there is connected user "user" - And there is SMTP client logged in as "user" - - Scenario: Only from and to headers to internal account - When SMTP client sends message - """ - From: Bridge Test <[userAddress]> - To: Internal Bridge - - hello - - """ - Then SMTP response is "OK" - And mailbox "Sent" for "user" has messages - | from | to | subject | - | [userAddress] | bridgetest@protonmail.com | | - And message is sent with API call - """ - { - "Message": { - "Subject": "", - "Sender": { - "Name": "Bridge Test" - }, - "ToList": [ - { - "Address": "bridgetest@protonmail.com", - "Name": "Internal Bridge" - } - ], - "CCList": [], - "BCCList": [], - "MIMEType": "text/plain" - } - } - """ - - Scenario: Only from and to headers to external account - When SMTP client sends message - """ - From: Bridge Test <[userAddress]> - To: External Bridge - - hello - - """ - Then SMTP response is "OK" - And mailbox "Sent" for "user" has messages - | from | to | subject | - | [userAddress] | pm.bridge.qa@gmail.com | | - And message is sent with API call - """ - { - "Message": { - "Subject": "", - "Sender": { - "Name": "Bridge Test" - }, - "ToList": [ - { - "Address": "pm.bridge.qa@gmail.com", - "Name": "External Bridge" - } - ], - "CCList": [], - "BCCList": [], - "MIMEType": "text/plain" - } - } - """ - - Scenario: Basic message to internal account - When SMTP client sends message - """ - From: Bridge Test <[userAddress]> - To: Internal Bridge - Subject: Plain text internal - Content-Disposition: inline - Content-Type: text/plain; charset=utf-8 - - This is body of mail 👋 - - """ - Then SMTP response is "OK" - And mailbox "Sent" for "user" has messages - | from | to | subject | - | [userAddress] | bridgetest@protonmail.com | Plain text internal | - And message is sent with API call - """ - { - "Message": { - "Subject": "Plain text internal", - "Sender": { - "Name": "Bridge Test" - }, - "ToList": [ - { - "Address": "bridgetest@protonmail.com", - "Name": "Internal Bridge" - } - ], - "CCList": [], - "BCCList": [], - "MIMEType": "text/plain" - } - } - """ - - Scenario: Basic message to external account - When SMTP client sends message - """ - From: Bridge Test <[userAddress]> - To: External Bridge - Subject: Plain text external - Content-Disposition: inline - Content-Type: text/plain; charset=utf-8 - - This is body of mail 👋 - - """ - Then SMTP response is "OK" - And mailbox "Sent" for "user" has messages - | from | to | subject | - | [userAddress] | pm.bridge.qa@gmail.com | Plain text external | - And message is sent with API call - """ - { - "Message": { - "Subject": "Plain text external", - "Sender": { - "Name": "Bridge Test" - }, - "ToList": [ - { - "Address": "pm.bridge.qa@gmail.com", - "Name": "External Bridge" - } - ], - "CCList": [], - "BCCList": [], - "MIMEType": "text/plain" - } - } - """ - - Scenario: Message without charset is utf8 - When SMTP client sends message - """ - From: Bridge Test <[userAddress]> - To: External Bridge - Subject: Plain text no charset external - Content-Disposition: inline - Content-Type: text/plain; - - This is body of mail without charset. Please assume utf8 - - """ - Then SMTP response is "OK" - And mailbox "Sent" for "user" has messages - | from | to | subject | - | [userAddress] | pm.bridge.qa@gmail.com | Plain text no charset external | - And message is sent with API call - """ - { - "Message": { - "Subject": "Plain text no charset external", - "Sender": { - "Name": "Bridge Test" - }, - "ToList": [ - { - "Address": "pm.bridge.qa@gmail.com", - "Name": "External Bridge" - } - ], - "CCList": [], - "BCCList": [], - "MIMEType": "text/plain" - } - } - """ - - Scenario: Message without charset is base64-encoded latin1 - When SMTP client sends message - """ - From: Bridge Test <[userAddress]> - To: External Bridge - Subject: Plain text no charset external - Content-Disposition: inline - Content-Type: text/plain; - Content-Transfer-Encoding: base64 - - dGhpcyBpcyBpbiBsYXRpbjEgYW5kIHRoZXJlIGFyZSBsb3RzIG9mIGVzIHdpdGggYWNjZW50czog - 6enp6enp6enp6enp6enp - - - """ - Then SMTP response is "OK" - And mailbox "Sent" for "user" has messages - | from | to | subject | - | [userAddress] | pm.bridge.qa@gmail.com | Plain text no charset external | - And message is sent with API call - """ - { - "Message": { - "Subject": "Plain text no charset external", - "Sender": { - "Name": "Bridge Test" - }, - "ToList": [ - { - "Address": "pm.bridge.qa@gmail.com", - "Name": "External Bridge" - } - ], - "CCList": [], - "BCCList": [], - "MIMEType": "text/plain" - } - } - """ - - Scenario: Message without charset and content is detected as HTML - When SMTP client sends message - """ - From: Bridge Test <[userAddress]> - To: External Bridge - Subject: Plain, no charset, no content, external - Content-Disposition: inline - Content-Type: text/plain; - - """ - Then SMTP response is "OK" - And mailbox "Sent" for "user" has messages - | from | to | subject | - | [userAddress] | pm.bridge.qa@gmail.com | Plain, no charset, no content, external | - And message is sent with API call - """ - { - "Message": { - "Subject": "Plain, no charset, no content, external", - "Sender": { - "Name": "Bridge Test" - }, - "ToList": [ - { - "Address": "pm.bridge.qa@gmail.com", - "Name": "External Bridge" - } - ], - "CCList": [], - "BCCList": [], - "MIMEType": "text/plain" - } - } - """ - - Scenario: RCPT does not contain all CC - When SMTP client sends "MAIL FROM:<[userAddress]>" - Then SMTP response is "OK" - When SMTP client sends "RCPT TO:" - Then SMTP response is "OK" - When SMTP client sends "DATA" - Then SMTP response is "OK" - When SMTP client sends - """ - From: Bridge Test <[userAddress]> - To: Internal Bridge - CC: Internal Bridge 2 - Content-Type: text/plain - Subject: RCPT-CC test - - This is CC missing in RCPT test. Have a nice day! -. - """ - Then SMTP response is "OK" - And mailbox "Sent" for "user" has messages - | from | to | cc | subject | - | [userAddress] | bridgetest@protonmail.com | bridgetest2@protonmail.com | RCPT-CC test | - And message is sent with API call - """ - { - "Message": { - "Subject": "RCPT-CC test", - "Sender": { - "Name": "Bridge Test" - }, - "ToList": [ - { - "Address": "bridgetest@protonmail.com", - "Name": "Internal Bridge" - } - ], - "CCList": [ - { - "Address": "bridgetest2@protonmail.com", - "Name": "Internal Bridge 2" - } - ], - "BCCList": [] - } - } - """ - And packages are sent with API call - """ - { - "Packages":[ - { - "Addresses":{ - "bridgetest@protonmail.com":{ - "Type":1 - }, - "bridgetest2@protonmail.com":{ - "Type":1 - } - }, - "Type":1, - "MIMEType":"text/plain" - } - ] - } - """ \ No newline at end of file diff --git a/tests/_features/smtp/send/plain_att.feature b/tests/_features/smtp/send/plain_att.feature deleted file mode 100644 index 7690bc13..00000000 --- a/tests/_features/smtp/send/plain_att.feature +++ /dev/null @@ -1,187 +0,0 @@ -Feature: SMTP sending of plain messages with attachments - Background: - Given there is connected user "user" - And there is SMTP client logged in as "user" - - Scenario: Basic message with attachment to internal account - When SMTP client sends message - """ - From: Bridge Test <[userAddress]> - To: Internal Bridge - Subject: Plain with attachment - Content-Type: multipart/related; boundary=bc5bd30245232f31b6c976adcd59bb0069c9b13f986f9e40c2571bb80aa16606 - - --bc5bd30245232f31b6c976adcd59bb0069c9b13f986f9e40c2571bb80aa16606 - Content-Disposition: inline - Content-Transfer-Encoding: quoted-printable - Content-Type: text/plain; charset=utf-8 - - This is body of mail with attachment - - --bc5bd30245232f31b6c976adcd59bb0069c9b13f986f9e40c2571bb80aa16606 - Content-Disposition: attachment; filename=outline-light-instagram-48.png - Content-Id: <9114fe6f0adfaf7fdf7a@protonmail.com> - Content-Transfer-Encoding: base64 - Content-Type: image/png - - iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAALVBMVEUAAAD///////////////// - //////////////////////////////////////+hSKubAAAADnRSTlMAgO8QQM+/IJ9gj1AwcIQd - OXUAAAGdSURBVDjLXJC9SgNBFIVPXDURTYhgIQghINgowyLYCAYtRFAIgtYhpAjYhC0srCRW6YIg - WNpoHVSsg/gEii+Qnfxq4DyDc3cyMfrBwl2+O+fOHTi8p7LS5RUf/9gpMKL7iT9sK47Q95ggpkzv - 1cvRcsGYNMYsmP+zKN27NR2vcDyTNVdfkOuuniNPMWafvIbljt+YoMEvW8y7lt+ARwhvrgPjhA0I - BTng7S1GLPlypBvtIBPidY4YBDJFdtnkscQ5JGaGqxC9i7jSDwcwnB8qHWBaQjw1ABI8wYgtVoG6 - 9pFkH8iZIiJeulFt4JLvJq8I5N2GMWYbHWDWzM3JZTMdeSWla0kW86FcuI0mfStiNKQ/AhEeh8h0 - YUTffFwrMTT5oSwdojIQ0UKcocgAKRH1HiqhFQmmJa5qRaYHNbRiSsOgslY0NdixItUTUWlZkedP - HXVyAgAIA1F0wP5btQZPIyTwvAqa/Fl4oacuP+e4XHAjSYpkQkxSiMX+T7FPoZJToSStzED70HCy - KE3NGCg4jJrC6Ti7AFwZLhnW0gMbzFZc0RmmeAAAAABJRU5ErkJggg== - --bc5bd30245232f31b6c976adcd59bb0069c9b13f986f9e40c2571bb80aa16606-- - - """ - Then SMTP response is "OK" - And mailbox "Sent" for "user" has messages - | from | to | subject | - | [userAddress] | bridgetest@protonmail.com | Plain with attachment | - And message is sent with API call - """ - { - "Message": { - "Subject": "Plain with attachment", - "Sender": { - "Name": "Bridge Test" - }, - "ToList": [ - { - "Address": "bridgetest@protonmail.com", - "Name": "Internal Bridge" - } - ], - "CCList": [], - "BCCList": [], - "MIMEType": "text/plain" - } - } - """ - - Scenario: Plain message with attachment to external account - When SMTP client sends message - """ - From: Bridge Test <[userAddress]> - To: External Bridge - Subject: Plain with attachment external - Content-Type: multipart/related; boundary=bc5bd30245232f31b6c976adcd59bb0069c9b13f986f9e40c2571bb80aa16606 - - --bc5bd30245232f31b6c976adcd59bb0069c9b13f986f9e40c2571bb80aa16606 - Content-Disposition: inline - Content-Transfer-Encoding: quoted-printable - Content-Type: text/plain; charset=utf-8 - - This is body of mail with attachment - - --bc5bd30245232f31b6c976adcd59bb0069c9b13f986f9e40c2571bb80aa16606 - Content-Disposition: attachment; filename=outline-light-instagram-48.png - Content-Id: <9114fe6f0adfaf7fdf7a@protonmail.com> - Content-Transfer-Encoding: base64 - Content-Type: image/png - - iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAALVBMVEUAAAD///////////////// - //////////////////////////////////////+hSKubAAAADnRSTlMAgO8QQM+/IJ9gj1AwcIQd - OXUAAAGdSURBVDjLXJC9SgNBFIVPXDURTYhgIQghINgowyLYCAYtRFAIgtYhpAjYhC0srCRW6YIg - WNpoHVSsg/gEii+Qnfxq4DyDc3cyMfrBwl2+O+fOHTi8p7LS5RUf/9gpMKL7iT9sK47Q95ggpkzv - 1cvRcsGYNMYsmP+zKN27NR2vcDyTNVdfkOuuniNPMWafvIbljt+YoMEvW8y7lt+ARwhvrgPjhA0I - BTng7S1GLPlypBvtIBPidY4YBDJFdtnkscQ5JGaGqxC9i7jSDwcwnB8qHWBaQjw1ABI8wYgtVoG6 - 9pFkH8iZIiJeulFt4JLvJq8I5N2GMWYbHWDWzM3JZTMdeSWla0kW86FcuI0mfStiNKQ/AhEeh8h0 - YUTffFwrMTT5oSwdojIQ0UKcocgAKRH1HiqhFQmmJa5qRaYHNbRiSsOgslY0NdixItUTUWlZkedP - HXVyAgAIA1F0wP5btQZPIyTwvAqa/Fl4oacuP+e4XHAjSYpkQkxSiMX+T7FPoZJToSStzED70HCy - KE3NGCg4jJrC6Ti7AFwZLhnW0gMbzFZc0RmmeAAAAABJRU5ErkJggg== - --bc5bd30245232f31b6c976adcd59bb0069c9b13f986f9e40c2571bb80aa16606-- - - """ - Then SMTP response is "OK" - And mailbox "Sent" for "user" has messages - | from | to | subject | - | [userAddress] | pm.bridge.qa@gmail.com | Plain with attachment external | - And message is sent with API call - """ - { - "Message": { - "Subject": "Plain with attachment external", - "Sender": { - "Name": "Bridge Test" - }, - "ToList": [ - { - "Address": "pm.bridge.qa@gmail.com", - "Name": "External Bridge" - } - ], - "CCList": [], - "BCCList": [], - "MIMEType": "text/plain" - } - } - """ - - Scenario: Plain message with attachment to two external accounts - When SMTP client sends message - """ - From: Bridge Test <[userAddress]> - To: External Bridge 1 - CC: External Bridge 2 - Subject: Plain with attachment external PGP and external CC - Content-Type: multipart/mixed; boundary=bc5bd30245232f31b6c976adcd59bb0069c9b13f986f9e40c2571bb80aa16606 - - --bc5bd30245232f31b6c976adcd59bb0069c9b13f986f9e40c2571bb80aa16606 - Content-Disposition: inline - Content-Transfer-Encoding: quoted-printable - Content-Type: text/plain; charset=utf-8 - - This is body of mail with attachment - - --bc5bd30245232f31b6c976adcd59bb0069c9b13f986f9e40c2571bb80aa16606 - Content-Disposition: attachment; filename=outline-light-instagram-48.png - Content-Id: <9114fe6f0adfaf7fdf7a@protonmail.com> - Content-Transfer-Encoding: base64 - Content-Type: image/png - - iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAALVBMVEUAAAD///////////////// - //////////////////////////////////////+hSKubAAAADnRSTlMAgO8QQM+/IJ9gj1AwcIQd - OXUAAAGdSURBVDjLXJC9SgNBFIVPXDURTYhgIQghINgowyLYCAYtRFAIgtYhpAjYhC0srCRW6YIg - WNpoHVSsg/gEii+Qnfxq4DyDc3cyMfrBwl2+O+fOHTi8p7LS5RUf/9gpMKL7iT9sK47Q95ggpkzv - 1cvRcsGYNMYsmP+zKN27NR2vcDyTNVdfkOuuniNPMWafvIbljt+YoMEvW8y7lt+ARwhvrgPjhA0I - BTng7S1GLPlypBvtIBPidY4YBDJFdtnkscQ5JGaGqxC9i7jSDwcwnB8qHWBaQjw1ABI8wYgtVoG6 - 9pFkH8iZIiJeulFt4JLvJq8I5N2GMWYbHWDWzM3JZTMdeSWla0kW86FcuI0mfStiNKQ/AhEeh8h0 - YUTffFwrMTT5oSwdojIQ0UKcocgAKRH1HiqhFQmmJa5qRaYHNbRiSsOgslY0NdixItUTUWlZkedP - HXVyAgAIA1F0wP5btQZPIyTwvAqa/Fl4oacuP+e4XHAjSYpkQkxSiMX+T7FPoZJToSStzED70HCy - KE3NGCg4jJrC6Ti7AFwZLhnW0gMbzFZc0RmmeAAAAABJRU5ErkJggg== - --bc5bd30245232f31b6c976adcd59bb0069c9b13f986f9e40c2571bb80aa16606-- - - """ - Then SMTP response is "OK" - And mailbox "Sent" for "user" has messages - | from | to | cc | subject | - | [userAddress] | pm.bridge.qa@gmail.com | bridgeqa@seznam.cz | Plain with attachment external PGP and external CC | - And message is sent with API call - """ - { - "Message": { - "Subject": "Plain with attachment external PGP and external CC", - "Sender": { - "Name": "Bridge Test" - }, - "ToList": [ - { - "Address": "pm.bridge.qa@gmail.com", - "Name": "External Bridge 1" - } - ], - "CCList": [ - { - "Address": "bridgeqa@seznam.cz", - "Name": "External Bridge 2" - } - ], - "BCCList": [], - "MIMEType": "text/plain" - } - } - """ diff --git a/tests/_features/smtp/send/same_message.feature b/tests/_features/smtp/send/same_message.feature deleted file mode 100644 index db89d816..00000000 --- a/tests/_features/smtp/send/same_message.feature +++ /dev/null @@ -1,45 +0,0 @@ -Feature: SMTP sending the same message twice - Background: - Given there is connected user "user" - And there is SMTP client logged in as "user" - When SMTP client sends message - """ - From: Bridge Test <[userAddress]> - To: Internal Bridge - Subject: Hello - - World - - """ - Then SMTP response is "OK" - - Scenario: The exact same message is not sent twice - When SMTP client sends message - """ - From: Bridge Test <[userAddress]> - To: Internal Bridge - Subject: Hello - - World - - """ - Then SMTP response is "OK" - And mailbox "Sent" for "user" has messages - | from | to | subject | - | [userAddress] | bridgetest@protonmail.com | Hello | - - Scenario: Slight change means different message and is sent twice - When SMTP client sends message - """ - From: Bridge Test <[userAddress]> - To: Internal Bridge - Subject: Hello. - - World - - """ - Then SMTP response is "OK" - And mailbox "Sent" for "user" has messages - | from | to | subject | - | [userAddress] | bridgetest@protonmail.com | Hello | - | [userAddress] | bridgetest@protonmail.com | Hello. | diff --git a/tests/_features/smtp/send/send_append.feature b/tests/_features/smtp/send/send_append.feature deleted file mode 100644 index ebf79b7f..00000000 --- a/tests/_features/smtp/send/send_append.feature +++ /dev/null @@ -1,50 +0,0 @@ -Feature: SMTP sending with APPENDing to Sent - Background: - Given there is connected user "user" - And there is IMAP client logged in as "user" - And there is IMAP client selected in "Sent" - And there is SMTP client logged in as "user" - - Scenario: Send message and append to Sent - # First do sending. - When SMTP client sends message - """ - To: Internal Bridge - Subject: Manual send and append - Message-ID: bridgemessage42 - - hello - - """ - Then SMTP response is "OK" - And mailbox "Sent" for "user" has 1 messages - And mailbox "Sent" for "user" has messages - | externalid | from | to | subject | - | bridgemessage42 | [userAddress] | bridgetest@protonmail.com | Manual send and append | - And message is sent with API call - """ - { - "Message": { - "Subject": "Manual send and append", - "ExternalID": "bridgemessage42" - } - } - """ - - # Then simulate manual append to Sent mailbox - message should be detected as a duplicate. - When IMAP client imports message to "Sent" - """ - To: Internal Bridge - Subject: Manual send and append - Message-ID: bridgemessage42 - - hello - - """ - Then IMAP response is "OK" - And mailbox "Sent" for "user" has 1 messages - - # Check that the external ID was not lost in the process. - When IMAP client sends command "FETCH 1 body.peek[header]" - Then IMAP response is "OK" - And IMAP response contains "bridgemessage42" diff --git a/tests/_features/smtp/send/two_messages.feature b/tests/_features/smtp/send/two_messages.feature deleted file mode 100644 index f8e652c2..00000000 --- a/tests/_features/smtp/send/two_messages.feature +++ /dev/null @@ -1,71 +0,0 @@ -Feature: SMTP sending two messages - Scenario: Send two messages in one connection - Given there is connected user "user" - And there is SMTP client logged in as "user" - When SMTP client sends message - """ - From: Bridge Test <[userAddress]> - To: Internal Bridge - - hello - - """ - Then SMTP response is "OK" - When SMTP client sends message - """ - From: Bridge Test <[userAddress]> - To: Internal Bridge - - world - - """ - Then SMTP response is "OK" - - Scenario: Send to two addresses - Given there is connected user "userMoreAddresses" - And there is "userMoreAddresses" in "split" address mode - And there is SMTP client "smtp1" logged in as "userMoreAddresses" with address "primary" - And there is SMTP client "smtp2" logged in as "userMoreAddresses" with address "secondary" - When SMTP client "smtp1" sends message - """ - From: Bridge Test <[userAddress]> - To: Internal Bridge - - hello - - """ - Then SMTP response to "smtp1" is "OK" - When SMTP client "smtp2" sends message - """ - From: Bridge Test <[userAddress]> - To: Internal Bridge - - world - - """ - Then SMTP response to "smtp2" is "OK" - - Scenario: Send to two users - Given there is connected user "user" - And there is connected user "userMoreAddresses" - And there is SMTP client "smtp1" logged in as "user" - And there is SMTP client "smtp2" logged in as "userMoreAddresses" - - When SMTP client "smtp1" sends message - """ - From: Bridge Test <[userAddress]> - To: Internal Bridge - - hello - - """ - Then SMTP response to "smtp1" is "OK" - When SMTP client "smtp2" sends message - """ - From: Bridge Test <[userAddress]> - To: Internal Bridge - - world - - """ - Then SMTP response to "smtp2" is "OK"