One email won't deliver

Support
1

**NethServer 8: , with just mail installed. New Install this week.
**Debian 13. Hi, I have one email address (out of 6) that will not receive email no matter what I do. Can make up any alias and add it and they will work inbound. Outbound email works fine. Mary.Kelly@DDD?.ie Not Working, but Mary@DDD?.ie or Mary1234@DDD?.ie receive email just fine. (False domain @DDD?) Just tried this one MaryKelly@DDD?.ie (No dot . between names) and it works fine. . Anyone come across this one? Many Thanks.

2

Hello Tony,
I thinks it’s a bit hard to help you with such request.

Please share your config and relevant logs.
You can find info about delivered mail under the postifx tag inside the logs.

3

Here is a log file from NS8 mail1 - Node 1. Won’t allow to upload a TXT file so Ill paste in in next reply.

4

NS8 Mail1

2026-05-13T14:22:13+01:00 [1:mail1:postfix/smtpd] connect from unknown[81.30.98.32]
2026-05-13T14:22:13+01:00 [1:mail1:postfix/smtpd] Anonymous TLS connection established from unknown[81.30.98.32]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
2026-05-13T14:22:13+01:00 [1:mail1:rspamd] (rspamd_proxy) <02964e>; proxy; proxy_accept_socket: accepted milter connection from 127.0.0.1 port 57904
2026-05-13T14:22:14+01:00 [1:mail1:dovecot] auth-worker(3978): conn unix:auth-worker (pid=3941,uid=90): auth-worker<1>: ldap(allen,81.30.98.32): unknown user
2026-05-13T14:22:16+01:00 [1:mail1:postfix/smtpd] warning: unknown[81.30.98.32]: SASL LOGIN authentication failed: (reason unavailable), sasl_username=allen
2026-05-13T14:22:16+01:00 [1:mail1:postfix/smtpd] lost connection after AUTH from unknown[81.30.98.32]
2026-05-13T14:22:16+01:00 [1:mail1:postfix/smtpd] disconnect from unknown[81.30.98.32] ehlo=1 auth=0/1 rset=1 commands=2/3
2026-05-13T14:22:16+01:00 [1:mail1:rspamd] (rspamd_proxy) <02964e>; milter; rspamd_milter_process_command: got connection from 81.30.98.32:10822
2026-05-13T14:22:16+01:00 [1:mail1:rspamd] (rspamd_proxy) <02964e>; proxy; proxy_milter_finish_handler: finished milter connection
2026-05-13T14:22:33+01:00 [1:mail1:postfix/smtpd] connect from unknown[81.30.98.47]
2026-05-13T14:22:34+01:00 [1:mail1:postfix/smtpd] Anonymous TLS connection established from unknown[81.30.98.47]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
2026-05-13T14:22:34+01:00 [1:mail1:rspamd] (rspamd_proxy) <d6645b>; proxy; proxy_accept_socket: accepted milter connection from 127.0.0.1 port 52166
2026-05-13T14:22:35+01:00 [1:mail1:dovecot] auth-worker(3978): conn unix:auth-worker (pid=3941,uid=90): auth-worker<2>: ldap(wpsadmin,81.30.98.47): unknown user
2026-05-13T14:22:37+01:00 [1:mail1:postfix/smtpd] warning: unknown[81.30.98.47]: SASL LOGIN authentication failed: (reason unavailable), sasl_username=wpsadmin
2026-05-13T14:22:37+01:00 [1:mail1:postfix/smtpd] lost connection after AUTH from unknown[81.30.98.47]
2026-05-13T14:22:37+01:00 [1:mail1:postfix/smtpd] disconnect from unknown[81.30.98.47] ehlo=1 auth=0/1 rset=1 commands=2/3
2026-05-13T14:22:37+01:00 [1:mail1:rspamd] (rspamd_proxy) <d6645b>; milter; rspamd_milter_process_command: got connection from 81.30.98.47:58928
2026-05-13T14:22:37+01:00 [1:mail1:rspamd] (rspamd_proxy) <d6645b>; proxy; proxy_milter_finish_handler: finished milter connection
2026-05-13T14:22:48+01:00 [1:mail1:postfix/smtpd] connect from unknown[81.30.98.194]
2026-05-13T14:22:48+01:00 [1:mail1:postfix/smtpd] Anonymous TLS connection established from unknown[81.30.98.194]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
2026-05-13T14:22:48+01:00 [1:mail1:rspamd] (rspamd_proxy) <cc0547>; proxy; proxy_accept_socket: accepted milter connection from 127.0.0.1 port 39168
2026-05-13T14:22:48+01:00 [1:mail1:dovecot] auth-worker(3978): conn unix:auth-worker (pid=3941,uid=90): auth-worker<3>: ldap(yjs,81.30.98.194): unknown user
2026-05-13T14:22:50+01:00 [1:mail1:postfix/smtpd] warning: unknown[81.30.98.194]: SASL LOGIN authentication failed: (reason unavailable), sasl_username=yjs
2026-05-13T14:22:50+01:00 [1:mail1:postfix/smtpd] lost connection after AUTH from unknown[81.30.98.194]
2026-05-13T14:22:50+01:00 [1:mail1:postfix/smtpd] disconnect from unknown[81.30.98.194] ehlo=1 auth=0/1 rset=1 commands=2/3
2026-05-13T14:22:50+01:00 [1:mail1:rspamd] (rspamd_proxy) <cc0547>; milter; rspamd_milter_process_command: got connection from 81.30.98.194:14390
2026-05-13T14:22:50+01:00 [1:mail1:rspamd] (rspamd_proxy) <cc0547>; proxy; proxy_milter_finish_handler: finished milter connection
2026-05-13T14:23:01+01:00 [1:mail1:postfix/smtpd] connect from unknown[81.30.98.44]
2026-05-13T14:23:01+01:00 [1:mail1:postfix/smtpd] Anonymous TLS connection established from unknown[81.30.98.44]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
2026-05-13T14:23:01+01:00 [1:mail1:rspamd] (rspamd_proxy) <f3054a>; proxy; proxy_accept_socket: accepted milter connection from 127.0.0.1 port 47808
2026-05-13T14:23:02+01:00 [1:mail1:dovecot] auth-worker(3978): conn unix:auth-worker (pid=3941,uid=90): auth-worker<4>: ldap(yamada,81.30.98.44): unknown user
2026-05-13T14:23:04+01:00 [1:mail1:postfix/smtpd] warning: unknown[81.30.98.44]: SASL LOGIN authentication failed: (reason unavailable), sasl_username=yamada
2026-05-13T14:23:04+01:00 [1:mail1:postfix/smtpd] lost connection after AUTH from unknown[81.30.98.44]
2026-05-13T14:23:04+01:00 [1:mail1:postfix/smtpd] disconnect from unknown[81.30.98.44] ehlo=1 auth=0/1 rset=1 commands=2/3
2026-05-13T14:23:04+01:00 [1:mail1:rspamd] (rspamd_proxy) <f3054a>; milter; rspamd_milter_process_command: got connection from 81.30.98.44:5380
2026-05-13T14:23:04+01:00 [1:mail1:rspamd] (rspamd_proxy) <f3054a>; proxy; proxy_milter_finish_handler: finished milter connection
2026-05-13T14:23:16+01:00 [1:mail1:rspamd] (controller) <5t8s4f>; map; http_map_finish: data is not modified for server sa-update.surbl.org, next check at Wed, 13 May 2026 13:28:16 GMT (timer based)
2026-05-13T14:23:18+01:00 [1:mail1:postfix/smtpd] connect from unknown[81.30.98.90]
2026-05-13T14:23:18+01:00 [1:mail1:postfix/smtpd] Anonymous TLS connection established from unknown[81.30.98.90]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
2026-05-13T14:23:18+01:00 [1:mail1:rspamd] (rspamd_proxy) <508c0f>; proxy; proxy_accept_socket: accepted milter connection from 127.0.0.1 port 45078
2026-05-13T14:23:18+01:00 [1:mail1:dovecot] auth-worker(3978): conn unix:auth-worker (pid=3941,uid=90): auth-worker<5>: ldap(tjj,81.30.98.90): unknown user
2026-05-13T14:23:20+01:00 [1:mail1:postfix/smtpd] warning: unknown[81.30.98.90]: SASL LOGIN authentication failed: (reason unavailable), sasl_username=tjj
2026-05-13T14:23:20+01:00 [1:mail1:postfix/smtpd] lost connection after AUTH from unknown[81.30.98.90]
2026-05-13T14:23:20+01:00 [1:mail1:postfix/smtpd] disconnect from unknown[81.30.98.90] ehlo=1 auth=0/1 rset=1 commands=2/3
2026-05-13T14:23:20+01:00 [1:mail1:rspamd] (rspamd_proxy) <508c0f>; milter; rspamd_milter_process_command: got connection from 81.30.98.90:1074
2026-05-13T14:23:20+01:00 [1:mail1:rspamd] (rspamd_proxy) <508c0f>; proxy; proxy_milter_finish_handler: finished milter connection
2026-05-13T14:25:08+01:00 [1:mail1:postfix/smtpd] connect from unknown[81.30.98.49]
2026-05-13T14:25:08+01:00 [1:mail1:postfix/smtpd] Anonymous TLS connection established from unknown[81.30.98.49]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
2026-05-13T14:25:08+01:00 [1:mail1:rspamd] (rspamd_proxy) <b061c3>; proxy; proxy_accept_socket: accepted milter connection from 127.0.0.1 port 35184
2026-05-13T14:25:08+01:00 [1:mail1:dovecot] auth-worker(3979): conn unix:auth-worker (pid=3941,uid=90): auth-worker<1>: ldap(kj,81.30.98.49): unknown user
2026-05-13T14:25:10+01:00 [1:mail1:postfix/smtpd] warning: unknown[81.30.98.49]: SASL LOGIN authentication failed: (reason unavailable), sasl_username=kj
2026-05-13T14:25:10+01:00 [1:mail1:postfix/smtpd] lost connection after AUTH from unknown[81.30.98.49]
2026-05-13T14:25:10+01:00 [1:mail1:postfix/smtpd] disconnect from unknown[81.30.98.49] ehlo=1 auth=0/1 rset=1 commands=2/3
2026-05-13T14:25:10+01:00 [1:mail1:rspamd] (rspamd_proxy) <b061c3>; milter; rspamd_milter_process_command: got connection from 81.30.98.49:33334
2026-05-13T14:25:10+01:00 [1:mail1:rspamd] (rspamd_proxy) <b061c3>; proxy; proxy_milter_finish_handler: finished milter connection
2026-05-13T14:27:16+01:00 [1:mail1:postfix/smtpd] connect from unknown[81.30.98.181]
2026-05-13T14:27:16+01:00 [1:mail1:postfix/smtpd] Anonymous TLS connection established from unknown[81.30.98.181]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
2026-05-13T14:27:16+01:00 [1:mail1:rspamd] (rspamd_proxy) <80e975>; proxy; proxy_accept_socket: accepted milter connection from 127.0.0.1 port 38456
2026-05-13T14:27:16+01:00 [1:mail1:dovecot] auth-worker(3980): conn unix:auth-worker (pid=3941,uid=90): auth-worker<1>: ldap(pierangelo,81.30.98.181): unknown user
2026-05-13T14:27:18+01:00 [1:mail1:postfix/smtpd] warning: unknown[81.30.98.181]: SASL LOGIN authentication failed: (reason unavailable), sasl_username=pierangelo
2026-05-13T14:27:18+01:00 [1:mail1:postfix/smtpd] lost connection after AUTH from unknown[81.30.98.181]
2026-05-13T14:27:18+01:00 [1:mail1:postfix/smtpd] disconnect from unknown[81.30.98.181] ehlo=1 auth=0/1 rset=1 commands=2/3
2026-05-13T14:27:18+01:00 [1:mail1:rspamd] (rspamd_proxy) <80e975>; milter; rspamd_milter_process_command: got connection from 81.30.98.181:32154
2026-05-13T14:27:18+01:00 [1:mail1:rspamd] (rspamd_proxy) <80e975>; proxy; proxy_milter_finish_handler: finished milter connection
2026-05-13T14:27:32+01:00 [1:mail1:rspamd] (controller) <s4ti79>; monitored; rspamd_monitored_dns_cb: DNS reply returned 'no error' for score.senderscore.com while 'no records with this name' was expected when querying for '1.0.0.127.score.senderscore.com'(likely DNS spoofing or BL internal issues)
2026-05-13T14:28:39+01:00 [1:mail1:postfix/smtpd] connect from unknown[81.30.98.52]
2026-05-13T14:28:39+01:00 [1:mail1:postfix/smtpd] Anonymous TLS connection established from unknown[81.30.98.52]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
2026-05-13T14:28:39+01:00 [1:mail1:rspamd] (rspamd_proxy) <f7ea0d>; proxy; proxy_accept_socket: accepted milter connection from 127.0.0.1 port 32886
2026-05-13T14:28:39+01:00 [1:mail1:dovecot] auth-worker(3981): conn unix:auth-worker (pid=3941,uid=90): auth-worker<1>: ldap(oxford,81.30.98.52): unknown user
2026-05-13T14:28:41+01:00 [1:mail1:postfix/smtpd] warning: unknown[81.30.98.52]: SASL LOGIN authentication failed: (reason unavailable), sasl_username=oxford
2026-05-13T14:28:41+01:00 [1:mail1:postfix/smtpd] lost connection after AUTH from unknown[81.30.98.52]
2026-05-13T14:28:41+01:00 [1:mail1:postfix/smtpd] disconnect from unknown[81.30.98.52] ehlo=1 auth=0/1 rset=1 commands=2/3
2026-05-13T14:28:41+01:00 [1:mail1:rspamd] (rspamd_proxy) <f7ea0d>; milter; rspamd_milter_process_command: got connection from 81.30.98.52:32140
2026-05-13T14:28:41+01:00 [1:mail1:rspamd] (rspamd_proxy) <f7ea0d>; proxy; proxy_milter_finish_handler: finished milter connection
2026-05-13T14:29:14+01:00 [1:mail1:postfix/anvil] statistics: max connection rate 1/60s for (submissions:81.30.98.158) at May 13 13:19:14
2026-05-13T14:29:14+01:00 [1:mail1:postfix/anvil] statistics: max connection count 1 for (submissions:81.30.98.158) at May 13 13:19:14
2026-05-13T14:29:14+01:00 [1:mail1:postfix/anvil] statistics: max cache size 4 at May 13 13:23:01
2026-05-13T14:30:12+01:00 [1:mail1:postfix/smtpd] connect from unknown[81.30.98.66]
2026-05-13T14:30:12+01:00 [1:mail1:postfix/smtpd] Anonymous TLS connection established from unknown[81.30.98.66]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
2026-05-13T14:30:12+01:00 [1:mail1:rspamd] (rspamd_proxy) <382849>; proxy; proxy_accept_socket: accepted milter connection from 127.0.0.1 port 56846
2026-05-13T14:30:13+01:00 [1:mail1:dovecot] auth-worker(3982): conn unix:auth-worker (pid=3941,uid=90): auth-worker<1>: ldap(planner,81.30.98.66): unknown user
2026-05-13T14:30:15+01:00 [1:mail1:postfix/smtpd] warning: unknown[81.30.98.66]: SASL LOGIN authentication failed: (reason unavailable), sasl_username=planner
2026-05-13T14:30:15+01:00 [1:mail1:postfix/smtpd] lost connection after AUTH from unknown[81.30.98.66]
2026-05-13T14:30:15+01:00 [1:mail1:postfix/smtpd] disconnect from unknown[81.30.98.66] ehlo=1 auth=0/1 rset=1 commands=2/3
2026-05-13T14:30:15+01:00 [1:mail1:rspamd] (rspamd_proxy) <382849>; milter; rspamd_milter_process_command: got connection from 81.30.98.66:5664
2026-05-13T14:30:15+01:00 [1:mail1:rspamd] (rspamd_proxy) <382849>; proxy; proxy_milter_finish_handler: finished milter connection
2026-05-13T14:31:35+01:00 [1:mail1:rspamd] (controller) <5t8s4f>; map; http_map_finish: data is not modified for server sa-update.surbl.org, next check at Wed, 13 May 2026 13:36:35 GMT (timer based)
2026-05-13T14:32:41+01:00 [1:mail1:postfix/smtpd] connect from unknown[81.30.98.207]
2026-05-13T14:32:41+01:00 [1:mail1:postfix/smtpd] Anonymous TLS connection established from unknown[81.30.98.207]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
2026-05-13T14:32:41+01:00 [1:mail1:rspamd] (rspamd_proxy) <3fef00>; proxy; proxy_accept_socket: accepted milter connection from 127.0.0.1 port 46360
2026-05-13T14:32:41+01:00 [1:mail1:dovecot] auth-worker(3983): conn unix:auth-worker (pid=3941,uid=90): auth-worker<1>: ldap(paging,81.30.98.207): unknown user
2026-05-13T14:32:43+01:00 [1:mail1:postfix/smtpd] warning: unknown[81.30.98.207]: SASL LOGIN authentication failed: (reason unavailable), sasl_username=paging
2026-05-13T14:32:43+01:00 [1:mail1:postfix/smtpd] lost connection after AUTH from unknown[81.30.98.207]
2026-05-13T14:32:43+01:00 [1:mail1:postfix/smtpd] disconnect from unknown[81.30.98.207] ehlo=1 auth=0/1 rset=1 commands=2/3
2026-05-13T14:32:43+01:00 [1:mail1:rspamd] (rspamd_proxy) <3fef00>; milter; rspamd_milter_process_command: got connection from 81.30.98.207:44580
2026-05-13T14:32:43+01:00 [1:mail1:rspamd] (rspamd_proxy) <3fef00>; proxy; proxy_milter_finish_handler: finished milter connection
2026-05-13T14:33:03+01:00 [1:mail1:postfix/smtpd] connect from unknown[81.30.98.33]
2026-05-13T14:33:04+01:00 [1:mail1:postfix/smtpd] Anonymous TLS connection established from unknown[81.30.98.33]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
2026-05-13T14:33:04+01:00 [1:mail1:rspamd] (rspamd_proxy) <208f10>; proxy; proxy_accept_socket: accepted milter connection from 127.0.0.1 port 50874
2026-05-13T14:33:05+01:00 [1:mail1:dovecot] auth-worker(3983): conn unix:auth-worker (pid=3941,uid=90): auth-worker<2>: ldap(klein,81.30.98.33): unknown user
2026-05-13T14:33:07+01:00 [1:mail1:postfix/smtpd] warning: unknown[81.30.98.33]: SASL LOGIN authentication failed: (reason unavailable), sasl_username=klein
2026-05-13T14:33:07+01:00 [1:mail1:postfix/smtpd] lost connection after AUTH from unknown[81.30.98.33]
2026-05-13T14:33:07+01:00 [1:mail1:postfix/smtpd] disconnect from unknown[81.30.98.33] ehlo=1 auth=0/1 rset=1 commands=2/3
2026-05-13T14:33:07+01:00 [1:mail1:rspamd] (rspamd_proxy) <208f10>; milter; rspamd_milter_process_command: got connection from 81.30.98.33:61044
2026-05-13T14:33:07+01:00 [1:mail1:rspamd] (rspamd_proxy) <208f10>; proxy; proxy_milter_finish_handler: finished milter connection
2026-05-13T14:33:32+01:00 [1:mail1:postfix/smtpd] connect from unknown[81.30.98.142]
2026-05-13T14:33:32+01:00 [1:mail1:postfix/smtpd] Anonymous TLS connection established from unknown[81.30.98.142]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
2026-05-13T14:33:32+01:00 [1:mail1:rspamd] (rspamd_proxy) <a437e1>; proxy; proxy_accept_socket: accepted milter connection from 127.0.0.1 port 59302
2026-05-13T14:33:33+01:00 [1:mail1:dovecot] auth-worker(3983): conn unix:auth-worker (pid=3941,uid=90): auth-worker<3>: ldap(host1,81.30.98.142): unknown user
2026-05-13T14:33:35+01:00 [1:mail1:postfix/smtpd] warning: unknown[81.30.98.142]: SASL LOGIN authentication failed: (reason unavailable), sasl_username=host1
2026-05-13T14:33:35+01:00 [1:mail1:postfix/smtpd] lost connection after AUTH from unknown[81.30.98.142]
2026-05-13T14:33:35+01:00 [1:mail1:postfix/smtpd] disconnect from unknown[81.30.98.142] ehlo=1 auth=0/1 rset=1 commands=2/3
2026-05-13T14:33:35+01:00 [1:mail1:rspamd] (rspamd_proxy) <a437e1>; milter; rspamd_milter_process_command: got connection from 81.30.98.142:65504
2026-05-13T14:33:35+01:00 [1:mail1:rspamd] (rspamd_proxy) <a437e1>; proxy; proxy_milter_finish_handler: finished milter connection
2026-05-13T14:35:45+01:00 [1:mail1:postfix/smtpd] connect from unknown[81.30.98.53]
2026-05-13T14:35:45+01:00 [1:mail1:postfix/smtpd] Anonymous TLS connection established from unknown[81.30.98.53]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
2026-05-13T14:35:45+01:00 [1:mail1:rspamd] (rspamd_proxy) <1e3d37>; proxy; proxy_accept_socket: accepted milter connection from 127.0.0.1 port 57484
2026-05-13T14:35:48+01:00 [1:mail1:dovecot] auth-worker(3984): conn unix:auth-worker (pid=3941,uid=90): auth-worker<1>: ldap(web0f1,81.30.98.53): unknown user
2026-05-13T14:35:50+01:00 [1:mail1:postfix/smtpd] warning: unknown[81.30.98.53]: SASL LOGIN authentication failed: (reason unavailable), sasl_username=web0f1
2026-05-13T14:35:50+01:00 [1:mail1:postfix/smtpd] lost connection after AUTH from unknown[81.30.98.53]
2026-05-13T14:35:50+01:00 [1:mail1:postfix/smtpd] disconnect from unknown[81.30.98.53] ehlo=1 auth=0/1 rset=1 commands=2/3
2026-05-13T14:35:50+01:00 [1:mail1:rspamd] (rspamd_proxy) <1e3d37>; milter; rspamd_milter_process_command: got connection from 81.30.98.53:49488
2026-05-13T14:35:50+01:00 [1:mail1:rspamd] (rspamd_proxy) <1e3d37>; proxy; proxy_milter_finish_handler: finished milter connection
2026-05-13T14:35:59+01:00 [1:mail1:postfix/smtpd] connect from unknown[81.30.98.77]
2026-05-13T14:35:59+01:00 [1:mail1:postfix/smtpd] Anonymous TLS connection established from unknown[81.30.98.77]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
2026-05-13T14:35:59+01:00 [1:mail1:rspamd] (rspamd_proxy) <3cf1f2>; proxy; proxy_accept_socket: accepted milter connection from 127.0.0.1 port 41002
2026-05-13T14:35:59+01:00 [1:mail1:dovecot] auth-worker(3984): conn unix:auth-worker (pid=3941,uid=90): auth-worker<2>: ldap(takata,81.30.98.77): unknown user
2026-05-13T14:36:01+01:00 [1:mail1:postfix/smtpd] warning: unknown[81.30.98.77]: SASL LOGIN authentication failed: (reason unavailable), sasl_username=takata
2026-05-13T14:36:01+01:00 [1:mail1:postfix/smtpd] lost connection after AUTH from unknown[81.30.98.77]
2026-05-13T14:36:01+01:00 [1:mail1:postfix/smtpd] disconnect from unknown[81.30.98.77] ehlo=1 auth=0/1 rset=1 commands=2/3
2026-05-13T14:36:01+01:00 [1:mail1:rspamd] (rspamd_proxy) <3cf1f2>; milter; rspamd_milter_process_command: got connection from 81.30.98.77:49134
2026-05-13T14:36:01+01:00 [1:mail1:rspamd] (rspamd_proxy) <3cf1f2>; proxy; proxy_milter_finish_handler: finished milter connection
2026-05-13T14:37:03+01:00 [1:mail1:rspamd] (controller) <5t8s4f>; map; http_map_finish: data is not modified for server sa-update.surbl.org, next check at Wed, 13 May 2026 13:42:03 GMT (timer based)
2026-05-13T14:37:51+01:00 [1:mail1:postfix/smtpd] connect from unknown[81.30.98.62]
2026-05-13T14:37:51+01:00 [1:mail1:postfix/smtpd] Anonymous TLS connection established from unknown[81.30.98.62]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
2026-05-13T14:37:51+01:00 [1:mail1:rspamd] (rspamd_proxy) <579998>; proxy; proxy_accept_socket: accepted milter connection from 127.0.0.1 port 59008
2026-05-13T14:37:51+01:00 [1:mail1:dovecot] auth-worker(3985): conn unix:auth-worker (pid=3941,uid=90): auth-worker<1>: ldap(other,81.30.98.62): unknown user
2026-05-13T14:37:53+01:00 [1:mail1:postfix/smtpd] warning: unknown[81.30.98.62]: SASL LOGIN authentication failed: (reason unavailable), sasl_username=other
2026-05-13T14:37:53+01:00 [1:mail1:postfix/smtpd] lost connection after AUTH from unknown[81.30.98.62]
2026-05-13T14:37:53+01:00 [1:mail1:postfix/smtpd] disconnect from unknown[81.30.98.62] ehlo=1 auth=0/1 rset=1 commands=2/3
2026-05-13T14:37:53+01:00 [1:mail1:rspamd] (rspamd_proxy) <579998>; milter; rspamd_milter_process_command: got connection from 81.30.98.62:10476
2026-05-13T14:37:53+01:00 [1:mail1:rspamd] (rspamd_proxy) <579998>; proxy; proxy_milter_finish_handler: finished milter connection
2026-05-13T14:38:31+01:00 [1:mail1:postfix/smtpd] connect from unknown[81.30.98.144]
2026-05-13T14:38:31+01:00 [1:mail1:postfix/smtpd] Anonymous TLS connection established from unknown[81.30.98.144]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
2026-05-13T14:38:31+01:00 [1:mail1:rspamd] (rspamd_proxy) <996f7a>; proxy; proxy_accept_socket: accepted milter connection from 127.0.0.1 port 38976
2026-05-13T14:38:31+01:00 [1:mail1:dovecot] auth-worker(3985): conn unix:auth-worker (pid=3941,uid=90): auth-worker<2>: ldap(s203,81.30.98.144): unknown user
2026-05-13T14:38:33+01:00 [1:mail1:postfix/smtpd] warning: unknown[81.30.98.144]: SASL LOGIN authentication failed: (reason unavailable), sasl_username=s203
2026-05-13T14:38:33+01:00 [1:mail1:postfix/smtpd] lost connection after AUTH from unknown[81.30.98.144]
2026-05-13T14:38:33+01:00 [1:mail1:postfix/smtpd] disconnect from unknown[81.30.98.144] ehlo=1 auth=0/1 rset=1 commands=2/3
2026-05-13T14:38:33+01:00 [1:mail1:rspamd] (rspamd_proxy) <996f7a>; milter; rspamd_milter_process_command: got connection from 81.30.98.144:47516
2026-05-13T14:38:33+01:00 [1:mail1:rspamd] (rspamd_proxy) <996f7a>; proxy; proxy_milter_finish_handler: finished milter connection
2026-05-13T14:39:09+01:00 [1:mail1:postfix/smtpd] connect from unknown[81.30.98.201]
2026-05-13T14:39:09+01:00 [1:mail1:postfix/smtpd] Anonymous TLS connection established from unknown[81.30.98.201]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
2026-05-13T14:39:09+01:00 [1:mail1:rspamd] (rspamd_proxy) <b178be>; proxy; proxy_accept_socket: accepted milter connection from 127.0.0.1 port 57018
2026-05-13T14:39:10+01:00 [1:mail1:dovecot] auth-worker(3985): conn unix:auth-worker (pid=3941,uid=90): auth-worker<3>: ldap(museum,81.30.98.201): unknown user
2026-05-13T14:39:12+01:00 [1:mail1:postfix/smtpd] warning: unknown[81.30.98.201]: SASL LOGIN authentication failed: (reason unavailable), sasl_username=museum
2026-05-13T14:39:12+01:00 [1:mail1:postfix/smtpd] lost connection after AUTH from unknown[81.30.98.201]
2026-05-13T14:39:12+01:00 [1:mail1:postfix/smtpd] disconnect from unknown[81.30.98.201] ehlo=1 auth=0/1 rset=1 commands=2/3
2026-05-13T14:39:12+01:00 [1:mail1:rspamd] (rspamd_proxy) <b178be>; milter; rspamd_milter_process_command: got connection from 81.30.98.201:35874
2026-05-13T14:39:12+01:00 [1:mail1:rspamd] (rspamd_proxy) <b178be>; proxy; proxy_milter_finish_handler: finished milter connection
2026-05-13T14:39:14+01:00 [1:mail1:postfix/anvil] statistics: max connection rate 1/60s for (submissions:81.30.98.66) at May 13 13:30:12
2026-05-13T14:39:14+01:00 [1:mail1:postfix/anvil] statistics: max connection count 1 for (submissions:81.30.98.66) at May 13 13:30:12
2026-05-13T14:39:14+01:00 [1:mail1:postfix/anvil] statistics: max cache size 3 at May 13 13:33:32
2026-05-13T14:40:59+01:00 [1:mail1:rspamd] (controller) <s4ti79>; monitored; rspamd_monitored_dns_cb: DNS reply returned 'no error' for score.senderscore.com while 'no records with this name' was expected when querying for '1.0.0.127.score.senderscore.com'(likely DNS spoofing or BL internal issues)
2026-05-13T14:41:19+01:00 [1:mail1:postfix/smtpd] connect from unknown[81.30.98.84]
2026-05-13T14:41:19+01:00 [1:mail1:postfix/smtpd] Anonymous TLS connection established from unknown[81.30.98.84]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
2026-05-13T14:41:19+01:00 [1:mail1:rspamd] (rspamd_proxy) <509cd4>; proxy; proxy_accept_socket: accepted milter connection from 127.0.0.1 port 35436
2026-05-13T14:41:19+01:00 [1:mail1:dovecot] auth-worker(3986): conn unix:auth-worker (pid=3941,uid=90): auth-worker<1>: ldap(hamza,81.30.98.84): unknown user
2026-05-13T14:41:21+01:00 [1:mail1:postfix/smtpd] warning: unknown[81.30.98.84]: SASL LOGIN authentication failed: (reason unavailable), sasl_username=hamza
2026-05-13T14:41:21+01:00 [1:mail1:postfix/smtpd] lost connection after AUTH from unknown[81.30.98.84]
2026-05-13T14:41:21+01:00 [1:mail1:postfix/smtpd] disconnect from unknown[81.30.98.84] ehlo=1 auth=0/1 rset=1 commands=2/3
2026-05-13T14:41:21+01:00 [1:mail1:rspamd] (rspamd_proxy) <509cd4>; milter; rspamd_milter_process_command: got connection from 81.30.98.84:15394
2026-05-13T14:41:21+01:00 [1:mail1:rspamd] (rspamd_proxy) <509cd4>; proxy; proxy_milter_finish_handler: finished milter connection
2026-05-13T14:42:49+01:00 [1:mail1:rspamd] (controller) <5t8s4f>; map; http_map_finish: data is not modified for server sa-update.surbl.org, next check at Wed, 13 May 2026 13:47:49 GMT (timer based)
2026-05-13T14:43:32+01:00 [1:mail1:postfix/smtpd] connect from unknown[81.30.98.174]
2026-05-13T14:43:32+01:00 [1:mail1:postfix/smtpd] Anonymous TLS connection established from unknown[81.30.98.174]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
2026-05-13T14:43:32+01:00 [1:mail1:rspamd] (rspamd_proxy) <feb3fb>; proxy; proxy_accept_socket: accepted milter connection from 127.0.0.1 port 38800
2026-05-13T14:43:33+01:00 [1:mail1:dovecot] auth-worker(3987): conn unix:auth-worker (pid=3941,uid=90): auth-worker<1>: ldap(gpadmin,81.30.98.174): unknown user
2026-05-13T14:43:35+01:00 [1:mail1:postfix/smtpd] warning: unknown[81.30.98.174]: SASL LOGIN authentication failed: (reason unavailable), sasl_username=gpadmin
2026-05-13T14:43:35+01:00 [1:mail1:postfix/smtpd] lost connection after AUTH from unknown[81.30.98.174]
2026-05-13T14:43:35+01:00 [1:mail1:postfix/smtpd] disconnect from unknown[81.30.98.174] ehlo=1 auth=0/1 rset=1 commands=2/3
2026-05-13T14:43:35+01:00 [1:mail1:rspamd] (rspamd_proxy) <feb3fb>; milter; rspamd_milter_process_command: got connection from 81.30.98.174:19560
2026-05-13T14:43:35+01:00 [1:mail1:rspamd] (rspamd_proxy) <feb3fb>; proxy; proxy_milter_finish_handler: finished milter connection
2026-05-13T14:43:40+01:00 [1:mail1:postfix/smtpd] connect from unknown[81.30.98.158]
2026-05-13T14:43:40+01:00 [1:mail1:postfix/smtpd] Anonymous TLS connection established from unknown[81.30.98.158]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
5

