Questions about queued reports and failed sending

[GoogleCodeExporter]

This is more a behavioural question than a real 'issue' (it can always change 
if it turns out to be a bug).

What is the intended behaviour regarding the sending of unsent reports? Will 
reports only be stored when selecting the 'send later' option (this of course 
implies the SEND_QUEUED_REPORTS option)? 

I'm asking because of the following: 
- Say you have a 64-bit application
- Say you have 32-bit Outlook
- Now also assume you send first via SMTP and then via SMAPI and that SMTP has 
failed (for whatever reason)
Now SMAPI *will* also fail since you have a 64-bit 'client' and 32-bit Outlook. 
The 'problem' is now that you are not reminded about this unsent report. 

So
- Is this intended/expected? 
- Are reports only supposed be stored/queued when you select the 'send later' 
option, or also when it failed?

Original issue reported on code.google.com by cron...@gmail.com on 20 Nov 2012 at 8:28

[GoogleCodeExporter]

I think this behavior is by design. There are two situations:

1. Queue is disabled. If report can't be sent, it is just removed. A popup 
dialog appears notifying the user if error report delivery fails. In case of 
SMAPI, there is no way to detect if the message was actually delivered or not. 

2. Queue is enabled. If report delivery fails, it is stored for postponed 
delivery. 

Please let me know if this is clear.

Original comment by zexspect...@gmail.com on 20 Nov 2012 at 3:05

• Changed state: Reviewed

[GoogleCodeExporter]

OK, so just so we're clear:

1. I have checked, CR_INST_SEND_QUEUED_REPORTS is specified (I get reminded 
when I click the 'send later' button)
2. All successful sends are removed from the queue

It seems however that when sending via SMAPI and it fails, the queue is also 
cleared. I'll do some more debugging and log the results here.

Original comment by cron...@gmail.com on 21 Nov 2012 at 5:06

[GoogleCodeExporter]

OK, no bug. User expectation problem. User interpreted 'never remind' as 'never 
remind for THIS report'.

Original comment by cron...@gmail.com on 21 Nov 2012 at 8:34

[GoogleCodeExporter]

Closing the issue.

Original comment by zexspect...@gmail.com on 21 Nov 2012 at 8:46

• Changed state: Invalid