- Is it OK if messages sent via WhisperBack don’t get an auto-reply
- Is it OK if messages sent via WhisperBack don’t get an auto-reply
email? - Can the last page of the WhisperBack report show the user a link to a web version of the auto-reply email?
email? - Can the last page of the WhisperBack report show the user a link to a web version of the auto-reply email?
(Perhaps, after submission, a part of the auto-reply can be shown, and a link to "latest hot topics and such")
(Perhaps, after submission, a part of the auto-reply can be shown, and a link to "latest hot topics and such")
- WhisperBack users should receive a non-changing version of the Auto-reply in the interface after (or before) sending a report, and also the auto-reply by mail if they add an email address. Because:
WhisperBack users should receive a non-changing version of the Auto-reply in the interface after (or before) sending a report, and also the auto-reply by mail if they add an email address. Because:
- People sometimes do not read the interface messages, but they read the email.
- People sometimes do not read the interface messages, but they read the email.
- The WhisperBack message can be localized, which the email will not be.
- The WhisperBack message can be localized, which the email will not be.
- The user may be using an old version of Tails, so the known issues should be consulted online.
- The user may be using an old version of Tails, so the known issues should be consulted online.
- Is it OK if every message, even if it’s not the beginning of a
- Is it OK if every message, even if it’s not the beginning of a
thread, gets an auto-reply email?
thread, gets an auto-reply email?
No, as we said in the reqs, 'Non-WhisperBack emails: Only the 1st email in a thread triggers the auto-reply. Otherwise it would be very noisy for the user and send mixed signals ("we need more info from you but we might not answer a second time").'
- No, as we said in the reqs, 'Non-WhisperBack emails: Only the 1st email in a thread triggers the auto-reply. Otherwise it would be very noisy for the user and send mixed signals ("we need more info from you but we might not answer a second time").'
- Can we track opening posts in email headers? Should we rely on the Re: in the subject line? - What about the "In-Reply-To" field:
- Can we track opening posts in email headers? Should we rely on the Re: in the subject line? - What about the "In-Reply-To" field
- we can rely on the fact that people writing an email to the help desk write to tails-support-private@ and receive a reply from tails-bugs@, so their second email will be to tails-bugs@
- we can rely on the fact that people writing an email to the help desk write to tails-support-private@ and receive a reply from tails-bugs@, so their second email will be to tails-bugs@
- We can also use mail headers:
- We can also use mail headers:
- Send the auto-reply only if the headers "In-Reply-To:" and 'References:' are empty or do not exist, then:
- Send the auto-reply only if the headers "In-Reply-To:" and 'References:' are empty or do not exist, then:
