Comments (13)
PR-1112 Microsoft E-Mail not allowed to send as [email protected]
from chatwoot.
hello, i'm having the same issue.
same context, i can receive the emails, but i can't send them, i get the same error
from chatwoot.
@drauber @mattos123 This seems like a configuration issue, reply+ emails are generated only for the forwarded emails category. If you use Microsoft email and have used the Oauth Signin flow, this shouldn't be happening. Is there any additional information which you can provide here?
from chatwoot.
i've configured the .env with smtp credentials,
created an inbox using the same email i use as smtp.
when i configure the inbox using microsoft azure app, i sign in as follow on the picture,
from chatwoot.
I haven't configure SMTP in .env, I only set the azure app id and azure secret token, i want to use only the IMAP of Office365.
I don't knwo what other information you need to check if this problem? What else can be useful?
Thansk
from chatwoot.
I haven't configure SMTP in .env, I only set the azure app id and azure secret token, i want to use only the IMAP of Office365. I don't knwo what other information you need to check if this problem? What else can be useful?
This is fine, you don't need to configure SMTP.
Can you please post the full logs not just the lines which you have added, but the logs from the time when you sent the message and the error is thrown?
from chatwoot.
i've configured the .env with smtp credentials, created an inbox using the same email i use as smtp.
You shouldn't be configuring the SMTP in env with your Microsoft email. This config is used to send account notification emails which would not work on a personal / work email with Microsoft.
from chatwoot.
guys, i found the solution....
(PTBR)
Acesse o Centro de Administração do Microsoft 365:
Vá para admin.microsoft.com.
Navegue até a Central de Administração do Exchange:
No menu de navegação, vá para Admin centers e selecione Exchange.
Configurar uma Regra de Fluxo de Email:
No painel de navegação à esquerda, clique em Mail flow.
Vá para a aba Rules.
Clique em + para adicionar uma nova regra e selecione Create a new rule.
Definir a Regra:
Dê um nome à regra, por exemplo, "Allow Send As for Alias".
Em Apply this rule if... (Aplique esta regra se...), selecione The sender is... e escolha [email protected].
Em Do the following... (Faça o seguinte...), selecione Modify the message properties... e depois Set a message header.
Em Set the message header, defina:
Message header: Microsoft.Exchange.Data.HeaderName
Value: [email protected].
(ENUS)
860 / 5.000
Access the Microsoft 365 Admin Center:
Go to admin.microsoft.com.
Navigate to the Exchange Admin Center:
In the navigation menu, go to Admin centers and select Exchange.
Configure a Mail Flow Rule:
In the left navigation pane, click Mail flow.
Go to the Rules tab.
Click + to add a new rule and select Create a new rule.
Define the Rule:
Give the rule a name, for example, "Allow Send As for Alias".
In Apply this rule if..., select The sender is... and choose [email protected].
Under Do the following..., select Modify the message properties... and then Set a message header.
In Set the message header, define:
Message header: Microsoft.Exchange.Data.HeaderName
Value: [email protected].
IMPORTANT!!!
must create a rule for each email you want to use as an inbox on chatwoot, example,
you have 1 email on your .env , this is email is called "suporte@domain"
on the inbox, you created, you have the email "mattos@domain",
on the other inbox, you created, you have the email "giovani@domain",
you have to create a rule on azure portal, for mattos, and another for giovani
from chatwoot.
I haven't configure SMTP in .env, I only set the azure app id and azure secret token, i want to use only the IMAP of Office365. I don't knwo what other information you need to check if this problem? What else can be useful?
This is fine, you don't need to configure SMTP.
Can you please post the full logs not just the lines which you have added, but the logs from the time when you sent the message and the error is thrown?
I can't reproduce the error now, yesterday i update the production env with this changed code.. and the error is not present now. But i'm try to setup a test environment with other Azure Application to try discover the root problem.
from chatwoot.
i've configured the .env with smtp credentials, created an inbox using the same email i use as smtp.
You shouldn't be configuring the SMTP in env with your Microsoft email. This config is used to send account notification emails which would not work on a personal / work email with Microsoft.
i understand, but , i configured the account "suporte" with smtp capabilities, and also use as a normal mailbox, thats the reason i use the same account with smtp on .env, and as an inbox on the web aplication
from chatwoot.
I haven't configure SMTP in .env, I only set the azure app id and azure secret token, i want to use only the IMAP of Office365. I don't knwo what other information you need to check if this problem? What else can be useful?
This is fine, you don't need to configure SMTP.
Can you please post the full logs not just the lines which you have added, but the logs from the time when you sent the message and the error is thrown?I can't reproduce the error now, yesterday i update the production env with this changed code.. and the error is not present now. But i'm try to setup a test environment with other Azure Application to try discover the root problem.
(ptbr)
consegui resolver o erro do send as reply+ denied, com o caminho que orientei acima, acredito que removendo a logica do reply+ do codigo fonte do chatwoot quebre a continuidade do email
(enus)
I managed to resolve the send as reply+ denied error, with the path I suggested above, I believe that removing the reply+ logic from the chatwoot source code breaks the continuity of the email
from chatwoot.
Não quebra não @mattos123
Fiz isso ontem e já está em produção👍
Obrigado pela sugestão.
from chatwoot.
I haven't configure SMTP in .env, I only set the azure app id and azure secret token, i want to use only the IMAP of Office365. I don't knwo what other information you need to check if this problem? What else can be useful?
This is fine, you don't need to configure SMTP.
Can you please post the full logs not just the lines which you have added, but the logs from the time when you sent the message and the error is thrown?I can't reproduce the error now, yesterday i update the production env with this changed code.. and the error is not present now. But i'm try to setup a test environment with other Azure Application to try discover the root problem.
changed the source code the same way as you did, an it worked, thanks for the tip
from chatwoot.
Related Issues (20)
- Contact attributes are missing on the web version since 1-2 months ago HOT 4
- add function create tag in swagger HOT 1
- It's possible to write and send messsage after whatsapp 24 hours windows restrictions HOT 2
- Email invitation wont send email & unable to reset user password. HOT 6
- Can not access api.telegram.org or any other domains HOT 2
- Edit Attribute does not work anymore HOT 4
- Order message a in conversation by date/timestamp HOT 4
- Export / Import (Backup) all Conversations HOT 2
- Clipboard copying from dashboard app does not work HOT 1
- API docs invalid filter_operator samples HOT 1
- Enabling Business Hours, not setting any days hangs browser HOT 2
- Logo and agents profile pictures are not displayed on mobile HOT 2
- Instangram Unsend only work with Mobile App HOT 2
- [Bug] Sometimes not attaching error in message (ie: Message Undeliverable) HOT 3
- Second inbox does not receive message HOT 2
- Provider config Invalid Credentials when updating WhatsApp API key HOT 3
- Error attachment image HOT 4
- Clicking on Chatwoot bubble does not show the chat widget HOT 7
- Webhook event for contact deleted HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from chatwoot.