Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Rietveld does not fill the In-Reply-To and References not filled in correctly #296

Open
GoogleCodeExporter opened this issue Mar 28, 2015 · 13 comments
Open

Rietveld does not fill the In-Reply-To and References not filled in correctly #296

GoogleCodeExporter opened this issue Mar 28, 2015 · 13 comments
Labels
auto-migrated Component-Server Priority-High Type-Defect

Comments

@GoogleCodeExporter
Copy link 

What steps will reproduce the problem?
1. Send mail
2. Send review mail

What is the expected output? What do you see instead?
The expected output is correct threading of the responses in normal email 
systems. Since rietveld does not fill in the In-Reply-To and References fields, 
many mail systems have problems threading the responses correctly.

Please see http://www.ietf.org/rfc/rfc2822.txt 3.6.4

Original issue reported on code.google.com by kli...@google.com on 26 Apr 2011 at 5:56
@GoogleCodeExporter
Copy link
Author 

Ping? This is very important to us, as we want to use rietveld on an open 
source project, and this bug prevents the open-source archiving to work 
correctly, which prevents us from using rietveld.

Original comment by kli...@google.com on 16 May 2011 at 6:18

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author 

The correct link is http://tools.ietf.org/html/rfc5322#section-3.6.4 because 
2822 is obsolete.

Original comment by techtonik@gmail.com on 16 May 2011 at 9:01

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author 

I can't find how to set custom message headers 
http://code.google.com/appengine/docs/python/mail/emailmessagefields.html

Original comment by techtonik@gmail.com on 16 May 2011 at 9:17

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author 

I've tracked it down to 
http://code.google.com/p/googleappengine/issues/detail?id=2802

Original comment by techtonik@gmail.com on 16 May 2011 at 9:21

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author 

Updated the referenced appengine bug...

Original comment by kli...@google.com on 16 May 2011 at 9:28

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author 

Increase community awareness 
https://groups.google.com/forum/#!topic/google-appengine/xSm5i2xc4lw

Original comment by techtonik@gmail.com on 17 May 2011 at 6:47

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author 

Increasing priority. When the mails in an inbox are not threaded it's not easy 
to follow the review progress. However we still rely on App Engine issue 2802 
to be fixed to implement correct mail headers here.

Original comment by albrecht.andi on 19 May 2011 at 6:40

  • Changed state: Accepted
  • Added labels: Priority-High
  • Removed labels: Priority-Medium

@GoogleCodeExporter
Copy link
Author 

AppEngine issue 2802 is fixed in SDK 1.5.2

Original comment by techtonik@gmail.com on 21 Jul 2011 at 8:29

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author 

Issue 300 has been merged into this issue.

Original comment by albrecht.andi on 13 Aug 2011 at 7:28

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Original comment by albrecht.andi on 6 Apr 2012 at 6:31

  • Added labels: Component-Server
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author 

The relevant upstream bug is 
https://code.google.com/p/googleappengine/issues/detail?id=6425

Original comment by maruel@chromium.org on 16 Oct 2013 at 4:45

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author 

Issue 465 has been merged into this issue.

Original comment by maruel@chromium.org on 16 Oct 2013 at 4:48

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author 

Does status accepted mean this is no longer an issue? I'm using Rietveld 
directly with Google Apps, and it isn't sending emails with In-Reply-To set. 
The POST to /publish shows a value for in_reply_to in the form data, but the 
emails don't have In-Reply-To in the headers. Thanks for any insight/tips.

Original comment by skor...@gmail.com on 19 Dec 2013 at 7:11

  • Added labels: ****
  • Removed labels: ****

This was referenced Mar 28, 2015
Closed
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Component-Server Priority-High Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter