Email Archives - File transfer tool from Limagito

23 Oct
What are the steps to configure a mail alert
Q: What is the steps to configure a mail alert ?
A: First select the Rule you want to configure.
Next, Select ‘Moving Rule’ Menu> ‘Rule Events’ item:

Important, each enabled event will use its own setup. So you’ll have to do the setup for each enabled event. In this example we enabled and added a setup for the ‘On Error’ event only.
Maybe it is a good idea to enable ‘Success event memory’ and ‘Error event Memory’. This way the events will only be triggered when the status changes between Success <> Error and not with every Success and Error event.

#filetransfer #filemanagement
If you need any help with this ‘configure a mail alert’ request, please let us know.
Best Regards,
Limagito Team
By Limagito-Team Email Events alert, email alert
02 Oct
How to send encrypted emails using a public key
In version v2023.10.1.0 we added an option to send encrypted emails.
Open the SMTP as Destination option. The “Sign / Encrypt” tab is only available when our second API vendor CK is selected. This option is also available in our Rule Events Email option.
Select “Sign / Encrypt” tab:
Enable Encrypt Email: this will encrypt the email using the certificate file. When sending an encrypted email, it is the recipient’s certificate (Public Key part) that is used for encryption. Only the public key
is needed to encrypt. The recipient is the only one possessing the private key, and therefore is the only one able to decrypt.
Certificate File: Load an RSA-based certificate. Encrypting an email only requires the public key (Decrypting an email requires the private key).
Loads a certificate from a .cer, .crt, .p7b, or .pem file. This method accepts certificates from files in any of the following formats:
1. DER encoded binary X.509 (.CER)
2. Base-64 encoded X.509 (.CER)
3. Cryptographic Message Syntax Standard – PKCS #7 Certificates (.P7B)
4. PEM format
Key Length: When the email is sent encrypted (using PKCS7 public-key encryption), this selects the key length of the underlying symmetric encryption algorithm.
The possible values allowed depend on the Pkcs7CryptAlg property. For “aes”, the key length may be 128, 192, or 256.
For “3des” the key length must be 192. For “des” the key length must be 40. For “rc2” the key length can be 40, 56, 64, or 128.
Use Oaep Padding: Selects the RSA encryption scheme when encrypting email. The default value is disabled, which selects RSAES_PKCS1-V1_5. If set to enabled, then RSAES_OAEP is used.
Oaep Has Algorithm: Selects the hash algorithm for use within OAEP padding when encrypting email using RSAES-OAEP. The valid choices are sha1 , sha256 , sha384 , sha512.

If you need any information about this ‘send encrypted emails’ option, please let us know.
#email #smtp #filetransfer #filemanagement
Best regards,
Limagito Team
By Limagito-Team Email SMTP encrypted emails
30 Sep
How to send signed emails using PFX File
In version v2023.9.30.0 we added an option to send signed emails.
Open the SMTP as Destination option. The “Sign / Encrypt” tab is only available when our second API vendor CK is selected. This option is also available in the Rule Events Email option.
Select “Sign / Encrypt” tab:
Signature PFX File: The PFX file to be used as source for locating the certificate and private key required for signing.
Signature Password: The PFX file’s password
Find Cert By Subject (optional): Finds a certificate where one of the Subject properties (SubjectCN, SubjectE, SubjectO, SubjectOU, SubjectL, SubjectST, SubjectC) matches exactly (but case insensitive) with the passed string. A match in SubjectCN will be tried first, followed by SubjectE, and SubjectO. After that, the first match found in SubjectOU, SubjectL, SubjectST, or SubjectC, but in no guaranteed order, is returned. All matches are case insensitive.
Signature Algorithm (optional): Selects the signature algorithm to be used when sending signed (PKCS7) email. The default value is PKCS1-v1_5 . This can be set to RSASSA-PSS (or simply pss ) to use the RSASSA-PSS signature scheme. Note: This property only applies when signing with an RSA private key. It does not apply for ECC or DSA private keys.
Sign Hash Algorithm (optional): Selects the underlying hash algorithm used when sending signed (PKCS7) email. Possible values are sha1 , sha256 , sha384 , sha512 , md5 , and md2 .
Use Opaque Signing: When enabled, a signed email is generated as signed-data. When disabled, a signed email is generated as multipart/signed. A multipart/signed email is such that the signature is contained in a separate MIME body part and the original content of the email is not encapsulated within the signature. A signed-data email is such that it’s non-multipart MIME (content type is “application/pkcs7-signature”) and the original email is encapsulated within the signature.
If you need any info about this ‘send signed emails’ option, please let us know.
#email #smtp #filetransfer #filemanagement
Best regards,
Limagito Team
By Limagito-Team Email SMTP pfx, signed email