Email - Invalid token in the email address

Email - Invalid token in the email address

Error: When testing email settings or sending emails, the client gets the following error:

invalid addr-spec token at offset 0 OR invalid local-part token at offset 0

If the zeckoPay is version 2.0, then this error is due to invalid email address(es).

Check From email's and Recipient's email address.

Also, go into the Email tab, and check email addresses here. Note: If multiple BCC recipients, make sure there is no space before or after the semi-colon.


    • Related Articles

    • Email - Payee Notification error due to an unexpected token

      Payee Notification Error The following error occurs when sending notification to payees: Unexpected token at offset 22 Issue: Check the supplier's email address for trailing white space or an invalid character. Instructions: From your zeckoPay, go to ...

    • Email Settings - Test Email Settings error

      Overview: When testing email settings or sending emails, the following errors are shown: invalid addr-spec token at offset 0 OR invalid local-part token at offset 0 On zeckoPay 2.0 version, this error is due to invalid email address(es). Resolution: ...

    • Select Payables - Invalid Email Settings error

      Overview: When clicking on Select Payables, you receive the following error: Email information is not valid. Please check your settings before trying to process EFT files. This is most likely due to missing Body in the Email. Resolution: Log in to ...

    • Email - Email Error 451

      Email Error 451 zeckoPay reported an issue with emailing payee. The error says 451 system busy try again later. The main error is SMTP 451 error: 451 4.3.0 Mail server temporarily rejected message 451 You have exceeded your messaging limits You have ...

    • Email - TLS 1.0 are not supported error

      Error while emailing Error: When testing email settings or sending emails, you get the following error: 421 4.7.66 TLS 1.0 and 1.1 are not supported. Please upgrade/update your client to support TLS 1.2. Visit https://aka.ms/smtp_auth_tls. ...