Open ririko5834 opened 4 months ago
I already made issue on anonaddy repo last year https://github.com/anonaddy/anonaddy/issues/485 But even after a year and rebrand to addy.io I still cant receive emails from serv@intime.sk which sucks because idk when courier will deliver me a package.
I host anonaddy using this container on portainer panel. willbrowningme can't reproduce the issue, but he tested only locally without using docker, I hope you can help me to fix it
I'm not sure I can help... for me postfix is akin to black magic. However in the past I realised I misconfigured stuff that prevented delivery by logging in to the rspamd web interface and going to the History tab. If you go there, do you see any errors?
those emails from serv@intime.sk passed
I can see there are quite a few "cannot connect upstream" errors down below in the Errors list.
When those errors repeatedly happened to me in the past, they were due to the fact that rspamd could not communicate with the redis server. And that led to undelivered emails, despite the fact rspamd "passed" the emails.
Now, I'm not sure whether your issue is the same as mine. For me rspamd is even more esoteric than postfix, and the errors logged don't help. But maybe you can try to figure out why the redis server might not be reachable (wrong container name? wrong port? redis is requiring a password that wasn't set in REDIS_PASSWORD
?...) and see whether it helps fixing things.
It doesnt show any logs, I host both anonaddy, mysql and redis using docker compose https://github.com/anonaddy/docker/blob/master/examples/rspamd/compose.yml I didn't set any password for it
redis logs: redis env:
anonaddy env:
trying to ping redis db from anonaddy container:
It seems to work, so redis should be reachable
From what I can see, the redis setup should be fine.
However ping redis:6379
only pings the redis host (container), not its actual port 6379.
If you want a more thorough test, run this command from the shell in the anonaddy container:
db42ab424180:/var/www/anonaddy# nc redis 6379
then you should get a prompt on an empty line. Type:
PING
you should get some kind of response back. I get:
-NOAUTH Authentication required.
because I set up redis with a password.
I expect it works, because you didn't set up a custom redis port. In which case, unfortunately I don't know where to look further to investigate your issue.
yes, that works. so the issue clearly is somewhere else I have no clue of... :-(
@willbrowningme can you take a look at it and investigate it running it using docker
What other steps to investigate it?
Cant anyone help me to write some script which will run regularly and will forward/send all emails from serv@intime.sk that got stuck in postqueue to different email address or to discord webhoook? This would work as a tempfix. Its really annoying that I cant receive delivery notifications for my parcels from courier company
?
@buxm
@ririko5834 unfortunately I can't help with your script: as said, I'm totally unfamiliar with postfix.
Support guidelines
I've found a bug and checked that ...
Description
I selfhost anonaddy using docker. But anonaddy seems to not forward some emails. For example, I don't get emails from the courier company that my package will be delivered the next day. Other emails I usually normally have. Can you check it?
I don't receive emails from serv@intime.sk (they are not forwarded on anonaddy). I receive emails from that mail address normally on my gmail.
After running postqueue -p, I can see there the undelivered emails in queue
Later, there are more emails:
None of them are listed in failed delivery tab, why?
Logs:
Why was it deferred? There are many of those logs
None of those emails were saved in failed deliveries, how does failed delivery work, it saves there only if the alias recipient email address refused the forwarded email.
I would appreciate any help. Do you think that it's caused because the sender serv@intime.sk did not pass all anonaddy anti-spam checks? If yes, is there a way to whitelist that domain so it will skip all the checks and forward it straight?
Expected behaviour
Forward them normally
Actual behaviour
Emails from serv@intime.sk get stuck in the queue
Steps to reproduce
.
Docker info
Docker Compose config
No response
Logs
Additional info
No response