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

Smtp sending tracking issue #14

Open
7 of 11 tasks
MTRNord opened this issue May 30, 2022 · 0 comments
Open
7 of 11 tasks

Smtp sending tracking issue #14

MTRNord opened this issue May 30, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@MTRNord
Copy link
Collaborator

MTRNord commented May 30, 2022

Known todos:

  • Smtp sending should try tls #12
  • Smtp sending doesn't exit if we get an error on the rcpt to commsnd #13
  • Make sure we don't crash the job if only one of the servers didn't like our email.
  • dmarc (This is more something for the web interface to generate. I added it to my test setup now)
  • spf (This is more something for the web interface to generate. I added it to my test setup now)
  • dkim (we dont verify it at this stage)
  • Use STARTTLS when sending
  • dane
  • arc
  • Notify the user about the messages' status, similar to how postfix does
  • Fix parser: Failed to parse fetch arguments: "Parsing Error: VerboseError { errors: [(\" RFC822.HEADER FLAGS)\", Char(')')), (\"(UID RFC822.SIZE RFC822.HEADER FLAGS)\", Context(\"fetch_arguments\"))] }" request was (UID RFC822.SIZE RFC822.HEADER FLAGS) (Turns out we got deprecated requests)

And likely more...

@MTRNord MTRNord changed the title Stmp sending tracking issue Smtp sending tracking issue May 30, 2022
@MTRNord MTRNord added the enhancement New feature or request label May 30, 2022
@MTRNord MTRNord pinned this issue Jun 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant