-
-
Notifications
You must be signed in to change notification settings - Fork 51
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
Email receiving (and sending) broken since 0.8.0-r0 #70
Comments
@KevinRoebert Maybe linked to #67. Can you try with |
The error persists even with the |
I've also tried older images like 0.7.4 and forced a redownload. It works with images < 0.8.0. |
@KevinRoebert Ok thanks for your feedback! Might be an issue with Postfix since Alpine 3.14. Will take a look and keep you in touch. |
Could you try updating your
See if that sorts it. |
@willbrowningme Don't think that's issue, this is already handled. |
@KevinRoebert I've made some changes in #71, can you try with |
Does not fix the problem. Here is the log:
Doesn't work either. The log is attached: |
Tested with |
@KevinRoebert Thanks for your feedback! Can you enable @willbrowningme I wonder if this is not due to the changes to |
|
@crazy-max yes it seems okay to me, here is a full
and here is the
The only other change I can think of is the one I mentioned above in this thread, to try changing the values in
to:
|
0.8 does not work for me either but in 0.7.5 the tls conenction works and thus mail forwarding works as well |
@Imaskiller have you tried changing your
This is the only thing I can think it could be. |
@willbrowningme I will make a change and push that. Btw |
@KevinRoebert Can you try with |
Nope this does not help either.
|
@Imaskiller it is related to the change from using sendmail to smtp as the Laravel mail driver then. Could you try updating your
|
How do I change it? If i change the file and restart the container i get this error:
I also tried volume-binding the changed file but i get the same error and I am not receiving any mails after the change. |
Can you try with |
Unfortunately that still does not fix it. TLS connections cannot be established and ends with the following error in the end:
I also tried
But it fails with the same error in the end. Edit: 0.7.5 works still works fine though |
@Imaskiller @KevinRoebert Should be fixed with latest release (0.8.1). |
Now there is another error. The log is attached: |
@KevinRoebert I've pushed another fix to handle postfix relay restrictions. Can you try with |
@crazy-max same error for me with pr76
|
The updated
Should mean that permit_mynetworks accepts connections from localhost. Could there be an issue with the current mynetworks vaiable in
Or perhaps the fact that the Postfix does not recognise this as a local connection from mynetworks due to the Docker setup? I can't recreate this issue with a self-hosted instance that was set up manually. |
Does not fix the error. The error message is the same as before. |
Docker containers using the private subnet |
@KevinRoebert @Imaskiller Ok found the issue. Can you |
Does fix the problem. |
Behaviour
Steps to reproduce this issue
anonaddy/anonaddy:0.7.5
toanonaddy/anonaddy:0.8.0
ANONADDY_DNS_RESOLVER
to any public DNS resolver, e.g.,1.1.1.1
or8.8.8.8
(Tried with the following settings:127.0.0.1
,1.1.1.1
,8.8.8.8
)Expected behaviour
Actual behaviour
Configuration
docker --version
) :Docker version 20.10.7, build f0df350
docker-compose --version
) :docker-compose version 1.27.4, build 40524192
Ubuntu 20.04.2 LTS
uname -a
) :Linux *********.eu 5.4.0-77-generic #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
docker-compose.yml
,.env
, ...anonaddy.env.txt
docker-compose.yml.txt
Docker info
Logs
The text was updated successfully, but these errors were encountered: