X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/d1f88ee75bc70956716669ca68653c29439d6661..651cdd4b2a85f4e5f9d298a7eea7d0e6d94442b1:/doc/todo/passwordauth:_sendmail_interface.mdwn?ds=inline diff --git a/doc/todo/passwordauth:_sendmail_interface.mdwn b/doc/todo/passwordauth:_sendmail_interface.mdwn index 4714a7a09..a640d6516 100644 --- a/doc/todo/passwordauth:_sendmail_interface.mdwn +++ b/doc/todo/passwordauth:_sendmail_interface.mdwn @@ -1,4 +1,4 @@ -[[tag wishlist]] +[[!tag wishlist plugins/passwordauth]] For sending out password reminder emails, the [[plugins/passwordauth]] plugin currently uses the *[Mail::Sendmail](http://search.cpan.org/perldoc?Mail::Sendmail)* module. @@ -24,7 +24,7 @@ in the ikiwiki source code, where emailing is done. --[[tschwinge]] -> One that is in Debian is [[cpan Email::Send]], which can do SMTP and +> One that is in Debian is [[!cpan Email::Send]], which can do SMTP and > sendmail and some other methods and falls back through methods until one > succeeds. I haven't tried to use it but it looks like a feasable > candidate. @@ -34,17 +34,20 @@ in the ikiwiki source code, where emailing is done. OK, so I'll have a look at replacing all email handling with *Email::Send*. -[[tag patch]] -** +[[!tag patch]] +** Remaining TODOs: * Resolve TODOs as denoted inside the patch. - * Is it worthwhile to use and depend on [[cpan Return::Value]] + * Update for the last years of ikiwiki development, such as adapting the + [[plugins/notifyemail]] plugin. + * Is this + [[UTF-8-safe|bugs/password_reset_fails_with___34__Wide_character_in_subroutine_entry__34__]]? + * Is it worthwhile to use and depend on [[!cpan Return::Value]] just for this bit of functionality? * Debian news file. * ikiwiki news file. - * Are commit emails still working? --[[tschwinge]] @@ -53,3 +56,10 @@ Remaining TODOs: > lost it. --[[Joey]] Resent. --[[tschwinge]] + +> Debian now has Mail::Sender, Mail::SendEasy, and Email::Sender +> (which, according to its dpkg description, "replaces the old and sometimes +> problematic Email::Send library, which did a decent job at handling very +> simple email sending tasks, but was not suitable for serious use, for a +> variety of reasons"). Are any of those any better? It's unfortunate that +> there doesn't seem to be a clear "best practice"... --[[smcv]]