An invalid character was found in the mail header: ';'.

SOLVED

Sending to multiple email addresses resules in invalid char of ;

Sage Small Business Edition (Version 2019 - 7.92.09)


Update client with multiple emails

[email protected];[email protected]

This will save
- must be ; with no spaces - cannot use , or space to seperte email adresses
- if saving with , or space the save states it is an invalid email format.

now go to invoices
- can preview invoice
- but cannot email
- states "An invalid character was found in the mail header: ';'."

Top Replies

  • Hi  ,

    Thanks for reaching out. The support team has recently addressed this issue with a new fix. To resolve the "An invalid character was found in the email header" error when attempting to…

  • +1
    verified answer

    Hi  ,

    Thanks for reaching out. The support team has recently addressed this issue with a new fix. To resolve the "An invalid character was found in the email header" error when attempting to send to multiple email addresses separated by a semicolon, please follow these steps:

    1. Close the BusinessVision program.
    2. Navigate to the C:\BusinessVision folder on your computer, and rename the file named Sage.BusinessVision.SMTPClient.dll to Sage.BusinessVision.SMTPClientOLD.dll.
    3. Download the "Send to multiple email addresses fix" from the Sage Knowledgebase and unzip it. You will find a new Sage.BusinessVision.SMTPClient.dll file within the package.
    4. Copy this new Sage.BusinessVision.SMTPClient.dll file into the C:\BusinessVision folder to replace the old one.
    5. Test sending an email to multiple addresses to confirm that the issue is resolved.

    For more detailed instructions or if you encounter any issues during this process, please refer to the solution article directly or contact Sage Support for further assistance. Hope this helps!

    Warm regards,
    Erzsi

  • 0 in reply to Erzsi_I

    Hello ERZSI_I;

    Thank you for the fix.  Installed the updated Sage.BusinessVision.SMTPClient.dll & tested. Working.

    ---

    Now why I could not find this fix searching the support??