Google AI sorted it. The dot was causing the issue. Here is the procedure.

Recommended Next Step

Please send a fresh test email from an external account to Mary.Kelly@DDD?.ie. Right after doing so, run the grep or journalctl command above and paste the lines matching “mary”.

Additionally, what is the exact output of running postconf recipient_delimiter inside your Postfix instance?

AI responses may include mistakes. Learn more

root@debian13:~# postconf recipient_delimiter -bash: postconf: command not found

Because NethServer 8 uses a modern microservices architecture running inside Podman containers, Postfix is not installed directly on your Debian 13 host. This is why the postconf command is not found.

Step 1: Run the command inside the Mail container

To inspect or query the Postfix configuration, you must execute the command directly inside the running mail1 podman container.

Run this exact command on your Debian host:

bash

podman exec -ti mail1 postconf recipient_delimiter

Use code with caution.

Step 2: Extract the Mary.Kelly logs via Journalctl

Because NethServer 8 logs to the systemd journal instead of traditional flat text files, you need to extract the mail application logs through journalctl on your host.

Run this command to see exactly what happens to the incoming emails for Mary:

bash

journalctl _CONTAINER_NAME=mail1 | grep -i "mary"

Use code with caution.

Expected Outcomes and Fixes

Once you run the commands above, you will see one of two problems:

  1. If recipient_delimiter = . is returned:
    Postfix is actively splitting the email address at the dot. It treats Mary.Kelly as user Mary with an extension string of Kelly. Because an account or alias for Mary already exists, Postfix routes the mail directly into the Mary inbox or drops it due to conflict.
  2. If the logs show User unknown in virtual mailbox table:
    The NethServer 8 Account Provider backend (OpenLDAP or Samba Active Directory) is rejecting the dot character inside the user lookup map configuration.

