On 14/07/2011 22:42, simon haywood wrote:
The site populates the writetothem forms - which is something we believed we were specifically prohibited from doing.
Prepopulating the message body would be against our terms of use, yes, as you say. That site does not do that, but provides guidance on what to write in your message instead.
Perhaps one day we will be able to integrate that code (or similar) in order to allow people to set up their own guidance-based campaigns on WriteToThem more easily.
Yes. Absolutely. That is one of the reasons why I planned to use an SMTP relay service (to which I would authenticate) - and have the MTA (Postfix, for example) handle all that. So we're back to my original question.
As has already been said, you can't really put someone else's address as your SMTP envelope, as then it could fail for e.g. any sender with an SPF record and a recipient that checks SPF ( http://en.wikipedia.org/wiki/Sender_Policy_Framework ) - you would be seen as forging messages. So assuming you have your own domain as the envelope (this is independent of what you have as the From: or Reply-To: email headers), you will have to deal with any bounces that occur - your MTA will get them, but it won't do anything with them. You would have to write code to e.g. stop the recipient address being used for a period of time (or just disable it until manually checked/changed), and/or to let the user know their message has not actually been sent.
ATB, Matthew _______________________________________________ developers-public mailing list [email protected] https://secure.mysociety.org/admin/lists/mailman/listinfo/developers-public Unsubscribe: https://secure.mysociety.org/admin/lists/mailman/options/developers-public/archive%40mail-archive.com
