Open btlogy opened 1 year ago
Only one concerns: Message-ID: <63ee35fe.ca0a0220.921b6.38d5SMTPIN_ADDED_MISSING@mx.google.com> ? Adding a message id is quite simple at least when using Python
Only one concerns: Message-ID: <63ee35fe.ca0a0220.921b6.38d5SMTPIN_ADDED_MISSING@mx.google.com> ?
Message-ID: <63ee35fe.ca0a0220.921b6.38d5SMTPIN_ADDED_MISSING@mx.google.com>
Adding a message id is quite simple at least when using Python
Originally posted by @btlogy and @wuan in https://github.com/LeastAuthority/mw-projects/issues/83#issuecomment-1433134200 and https://github.com/LeastAuthority/mw-projects/issues/83#issuecomment-1433150031
This being said, it is not (yet) required, and maybe we should focus on using our own MTA to route those emails (which should add the Message-ID).
Originally posted by @btlogy and @wuan in https://github.com/LeastAuthority/mw-projects/issues/83#issuecomment-1433134200 and https://github.com/LeastAuthority/mw-projects/issues/83#issuecomment-1433150031
This being said, it is not (yet) required, and maybe we should focus on using our own MTA to route those emails (which should add the Message-ID).