Please run those two updated commands and paste the output so we can apply the precise template fix inside NethServer 8.

AI responses may include mistakes. Learn more

root@debian13:~# podman exec -ti mail1 postconf recipient_delimiter Error: no container with name or ID “mail1” found: no such container

In NethServer 8, modules run as distinct unprivileged users rather than global root containers. Because of this, the podman command executed as root cannot see the containers running inside the user-space context. [1]

To run the configuration inspection command successfully, you must direct podman to run under the specific service context of the mail application.

Step 1: Identify and Execute inside the Mail Container

Run this exact command on your Debian 13 host terminal to execute postconf inside the correct container namespace:

bash

runuser -l mail1 -c "podman exec -ti postfix postconf recipient_delimiter"

Use code with caution.

(Note: If your system assigned a different module ID during installation, replace mail1 with the respective module username).

Step 2: Extract Relevant Logs

To query logs safely across user-space boundaries on NethServer 8, utilize systemd’s journal filtered by the exact system unit file. Run this to trace what happens to inbound emails containing the dot character: [1]

bash

journalctl -u mail1 | grep -i "mary"

Use code with caution.

Next Steps and Resolution Paths

Once you get the outputs from the commands above, the resolution path will split based on the following rules:

  1. If the output returns recipient_delimiter = .:
    This confirms Postfix is treating Mary.Kelly as the primary user Mary plus an extension tag (Kelly). Because you already have a Mary user active, the system misroutes the email. You will need to change the global delimiter to a different character (like +) inside the NethServer template definitions.
  2. If the log output returns User unknown:
    The issue is not Postfix, but rather the underlying directory server backend (OpenLDAP or Samba Active Directory) filtering out or mishandling dots inside lookup queries.

