Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Email Bogus MIME version and other deliverability issues #7880

Open
2 tasks done
brandonkal opened this issue May 1, 2024 · 3 comments
Open
2 tasks done

[Bug]: Email Bogus MIME version and other deliverability issues #7880

brandonkal opened this issue May 1, 2024 · 3 comments
Labels
bug Something isn't working customization resources

Comments

@brandonkal
Copy link

Preflight Checklist

  • I could not find a solution in the documentation, the existing issues or discussions
  • I have joined the ZITADEL chat

Environment

ZITADEL Cloud

Version

Latest

Database

None

Database Version

No response

Describe the problem caused by this bug

mail-tester.com is reporting a Bogus MIME version header from the initial user email. I assume this is the same issue with the other transactional emails.

Other issues to improve deliverability:

  1. No text/plain version. This should be easy to fix.
  2. HTML version has font has low contrast

To reproduce

  1. Go to mail-tester.com and copy the email address
  2. Register a new user using this address
  3. Check the deliverability score

Screenshots

zitadel-email-issues

Expected behavior

No response

Operating System

No response

Relevant Configuration

No response

Additional Context

No response

@brandonkal brandonkal added the bug Something isn't working label May 1, 2024
@stebenz
Copy link
Collaborator

stebenz commented May 1, 2024

Hi @brandonkal

Not quite sure, I tried to find out if this is a case of case-sensitivity where there is no defined handling.
Created #7886 for the version.

With the definition under RFC-2045 it should be "MIME-Version", but with RFC-2045 Section 2:

 All numeric and octet values are given in decimal notation in this
 set of documents. All media type values, subtype values, and
 parameter names as defined are case-insensitive.  However, parameter
 values are case-sensitive unless otherwise specified for the specific
 parameter.

and "parameter names as defined are case-insesitive", I'm not sure if mail-tester.com maybe handles it wrong, do you have any information about that?

@brandonkal
Copy link
Author

Mail-tester is using SpamAssassin for that score. So I would think it is handling it correctly since SpamAssassin is commonly deployed

@stebenz
Copy link
Collaborator

stebenz commented May 7, 2024

@brandonkal we deployed a fix with v2.51.1 for the bogus MIME version, could you please check and then we can close this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working customization resources
Projects
Status: 🧐 Investigating
Development

No branches or pull requests

3 participants