關於此附加元件
At the moment Mail Redirect is not yet compatible with Thunderbird 78.*. I'm still working on a new version that works with Thunderbird 78.*. If you depend on this functionality, please don't upgrade to Thunderbird 78, but stay on version 68 and disable updates, until a compatible version of Mail Redirect is released.
The Mailredirect extension for Mozilla Thunderbird and Mozilla SeaMonkey adds the ability to redirect one or more email messages to one or more recipients.
The feature of email redirecting is also known as remailing or resending.
The extension is an answer for bug 12916
Not all email providers support redirection of messages. Most notably Microsoft does not support it at the moment, probably as a measure against SPAM. I think they do this in error, and also reported this to Microsoft, but unfortunately they haven't changed their policy yet.
If you run into issues with an email provider not supporting redirection of messages, please contact them and see if you can make them change their policy. You can point them to this add-on, bug 12916, or RFC2822 section 3.6.6.
As a workaround you can also redirect your messages through another email provider, e.g. Gmail, but this isn't always desirable, because then that email provider gains access to the messages you redirect, and those messages might contain sensitive information.
The Mailredirect extension for Mozilla Thunderbird and Mozilla SeaMonkey adds the ability to redirect one or more email messages to one or more recipients.
The feature of email redirecting is also known as remailing or resending.
The extension is an answer for bug 12916
Not all email providers support redirection of messages. Most notably Microsoft does not support it at the moment, probably as a measure against SPAM. I think they do this in error, and also reported this to Microsoft, but unfortunately they haven't changed their policy yet.
If you run into issues with an email provider not supporting redirection of messages, please contact them and see if you can make them change their policy. You can point them to this add-on, bug 12916, or RFC2822 section 3.6.6.
As a workaround you can also redirect your messages through another email provider, e.g. Gmail, but this isn't always desirable, because then that email provider gains access to the messages you redirect, and those messages might contain sensitive information.