Run these two revised commands and provide the output lines so we can specify the exact text template change needed for your server.

AI responses may include mistakes. Learn more

[image]

2 sites

  • Howto manage or customize NS8 podman containers

12 Jun 2025 — Podman provides rootless containers which are running as user. Most NS8 apps make use of these rootless containers. Those apps are…

[image]

[image]

NethServer Community

  • Podman-compose to automate setup - NethServer Community

8 Feb 2023 — Thanks. For most systems we are using Openshift and Helm but Podman is also OK. The script is a doable solution. We want to be abl…

[image]

[image]

NethServer Community

recipient_delimiter = + root@debian13:~# root@debian13:~# journalctl -u mail1 | grep -i “mary” root@debian13:~# root@debian13:~# runuser -l mail1 -c “podman exec -ti postfix postconf recipient_delimiter” recipient_delimiter = +

Since recipient_delimiter = + is configured, Postfix is not splitting the name at the dot. Because journalctl -u mail1 | grep -i "mary" returned absolutely nothing, the email traffic for Mary.Kelly@DDD?.ie is never reaching your Postfix server at all.

When a specific format like MaryKelly@ reaches your server but Mary.Kelly@ yields zero log lines, the issue is happening upstream before the data hits your Debian box.

  1. Check Your Upstream Spam Filter or Mail Gateway

