-
-
Notifications
You must be signed in to change notification settings - Fork 654
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 make Email catch-all to work in the intranet #426
Comments
The only thing I could imagine for is that the If it still doesnt work, try to give it write permissions for everyone (also all files inside that directory) |
Hello there, the image i linked show the errors from the debug but I just understood that those exceptions are raised when I try to send a test email without filling the fields. Otherwise the debug list is 0. I'm kinda lost here. |
As you are on Windows I would suggest to check out a different branch which should fix a lot of issues regarding mounts/Volumes. The PR for that is here: #383 When doing this, first try to spin it up with minimum required containers and without any custom configuration and go step by step:
|
If the above Windows branch still does not work, then it might be related to the Docker version. There seems to be an issue with Docker I would suggest to downgrade Docker back to However, as you are on Windows I would recommend to stay on the |
Ok thank you very much, I'll test it and report back. |
I am also currently building CI tests around this feature so it can be catched as early as possible. |
Hello there, I just tried a few things:
I'm a bit confused, it seems to be partially due to docker version and partially to my current master devilbox config. |
@masiorama thanks for digging into this. There's currently a general issue with Additionally when it comes to Windows, mounts a treated very differently, that's why I am in the middle of rewriting the mounts in question to Docker volumes. So stick with |
Intranet Email catch-all now has its own CI check against all This ensures compatibility against latest five Docker versions against latest five Compose versions for each and every PHP-FPM version. PR for that was here: https://github.com/cytopia/devilbox/pull/430/files#diff-3fac1a644d6e83bef0eca8aba4283dbaR1 However CI only tests against Linux (should be OS independent though) |
Thanks, I'm gonna test it in the next days. |
@masiorama does the release branch resolve your issue? |
@cytopia sorry for the huge delay, I'm gonna check it right now and keep you posted. |
If I'm not wrong, the branch to test is release/v1.0.0, right? |
Yes, that's the one.
Hmm, that's strange. Can you paste the PHP code that sends the email please. |
I'm using the test mail accessible from localhost, no custom code at all. |
That should work without any hassle. I even have CI tests on the email catch-all functionality of the intranet. The only thing I could currently think of is:
Can you diff your |
To be sure it is not something I did with the customization I simply cloned the branch on an empty folder, did a |
Could you run the following and see if it resolves it:
|
I did
update: Thanks! |
OK, maybe the |
Indeed it was never done recently. I tried with my other devilbox installation ( |
Ok, glad it works for you now. I will also update the documentation to emphasize the need to |
@masiorama thanks again for this catch. I've updated the documentation accordingly and emphasized the importance of https://github.com/cytopia/devilbox/pull/513/files |
Relevant documentation: |
ISSUE TYPE
Checklist
.env
file is attacheddocker-compose.override.yml
is attached (if it exists)cfg/
dir are attached (if customized)docker-compose logs
andlog/
output is addedOS / ENVIRONMENT
SUMMARY
I cannot catch any email, not even a test one from the very same Email page.
Here the debug logs from the intranet.
STEPS TO REPRODUCE
No idea
EXPECTED BEHAVIOUR
Email catch-all working again.
ACTUAL BEHAVIOUR
Complete empty table list, and debug errors list in the footer section.
OTHER INFORMATION
Start command
.env
cfg\php-ini-7.1\custom.ini
The text was updated successfully, but these errors were encountered: