X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/f2c4939f3869e2678577b4274519702b5cea203c..decb7051f6436aedfd0e9de934d149d9c5b22b36:/doc/todo/passwordauth:_sendmail_interface.mdwn

diff --git a/doc/todo/passwordauth:_sendmail_interface.mdwn b/doc/todo/passwordauth:_sendmail_interface.mdwn
index 37a1bd981..556240964 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,13 +24,38 @@ 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.
 > 
 > I don't much like the idea of supporting a lot of different email sending
-> modules.
-> 
+> modules.  --[[Joey]]
+
+OK, so I'll have a look at replacing all email handling with *Email::Send*.
+
+[[!tag patch]]
+*<http://schwinge.homeip.net/~thomas/tmp/ikiwiki-sendmail.patch>*
+
+Remaining TODOs:
+
+  * Resolve TODOs as denoted inside the patch.
+  * Is it worthwhile to use and depend on [[!cpan Return::Value]]
+    just for this bit of functionality?
+  * Debian news file.
+  * ikiwiki news file.
+
+--[[tschwinge]]
+
+
 > BTW, I think you recently sent a patch improving mail logging, but I've
 > 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]]