If your domain uses an external security gateway (such as Proxmox Mail Gateway, Barracuda, Cloudflare Email Routing, or an ISP spam filter) before forwarding mail to your NethServer 8 box:

  • That upstream gateway likely has an outdated local user cache or validation rule.
  • It is rejecting Mary.Kelly@ at the perimeter gateway layer and dropping it before your server can log the connection.
  • Fix: Log into your upstream filtering panel, clear the recipient verification cache, or manually add the Mary.Kelly@ alias there.
  1. Verify External DNS MX Records

Ensure your domain does not have multiple MX records pointing to different servers where one server handles the dot format differently. Run this command to check your external routing:

bash

dig MX yourdomain.ie

Use code with caution.

  1. Generate an Internal Test Log

To prove 100% that your NethServer 8 configuration accepts the dot address perfectly when bypassed by external networks, inject a test email locally from your host command line.

Run this command on your Debian terminal to force an internal SMTP injection:

bash

runuser -l mail1 -c "podman exec -i postfix sendmail -f external-test@example.com Mary.Kelly@yourdomain.ie" <<EOF
Subject: Internal Dot Address Test
This is a local injection test to bypass external networks.
EOF

Use code with caution.

(Replace yourdomain.ie with your true domain string).

Next Steps

  1. Execute the local injection test command above.
  2. Immediately run your log check again: journalctl -u mail1 | grep -i "mary"
  3. If the email arrives in her inbox during this test, you have definitive proof that an upstream external firewall, gateway, or MX router is dropping the external emails.

