Email

  • 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.

    limagito file mover smtp as destination

    • 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.

    limagito file mover send signed email

    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 ,
  • 25 Sep

    Sending Mails (SMTP) via an SSH tunnel

    In version v2023.9.25.0 we added an option that allows you sending emails using SMTP via an SSH tunnel.

    • Important is to use our second API vendor – CK

    limagito file mover smtp as destination

    • Select the SSH Tab for your setup:

    This option let us connect to an SSH server and creates a tunnel for SMTP. The ‘Host’ is the hostname (or IP address) of the SSH server. The ‘Port’ is typically 22, which is the standard SSH port number. At this moment only SSH authentication using username and password is possible.

    limagito file mover smtp over a ssh tunnel

    • In version v2023.9.30.0 we added “SSH Public-Key Authentication”:

    – Authenticates with the SSH server using public-key authentication. The corresponding public key must have been installed on the SSH server. Authentication will succeed if the matching “Username” is provided.

    limagito file mover smtp via an SSH tunnel

    If you need any info about this option, please let us know.

    #smtp #ssh #filetransfer #filemanagement

    Best regards,

    Limagito Team

    By Limagito-Team Email SMTP ,
  • 18 Jun

    SMTP Error Message could not be assembled due to error 1

    Q: We had an issue with one of our servers, and had to rebuild it from scratch. When we rebuilt our workflows all seemed to be fine however we are getting the following error when we try to initiate an SMTP workflow.
    6/14/2022 5:03:47 PM SendSMTPMsg Exception: Message could not be assembled due to error 1
    We don’t see any errors on the SMTP server, and this is the same setup we had in place before the previous server failed.
    Can you give us a direction on this? I am not sure what error 1 means, and I am unable to find it in the documentation.

    A: Did you copy/paste some text into the body (or subject) field? Could you clear the body completely and do a test please.

    This is most likely the message contains a character which is not covered by the current charset. If you didn’t set any charset, “iso-8859-1” is used by default.
    Also, please make sure you’ve provided at least one “from” address and at least one “to” address. This could be the reason of the error also.

    For SMTP we also have a CharSet option. In your case I would set it to:   utf-8

    assembled due to error 1

    #SMTP #Filetransfer #Filemanagement

    If you need any info about this ‘assembled due to error 1’ request, please let us know.

    Best regards,

    Limagito Team

SEARCH