Open
Bug 1252079
Opened 10 years ago
Updated 3 years ago
Cannot send message From custom from when there is no valid email address in account settings.
Categories
(Thunderbird :: Message Compose Window, defect)
Tracking
(Not tracked)
NEW
People
(Reporter: abbGZcvu_bugzilla.mozilla.org, Unassigned)
References
Details
Attachments
(1 file)
|
6.85 KB,
image/png
|
Details |
I have a domain that I control and for which I use many different email addresses. I've created one account for this domain and I am trying to use the new "arbitrary From:" field feature in order to send emails from the various email addresses. See bug 87987 for details on this new feature.
Since there is not one main email address for this account, I have not set an email address in the account settings. This also prevents me from accidentally sending an email without providing the right "from:" address.
However, if I attempt to respond to an email, type an address in the "from:" field and send the email, I get an error that the return mail address is invalid (Screenshot attached). It is asking me to set an email address in my account settings. As I've explained, I don't want to do that and it should not be necessary: the from: address should be used as the return address.
Note: this is not limited to responding to emails: composing a new email has the same issue.
Note: when I modify my account settings to have the email address <account-setings@mydomain.com> and send an email from <from@mydomain.com>, the email will have the following headers:
Return-Path: <account-settings@mydomain.com>
From: <from@mydomain.com>
To fix this issue, if no email address is provided in the account settings, the Return-Path should also be set to the from: field (<from@mydomain.com>) and no error should be shown.
Updated•10 years ago
|
Summary: Cannot send message when there is no valid email address in account settings. → Cannot send message From custom from when there is no valid email address in account settings.
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•