Let me know if the local injection test successfully creates log entries or delivers the mail.

AI responses may include mistakes. Learn more

This is a local injection test to bypass external networks. Wow, yes working now, many thanks.

That is fantastic news. The local injection test confirming successful delivery means your NethServer 8 configuration, Postfix container, and internal LDAP directory routing are 100% correct and working perfectly.

Since the server handles the dot perfectly when bypassed, the external block is definitely happening at an upstream layer.

Why It Fails From the Outside (And How to Fix It)

When external senders email Mary.Kelly@, the traffic is dropped or misrouted before it can ever hit your Debian 13 server. Check these three external locations to completely resolve the issue:

  1. Upstream Mail Filtering Gateways (Most Likely)

If you route your domain’s inbound email through an external security cleaning service (such as Proxmox Mail Gateway, Barracuda, SpamTitan, or your ISP’s perimeter filter) before it hits NethServer:

  • The gateway maintains its own Recipient Verification database.
  • It likely cached the old mailbox layout from before your NethServer 8 migration this week.
  • The Fix: Log into your upstream filtering control panel, locate the recipient verification or user cache settings, and run a sync/clear cache operation. If it does not use automatic sync, manually add Mary.Kelly@yourdomain.ie to the allowed recipient list inside that gateway.
  1. Cloudflare or DNS Email Routing

If your domain’s DNS is managed via Cloudflare or a similar provider, check if Email Routing features are toggled on:

  • Active DNS-level email forwarding rules will intercept explicit address strings and silently drop variants they do not recognize.
  • The Fix: Ensure Cloudflare Email Routing is completely disabled if your NethServer is meant to handle all MX traffic directly, or add the explicit rule for the dot-separated address in their dashboard.
  1. Split-MX or Backup Mail Servers

Check if your public DNS zone contains multiple MX (Mail Exchanger) records with different priority numbers:

  • If a backup MX server exists with an older database, external senders might randomly hit that secondary server, which will reject the dot format.
  • Run dig MX yourdomain.ie to verify that only your new NethServer 8 WAN IP is listed as the destination.

Now that you know your server setup is flawless, check your upstream routing panels or external filter logs to see exactly where those external messages are getting stopped. Let me know if you need help analyzing your upstream filter settings or DNS MX records!