Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Can sent from one account but not another with the same SMTP

  • 7 réponses
  • 1 a ce problème
  • 31 vues
  • Dernière réponse par Bill de Haan

more options

Hi all;

I'm running Thunderbird 78.6.0 (32-bit), Windows 10.

I have two accounts on a domain, call them [email protected] and [email protected]. This domain does not have an SMTP server.

I have a third account on a commercial service - Mailbox.org - call it [email protected].

In the Outgoing SMTP server section of Account Settings, I've set up the Mailbox.org SMTP as the server, with the [email protected] login settings.

Both account [email protected] and [email protected] have "Outgoing Server (SMTP)" pointing to that default "Mailbox.org (SMTP)"

When I send as [email protected], it sents without problem.

When I send as user [email protected], it sends without problem.

When I send as user [email protected], it fails with "<[email protected]> Sender address rejected".

The thing is, all three point to the same SMTP server, with the same SMTP credentials. I've deleted the password and reset it, with no difference.

For some reason, when using primary@domain, the SMTP server uses the stored [email protected] settings, as it should. But when using secondary@domain, somehow the SMTP server is ignoring those credentials. I don't see any configuration differences between primary and secondary.

In Thunderbird, account [email protected] has the outgoing SMTP server configured to use the [email protected] account's credentials. I can't see how primary and secondary are any different, other than one works, and the other doesn't.

I've duplicated the SMTP settings to an SMTP2 server, with the same result. The primary can always send, but the secondary cannot.

This is probably something simple, and some setting somewhere, but I can't find it.

Hi all; I'm running Thunderbird 78.6.0 (32-bit), Windows 10. I have two accounts on a domain, call them [email protected] and [email protected]. This domain does not have an SMTP server. I have a third account on a commercial service - Mailbox.org - call it [email protected]. In the Outgoing SMTP server section of Account Settings, I've set up the Mailbox.org SMTP as the server, with the [email protected] login settings. Both account [email protected] and [email protected] have "Outgoing Server (SMTP)" pointing to that default "Mailbox.org (SMTP)" When I send as [email protected], it sents without problem. When I send as user [email protected], it sends without problem. When I send as user [email protected], it fails with "<[email protected]> Sender address rejected". The thing is, all three point to the same SMTP server, with the same SMTP credentials. I've deleted the password and reset it, with no difference. For some reason, when using primary@domain, the SMTP server uses the stored [email protected] settings, as it should. But when using secondary@domain, somehow the SMTP server is ignoring those credentials. I don't see any configuration differences between primary and secondary. In Thunderbird, account [email protected] has the outgoing SMTP server configured to use the [email protected] account's credentials. I can't see how primary and secondary are any different, other than one works, and the other doesn't. I've duplicated the SMTP settings to an SMTP2 server, with the same result. The primary can always send, but the secondary cannot. This is probably something simple, and some setting somewhere, but I can't find it.

Solution choisie

Bill de Haan said

So I guess the question isn't really why the secondary worked, but how the primary email works in the first place?

That's a question for the Mailbox.org folks to answer. Thunderbird has zero influence over what is permitted or rejected on the provider's side.

Lire cette réponse dans son contexte 👍 0

Toutes les réponses (7)

more options

have you checked the settings in mailbox.org that you have registered [email protected] as a permitted sending email address. My guess is not so they are not allowing it.

more options

Matt said

have you checked the settings in mailbox.org that you have registered [email protected] as a permitted sending email address. My guess is not so they are not allowing it.

Hi Matt;

There are no settings in Mailbox.org to set. They don't allow any secondary domains. That's why it's configured in Thunderbird to log in as the [email protected] account when sending.

In Thunderbird, the settings log in to the SMTP Server section are:

Connection Security: SSL/TLS Authentication method: Normal Password User Name: [email protected]

When sending from [email protected], it correctly uses the [email protected] credentials. When sending from [email protected], it doesn't.

That's the thing. Other than their name and password, I can't see anything anywhere that differentiates primary and secondary. I never configured Mailbox.org, and the same SMTP credentials for Thunderbird are used by both primary and secondary. One works, the other doesn't.

more options

Modifié le par Toad-Hall

more options

Toad-Hall said

Mailbox would need to know about all the email addresses. https://kb.mailbox.org/display/MBOKBEN/Using+e-mail+addresses+of+your+domain

Thanks.

But now, I'm even *more* confused. I never configured Mailbox.org to send from primary in the first place. My domain's DNS hasn't changed in years.

So I guess the question isn't why isn't secondary working, but how is primary working?

more options

Toad-Hall said

Mailbox would need to know about all the email addresses. https://kb.mailbox.org/display/MBOKBEN/Using+e-mail+addresses+of+your+domain

Thanks. But now I'm even more confused.

I never configured Mailbox.org with primary, and my domain's DNS hasn't been changed since before I started using Mailbox.

So I guess the question isn't really why the secondary worked, but how the primary email works in the first place?

more options

Solution choisie

Bill de Haan said

So I guess the question isn't really why the secondary worked, but how the primary email works in the first place?

That's a question for the Mailbox.org folks to answer. Thunderbird has zero influence over what is permitted or rejected on the provider's side.

more options

Stans said

That's a question for the Mailbox.org folks to answer. Thunderbird has zero influence over what is permitted or rejected on the provider's side.

Yes, that's fair enough. I'll follow up with them.