Messages and limitations of the Gmail connector
Message code list of GMAIL category
The following message codes correspond to errors that occur in Gmail Connector.
This message code is output when an undefined error occurs.
|
Cause |
Solution |
|---|---|
|
An undefined error occurred. |
Check the error message or the help of the operation in which the error has occurred. |
Corresponding error
-
None
This message code is output when the login to the Gmail server has failed.
|
Cause |
Solution |
|---|---|
|
In the Receive E-mail (POP3) operation, login failed because POP isn't enabled in the Gmail settings. |
Enable POP in the Gmail settings of the target user. |
|
In the Receive E-mail (IMAP4) operation, login failed because IMAP isn't enabled in the Gmail settings. |
Enable IMAP in the Gmail settings of the target user. |
|
User name or Password for the operation in which the error occurred is invalid. |
Check User name or Password for the operation in which the error occurred. |
|
User name or Authentication (Gmail OAuth 2.0) for the operation in which the error occurred is invalid. |
Check User name or Authentication (Gmail OAuth 2.0) for the operation in which the error occurred. |
Corresponding error
-
javax.mail.AuthenticationFailedException
-
OAuth2AuthenticationFailedException
This message code is output when connecting to the Gmail server has failed.
|
Cause |
Solution |
|---|---|
|
Failed to establish a connection to Gmail |
Check the network reachability. |
Corresponding error
-
com.sun.mail.util.MailConnectException
This message code is output when no recipient address is specified.
|
Cause |
Solution |
|---|---|
|
To/Cc/Bcc of the Send One E-mail operation is incorrect. |
Check that all of the following requirements for the Send One E-mail operation are met:
|
|
The recipient address in the input data for the Send Multiple E-mails operation is incorrect. |
Check that all of the following requirements for the Send Multiple E-mails operation are met:
|
Corresponding error
-
RecipientsNotFoundException
This message code is output when no sender is specified for From.
|
Cause |
Solution |
|---|---|
|
No sender is specified in the input data for the Send Multiple E-mails operation. |
Check that a sender is specified in the input data for the Send Multiple E-mails operation. |
Corresponding error
-
SenderNotFoundException
This message code is output when the email address specified for the sender is invalid.
|
Cause |
Solution |
|---|---|
|
The sender specified in the input data for the Send Multiple E-mails operation is invalid. |
Check that the sender in the input data for the Send Multiple E-mails operation is valid. |
Corresponding error
-
InvalidMailAddressException
This message code is output when sending messages has failed.
|
Cause |
Solution |
|---|---|
|
The Send One E-mail operation has failed to send an email. |
Check that To/Cc/Bcc / Mail Address for the Send One E-mail operation is correct. |
|
The Send Multiple E-mails operation has failed to send emails. |
Check that the To, CC, and BCC in the input data for the Send Multiple E-mails operation are correct. |
Corresponding error
-
javax.mail.SendFailedException
Exception messages of GMAIL category
|
Exception name |
Cause |
Solution |
|---|---|---|
|
AuthorizationException <Detailed information...> |
Failed in authentication/authorization. |
Check the detailed information of the exception. Check Client ID or Client secret. Check the settings of the application authentication information on Google Cloud Platform. |
|
com.sun.mail.util.MailConnectException: |
Failed to establish a connection to the Gmail IMAP4 server. |
Check the network reachability. |
|
com.sun.mail.util.MailConnectException: |
Failed to establish a connection to Gmail POP3 server. |
Check the network reachability. |
|
com.sun.mail.util.MailConnectException: |
Failed to establish a connection to the Gmail SMTP server. |
Check the network reachability. |
|
InvalidMailAddressException <Sender> is an invalid email address. |
The sender specified in the input data is invalid. |
Check that the sender specified in the input data is valid. |
|
InvalidPropertyConfigurationException <Property name> is not specified. |
<Property name> isn't specified. |
Specify <property name>. |
|
InvalidSchemaException |
The schema of the input data is invalid. |
Check the schema of the input data. |
|
java.io.UnsupportedEncodingException |
Encoding set to Encoding isn't supported. |
Check the encoding specified in Encoding. |
|
javax.mail.AuthenticationFailedException: [AUTHENTICATIONFAILED] Invalid credentials (Failure) |
User name or Password is incorrect. |
Check User name or Password. |
|
javax.mail.AuthenticationFailedException: [AUTH] Username and password not accepted. |
User name or Password is incorrect. |
Check User name or Password. |
|
javax.mail.AuthenticationFailedException: Invalid credentials <String> |
User name or Password is incorrect. |
Check User name or Password. |
|
javax.mail.AuthenticationFailedException: |
User name or Password is incorrect. |
Check User name or Password. |
|
javax.mail.AuthenticationFailedException: [ALERT] Your account is not enabled for IMAP use. Please visit your Gmail settings page and enable your account for IMAP access. (Failure) |
IMAP isn't enabled in the Gmail settings. |
Enable IMAP in the Gmail settings of the target user. |
|
javax.mail.AuthenticationFailedException: [SYS/PERM] Your account is not enabled for POP access. Please visit your Gmail settings page and enable your account for POP access. |
POP isn't enabled in the Gmail settings. |
Enable POP in the Gmail settings of the target user. |
|
javax.mail.SendFailedException |
Failed to send email. |
Check that the To, CC, and BCC in the input data are correct. |
|
javax.mail.SendFailedException |
Failed to send email. |
Check To/Cc/Bcc / Mail Address. |
|
OAuth2AuthenticationFailedException OAuth 2.0 authorization has failed. |
User name or Authentication (Gmail OAuth 2.0) is invalid. |
Check User name or Authentication (Gmail OAuth 2.0). |
|
RecipientsNotFoundException |
To/Cc/Bcc is incorrect. |
Check the following: - At least one email address is specified for To/Cc/Bcc. - To/Cc/Bcc / Category is correct. - To/Cc/Bcc / Mail Address is entered. - To/Cc/Bcc / Mail Address doesn't contain any multi-byte characters. |
|
RecipientsNotFoundException |
The recipient address specified in the input data is invalid. |
Check the following: - A recipient address is specified in the input data. - The recipient address specified in the input data doesn't contain any multi-byte characters. |
|
ResourceNotFoundException Resource definition could not be found. Name: [] |
Destination isn't specified. |
Specify Destination. |
|
ResourceNotFoundException Resource definition could not be found. Name: [<connection resource name>] |
The resource definition selected in Destination isn't found. |
Check the connection resource specified in Destination. |
|
ResourceNotFoundException Resource definition could not be found. Name: [] |
Destination or Authentication (Gmail OAuth 2.0) isn't specified. |
Specify Destination or Authentication (Gmail OAuth 2.0). |
|
ResourceNotFoundException Resource definition could not be found. Name: [<connection resource name>] |
The resource definition selected in Destination or Authentication (Gmail OAuth 2.0) isn't found. |
Check the connection resource specified in Destination or Authentication (Gmail OAuth 2.0). |
|
SenderNotFoundException |
No sender is specified in the input data. |
Check whether the sender has been specified in the input data. |
|
TokenException Token could not be updated. <Detailed information...> |
Refresh Request failed. |
Check the detailed information of the exception. Perform Publish refresh token again. |
|
TokenException Refresh token could not be obtained. <Detailed information...> |
Token Request failed. |
Check the detailed information of the exception. |
Limitations of GMAIL category
Notes
-
The behavior described in the help pages is subject to change depending on specification changes in the destination.
Connection resource properties (destination)
Specification limits
None.
Specification limits
-
According to Google's policy, authentication using only user name and password won't be available after September 30, 2024.
https://www.hulft.com/application/files/7717/1333/7601/information_20240418.pdf (Japanese language only)
Receive E-mail (POP3) will be no longer available. So, change to Receive E-mail (IMAP4) and select OAuth 2.0 AUTH in Authentication mode.
-
To use Gmail POP3 server, you need to enable POP in the Gmail settings of the target user.
For information about how to enable POP and how the POP3 server operates, refer to the help for Gmail.
-
The settings to delete received messages or mark messages as read are configured in the Gmail settings of the target user.
-
To receive again messages which have already been received, enable POP again in the Gmail settings of the target user.
-
Divided attachment files can't be consolidated.
-
For attachment files, only base64 format is supported. uuencode format and BinHex format aren't supported.
-
If an attachment file is sent as a form of rich text (Content-Type = application/ms-tnef) by Outlook, this connector can't receive it properly.
-
For multipart messages, only one level is available.
Multipart messages can be handled, but nested multipart messages can't be handled.
In the first example below, this connector handles the first part of a multipart message as the body (body element) and handles the second and subsequent parts as attachments (file elements of a child element of the attachedfiles element). This is the same for both sending and receiving.
-
Example 1: Multipart message not nested (usual attachment format)
-----Boundary 1-----
Message
-----Boundary 1-----
Message
-----Boundary 1-----
Message
------------------------
-
Example 2: Nested multipart message (Outlook message in HTML format with an attachment, or message forwarded by specific mailers (message/rfc822))
-----Boundary 1-----
-----Boundary 2-----
Message
-----Boundary 2-----
Message
-----Boundary 2-----
Message
------------------------
-----Boundary 1-----
-----Boundary 3-----
Message
-----Boundary 3-----
Message
-----Boundary 3-----
Message
------------------------
-----Boundary 1-----
-----Boundary 4-----
Message
-----Boundary 4-----
Message
-----Boundary 4-----
Message
------------------------
------------------------
-
-
Be careful when handling platform-dependent characters and specific characters.
-
Specific characters
Character
Code point (Unicode)
―
U+2014
～
U+301C
∥
U+2016
－
U+2212
￠
U+00A2
￡
U+00A3
￢
U+00AC
-
When receiving JIS messages: the specific characters above are mapped to Shift_JIS code. Perform the subsequent process in Shift_JIS.
-
When sending UTF-8 messages: the specific characters above are mapped to Windows31-J code. Perform the subsequent process in Windows31-J.
-
-
Platform-dependent characters (CP932)
Transmit and receive the following platform-dependent characters as UTF-8.
Character
Code point (Unicode)
①
U+2460
②
U+2461
③
U+2462
④
U+2463
⑤
U+2464
⑥
U+2465
⑦
U+2466
⑧
U+2467
⑨
U+2468
⑩
U+2469
⑪
U+246A
⑫
U+246B
⑬
U+246C
⑭
U+246D
⑮
U+246E
⑯
U+246F
⑰
U+2470
⑱
U+2471
⑲
U+2472
⑳
U+2473
Ⅰ
U+2160
Ⅱ
U+2161
Ⅲ
U+2162
Ⅳ
U+2163
Ⅴ
U+2164
Ⅵ
U+2165
Ⅶ
U+2166
Ⅷ
U+2167
Ⅸ
U+2168
Ⅹ
U+2169
㍉
U+3349
㌔
U+3314
㌢
U+3322
㍍
U+334D
㌘
U+3318
㌧
U+3327
㌃
U+3303
㌶
U+3336
㍑
U+3351
㍗
U+3357
㌍
U+330D
㌦
U+3326
㌣
U+3323
㌫
U+332B
㍊
U+334A
㌻
U+333B
㎜
U+339C
㎝
U+339D
㎞
U+339E
㎎
U+338E
㎏
U+338F
㏄
U+33C4
㎡
U+33A1
㍻
U+337B
〝
U+301D
〟
U+301F
№
U+2116
㏍
U+33CD
℡
U+2121
㊤
U+32A4
㊥
U+32A5
㊦
U+32A6
㊧
U+32A7
㊫
U+32AB
㈱
U+3231
㈲
U+3232
㈹
U+3239
㍾
U+337E
㍽
U+337D
㍼
U+337C
≒
U+2252
≡
U+2261
∫
U+222B
∮
U+222E
∑
U+2211
√
U+221A
⊥
U+22A5
∠
U+2220
∟
U+221F
⊿
U+22BF
∵
U+2235
∩
U+2229
∪
U+222A
ⅰ
U+2170
ⅱ
U+2171
ⅲ
U+2172
ⅳ
U+2173
ⅴ
U+2174
ⅵ
U+2175
ⅶ
U+2176
ⅷ
U+2177
ⅸ
U+2178
ⅹ
U+2179
￢
U+FFE2
￤
U+FFE4
＇
U+FF07
＂
U+FF02
-
-
The order of appearance of the headers isn't guaranteed.
-
PGP and S/MIME aren't supported.
-
BCC data can't be obtained.
Notes
-
SSL is used in communication between Gmail POP3 server and this connector.
Specification limits
-
According to Google's policy, authentication using only user name and password won't be available after September 30, 2024.
https://www.hulft.com/application/files/7717/1333/7601/information_20240418.pdf (Japanese language only)
If Password AUTH is selected in Authentication mode for the Receive E-mail (IMAP4) operation, change to OAuth 2.0 AUTH.
-
To use Gmail IMAP4 server, you need to enable IMAP in the Gmail settings of the target user.
For information about how to enable IMAP and how the IMAP4 server operates, refer to the help for Gmail.
-
Divided attachment files can't be consolidated.
-
For attachment files, only base64 format is supported. uuencode format and BinHex format aren't supported.
-
If an attachment file is sent as a form of rich text (Content-Type = application/ms-tnef) by Outlook, this connector can't receive it properly.
-
For multipart messages, only one level is available.
Multipart messages can be handled, but nested multipart messages can't be handled.
In the first example below, this connector handles the first part of a multipart message as the body (body element) and handles the second and subsequent parts as attachments (file elements of a child element of the attachedfiles element). This is the same for both sending and receiving.
-
Example 1: Multipart message not nested (usual attachment format)
-----Boundary 1-----
Message
-----Boundary 1-----
Message
-----Boundary 1-----
Message
------------------------
-
Example 2: Nested multipart message (Outlook message in HTML format with an attachment, or message forwarded by specific mailers (message/rfc822))
-----Boundary 1-----
-----Boundary 2-----
Message
-----Boundary 2-----
Message
-----Boundary 2-----
Message
------------------------
-----Boundary 1-----
-----Boundary 3-----
Message
-----Boundary 3-----
Message
-----Boundary 3-----
Message
------------------------
-----Boundary 1-----
-----Boundary 4-----
Message
-----Boundary 4-----
Message
-----Boundary 4-----
Message
------------------------
------------------------
-
-
Be careful when handling platform-dependent characters and specific characters.
-
Specific characters
Character
Code point (Unicode)
―
U+2014
～
U+301C
∥
U+2016
－
U+2212
￠
U+00A2
￡
U+00A3
￢
U+00AC
-
When receiving JIS messages: the specific characters above are mapped to Shift_JIS code. Perform the subsequent process in Shift_JIS.
-
When sending UTF-8 messages: the specific characters above are mapped to Windows31-J code. Perform the subsequent process in Windows31-J.
-
-
Platform-dependent characters (CP932)
Transmit and receive the following platform-dependent characters as UTF-8.
Character
Code point (Unicode)
①
U+2460
②
U+2461
③
U+2462
④
U+2463
⑤
U+2464
⑥
U+2465
⑦
U+2466
⑧
U+2467
⑨
U+2468
⑩
U+2469
⑪
U+246A
⑫
U+246B
⑬
U+246C
⑭
U+246D
⑮
U+246E
⑯
U+246F
⑰
U+2470
⑱
U+2471
⑲
U+2472
⑳
U+2473
Ⅰ
U+2160
Ⅱ
U+2161
Ⅲ
U+2162
Ⅳ
U+2163
Ⅴ
U+2164
Ⅵ
U+2165
Ⅶ
U+2166
Ⅷ
U+2167
Ⅸ
U+2168
Ⅹ
U+2169
㍉
U+3349
㌔
U+3314
㌢
U+3322
㍍
U+334D
㌘
U+3318
㌧
U+3327
㌃
U+3303
㌶
U+3336
㍑
U+3351
㍗
U+3357
㌍
U+330D
㌦
U+3326
㌣
U+3323
㌫
U+332B
㍊
U+334A
㌻
U+333B
㎜
U+339C
㎝
U+339D
㎞
U+339E
㎎
U+338E
㎏
U+338F
㏄
U+33C4
㎡
U+33A1
㍻
U+337B
〝
U+301D
〟
U+301F
№
U+2116
㏍
U+33CD
℡
U+2121
㊤
U+32A4
㊥
U+32A5
㊦
U+32A6
㊧
U+32A7
㊫
U+32AB
㈱
U+3231
㈲
U+3232
㈹
U+3239
㍾
U+337E
㍽
U+337D
㍼
U+337C
≒
U+2252
≡
U+2261
∫
U+222B
∮
U+222E
∑
U+2211
√
U+221A
⊥
U+22A5
∠
U+2220
∟
U+221F
⊿
U+22BF
∵
U+2235
∩
U+2229
∪
U+222A
ⅰ
U+2170
ⅱ
U+2171
ⅲ
U+2172
ⅳ
U+2173
ⅴ
U+2174
ⅵ
U+2175
ⅶ
U+2176
ⅷ
U+2177
ⅸ
U+2178
ⅹ
U+2179
￢
U+FFE2
￤
U+FFE4
＇
U+FF07
＂
U+FF02
-
-
The order of appearance of the headers isn't guaranteed.
-
PGP and S/MIME aren't supported.
-
BCC data can't be obtained.
Notes
-
SSL is used in communication between Gmail IMAP4 server and this connector.
Specification limits
-
According to Google's policy, authentication using only user name and password won't be available after September 30, 2024.
https://www.hulft.com/application/files/7717/1333/7601/information_20240418.pdf (Japanese language only)
If SMTP AUTH (LOGIN) is selected in Authentication mode for the Send Multiple E-mails operation, change to OAuth 2.0 AUTH.
-
For information about how Gmail SMTP server operates, refer to the help for Gmail.
-
Be careful when handling platform-dependent characters and specific characters.
-
Specific characters
If you send the following specific characters, send them in UTF-8.
Character
Code point (Unicode)
―
U+2014
～
U+301C
∥
U+2016
－
U+2212
￠
U+00A2
￡
U+00A3
￢
U+00AC
-
Platform-dependent characters (CP932)
Transmit and receive the following platform-dependent characters as UTF-8.
Character
Code point (Unicode)
①
U+2460
②
U+2461
③
U+2462
④
U+2463
⑤
U+2464
⑥
U+2465
⑦
U+2466
⑧
U+2467
⑨
U+2468
⑩
U+2469
⑪
U+246A
⑫
U+246B
⑬
U+246C
⑭
U+246D
⑮
U+246E
⑯
U+246F
⑰
U+2470
⑱
U+2471
⑲
U+2472
⑳
U+2473
Ⅰ
U+2160
Ⅱ
U+2161
Ⅲ
U+2162
Ⅳ
U+2163
Ⅴ
U+2164
Ⅵ
U+2165
Ⅶ
U+2166
Ⅷ
U+2167
Ⅸ
U+2168
Ⅹ
U+2169
㍉
U+3349
㌔
U+3314
㌢
U+3322
㍍
U+334D
㌘
U+3318
㌧
U+3327
㌃
U+3303
㌶
U+3336
㍑
U+3351
㍗
U+3357
㌍
U+330D
㌦
U+3326
㌣
U+3323
㌫
U+332B
㍊
U+334A
㌻
U+333B
㎜
U+339C
㎝
U+339D
㎞
U+339E
㎎
U+338E
㎏
U+338F
㏄
U+33C4
㎡
U+33A1
㍻
U+337B
〝
U+301D
〟
U+301F
№
U+2116
㏍
U+33CD
℡
U+2121
㊤
U+32A4
㊥
U+32A5
㊦
U+32A6
㊧
U+32A7
㊫
U+32AB
㈱
U+3231
㈲
U+3232
㈹
U+3239
㍾
U+337E
㍽
U+337D
㍼
U+337C
≒
U+2252
≡
U+2261
∫
U+222B
∮
U+222E
∑
U+2211
√
U+221A
⊥
U+22A5
∠
U+2220
∟
U+221F
⊿
U+22BF
∵
U+2235
∩
U+2229
∪
U+222A
ⅰ
U+2170
ⅱ
U+2171
ⅲ
U+2172
ⅳ
U+2173
ⅴ
U+2174
ⅵ
U+2175
ⅶ
U+2176
ⅷ
U+2177
ⅸ
U+2178
ⅹ
U+2179
￢
U+FFE2
￤
U+FFE4
＇
U+FF07
＂
U+FF02
-
-
Some formats of RFC2231 encoding can't be read. If the file name of the attachment contains Japanese, it will be encoded in RFC2231, but if the file name is long, it may not be able to be handled.
Example:
filename*1=...
filename*2=...
-
The order of appearance and location of the specified headers isn't guaranteed.
-
If the header value is an empty character or null, the header isn't included in the message.
-
Content-Type can't be set for individual attachment files.
-
If you send a text-format attachment file, the default encoding of the OS will be set to the charset parameters of Content-Type. You can't individually set the charset parameter value.
-
Therefore, depending on the encoding of the attached file, it may not match the encoding of the charset parameter, and when you preview the contents of the attached file with specific mailers, the text may be garbled.
In this case, you may be able to avoid garbling by not adding the charset parameter to Content-Type of the attached file.
-
-
PGP and S/MIME aren't supported.
Notes
-
SSL is used in communication between Gmail SMTP server and this connector.
Specification limits
-
According to Google's policy, authentication using only user name and password won't be available after September 30, 2024.
https://www.hulft.com/application/files/7717/1333/7601/information_20240418.pdf (Japanese language only)
If SMTP AUTH (LOGIN) is selected in Authentication mode for the Send One E-mail operation, change to OAuth 2.0 AUTH.
-
For information about how Gmail SMTP server operates, refer to the help for Gmail.
-
Be careful when handling platform-dependent characters and specific characters.
-
Specific characters
If you send the following specific characters, send them in UTF-8.
Character
Code point (Unicode)
―
U+2014
～
U+301C
∥
U+2016
－
U+2212
￠
U+00A2
￡
U+00A3
￢
U+00AC
-
Platform-dependent characters (CP932)
Transmit and receive the following platform-dependent characters as UTF-8.
Character
Code point (Unicode)
①
U+2460
②
U+2461
③
U+2462
④
U+2463
⑤
U+2464
⑥
U+2465
⑦
U+2466
⑧
U+2467
⑨
U+2468
⑩
U+2469
⑪
U+246A
⑫
U+246B
⑬
U+246C
⑭
U+246D
⑮
U+246E
⑯
U+246F
⑰
U+2470
⑱
U+2471
⑲
U+2472
⑳
U+2473
Ⅰ
U+2160
Ⅱ
U+2161
Ⅲ
U+2162
Ⅳ
U+2163
Ⅴ
U+2164
Ⅵ
U+2165
Ⅶ
U+2166
Ⅷ
U+2167
Ⅸ
U+2168
Ⅹ
U+2169
㍉
U+3349
㌔
U+3314
㌢
U+3322
㍍
U+334D
㌘
U+3318
㌧
U+3327
㌃
U+3303
㌶
U+3336
㍑
U+3351
㍗
U+3357
㌍
U+330D
㌦
U+3326
㌣
U+3323
㌫
U+332B
㍊
U+334A
㌻
U+333B
㎜
U+339C
㎝
U+339D
㎞
U+339E
㎎
U+338E
㎏
U+338F
㏄
U+33C4
㎡
U+33A1
㍻
U+337B
〝
U+301D
〟
U+301F
№
U+2116
㏍
U+33CD
℡
U+2121
㊤
U+32A4
㊥
U+32A5
㊦
U+32A6
㊧
U+32A7
㊫
U+32AB
㈱
U+3231
㈲
U+3232
㈹
U+3239
㍾
U+337E
㍽
U+337D
㍼
U+337C
≒
U+2252
≡
U+2261
∫
U+222B
∮
U+222E
∑
U+2211
√
U+221A
⊥
U+22A5
∠
U+2220
∟
U+221F
⊿
U+22BF
∵
U+2235
∩
U+2229
∪
U+222A
ⅰ
U+2170
ⅱ
U+2171
ⅲ
U+2172
ⅳ
U+2173
ⅴ
U+2174
ⅵ
U+2175
ⅶ
U+2176
ⅷ
U+2177
ⅸ
U+2178
ⅹ
U+2179
￢
U+FFE2
￤
U+FFE4
＇
U+FF07
＂
U+FF02
-
-
Some formats of RFC2231 encoding can't be read. If the file name of the attachment contains Japanese, it will be encoded in RFC2231, but if the file name is long, it may not be able to be handled.
Example:
filename*1=...
filename*2=...
-
The order of appearance and location of the specified headers isn't guaranteed.
-
If the header value is an empty character or null, the header isn't included in the message.
-
Content-Type can't be set for individual attachment files.
-
If you send a text-format attachment file, the default encoding of the OS will be set to the charset parameters of Content-Type. You can't individually set the charset parameter value.
-
Therefore, depending on the encoding of the attached file, it may not match the encoding of the charset parameter, and when you preview the contents of the attached file with specific mailers, the text may be garbled.
In this case, you may be able to avoid garbling by not adding the charset parameter to Content-Type of the attached file.
-
-
PGP and S/MIME aren't supported.
Notes
-
SSL is used in communication between Gmail SMTP server and this connector.