Wt

The e-mail verification is enabled by default in the example already. I just tested it and it should at least work with the master branch.

Also, the e-mail sent will be logged. You will have to copy-paste the URL in the log, replacing =3D with =.

You can specify the server to connect to to send the e-mail with the smtp-host and smtp-port properties. See the documentation about properties in the library overview.

Yes, my bad, I played with it before checking the code and sending the report, you are right, mail verification is required by default in the example.

And it still does not work. As I test it, I use a localhost Postfix server, and use a local address (xxx@localhost), then check the mail with mailx and copy the link to my browser. I had no need to configure any SMTP server in my situation.

But your comment showed me the source of the problem :

""\"

(...)

Please click here to confirm your registration or copy and paste the

following URL into your browser: (Note: be sure to copy the entire

URL, including any part of it which goes onto a second line.)

http://localhost:9090/?_=3D/auth/mail/fv0wBQdAfFNkEH68BnDmCV5LCECapTib

(...)

""\"

I did not notice the "3D", even in the raw text part of the mail. Which is an error, but certainly does not show to most users, who click directly on a link from the HTML-formatted version of the mail.

So the bug is real and you should fix it, but not a real problem.

Thanks for your help!

The "3D" you see in the logs after a "=" and when you look at the mails in the raw format are escape characters resulting from the usage of the "quoted-printable" encoding. When you look at the mail using a mail client, you should not see any of these escape characters and it should just work.

Note that newlines are escaped as well. So if you see a link that ends with a "=" on a line, and continues on the next line you should copy everything, including the next line, and remove the "=".

E.g.:

http://127.0.0.1:8000/?_=3D/auth/mail/iWDNRqhlAphRJLcMKCJnjHKE11Z=

iVbiv

becomes

http://127.0.0.1:8000/?_=/auth/mail/iWDNRqhlAphRJLcMKCJnjHKE11ZiVbiv

I hope this helps.

Yes, but precisely... Is mime encoding in the final "pure text" part of the mail appropriate? I think not. The pure text is not supposed to generate clickable links, it is supposed to be read, copied(-pasted), precisely "as is", and nothing else.

Anyway, I consider virtually no one reads the mails in their text form, so...

And yes, you helped!