Email not flowing #10
Comments
|
Same behavior for me. I tried sending a email to the website to check if an alias was created automatically, but without success. How can I check if the postfix container receives mails? |
|
Like I said in the README, this image is a draft for the moment. Not yet tested myself. I'll let you know when I have time to test this image completely. |
|
The following patch makes me receive the confirmation mail. The 'anonaddy' docker container was missing a postfix service to deliver the locally queued verification mails. index f6495f6..82fd49d 100644
--- a/rootfs/etc/cont-init.d/04-svc-main.sh
+++ b/rootfs/etc/cont-init.d/04-svc-main.sh
@@ -7,6 +7,8 @@ if [ "$SIDECAR_CRON" = "1" ] || [ "$SIDECAR_POSTFIX" = "1" ]; then
exit 0
fi
+postfix start
+
# Migrate
su-exec anonaddy:anonaddy php artisan migrate --no-interaction --force
su-exec anonaddy:anonaddy php artisan cache:clear --no-interactionDid not have any luck with receiving emails yet tho. |
|
@alex-phillips With the patch from my previous message and this patch i got it working. I will make a PR with both. A index 606af1e..b225298 100644
--- a/examples/compose/docker-compose.yml
+++ b/examples/compose/docker-compose.yml
@@ -47,7 +47,7 @@ services:
- anonaddy
ports:
- target: 2500
- published: 2500
+ published: 25
protocol: tcp
volumes:
- "./data:/data" |
|
@bastidest So the port change to 25 fixes receiving email, but I'm still unable to send email (specifically the confirmation email). I see now with the In the logs below, my recipient email was added (REAL_EMAIL@gmail.com), but it looks unusual in the log lines. Not sure if this is correct or not? |
|
@alex-phillips My (successful) mail delivery looks like that: |
|
@bastidest Right, so if you look at my postfix logs, this specifically: Can you glance over my files above or perhaps post yours? |
|
Hi @bastidest,
It is not good practice to start a service this way (see https://github.com/just-containers/s6-overlay/). Also the sidecar postfix container already do this job.
Default smtp port (25) should be ok for you but some distrib do not allow binding to unprivileged ports. But in our case we have to bind to port 25 like you said because there is no way to tell a sending server what port you're listening on using MX. |
|
@crazy-max Is it possible that these containers need to share the same network then? Is the anonaddy container attempting to send to postfix, but since its technically running in another container, it's not working properly? |
If you use the compose file in the examples folder, they are intrinsically part of the same network.
I don't know if anonaddy is communicating directly with postfix. If it does, I don't see anything to configure the postfix server address on anonaddy. Any idea @willbrowningme? |
|
@crazy-max yes they are on the same network, but if you use |
It appears to me that anonaddy is using Laravel as web framework. The current configuration tells Laravel to use the Maybe set the driver to SMTP and use the existing
I don't get your point. AFAIK mail servers need to be reachable under their well-known port. |
When an email arrives at the server it is handled by Postfix. Postfix then pipes the received email through to the Laravel application (the lines in /etc/postfix/master.cf do this). The Laravel application then determines where to forward the email onto by consulting the database, it sends the email using sendmail (set in config/mail.php - @alex-phillips The reason you can see REAL_EMAIL@gmail.com is probably because of the variable envelope return path (VERP) being set. I'm hoping to release the full detailed instructions for manually setting up the server soon which should help greatly with this Docker image. |
@bastidest Yes that should do it.
@willbrowningme I think I'll have time next week to test the documentation you sent me. |
|
@alex-phillips @bastidest Should be fixed with latest image |
|
@crazy-max I'm now getting a 500 now when attempting to send the confirmation email. I'm trying to add in an error_log directive to the nginx config, but every time I restart the container it reverts my changes. Are you logging errors anywhere so I can see what exactly the 500 is? |
|
@crazy-max Looks like this is the error: |
|
You can disregard that 500 error - I had the wrong hostname set for MAIL_HOST. That's returning successfully now, postfix outputs the following, which looks normal: But still not getting the confirmation email at the destination. |
|
I am unable to do the initial login now.
when logging in with What I did:
I set |
|
@bastidest Did you run the seed command? |
|
@alex-phillips thank you that worked |
|
Anyone have any luck getting this working? |
|
Same problem, but I don't need to send emails yet. So I modified the database to approve the domains whithout to receive the confirmation email But still not working. This is the error when postfix receive an email sent from Gmail. I'll see how this thread goes |
|
I'll start the tests on the Docker image and I'll get back to you on that issue. |
|
Ok I was able to reproduce this issue on a VPS. Keep you in touch. |
|
@bastidest @alex-phillips @brincowale I've made some changes to this image and now everything seems to work. See CHANGELOG and the new compose example. |
|
Great! I look forward to giving this a try. Thanks! |
|
Hello @alex-phillips, I am having a very similar issue happen. I can access the web interface, create a user but the verification email won't send. I'm woundering if this has something to do with the most recent version of anonaddy (0.8.0) what version were you able to get this running with? Thanks in advance |
Behaviour
After setup, it is unable to send verification emails. Manually verifying (changing column in DB) and sending to an alias with my email as the forwarded address doesn't seem to be sending either. None of the containers logs seem to show anything helpful (or that anything is happening at all).
Steps to reproduce this issue
Expected behaviour
Verification email should come to inbox (or at least spam?)
Actual behaviour
No email received, inbox or spam. Tried multiple email providers. Nothing signification (good or bad) in container logs.
Configuration
Docker version (type
docker --version) : Docker version 19.03.6, build 369ce74a3cDocker compose version if applicable (type
docker-compose --version) : docker-compose version 1.21.2, build a133471Platform (Debian 9, Ubuntu 18.04, ...) : Ubuntu 18.04
System info (type
uname -a) : Linux 4.15.0-88-generic Simplify Dockerfile Alpine Linux apk usage #88-Ubuntu SMP Tue Feb 11 20:11:34 UTC 2020 x86_64 x86_64 x86_64 GNU/LinuxInclude all necessary configuration files :
docker-compose.yml,.env, ...docker-compose.yml
anonaddy.env
Docker info
Logs
anonaddy
anonaddy_postfix
anonaddy_redis
mariadb
The text was updated successfully, but these errors were encountered: