canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,628
edits
No edit summary |
No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 4: | Line 4: | ||
|Feature health=OK | |Feature health=OK | ||
|Feature status note=up for grabs | |Feature status note=up for grabs | ||
}} | }} | ||
{{FeatureTeam | {{FeatureTeam | ||
| Line 17: | Line 15: | ||
This allows the user to continue working with email, whilst still sending the email. | This allows the user to continue working with email, whilst still sending the email. | ||
If there is an error whilst sending the email, then Thunderbird can decide what to do, whether to try again later, or notify the user, or a mixture of both. | |||
One area we have to be careful with is shutdown - if Thunderbird is in the process of sending an email, we shouldn't abort that - but allow it to be finished (whilst also informing the user). Additionally, if emails are waiting to be sent, we should potentially alert about those as well. | |||
|Feature requirements=* Save email locally | |||
* Send email in the background without interrupting user | |||
* Attempt to re-send email without user interaction if the send fails | |||
* Gracefully handle persistent failures | |||
|Feature implementation plan=At its heart, this feature uses the send later functionality to operate. When enabled, emails are saved in the Outbox (in Local Folders) without the "Queued" flag set on them. nsMsgSendLater then detects the presence of the email and sends it in the background, with status reporting to the activity manager. | |||
Currently the basic implementation works, but error and edge cases aren't correctly handled. For testing purposes mailnews.sendInBackground can be set to true. | |||
{{Bug|511079}} is the tracking bug with dependencies showing the current issues. | |||
|Feature qa review=[[Thunderbird/TestPlans/SendInBackground]] | |||
}} | }} | ||
{{FeatureInfo | {{FeatureInfo | ||