Search Email Account doctype
From here you can configure email, no need to install erpnext.
you can find all your send/Recieved email in the Communication doctype. frappe running a scheduler every 10 min to fetch email
for more information refer this ducument
I have found the Email settings in Desk App, I have added an Email Domain, added email account, set the required credentials like smtp server url, port and password, but when I try to send email to a contact, nothing happen.
Check Email Queue doctype. Also check email queue status if it is Suspended then start.
What is current status if it is Resume Sending then make it Suspend Sending same like this screenshot
The status now is Suspend Sending.
Even if I enter to one queue and press the button of Send Now, it doesn’t send the email and the status remains Not Sent.
Here is the SMTP and IMAP configuration, I tested the credentials on Spark email client and it works just fine, but in Frappe CRM it’s not working
Does anyone have an idea how to solve this issue.
I signed up for Frappe Cloud trial, used the same SMTP credentials and it works just fine.
Hi,
Are there any messages in the Error Log List. or do the queue entries have any clues?
It’s empty.
I have tried to send emails using the Python SMTP module form the docker container and it works just fine, the email has been sent.
But when trying to send emails from Frappe CRM, the email is in the Email Queue, but it’s not being sent.
I have activated the scheduler, and still not working.
I spun up a Docker CRM instance and seem to have the same issue. Messages remain in queue , no error messages. The System Health Report page shows messages as “Pending”. bench scheduler status says it’s enabled for the site.
Exactly, I’m trying to build a test env using Ubuntu VM to install it directly and activate production mode and see.
Based on your test, the normal version (without docker) does it have the same issue?
I installed the Docker version from as described here. , That installs crm 2.0.0-dev, frappe 15.x.x-develop. It appears to have the same problem that you have described. .
Yeah, I have tried both development version and production version, the production version is not running properly also. after running the installation script, I got this error:
service "configurator" didn't complete successfully: exit 255
Docker Compose failed, please check the container logs
Command '['docker', 'compose', '-p', 'crm_prod_setup', '-f', '/home/ubuntu/crm_prod_setup-compose.yml', 'up', '--force-recreate', '--remove-orphans', '-d']' returned non-zero exit status 1.
I tried the easy install script, it failed with a similar message but it also clobbered all by other Docker test apps and they may have been a factor. If I get time I’ll spin up a VM dedicated to crm but it isn’t something I’m planning on using in production soon.
Waiting for your feedback.
Hi,
Does anyone find a solution for this issue?
I haven’t had a chance to experiment, however I noticed in the docker init,sh that bench --site crm.localhost set-config mute_emails 1. I don’t know what that is for.
https://github.com/frappe/crm/blob/develop/docker/init.sh
I’ll try changing that and recomposing to see if it has any bearing.
I changed the bench --site crm.localhost set-config mute_emails to 0
.
I logged in as Administrator and added a user using a yahoo.com address, generating an app password in yahoo to use for the app. I did not add an email domain or account , only used the create user email In the user settings I went to the Password button and it did send a password reset link to the address.
I added a second user with a different email address and the app sent that address and invitation, using the yahoo account which was set as default sending.
The only other change I made was to edit the common_site_config.json in the container and change the redis addresses to the redis container ip explicitly, I don’t know if that was a factor or not.
I did not change the redis image to redis-stack.
EDIT Unfortunately, sending of emails from the app itself is still failing. Still in queue,
Thanks for the update.
I hope someone from the core team can review this issue. I have created a GitHub issue since a while now, but no response.