One word - spam. I'm pretty sure these limitations are carefully designed by Google to prevent spammers using appengine. This is another yet thing that spammers have spoiled - I only hope karma exists, so these b******s, their children and grandchildren live in misery for ever more.
On Nov 7, 2:20 am, voscausa <robert....@gmail.com> wrote: > In Gmail you can forward messages with a filter. The receiver of this > relayed messages does not see any difference. The sender is the > original sender. In the “delivered-to” field of the message header > you can find the relay mail address. > > I tried to build the same functionality with GAE. Relaying messages in > my apps domain based on the address of the sender. So when clients > send mail to: contac...@mydomain.com , the clients mail is relayed to > his personal account manager. > > But GAE does not let you not relay messages: “Unauthorized sender” > When you send mail, you are not allowed to use the original sender > (any name) as the relay sender. You have to use an address you own for > the relay sender. > > Why is that? Gmail allows it and even with apps script you can specify > any name of the sender. Is this a spam measure? App engine should > have a relaying protocol. Gmail uses a collection of forwarding > addresses for this purpose. > > I also tried to send mail with the python smtplib. It works with the > SDK, but is not allowed when you publish the script. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
