Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Urbain YANG
@urbainy
It seems that you are right, after I simplified the code by delete all the code of lettre, the issue is still there. That's why I ask that issue in the warp channel.
Urbain YANG
@urbainy
How to compose an email with html body?
It seems that I have found the answer from the example folder from the repo, sorry for disturbing!
Mathijs van Veluw
@BlackDex
Hello people
I have a question regarding tracing.
It doesn't seem to work anymore since beta.1
Alpha.5 is ok
Mathijs van Veluw
@BlackDex
hmm, seems to be some strange combi with other libararies
Mathijs van Veluw
@BlackDex
Seems that after a cargo update i lost tracing-futures
that is the only difference i can see
Mathijs van Veluw
@BlackDex
Seems that having the latest reqwest together with letter is causing the issue
h2 is updated from 0.2.7 too 0.3.0
And that removes tracing-futures
Paolo Barbolini
@paolobarbolini
Interesting issue @BlackDex. I'll try testing it on my end. Just to double check, is tracing working for the rest of the crates? Usually hyper prints a lot of stuff with RUST_LOG in debug mode
Mathijs van Veluw
@BlackDex
@paolobarbolini, i have to check, that is a good one
I created a SMTP_DEBUG option which toggles specifically the debug log level for lettre only.
and we put hyper::server on Warn always, since it causes to much logging indeed
lets see if i disable those overrideds and set debug on by default for all
Mathijs van Veluw
@BlackDex
@paolobarbolini, for the other crates it looks like i get the same output regarding the version of reqwest.
Paolo Barbolini
@paolobarbolini
Does it get back to working again if you import tracing-futures in your project?
Mathijs van Veluw
@BlackDex
nope, tried that
i'm now tracing all the commits to Cargo.toml on our side and see where it failed, and which other deps are changed.
Mathijs van Veluw
@BlackDex
could it be tokio
Paolo Barbolini
@paolobarbolini
I think the major difference between tokio 0.2 and 1 in regards to tracing is that they put it behind --cfg tokio_unstable https://github.com/tokio-rs/tokio/blob/73848139790b07a084fa3c84d334f8fabe38de04/tokio/Cargo.toml#L103
Mathijs van Veluw
@BlackDex
but, that would mean that somehow when compiling, lettre doesn't get the correct versions, or it's missing a dep
i just build the latest master, no tracing, if i force reqwest to be =0.10.10 it does work.
Paolo Barbolini
@paolobarbolini
It could be that hyper 0.13 enabled the log feature of tracing, while 0.14 doesn't anymore
Mathijs van Veluw
@BlackDex
indeed!
image.png
they removed log from tracing
Mathijs van Veluw
@BlackDex
Created a PR: lettre/lettre#584
That fixed the issue :)
Thanks for the support
Jason Tsorlinis
@jtsorlinis
Hey guys I'm getting this error randomly when bulk sending emails with 0.10.0-beta.3
Error: lettre::transport::smtp::Error { kind: Transient(Code { severity: TransientNegativeCompletion, category: Connections, detail: One }) }
When sending 500 emails I will randomly get this error on 20-30 of them
Is it possible I'm just sending emails too fast for the smtp server to handle?
Alexis Mousset
@amousset:matrix.org
[m]
@jtsorlinis: 421 could be rate limiting indeed, enabling logging with tracing could help troubleshoot the problem by displaying the complete server response
尼亚
@ch3ck
Hey Guys, I"m trying to parse binary data in my emails, but while using mailparse weird characters are not decoded properly
Any pointers with letter?
Alexis Mousset
@amousset:matrix.org
[m]
Hi, lettre does not parse email (for now) so it won't help you with this
尼亚
@ch3ck
Thanks
Alexis Mousset
@amousset:matrix.org
[m]
You can have a look at https://crates.io/crates/email which also parses emails
vidyli
@vidyli

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

image.png
please help.
you the mailhog received a request
in the bove picture
but lettre give the error above.
paolobarbolini
@paolobarbolini:matrix.org
[m]
I replied on the issue