Re: Cumulative comments.py 1.3.0 patch that includes utf8 fix

<quote who="will guaraldi" date="Tue, Nov 21, 2006 at 10:25:33AM -0600">
> On Mon, 20 Nov 2006, Michael Olson wrote:
> >
> > Before I forget to mention this again: comments are still managing to 
> > slip through without an email notification being sent, even after 
> > applying my version of this patch.  I haven't yet figured out why.  I 
> > might try out the svn version of comments.py sometime soon to see if 
> > it's fixed there.
> 
> I checked my pyblosxom.log and noticed that comments that have a malformed 
> email address don't get through.

Right! I configured it so all comments come from a fixed address instead
of having to appear to some the address that was listed on the form.
Even if the address is well formed, mailers may do a reverse lookup and,
if it fails, not send it. I think it makes more sense to have the mail
come from a constant address and then list the from address in the
content of hte email.

Regards,
Mako


-- 
Benjamin Mako Hill
[email protected]
http://mako.cc/

Creativity can be a social contribution, but only in so
far as society is free to use the results. --RMS

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

_______________________________________________
pyblosxom-users mailing list
pyblosxom-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/pyblosxom-users

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)

iD8DBQFFZI99ic1LIWB1WeYRArHgAJ9Jx2uJojf3EL7Sfe4d/NEAHrKCvACfR/nZ
SJvmOw3vfilmGT4oxa9RY7s=
=mCAL
-----END PGP SIGNATURE-----