SMTP mailer problem
Settings are set in docker-compose yaml file,worker section.
EMAIL_DRIVER: smtp
EMAIL_FROM_ADDRESS: [email protected]
EMAIL_SYSTEM_ADDRESS: [email protected]
EMAIL_FROM_NAME: CRM-SYSTEM-TWENTY
.....
email host, port, smtp_user, smtp_pass are also set.
But still receiving invice email from: Felix from Twenty <[email protected]>
48 Replies
I would check to make sure the port is smtp ports are open. What hosting provider are you using?
ports are OK. messages are incoming, but sender is WRONG
what version?
0.32
fresh install
I would just search the codebase for "Felix from Twenty <[email protected]>"
Then work your way backwards.
im not a developer
I'm not sure what the invoice email is?
deploying canned food .... docker
what are you talking about??
What does that mean?
INVITE ;))
Are you a selfhosted customer?
yes, self hosted
OH!! Invite!!
invite email ... typo
yeah, I haven't been using that feature. I just use the link. I'll have to take a look at it.
now trying to enable gmail .... but probably it would be correct to start new thread on that subject
Yeah, and that's realtively documented.
i havent seen any
explaining what is needed for what
i saw that thread but it needs to be clearified so you will get less stupid questions
You'll essentially need to create a new project in google console and set the permissions needed to support the functionality.
already setup project, now trying to figure what is needed for what
You have scopes for both gmail and also the calendar.
Just pay attention to the ENV because in my exprience these env vars change slightly from version to version.
and what entries are needed in docker compose file
env var change is one of things i really hate ... but probably this is what early alpha versions are about
You'll have to read the scopes for each permission and create the token/secret, but you can change the scopes until you have success. Just use those scopes in test mode. You don't need to request access from google.
yes, but i have to match .env settings and gcp api stuff
correct.
also what is minimum to have gmail messages synced
That thread above will help you identify those.
I hope that helps.
not very clear post ... for non developer 😉
for example do it really has to be like:
AUTH_GOOGLE_APIS_CALLBACK_URL should be http://localhost:3000/auth/google-apis/get-access-token
if i access it through nginx upstream proxy
lets move to new thread with this subject.
The call back url is going to be whatever the URL you're using to access the front end.
So if you're using http(s)://localhost:3000 then yes. If you're using https://mytwentyinstance.com to access your front end then you'd use that.
It'll change soon and you'll be able to do it from UI instead of changing file directly
Here's the stage 1 of it https://github.com/twentyhq/twenty/issues/8173
yes, but it is still unclear what is REQUIRED for what and whad do we need @crm side and what @google side
Ooh, that's what you meant
and which settings are required for email integration and which for google auth
thats why i setup new thread stating integration with google mail
will have separate for google auth
I'll research that later and answer your questions, is that OK?
yes sure
do you see THAT topic?
https://discord.com/channels/1130383047699738754/1304106786118434977
Yep
I'll try to test it and give back information here as deploying documentation isn't working right now
here is link to other topic about google auth https://discord.com/channels/1130383047699738754/1304117497678659595
@Latvia do you still need assistance here?
- regarding the mail sender issue, please ssh in your container, run 'env' and make sure your env variables are taken into account
- regarding the mail sync, it has not changed so the linked threads are still correct ==> we will likely document it soon as it is stable now
Using messaging sync in self hosting is still not straight forward right now, but we can help you get it right
@Latvia I found reported issue like the one you wrote about https://github.com/twentyhq/twenty/issues/7001
GitHub
Send workspace invitation email from the logged-in user · Issue #70...
Current Behavior Currently, invitations to workspaces are sent from the server's default message sender Desired Behavior Invitations should appear to be sent by the person who created the invit...
I think this is a bit different, this issue is about sending the invite as the workspace owner (which is a special case for invites) but you will still have the issue for password reset emails for example. You should be able to override the twenty admin sender email using the env vars
correct entries are already in .env (compose yaml) please look at 1st post
@Latvia they are in your docker-compose .env but could you check that they make it to the container:
- ssh in your container and run "env"
Could you paste the output here (while masking the private data of course)