You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FileTransport API seems a little bit inflexible as you can't change the file name. Even if you specify the message id, like lettre::Message::builder().message_id(Some(String::from("my-customized-id")))..., the .eml file name is still a UUID.
Is it expected behaviour that specifying the message id does not change the .eml file name? If not expected, I'm happy to open an issue with reproducible code example.
As a default UUID is fine, but concerning flexibility and usability, the possibility of a user-defined file name would be great.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
FileTransport
API seems a little bit inflexible as you can't change the file name. Even if you specify the message id, likelettre::Message::builder().message_id(Some(String::from("my-customized-id")))...
, the .eml file name is still a UUID.Is it expected behaviour that specifying the message id does not change the .eml file name? If not expected, I'm happy to open an issue with reproducible code example.
As a default UUID is fine, but concerning flexibility and usability, the possibility of a user-defined file name would be great.
Beta Was this translation helpful? Give feedback.
All reactions