You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
... the documentation does not mention anything about my problem
... there are no open or closed issues that are related to my problem
Description
I recently installed AnonAddy docker - and love the service. I followed all the guides and got almost everything to work - I'm able to send and receive emails, I have TLS working, and almost everything is great - EXCEPT for a lingering SPF authentication issue that I can't seem to shake.
Whenever an email is sent to an alias email account, the SPF reflects the IP address of the email server for the original sender and NOT the IP address of my AnonAddy server. This causes the SPF to fail.
For example, If a user from Gmail sends an email to my alias myalias@mail.mydomain.com, the received SPF shows a Gmail IP and NOT the the IP of my AnonAddy server. This is causing the emails to get dumped into my junk mail box.
I've tried to modify a bunch of settings to wit's end, and can't figure out how to fix this. Am I doing something wrong?
Here is my configuration. Hoping somebody can guide me to the right direction. I have the a static IP, and my ptr records point to my IP (reverse dns works). I am using mail.myhost.com as a base email domain, as I have a different email server running on the root domain myhost.com.
Base Details
Email Domain:mail.myhost.com AnonAddy Host:webmail.myhost.com Server IP:3.3.3.3 (Example)
I have TLS certs for my domain generated using .acme.sh, and have mapped the cert and key to /certs in the anonaddy container.
## General System Config
TZ=America/Los_Angeles
PUID=1000
PGID=1000
MEMORY_LIMIT=256M
UPLOAD_MAX_SIZE=16M
OPCACHE_MEM_SIZE=128
REAL_IP_FROM=0.0.0.0/32
REAL_IP_HEADER=X-Forwarded-For
LOG_IP_VAR=http_x_forwarded_for
## APP Environments
APP_KEY=<redacted>
APP_DEBUG=true
# URL Of AnonAddy Install
APP_URL=https://webmail.myhost.com # Can be whatever
ANONADDY_RETURN_PATH=bounces@mail.myhost.com
ANONADDY_ADMIN_USERNAME=anonaddy
ANONADDY_ENABLE_REGISTRATION=true
ANONADDY_DOMAIN=mail.myhost.com
#ANONADDY_ALL_DOMAINS=mail.myhost.com
ANONADDY_HOSTNAME=smtp.myhost.com
ANONADDY_DNS_RESOLVER=127.0.0.1
ANONADDY_SECRET=37WYeWU6k00WttSqedDm
ANONADDY_LIMIT=200 # Number of emails a user can forward and reply per hour
ANONADDY_BANDWIDTH_LIMIT=1048576000 # Monthly bandwidth limit for users in bytes domains to use
ANONADDY_NEW_ALIAS_LIMIT=30 # Number of new aliases a user can create each hour
ANONADDY_ADDITIONAL_USERNAME_LIMIT=50 # Number of additional usernames a user can add to their account
## RSPAMD Config
RSPAMD_ENABLE=true
RSPAMD_NO_LOCAL_ADDRS=true
RSPAMD_WEB_PASSWORD=oneworld
## Mail Config
MAIL_FROM_NAME=AnonAddy
MAIL_FROM_ADDRESS=anonaddy@mail.myhost.com
## Postfig Configuration
POSTFIX_DEBUG=true
POSTFIX_SMTPD_TLS=true
POSTFIX_SMTP_TLS=true
#Certs
POSTFIX_SMTPD_TLS_CERT_FILE=/certs/fullchain.pem
POSTFIX_SMTPD_TLS_KEY_FILE=/certs/privkey.pem
Anonaddy config in docker-compose.yml
anonaddy:
image: anonaddy/anonaddy:latest
container_name: anonaddy
depends_on:
- db
- redis
ports:
- target: 25
published: 25
protocol: tcp
volumes:
- "./data:/data"
## mydomain.com
- "/etc/mydomains/mydomain.com/fullchain.cer:/certs/fullchain.pem:ro" # Link to certs created by Acme.sh
- "/etc/mydomains/mydomain.com/privkey.key:/certs/privkey.pem:ro" # Link to key for islnt.com created by Acme.sh
env_file:
- "./anonaddy.env"
environment:
- "DB_HOST=db"
- "DB_DATABASE=${MYSQL_DATABASE}"
- "DB_USERNAME=${MYSQL_USER}"
- "DB_PASSWORD=${MYSQL_PASSWORD}"
- "REDIS_HOST=redis"
restart: always
Expected behaviour
I expected the SPF to pass. The emails should be regenerated from AnonAddy, and the SPF should reflect the IP address of the AnonAddy server.
Actual behaviour
The SPF is failing. I ran the headers through MX toolbox, and the SPF authentication fails. The SPF reflects the IP address of the email provider of the sender. SPF alignment looks to be okay, and and DKIM alignment also looks okay.
Steps to reproduce
Described above. Anytime I receive an email sent to my alias, the email SPF authentication fails. The IP address shows the IP of Gmail (or any other provider) rather than my AnonAddy server.
Support guidelines
I've found a bug and checked that ...
Description
I recently installed AnonAddy docker - and love the service. I followed all the guides and got almost everything to work - I'm able to send and receive emails, I have TLS working, and almost everything is great - EXCEPT for a lingering SPF authentication issue that I can't seem to shake.
Whenever an email is sent to an alias email account, the SPF reflects the IP address of the email server for the original sender and NOT the IP address of my AnonAddy server. This causes the SPF to fail.
For example, If a user from Gmail sends an email to my alias
myalias@mail.mydomain.com
, the received SPF shows a Gmail IP and NOT the the IP of my AnonAddy server. This is causing the emails to get dumped into my junk mail box.I've tried to modify a bunch of settings to wit's end, and can't figure out how to fix this. Am I doing something wrong?
Here is my configuration. Hoping somebody can guide me to the right direction. I have the a static IP, and my ptr records point to my IP (reverse dns works). I am using
mail.myhost.com
as a base email domain, as I have a different email server running on the root domainmyhost.com
.Base Details
Email Domain:
mail.myhost.com
AnonAddy Host:
webmail.myhost.com
Server IP:
3.3.3.3
(Example)I have TLS certs for my domain generated using
.acme.sh
, and have mapped the cert and key to/certs
in the anonaddy container.DNS Configuration
A Records
smtp -> 3.3.3.3
MX Record
mail -> smtp.myhost.com
DKIM Record
default._domainkey.mail -> v=DKIM1; k=rsa; p=<Something long>
DMARC Record
_dmarc.mail -> v=DMARC1; p=reject; sp=none; aspf=r; fo=1:d:s
SPF Record
mail -> v=spf1 mx ~all
anonaddy.env
ConfigurationAnonaddy config in
docker-compose.yml
Expected behaviour
I expected the SPF to pass. The emails should be regenerated from AnonAddy, and the SPF should reflect the IP address of the AnonAddy server.
Actual behaviour
The SPF is failing. I ran the headers through MX toolbox, and the SPF authentication fails. The SPF reflects the IP address of the email provider of the sender. SPF alignment looks to be okay, and and DKIM alignment also looks okay.
Steps to reproduce
Described above. Anytime I receive an email sent to my alias, the email SPF authentication fails. The IP address shows the IP of Gmail (or any other provider) rather than my AnonAddy server.
Docker info
Docker Compose config
Logs
Additional info
No response
The text was updated successfully, but these errors were encountered: