[google-appengine] Re: Really frustrated by Google's inaction on fixing certain e-mail bugs for years
Sorry if this seems callous, but IMHO the send email api is a waste of precious developer resources. How many Googlers are currently working on it? -- 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-appengine@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.
[google-appengine] Re: Really frustrated by Google's inaction on fixing certain e-mail bugs for years
On Friday, March 16, 2012 11:14:30 AM UTC+3, PK wrote: Issue 2383 http://code.google.com/p/googleappengine/issues/detail?id=2383 Filed on *Nov 11 2009* 8bit Mail encoding Let me point out the two important aspects of this (correct me if I wrong): 1. Emails in pretty valid 8bit encoding are silently ignored (users are not notified about errors) 2. This is marked as a Feature -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/IQxs2L5dzucJ. To post to this group, send email to google-appengine@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.
[google-appengine] Re: Really frustrated by Google's inaction on fixing certain e-mail bugs for years
I really do not understand why Brandon insists on this one, he is really not helping us to raise the visibility of this with Google. What are these unsubstantiated theories that Google does not decode 8bit encoded MIME messages for security reasons. I have a really simple feature here---part of a much bigger service. It receives e-mails, decodes them, processes them, encodes them again and forwards them. Pretty cool!! For most e-mails it works and I have many happy users. For some encodings (like 8bit) it does not and raises an exception and for those users I cannot provide the service and then they go to my customer and compain. Like it or not there are e-mail clients out there to this day that generate e-mail message with such encodings. As I point in the bug, and the reason that triggered this message, I just found an e-mail like that yesterday night from a CS Professor at Stanford. I cannot control what e-mail clients my users use and I should not Thanks for reading, PK On Friday, March 16, 2012 3:12:35 AM UTC-7, anatoly techtonik wrote: On Friday, March 16, 2012 11:14:30 AM UTC+3, PK wrote: Issue 2383http://code.google.com/p/googleappengine/issues/detail?id=2383 Filed on *Nov 11 2009* 8bit Mail encoding Let me point out the two important aspects of this (correct me if I wrong): 1. Emails in pretty valid 8bit encoding are silently ignored (users are not notified about errors) 2. This is marked as a Feature -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/0ec_0sSZc58J. To post to this group, send email to google-appengine@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.
RE: [google-appengine] Re: Really frustrated by Google's inaction on fixing certain e-mail bugs for years
What are these unsubstantiated theories that Google does not decode 8bit encoded MIME messages for security reasons. Strong Typing (and Encoding) are pretty core to python. Accepting all codings is actually not common in most functions. This may not seem like a security thing, but it is certainly a Testing overhead, and a potential outputs issue (plus all the dependencies then have to support the encoding as well. There are a number of things that Python errors horribly if there is a non-standard or unexpected encoding on a character. It's a pain in the ass, but it is the way of the world. -- 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-appengine@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.
