=0.10.10 it does work.
I got an very geric error
error = lettre::transport::smtp::Error {
kind: Client,
source: Error(
None,
),
}&client = SmtpClient {
info: SmtpInfo {
hello_name: Domain(
"vidys-MacBook-Pro.local",
),
server: "localhost",
port: 1025,
tls: Wrapper,
authentication: [
Plain,
Login,
],
credentials: Some(
Credentials,
),
timeout: Some(
60s,
),
},
}mailhog is listened at 1025
smtp (duh), but it actually just seems to be a very old version of lettre. Could you maybe add a note to the crates.io page pointing potential users to lettre?
🤔 my Matrix client didn't get the notification, fortunately Gitter notifies you by email every once in a while.
I think this is a good idea xiretza , I just searched "SMTP" on crates.io and lettre is on the second page Alexis Mousset. We should probably do a new release of the SMTP crate with both the description and readme telling to use lettre instead
% dig lettre.rs
; <<>> DiG 9.16.16 <<>> lettre.rs
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 28190
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;lettre.rs. IN A
;; Query time: 185 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Thu Sep 30 07:14:19 EDT 2021
;; MSG SIZE rcvd: 38
4 replies
In that case adding DKIM could be something useful. But other than that, it should be something done by the sending-server
I disagree that DKIM should always be done by the sending-server. Right now getting a "clean" IP is very hard and it is very useful to pay someone for a trusted IP (and maybe some other sending features). However I would rather not trust them to be able to sign messages on be behalf.
For my currently use case I plan on migrating to signing in my app then sending to a relay mostly for their trusted IP.
Eventually I do plan on migrating to direct-sending but I don't have enough domain reputation or a trusted enough IP yet.