Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"From" shows correctly on reply window but gets sent as the first account setup #6

Open
alex9099 opened this issue Jul 30, 2022 · 9 comments
Labels
bug Something isn't working

Comments

@alex9099
Copy link

When i receive an email on a catch all address it gets moved to the corresponding folder as it should, but when i try replying it shows the correct sender on the write/reply window but when sending it seems to use the first acount setup on thunderbird.

I have 6 accounts setup, most with the same display name. I'm guessing the problem may lay there?

I'm on thunderbird 91.11.0 - arch linux

CatchAllBird Version 1.0.6

@Jabb0
Copy link
Owner

Jabb0 commented Aug 1, 2022

Hello and thanks for the interest.

The selection of the identity is done by thunderbird itself. Once a fitting identity is present it will be selected.

As the from field is correct I assume this works. I wonder why it still uses the first account.

Can you provide me with (anonymized) schema of your setup and some identities?

EDIT: Please check (in the account settings) if the identity looks correct (most importantly the email is correct).

@alex9099
Copy link
Author

alex9099 commented Aug 4, 2022

Sorry for the delay, here it goes

image
It gets put on the right folder ^

image
When i reply it shows the right email to reply preselected ^

image
Then it arrives like this ^

image
The headers show this

On account settings it seems ok, email is geral@mydomain, both accounts have the same "Your name" though, but smtp server and email address are different, as expected

Altough, now that i'm trying again, it seems like this may be a thunderbird issue, if i manually set the sender field it gives the same result

edit: oh... it seems like it's using the default SMTP server, which is set to be gmail, thus this error. Maybe the addon should that that into consideration and set the smtp server to be the same as the main identity?

@Jabb0
Copy link
Owner

Jabb0 commented Aug 4, 2022

Thanks for the detailed information.

I think you found quite a major bug, when using multiple accounts.
It seems like during identity creation the mail server of the new identity is set incorrectly.
Really interesting that this did not cause issues for me.

@Jabb0
Copy link
Owner

Jabb0 commented Aug 4, 2022

So here's the thing:

The way the AddOn can create identities does not allow to specify the per-identity SMTP server. So even tho the identity is copied from the main identity of the email account, the default SMTP server is used for the new identity (why so ever).
And thunderbird does not use the default SMTP server per account but the one for the whole installation. Although there is a distinct SMTP server setting per account...
Therefore, if one has multiple email accounts and the catch-all is not the default one, all identities have the wrong SMTP server. This is pretty bad and a API design issue on thunderbirds end (if you ask me).

Actually in my case I have the issue too. But my default mail server seems not to care and sends out the email anyways ^^
I did not notice this because the UI just says "Default SMTP" server and I would never have guessed that this is not per account as there is a per-account default one.

I will have a look how this can be mitigated. Unfortunately, it is not even possible to access the settings to perform some kind of sanity check.

@Jabb0
Copy link
Owner

Jabb0 commented Aug 4, 2022

Alright.

So for now it's a fact that - caused by the limitations of the thunderbird API - the AddOn only works with a single catch-all address. And this SMTP server needs to be the default one set in thunderbird.

Good news: The existing identities are fine, because they point to "default". One just needs to change the default in thunderbird settings.

Thus, the mitigation is to
Account-Settings -> Outgoing Server (SMTP) -> Your SMTP Server -> Set Default

I see three ways to resolve this:

  1. Change the default smtp server as described above. I will add a prompt to the AddOn that informs of this fact if a user has more than one email Account. With this solution only a single catch-all address should be possible.
  2. Ask the thunderbird developers to either allow setting the SMTP server via an AddOn or fix the default to the account default one.
  3. Use the "experiment" APIs of thunderbird AddOns. This is more complex and nothing I can pursue at this time.

Thank you really much for the report. And sorry for the inconvenience.

EDIT: Because credentials are stored in the SMTP server config I assume that only a single catch-all address will work.

@Jabb0
Copy link
Owner

Jabb0 commented Aug 5, 2022

Hi @alex9099
I have created a new version of the AddOn that informs about the fact and advises to set the default SMTP server to the one of the catch-all address.

This is only a workaround and for full functionality way 2 and 3 from my last comment are relevant.

Well, who would have guessed that the creation is different from the one via the UI, and has such default values.

It is important for me to inform about this :) Hopefully it became clear.

@alex9099
Copy link
Author

alex9099 commented Aug 5, 2022

Thanks a lot! In my case i have the provider for my personal domains be mailbox.org (which uses the same server/credentials for all my domains, all on the same thunderbird account) so it's not much of a problem.

For me the workaround of setting the default smtp server works, but hopefully thunderbird will make the API to set the smtp server on identities sooner than later :)

Again, thanks a lot for this addon, saves a lot of time when handling a catch-all mailbox 👍

As the underlying issue is there, I think this should be kept open

@Jabb0
Copy link
Owner

Jabb0 commented Aug 7, 2022

Thanks for the feedback!

It's good to know that some provider use the same server/credentials.

Agreed, this issue should be kept open.

@Jabb0
Copy link
Owner

Jabb0 commented Dec 23, 2022

Hey,

the Mozilla feature request I wrote did not get solved.
Maybe it should be written as a bug?

Link is here

Therefore, this is not solvable yet 😢

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants