Closed vobornik closed 1 year ago
@vobornik it seems you were using the system with a non-compliant client that didn't provide a message ID in the MIME message. Can you please let me know what client software was used in this case to find out if it is a valid use case?
Hi, I am not surprised... It was a MS Outlook, current version of M365 suite during the initial new IMAP account connect procedure. I needed to fake a SMTP server to pass the initial check (the Outlook does not allow to add an IMAP account without a valid SMTP check). I wanted to let you know that this happens. I personally do not need to correct this, workaround found.
It's also possible to reproduce mentioned issue using following command in powershell:
Send-MailMessage -From 'test <test@example.com>' -To 'test <test@example.com>' -Subject 'Subject' -Body "Mail body" -SmtpServer '127.0.0.1' -Port 1025
Well I ran into the same issue trying out the docker image. I needed this for testing and I cannot change the current implementation to add the MESSAGE_ID.
I did some further research and indeed not all clients provide a message id. Because of this I provided a change making the message id optional. Will be release soon with version 2.1.3
Hi, I wanted to use the fake-smtp-server for testing Outlook new IMAP account procedure (it unfortunately requires SMTP for new IMAP), and this happened: