relay access denied 554 5.7.1 on 0.12.2/0.12.3 version . #145
Comments
|
That looks to me like it is attempting to deliver the message to ***@gmail.com locally which is why it is returning relay access denied. I think perhaps the following variables may need to be added to https://github.com/anonaddy/docker/blob/master/rootfs/etc/cont-init.d/00-env Not sure what port Docker uses for SMTP. P.s. if that is your real Mysql username and password you should change it. |
That also didn't help still the same issue.HTTP 500 Internal Server Error On 0.11.2 when am adding It also having the same error but removing these from environment variables solve the issue on 0.11.2 . But most of the mails goes into spam folder even with spf dmarc dkim dns. One more issue i am having is that i am unable to create MTS-STS policy & DANE on this docker container . I coun`t understand how to set it up. |
|
I have the same issue after updating to 0.12.3 Here are the logs: |
|
If you add |
|
@willbrowningme changing yes to no and vice-versa does nothing. Still having relay access denied error with smtp. |
|
Could this be linked to this change #122 ? |
|
Possibly, definitely worth a try. The only thing that has changed with v0.12.* vs v0.11.* is that the web application now uses Symfony mailer instead of Swift mailer, the SMTP settings should still work as they did previously. |
|
In the logs reported above the helo command seems to be Where |
|
Has anyone managed to test if this issue still persists when adding |
|
bit of testing with the MAIL_EHLO_DOMAIN env variable, seems it's ignored, still have the |
|
@ShawnTheShadow do you still have the same error with |
|
When editing inside the container, and restarting, it gives a /data/storage already exists error and dies, have to recreate the container, i know that's going to be a different issue, it also happens on restart of the system |
|
today i checked the debug log and found that neither hostname nor public ip matches. here is the complete log: |
|
I will make some enhancements to the image so we can add arbitrary env values, which is not currently possible. Edit: except if Anonaddy can read env vars from system env and not just the |
|
@crazy-max PHP environment variables can be accessed via But I don't know whether that would work as you mentioned or not. |
|
I do believe the issue is simply the missing |
Will revert that change and see how to improve injecting env vars in a follow-up |
Yes but Anonaddy doesn't read them currently to override ones from |
|
That's right, it doesn't read them to override those in https://laravel.com/docs/9.x/configuration#retrieving-environment-configuration When https://laravel.com/docs/9.x/configuration#configuration-caching |
|
Ok got it thanks! |
|
when i am using these env i am still getting relay access denied working log what should i do to get it fixed? as all mails dumps to spam folder. i have already set the records correctly and also validated through mxtoolbox and other online tools but i could not find the issue. here are the complete logs:
|
|
@sakearzoo it should be In your relay access denied.log in this section: I don't understand how |
|
@willbrowningme and can you suggest me how to add mta-sts and dane record to my docker container? i have added the latest log: |
You don't have to set all of them expect but the one from the README: https://github.com/anonaddy/docker#mail The others are populated automatically by the container in https://github.com/anonaddy/docker/blob/master/rootfs/etc/cont-init.d/13-config-anonaddy.sh Btw how do you set them? |
|
@crazy-max i have added those variable through environment variables directly on docker compose . could you share your docker-compose.yml file so that i could try with my stack? this is my docker-compose file |
these env vars except the ones defined in the README will not be used by AnonAddy, see #145 (comment). if you want to inject arbitrary env vars see https://github.com/anonaddy/docker#define-additional-env-vars |
|
ok trying that and how to add mta-sts & dane records ? is it possible to add? |
i have tried creating .env file inside data folder but still seems to be ignored those files. or is it automatically detected ? |
|
no you have to create a file volumes:
- "./data:/data"but again you don't need to set these env vars. it should work as it is. |
|
Using docker-compose yml file I have already mounted And created a file locally at Even if I don't specify those variables and i am still able to send emails, I won't be able to figure out why my emails are being routed to the spam folder. I've already set up ptr records, dkim, dmarc, and spf. My emails continue to land in the spam bin. Even if I open ports- 587 , 465 i am unable to establish connection at those ports . I am still confused about where i am going wrong . |
|
What are the ARC headers and authentication results in the email's headers? (With all PII removed of course) |
Maybe DMARC misconfiguration or your IP is blacklisted. You can check at https://multirbl.valli.org/lookup/ |
|
These are the details These are the arc header details. |
|
Looks like the DNS settings are all correct, check the blacklist check @crazy-max recommended, if you're doing it from home like from a nas, there are some blacklists that specifically block residental ip addresses |
|
@crazy-max i have checked its not in blacklist all green and also in mail checked original where it was clearly mentioned that spf, dkim , dmarc |
|
other than residential ip address blocking, only other thing i could think of would be poor ip/subnet reputation (which i had when i started my email server with dreamhost, took several months to improve it) |
|
@ShawnTheShadow that could be possible having bad ip reputation 😞 is there any proxy ip could help in this case ? Update: i have good reputation compared to others , checked just now. Other ips who's mail reaches to my inbox having bad reputation>90% abusive. Still don't know how they manage to send the mail to my inbox folder. |
|
I've started using mailgun for my email proxy, it's free for the first 1000 emails for the month, there's several others out there |
|
@ShawnTheShadow do you have any idea how to setup mta-stsv1 & dane record with anonaddy docker container ? |
Are you sure? That nearly impossible, you should have at least 3/4 blacklist. I'm on Vultr and their reput is good. I have 2 BL but unrelated as it concerns sanctions against others countries. One trick is to create VPS over and over until an IP looks good. But be careful admins tend to detect that kind of behavior. |
|
Locking this issue as it seems out of scope now. But feel free to open a thread on https://github.com/anonaddy/docker/discussions |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Behaviour
After setting docker container with anonaddy version edge/latest/0.12.3/0.12.2. I am having error i,e Relay access denied 554. and email is not sending for verification. But when i downgrade the version of anonaddy to 0.11.2 everything works fine without error. It seems that with latest version 0.12.x it is facing error.
Steps to reproduce this issue
Setup a vm with ubuntu 20.04 lts
Expected behaviour
Actual behaviour
Configuration
Docker version (type
docker --version) :Docker version 20.10.17, build 100c701Docker compose version if applicable (type
docker-compose --version) : Docker Compose version v2.2.2Platform (Debian 9, Ubuntu 18.04, ...) : ubuntu 20.04 LTS
System info (type
uname -a) : Linux containerr 5.11.0-1022 # 23 ~ 20.04.1-Ubuntu SMP Fri Nov 12 15:45:47 UTC 2021 aarch64 aarch64 aarch64 GNU/LinuxInclude all necessary configuration files :
docker-compose.yml,.env, ...docker-compose.yml
shared env:
Docker info
Logs
DNS
The text was updated successfully, but these errors were encountered: