search

jeboehm / docker-mailserver

Docker Mailserver based on the famous ISPMail guide
MIT License
353 stars 92 forks source link

Why do I have different behavior on me@domain.tld and service@domain.tld? #140

Closed kklepper closed 2 years ago

kklepper commented 2 years ago

☺️ Please check the troubleshooting page before opening a new issue. ☺️

https://github.com/jeboehm/docker-mailserver/wiki/Troubleshooting

Describe the bug A clear and concise description of what the bug is.

After moving to a dedicated server, I cannot receive mails on one particular address when sent with Thunderbird or from a third party (that's when it became obvious).

I can, however, receive emails to a different user which poses an enigma I do not know how to debug.

Why do I have different behavior on me@domain.tld and service@domain.tld?

To Reproduce Steps to reproduce the behavior:

No problem with sendmail to me@domain.tld or service@domain.tld, no problem with Thunderbird to service@domain.tld, but mails to me@domain.tld sent from Thunderbird or elsewhere do not arrive and do not appear in the logs of mailserver-mta nor mailserver-mda.

Expected behavior A clear and concise description of what you expected to happen.

Thunderbird should receive emails from anywhere like from the command line, i.e. just receive everything as it should.

Screenshots If applicable, add screenshots to help explain your problem.

Sent from the console of the machine the mailserver is hosted on from 11 different sender addresses to me@domain.tld and received immediately with Thunderbird without problem:

image

2 of those sender addresses sent from Thunderbird to service@domain.tld and also received immediately.

image

Docker environment (please complete the following information):

docker info

Client: Context: default Debug Mode: false

Server: Containers: 18 Running: 18 Paused: 0 Stopped: 0 Images: 49 Server Version: 20.10.7 Storage Driver: overlay2 Backing Filesystem: extfs Supports d_type: true Native Overlay Diff: true userxattr: false Logging Driver: json-file Cgroup Driver: cgroupfs Cgroup Version: 1 Plugins: Volume: local Network: bridge host ipvlan macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog Swarm: active NodeID: aq7jnr9wgw8jglkhvzuhdd9q9 Is Manager: true ClusterID: u8etkx97xn0a9a1oy23u4kk1r Managers: 1 Nodes: 1 Default Address Pool: 10.0.0.0/8 SubnetSize: 24 Data Path Port: 4789 Orchestration: Task History Retention Limit: 5 Raft: Snapshot Interval: 10000 Number of Old Snapshots to Retain: 0 Heartbeat Tick: 1 Election Tick: 10 Dispatcher: Heartbeat Period: 5 seconds CA Configuration: Expiry Duration: 3 months Force Rotate: 0 Autolock Managers: false Root Rotation In Progress: false Node Address: --- Manager Addresses: ---:2377 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc Default Runtime: runc Init Binary: docker-init containerd version: runc version: init version: Security Options: seccomp Profile: default Kernel Version: 5.4.0-88-generic Operating System: Ubuntu 20.04.3 LTS OSType: linux Architecture: x86_64 CPUs: 12 Total Memory: 31.35GiB Name: CS-1 ID: 4UZX:OZYG:74SY:TVBX:U43P:IMQN:LIGS:PKRV:Q7WT:MYN5:3JYX:OXRZ Docker Root Dir: /var/lib/docker Debug Mode: false Username: kklepper Registry: https://index.docker.io/v1/ Labels: Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false

WARNING: No swap limit support

docker-compose version

docker-compose version 1.25.0, build unknown docker-py version: 4.1.0 CPython version: 3.8.10 OpenSSL version: OpenSSL 1.1.1f 31 Mar 2020

Additional context Add any other context about the problem here.

Obviously, it is not a problem of firewall (as this applies to both) or Thunderbird, as the settings on Thunderbird for me@domain.tld is identical to that of service@domain.tld.

kklepper commented 2 years ago

I found out. Due to the server change, the DNS records were wrong. Sorry for the trouble.