-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Cannot create the attachments directory #51
Comments
|
I'm not an expert in Docker, but it looks for me that there is an SSL error between your host and the mail host. environment: So maybe you should try different ports like 587 or 465 for smtp and 143 or 993 for imap. All depends on your mail host of course. |
While troubleshooting I changed the SSL to a less secure reason for that. This is what I have now
|
This is my docker compose
|
Can you connect to this mailbox with a regular mail client? Could you maybe try port 143 for imap? Just to check if your mail server works with STARTTLS. |
Oh, that makes it more complicated as I never have used Cloudflare for my mail host. I guess this is the problem, but let's wait if @antedebaas has more ideas. Good luck! |
one of the problems with the checkmail button is that it is bound to php-max-execution time. this is 30seconds by default. |
Please what command do I run? |
docker exec -t dmarc-web-1 php /var/www/html/bin/console app:getreportsfrommailbox replace 'dmarc-web-1' with your container name |
Thank you |
let me know if this solved your issue |
try the following command: php .\bin\console secit:imap:validate-connections connection result should be success. |
|
This is the result I get |
Then the problem is on the mail server side |
I am unable to retrieve mail and this is what I found in logs, can someone please share how I can get this resolved with docker installation?
NOTICE: PHP message: [critical] Error thrown while running command "app:getreportsfrommailbox". Message: "Cannot create the attachments directory "/var/www/html/var/imap/attachments""
The text was updated successfully, but these errors were encountered: