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

To Ack or To Nack, that is the question #34

Closed
GoogleCodeExporter opened this issue Jun 4, 2015 · 5 comments
Closed

To Ack or To Nack, that is the question #34

GoogleCodeExporter opened this issue Jun 4, 2015 · 5 comments

Comments

@GoogleCodeExporter
Copy link

Generating message bounces presents some issues, including getting into 
infinite loops. 

The proposal is to instead do ACKs, using a cleaned up variation of MDN - RFC 
2298. 

Arien has thought through the details of MDN for the REST impl during the 
bakeoff. We should leverage that work and update the Agent Spec.

Original issue reported on code.google.com by umes...@microsoft.com on 24 Aug 2010 at 6:18

@GoogleCodeExporter
Copy link
Author

Original comment by umes...@microsoft.com on 24 Aug 2010 at 6:18

  • Added labels: Type-Enhancement
  • Removed labels: Type-Defect

@GoogleCodeExporter
Copy link
Author

Original comment by umes...@microsoft.com on 24 Aug 2010 at 6:19

  • Added labels: Priority-Critical
  • Removed labels: Priority-Medium

@GoogleCodeExporter
Copy link
Author

ACK using MDN.

Original comment by arien.ma...@gmail.com on 25 Aug 2010 at 9:49

@GoogleCodeExporter
Copy link
Author

This has now been implemented in the C# SMTP Gateway.
There is also a usable OM in nhinCommon

Original comment by umes...@microsoft.com on 7 Sep 2010 at 4:25

@GoogleCodeExporter
Copy link
Author

Sean - docs :-)

Original comment by umes...@microsoft.com on 7 Sep 2010 at 4:26

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant