starred/modoboa-modoboa
1
0
Fork 0
mirror of https://github.com/modoboa/modoboa.git synced 2026-04-25 08:56:02 +03:00
Code Issues 60 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #2516] Error sending mail from outside the webmail 451 4.3.5 #1618

New issue
Closed
opened 2026-02-27 11:18:08 +03:00 by kerem · 34 comments
kerem commented 2026-02-27 11:18:08 +03:00
Owner
Copy link

Originally created by @Renaud-DELEIRIS on GitHub (May 17, 2022).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/2516

Impacted versions

  • OS Type: Debian/Ubuntu
  • OS Version: 20.0
  • installer used: Yes
  • Webserver: Nginx

Steps to reproduce

I installed my server
Connect with admin and create simple user email
Send my first email and it work
Receive my first email and it work
I connect my account to outlook with:
mail server: mail.exemple.com
username: user@exemple.com
pass: pass
Incoming port: 993 SSL
Outgoing port: 587 STARTTLS
I connected successfuly and I can see my email

Current behavior

When I try to send email from outlook I got an error
I connected my account with node mailer and I got this error message:
response: '451 4.3.5 rcpt@gmail.com: Recipient address rejected: Server configuration problem'

Expected behavior

I should be able to send my mail from outlook as I do from my webmail

Originally created by @Renaud-DELEIRIS on GitHub (May 17, 2022). Original GitHub issue: https://github.com/modoboa/modoboa/issues/2516 # Impacted versions * OS Type: Debian/Ubuntu * OS Version: 20.0 * installer used: Yes * Webserver: Nginx # Steps to reproduce I installed my server Connect with admin and create simple user email Send my first email and it work Receive my first email and it work I connect my account to outlook with: mail server: mail.exemple.com username: user@exemple.com pass: pass Incoming port: 993 SSL Outgoing port: 587 STARTTLS I connected successfuly and I can see my email # Current behavior When I try to send email from outlook I got an error I connected my account with node mailer and I got this error message: response: '451 4.3.5 <rcpt@gmail.com>: Recipient address rejected: Server configuration problem' <!-- --> # Expected behavior I should be able to send my mail from outlook as I do from my webmail
kerem closed this issue 2026-02-27 11:18:08 +03:00
kerem commented 2026-02-27 11:18:09 +03:00
Author
Owner
Copy link

@tonioo commented on GitHub (May 18, 2022):

@Renaud-DELEIRIS Can you provide more information? Maybe an extract of your mail.log file?

<!-- gh-comment-id:1129762438 --> @tonioo commented on GitHub (May 18, 2022): @Renaud-DELEIRIS Can you provide more information? Maybe an extract of your mail.log file?
kerem commented 2026-02-27 11:18:09 +03:00
Author
Owner
Copy link

@Renaud-DELEIRIS commented on GitHub (May 18, 2022):

Hello,

here it is:

May 18 11:28:33 mail postfix/submission/smtpd[2085751]: connect from SERVERIP.rev.sfr.net[INCOMINGIP]
May 18 11:28:34 mail postfix/submission/smtpd[2085751]: Anonymous TLS connection established from SERVERIP.rev.sfr.net[INCOMINGIP]: TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-si>
May 18 11:28:34 mail dovecot: imap-login: Login: user=<user>, method=PLAIN, rip=INCOMINGIP, lip=SERVERIP, mpid=2085773, TLS, session=<session>
May 18 11:28:35 mail dovecot: imap-login: Login: user=<user>, method=PLAIN, rip=INCOMINGIP, lip=SERVERIP, mpid=2085826, TLS, session=<session>
May 18 11:28:35 mail postfix/submission/smtpd[2085751]: warning: problem talking to server 127.0.0.1:9999: Success
May 18 11:28:35 mail postfix/submission/smtpd[2085751]: NOQUEUE: reject: RCPT from SERVERIP.rev.sfr.net[INCOMINGIP]: 451 4.3.5 <rcpt@gmail.com>: Recipient address rejected: Server configuration problem; from=<support>
May 18 11:28:37 mail postfix/submission/smtpd[2085751]: lost connection after RCPT from SERVERIP.rev.sfr.net[INCOMINGIP]
May 18 11:28:37 mail postfix/submission/smtpd[2085751]: disconnect from SERVERIP.rev.sfr.net[INCOMINGIP] ehlo=2 starttls=1 auth=1 mail=1 rcpt=0/1 commands=5/6
<!-- gh-comment-id:1129902550 --> @Renaud-DELEIRIS commented on GitHub (May 18, 2022): Hello, here it is: ``` May 18 11:28:33 mail postfix/submission/smtpd[2085751]: connect from SERVERIP.rev.sfr.net[INCOMINGIP] May 18 11:28:34 mail postfix/submission/smtpd[2085751]: Anonymous TLS connection established from SERVERIP.rev.sfr.net[INCOMINGIP]: TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-si> May 18 11:28:34 mail dovecot: imap-login: Login: user=<user>, method=PLAIN, rip=INCOMINGIP, lip=SERVERIP, mpid=2085773, TLS, session=<session> May 18 11:28:35 mail dovecot: imap-login: Login: user=<user>, method=PLAIN, rip=INCOMINGIP, lip=SERVERIP, mpid=2085826, TLS, session=<session> May 18 11:28:35 mail postfix/submission/smtpd[2085751]: warning: problem talking to server 127.0.0.1:9999: Success May 18 11:28:35 mail postfix/submission/smtpd[2085751]: NOQUEUE: reject: RCPT from SERVERIP.rev.sfr.net[INCOMINGIP]: 451 4.3.5 <rcpt@gmail.com>: Recipient address rejected: Server configuration problem; from=<support> May 18 11:28:37 mail postfix/submission/smtpd[2085751]: lost connection after RCPT from SERVERIP.rev.sfr.net[INCOMINGIP] May 18 11:28:37 mail postfix/submission/smtpd[2085751]: disconnect from SERVERIP.rev.sfr.net[INCOMINGIP] ehlo=2 starttls=1 auth=1 mail=1 rcpt=0/1 commands=5/6 ```
kerem commented 2026-02-27 11:18:09 +03:00
Author
Owner
Copy link

@tonioo commented on GitHub (May 18, 2022):

Looks like the policy daemon does not start. Can you take a look at supervisor logs?

<!-- gh-comment-id:1129921078 --> @tonioo commented on GitHub (May 18, 2022): Looks like the policy daemon does not start. Can you take a look at supervisor logs?
kerem commented 2026-02-27 11:18:09 +03:00
Author
Owner
Copy link

@Renaud-DELEIRIS commented on GitHub (May 18, 2022):

Thanks for your help!

Can you tell me which one?

…pervisor/policyd-stdout---supervisor-qr70lt0t.log  …pervisor/radicale-stdout---supervisor-g9tvhwup.log  …pervisor/supervisord.log
<!-- gh-comment-id:1129923048 --> @Renaud-DELEIRIS commented on GitHub (May 18, 2022): Thanks for your help! Can you tell me which one? ``` …pervisor/policyd-stdout---supervisor-qr70lt0t.log …pervisor/radicale-stdout---supervisor-g9tvhwup.log …pervisor/supervisord.log ```
kerem commented 2026-02-27 11:18:09 +03:00
Author
Owner
Copy link

@Renaud-DELEIRIS commented on GitHub (May 18, 2022):

Nevermind they are all empty except the short one

2022-05-17 09:52:08,840 INFO waiting for policyd, radicale to die
2022-05-17 09:52:08,986 INFO stopped: radicale (exit status 0)
2022-05-17 09:52:08,986 WARN received SIGTERM indicating exit request
2022-05-17 09:52:10,537 INFO stopped: policyd (exit status 0)
2022-05-17 09:52:12,807 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.
2022-05-17 09:52:12,815 INFO Included extra file "/etc/supervisor/conf.d/policyd.conf" during parsing
2022-05-17 09:52:12,816 INFO Included extra file "/etc/supervisor/conf.d/radicale.conf" during parsing
2022-05-17 09:52:12,843 INFO RPC interface 'supervisor' initialized
2022-05-17 09:52:12,849 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2022-05-17 09:52:12,851 INFO supervisord started with pid 1371770
2022-05-17 09:52:13,854 INFO spawned: 'policyd' with pid 1371896
2022-05-17 09:52:13,858 INFO spawned: 'radicale' with pid 1371897
2022-05-17 09:52:14,877 INFO success: policyd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-17 09:52:14,877 INFO success: radicale entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-17 09:52:24,510 INFO waiting for policyd, radicale to die
2022-05-17 09:52:24,583 INFO stopped: radicale (exit status 0)
2022-05-17 09:52:24,583 WARN received SIGTERM indicating exit request
2022-05-17 09:52:25,021 INFO stopped: policyd (exit status 0)
2022-05-17 09:52:26,594 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.
2022-05-17 09:52:26,594 INFO Included extra file "/etc/supervisor/conf.d/policyd.conf" during parsing
2022-05-17 09:52:26,594 INFO Included extra file "/etc/supervisor/conf.d/radicale.conf" during parsing
2022-05-17 09:52:26,604 INFO RPC interface 'supervisor' initialized
2022-05-17 09:52:26,605 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2022-05-17 09:52:26,606 INFO supervisord started with pid 1372410
2022-05-17 09:52:27,610 INFO spawned: 'policyd' with pid 1372525
2022-05-17 09:52:27,615 INFO spawned: 'radicale' with pid 1372526
2022-05-17 09:52:28,617 INFO success: policyd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-17 09:52:28,617 INFO success: radicale entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
<!-- gh-comment-id:1129924424 --> @Renaud-DELEIRIS commented on GitHub (May 18, 2022): Nevermind they are all empty except the short one ``` 2022-05-17 09:52:08,840 INFO waiting for policyd, radicale to die 2022-05-17 09:52:08,986 INFO stopped: radicale (exit status 0) 2022-05-17 09:52:08,986 WARN received SIGTERM indicating exit request 2022-05-17 09:52:10,537 INFO stopped: policyd (exit status 0) 2022-05-17 09:52:12,807 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message. 2022-05-17 09:52:12,815 INFO Included extra file "/etc/supervisor/conf.d/policyd.conf" during parsing 2022-05-17 09:52:12,816 INFO Included extra file "/etc/supervisor/conf.d/radicale.conf" during parsing 2022-05-17 09:52:12,843 INFO RPC interface 'supervisor' initialized 2022-05-17 09:52:12,849 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2022-05-17 09:52:12,851 INFO supervisord started with pid 1371770 2022-05-17 09:52:13,854 INFO spawned: 'policyd' with pid 1371896 2022-05-17 09:52:13,858 INFO spawned: 'radicale' with pid 1371897 2022-05-17 09:52:14,877 INFO success: policyd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-05-17 09:52:14,877 INFO success: radicale entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-05-17 09:52:24,510 INFO waiting for policyd, radicale to die 2022-05-17 09:52:24,583 INFO stopped: radicale (exit status 0) 2022-05-17 09:52:24,583 WARN received SIGTERM indicating exit request 2022-05-17 09:52:25,021 INFO stopped: policyd (exit status 0) 2022-05-17 09:52:26,594 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message. 2022-05-17 09:52:26,594 INFO Included extra file "/etc/supervisor/conf.d/policyd.conf" during parsing 2022-05-17 09:52:26,594 INFO Included extra file "/etc/supervisor/conf.d/radicale.conf" during parsing 2022-05-17 09:52:26,604 INFO RPC interface 'supervisor' initialized 2022-05-17 09:52:26,605 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2022-05-17 09:52:26,606 INFO supervisord started with pid 1372410 2022-05-17 09:52:27,610 INFO spawned: 'policyd' with pid 1372525 2022-05-17 09:52:27,615 INFO spawned: 'radicale' with pid 1372526 2022-05-17 09:52:28,617 INFO success: policyd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-05-17 09:52:28,617 INFO success: radicale entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) ```
kerem commented 2026-02-27 11:18:09 +03:00
Author
Owner
Copy link

@tonioo commented on GitHub (May 18, 2022):

Nothing really interesting here.
Can you try to run this command:

/srv/modoboa/env/bin/python /srv/modoboa/instance/manage.py policy_daemon
<!-- gh-comment-id:1129931219 --> @tonioo commented on GitHub (May 18, 2022): Nothing really interesting here. Can you try to run this command: ``` /srv/modoboa/env/bin/python /srv/modoboa/instance/manage.py policy_daemon ```
kerem commented 2026-02-27 11:18:09 +03:00
Author
Owner
Copy link

@Renaud-DELEIRIS commented on GitHub (May 18, 2022):

It's seems like something already using my port 9999

Traceback (most recent call last):
  File "/srv/modoboa/instance/manage.py", line 22, in <module>
    main()
  File "/srv/modoboa/instance/manage.py", line 18, in main
    execute_from_command_line(sys.argv)
  File "/srv/modoboa/env/lib/python3.8/site-packages/django/core/management/__in                                                                                                                                                             it__.py", line 419, in execute_from_command_line
    utility.execute()
  File "/srv/modoboa/env/lib/python3.8/site-packages/django/core/management/__in                                                                                                                                                             it__.py", line 413, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/srv/modoboa/env/lib/python3.8/site-packages/django/core/management/base                                                                                                                                                             .py", line 354, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/srv/modoboa/env/lib/python3.8/site-packages/django/core/management/base                                                                                                                                                             .py", line 398, in execute
    output = self.handle(*args, **options)
  File "/srv/modoboa/env/lib/python3.8/site-packages/modoboa/policyd/management/                                                                                                                                                             commands/policy_daemon.py", line 39, in handle
    server = loop.run_until_complete(coro)
  File "/usr/lib/python3.8/asyncio/base_events.py", line 616, in run_until_compl      ete
    return future.result()
  File "/usr/lib/python3.8/asyncio/streams.py", line 94, in start_server
    return await loop.create_server(factory, host, port, **kwds)
  File "/usr/lib/python3.8/asyncio/base_events.py", line 1463, in create_server
    raise OSError(err.errno, 'error while attempting '
OSError: [Errno 98] error while attempting to bind on address ('127.0.0.1', 9999)address already in use

I tried a lot of things before installing modoboa maybe I missed to remove some?
Do you know what can possibly use this port?

<!-- gh-comment-id:1129934128 --> @Renaud-DELEIRIS commented on GitHub (May 18, 2022): It's seems like something already using my port 9999 ``` Traceback (most recent call last): File "/srv/modoboa/instance/manage.py", line 22, in <module> main() File "/srv/modoboa/instance/manage.py", line 18, in main execute_from_command_line(sys.argv) File "/srv/modoboa/env/lib/python3.8/site-packages/django/core/management/__in it__.py", line 419, in execute_from_command_line utility.execute() File "/srv/modoboa/env/lib/python3.8/site-packages/django/core/management/__in it__.py", line 413, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/srv/modoboa/env/lib/python3.8/site-packages/django/core/management/base .py", line 354, in run_from_argv self.execute(*args, **cmd_options) File "/srv/modoboa/env/lib/python3.8/site-packages/django/core/management/base .py", line 398, in execute output = self.handle(*args, **options) File "/srv/modoboa/env/lib/python3.8/site-packages/modoboa/policyd/management/ commands/policy_daemon.py", line 39, in handle server = loop.run_until_complete(coro) File "/usr/lib/python3.8/asyncio/base_events.py", line 616, in run_until_compl ete return future.result() File "/usr/lib/python3.8/asyncio/streams.py", line 94, in start_server return await loop.create_server(factory, host, port, **kwds) File "/usr/lib/python3.8/asyncio/base_events.py", line 1463, in create_server raise OSError(err.errno, 'error while attempting ' OSError: [Errno 98] error while attempting to bind on address ('127.0.0.1', 9999)address already in use ``` I tried a lot of things before installing modoboa maybe I missed to remove some? Do you know what can possibly use this port?
kerem commented 2026-02-27 11:18:09 +03:00
Author
Owner
Copy link

@Renaud-DELEIRIS commented on GitHub (May 18, 2022):

I got this running on port 9999:

COMMAND     PID    USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
python  1372525 modoboa    8u  IPv6 4330229      0t0  TCP localhost:9999 (LISTEN)
python  1372525 modoboa    9u  IPv4 4330230      0t0  TCP localhost:9999 (LISTEN)

with
sudo lsof -i tcp:9999

<!-- gh-comment-id:1129939727 --> @Renaud-DELEIRIS commented on GitHub (May 18, 2022): I got this running on port 9999: ``` COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME python 1372525 modoboa 8u IPv6 4330229 0t0 TCP localhost:9999 (LISTEN) python 1372525 modoboa 9u IPv4 4330230 0t0 TCP localhost:9999 (LISTEN) ``` with ```sudo lsof -i tcp:9999```
kerem commented 2026-02-27 11:18:09 +03:00
Author
Owner
Copy link

@tonioo commented on GitHub (May 18, 2022):

So actually the process is running as expected. Might be an ipv4/ipv6 confusion.
Can you check postfix configuration? (/etc/postfix/main.cf)

<!-- gh-comment-id:1129957029 --> @tonioo commented on GitHub (May 18, 2022): So actually the process is running as expected. Might be an ipv4/ipv6 confusion. Can you check postfix configuration? (/etc/postfix/main.cf)
kerem commented 2026-02-27 11:18:09 +03:00
Author
Owner
Copy link

@Renaud-DELEIRIS commented on GitHub (May 18, 2022):

What are you looking for in this?

I should not have ipv6, I didn't activate it on my digital ocean server

This mention the port 9999, tell me if you want to look in another part

# Recipient restriction rules
smtpd_recipient_restrictions =
      check_policy_service inet:127.0.0.1:9999
      permit_mynetworks
      permit_sasl_authenticated
      check_recipient_access
          proxy:pgsql:/etc/postfix/sql-maintain.cf
          proxy:pgsql:/etc/postfix/sql-relay-recipient-verification.cf
      reject_unverified_recipient
      reject_unauth_destination
      reject_non_fqdn_sender
      reject_non_fqdn_recipient
      reject_non_fqdn_helo_hostname
<!-- gh-comment-id:1129960571 --> @Renaud-DELEIRIS commented on GitHub (May 18, 2022): What are you looking for in this? I should not have ipv6, I didn't activate it on my digital ocean server This mention the port 9999, tell me if you want to look in another part ``` # Recipient restriction rules smtpd_recipient_restrictions = check_policy_service inet:127.0.0.1:9999 permit_mynetworks permit_sasl_authenticated check_recipient_access proxy:pgsql:/etc/postfix/sql-maintain.cf proxy:pgsql:/etc/postfix/sql-relay-recipient-verification.cf reject_unverified_recipient reject_unauth_destination reject_non_fqdn_sender reject_non_fqdn_recipient reject_non_fqdn_helo_hostname ```
kerem commented 2026-02-27 11:18:09 +03:00
Author
Owner
Copy link

@tonioo commented on GitHub (May 18, 2022):

Everything looks fine here. Now that I'm thinking about it, what Modoboa version do you run? Can you also check what version of aioredis in installed? (/srv/modoboa/env/bin/pip list)

<!-- gh-comment-id:1129969205 --> @tonioo commented on GitHub (May 18, 2022): Everything looks fine here. Now that I'm thinking about it, what Modoboa version do you run? Can you also check what version of aioredis in installed? (``/srv/modoboa/env/bin/pip list``)
kerem commented 2026-02-27 11:18:09 +03:00
Author
Owner
Copy link

@Renaud-DELEIRIS commented on GitHub (May 18, 2022):

I got
aioredis 2.0.1

and

modoboa                         2.0.0
modoboa-amavis                  1.4.0
modoboa-contacts                0.9.0
modoboa-pdfcredentials          1.5.0
modoboa-postfix-autoreply       1.7.0
modoboa-radicale                1.6.0
modoboa-sievefilters            1.6.0
modoboa-webmail                 1.7.0
<!-- gh-comment-id:1129973444 --> @Renaud-DELEIRIS commented on GitHub (May 18, 2022): I got ```aioredis 2.0.1``` and ``` modoboa 2.0.0 modoboa-amavis 1.4.0 modoboa-contacts 0.9.0 modoboa-pdfcredentials 1.5.0 modoboa-postfix-autoreply 1.7.0 modoboa-radicale 1.6.0 modoboa-sievefilters 1.6.0 modoboa-webmail 1.7.0 ```
kerem commented 2026-02-27 11:18:09 +03:00
Author
Owner
Copy link

@tonioo commented on GitHub (May 18, 2022):

Everything is fine too...
Can you run the policy daemon in debug mode? (add the --debug flag to command line options in supervisor configuration)
Or even better, stop the service spawned by supervisor and run the daemon manually using the previous command

<!-- gh-comment-id:1129983338 --> @tonioo commented on GitHub (May 18, 2022): Everything is fine too... Can you run the policy daemon in debug mode? (add the --debug flag to command line options in supervisor configuration) Or even better, stop the service spawned by supervisor and run the daemon manually using the previous command
kerem commented 2026-02-27 11:18:09 +03:00
Author
Owner
Copy link

@Renaud-DELEIRIS commented on GitHub (May 18, 2022):

I stoped supervisor service and launch
/srv/modoboa/env/bin/python /srv/modoboa/instance/manage.py policy_daemon --debug

But nothing is written

<!-- gh-comment-id:1129990465 --> @Renaud-DELEIRIS commented on GitHub (May 18, 2022): I stoped supervisor service and launch ```/srv/modoboa/env/bin/python /srv/modoboa/instance/manage.py policy_daemon --debug``` But nothing is written
kerem commented 2026-02-27 11:18:09 +03:00
Author
Owner
Copy link

@tonioo commented on GitHub (May 18, 2022):

While the process is running in foreground mode, try to send a new message and check the console output

<!-- gh-comment-id:1130001032 --> @tonioo commented on GitHub (May 18, 2022): While the process is running in foreground mode, try to send a new message and check the console output
kerem commented 2026-02-27 11:18:09 +03:00
Author
Owner
Copy link

@Renaud-DELEIRIS commented on GitHub (May 18, 2022):

Yes I did that and nothing shown up. It's probably bugging somewhere else

<!-- gh-comment-id:1130003738 --> @Renaud-DELEIRIS commented on GitHub (May 18, 2022): Yes I did that and nothing shown up. It's probably bugging somewhere else
kerem commented 2026-02-27 11:18:09 +03:00
Author
Owner
Copy link

@tonioo commented on GitHub (May 18, 2022):

Can you try to disable this service? (comment the corresponding line in main.cf and reload postfix)

<!-- gh-comment-id:1130005133 --> @tonioo commented on GitHub (May 18, 2022): Can you try to disable this service? (comment the corresponding line in main.cf and reload postfix)
kerem commented 2026-02-27 11:18:09 +03:00
Author
Owner
Copy link

@Renaud-DELEIRIS commented on GitHub (May 18, 2022):

So I commented what I send you in the main.cf

Now when I try to send message through Thunderbird It stuck on
Status: sending

<!-- gh-comment-id:1130010372 --> @Renaud-DELEIRIS commented on GitHub (May 18, 2022): So I commented what I send you in the main.cf Now when I try to send message through Thunderbird It stuck on ```Status: sending```
kerem commented 2026-02-27 11:18:09 +03:00
Author
Owner
Copy link

@tonioo commented on GitHub (May 18, 2022):

And what do you see in mail.log ?

<!-- gh-comment-id:1130014739 --> @tonioo commented on GitHub (May 18, 2022): And what do you see in mail.log ?
kerem commented 2026-02-27 11:18:09 +03:00
Author
Owner
Copy link

@Renaud-DELEIRIS commented on GitHub (May 18, 2022):

I got this

May 18 13:25:35 mail postfix/smtpd[2127096]: fatal: in parameter smtpd_relay_restrictions or smtpd_recipient_restrictions, specify at least one working instance of: reject_unauth_destination, defer_unauth_destination, reject, defer, def>
May 18 13:25:36 mail postfix/master[2124736]: warning: process /usr/lib/postfix/sbin/smtpd pid 2127096 exit status 1
May 18 13:25:36 mail postfix/master[2124736]: warning: /usr/lib/postfix/sbin/smtpd: bad command startup -- throttling
May 18 13:25:57 mail postfix/submission/smtpd[2127099]: fatal: in parameter smtpd_relay_restrictions or smtpd_recipient_restrictions, specify at least one working instance of: reject_unauth_destination, defer_unauth_destination, reject,>
May 18 13:25:58 mail postfix/master[2124736]: warning: process /usr/lib/postfix/sbin/smtpd pid 2127099 exit status 1
May 18 13:25:58 mail postfix/master[2124736]: warning: /usr/lib/postfix/sbin/smtpd: bad command startup -- throttling
<!-- gh-comment-id:1130016882 --> @Renaud-DELEIRIS commented on GitHub (May 18, 2022): I got this ``` May 18 13:25:35 mail postfix/smtpd[2127096]: fatal: in parameter smtpd_relay_restrictions or smtpd_recipient_restrictions, specify at least one working instance of: reject_unauth_destination, defer_unauth_destination, reject, defer, def> May 18 13:25:36 mail postfix/master[2124736]: warning: process /usr/lib/postfix/sbin/smtpd pid 2127096 exit status 1 May 18 13:25:36 mail postfix/master[2124736]: warning: /usr/lib/postfix/sbin/smtpd: bad command startup -- throttling May 18 13:25:57 mail postfix/submission/smtpd[2127099]: fatal: in parameter smtpd_relay_restrictions or smtpd_recipient_restrictions, specify at least one working instance of: reject_unauth_destination, defer_unauth_destination, reject,> May 18 13:25:58 mail postfix/master[2124736]: warning: process /usr/lib/postfix/sbin/smtpd pid 2127099 exit status 1 May 18 13:25:58 mail postfix/master[2124736]: warning: /usr/lib/postfix/sbin/smtpd: bad command startup -- throttling ```
kerem commented 2026-02-27 11:18:09 +03:00
Author
Owner
Copy link

@tonioo commented on GitHub (May 18, 2022):

Looks like your configuration is broken somewhere. Can you check your master.cf file?

<!-- gh-comment-id:1130031442 --> @tonioo commented on GitHub (May 18, 2022): Looks like your configuration is broken somewhere. Can you check your master.cf file?
kerem commented 2026-02-27 11:18:09 +03:00
Author
Owner
Copy link

@Renaud-DELEIRIS commented on GitHub (May 18, 2022):

Ok I have uncommented other line:

smtp      inet  n       -       -       -       1       postscreen
smtpd     pass  -       -       -       -       -       smtpd
  -o smtpd_proxy_filter=inet:[127.0.0.1]:10024
  -o smtpd_proxy_options=speed_adjust
dnsblog   unix  -       -       -       -       0       dnsblog

tlsproxy  unix  -       -       -       -       0       tlsproxy
submission inet n       -       -       -       -       smtpd
  -o syslog_name=postfix/submission
  -o smtpd_tls_security_level=encrypt
  -o tls_preempt_cipherlist=yes
  -o smtpd_sasl_auth_enable=yes
  -o smtpd_reject_unlisted_recipient=no
  -o smtpd_client_restrictions=permit_sasl_authenticated,reject
  -o smtpd_helo_restrictions=
  -o smtpd_sender_restrictions=reject_sender_login_mismatch
  -o milter_macro_daemon_name=ORIGINATING
  -o smtpd_proxy_filter=inet:[127.0.0.1]:10026

I remember changing something near this line but it was maybe before modoboa:
-o smtpd_sasl_auth_enable=yes
Is everything normal ?

Other:

# Amavis return path
#
127.0.0.1:10025 inet n    -       n       -       -     smtpd
        -o content_filter=
        -o smtpd_authorized_xforward_hosts=127.0.0.0/8
        -o smtpd_delay_reject=no
        -o smtpd_client_restrictions=permit_mynetworks,reject
        -o smtpd_helo_restrictions=
        -o smtpd_sender_restrictions=
        -o smtpd_recipient_restrictions=permit_mynetworks,reject
        -o smtpd_data_restrictions=reject_unauth_pipelining
        -o smtpd_end_of_data_restrictions=
        -o smtpd_restriction_classes=
        -o mynetworks=127.0.0.0/8
        -o smtpd_error_sleep_time=0
        -o smtpd_soft_error_limit=1001
        -o smtpd_hard_error_limit=1000
        -o smtpd_client_connection_count_limit=0
        -o smtpd_client_connection_rate_limit=0
        -o receive_override_options=no_header_body_checks,no_unknown_recipient_checks
        -o local_header_rewrite_clients=
<!-- gh-comment-id:1130036253 --> @Renaud-DELEIRIS commented on GitHub (May 18, 2022): Ok I have uncommented other line: ``` smtp inet n - - - 1 postscreen smtpd pass - - - - - smtpd -o smtpd_proxy_filter=inet:[127.0.0.1]:10024 -o smtpd_proxy_options=speed_adjust dnsblog unix - - - - 0 dnsblog tlsproxy unix - - - - 0 tlsproxy submission inet n - - - - smtpd -o syslog_name=postfix/submission -o smtpd_tls_security_level=encrypt -o tls_preempt_cipherlist=yes -o smtpd_sasl_auth_enable=yes -o smtpd_reject_unlisted_recipient=no -o smtpd_client_restrictions=permit_sasl_authenticated,reject -o smtpd_helo_restrictions= -o smtpd_sender_restrictions=reject_sender_login_mismatch -o milter_macro_daemon_name=ORIGINATING -o smtpd_proxy_filter=inet:[127.0.0.1]:10026 ``` I remember changing something near this line but it was maybe before modoboa: ```-o smtpd_sasl_auth_enable=yes``` Is everything normal ? Other: ``` # Amavis return path # 127.0.0.1:10025 inet n - n - - smtpd -o content_filter= -o smtpd_authorized_xforward_hosts=127.0.0.0/8 -o smtpd_delay_reject=no -o smtpd_client_restrictions=permit_mynetworks,reject -o smtpd_helo_restrictions= -o smtpd_sender_restrictions= -o smtpd_recipient_restrictions=permit_mynetworks,reject -o smtpd_data_restrictions=reject_unauth_pipelining -o smtpd_end_of_data_restrictions= -o smtpd_restriction_classes= -o mynetworks=127.0.0.0/8 -o smtpd_error_sleep_time=0 -o smtpd_soft_error_limit=1001 -o smtpd_hard_error_limit=1000 -o smtpd_client_connection_count_limit=0 -o smtpd_client_connection_rate_limit=0 -o receive_override_options=no_header_body_checks,no_unknown_recipient_checks -o local_header_rewrite_clients= ```
kerem commented 2026-02-27 11:18:09 +03:00
Author
Owner
Copy link

@tonioo commented on GitHub (May 18, 2022):

Yes, it looks fine. Instead of a comment, can you completely remove the line in the main.cf file?

<!-- gh-comment-id:1130038214 --> @tonioo commented on GitHub (May 18, 2022): Yes, it looks fine. Instead of a comment, can you completely remove the line in the main.cf file?
kerem commented 2026-02-27 11:18:09 +03:00
Author
Owner
Copy link

@Renaud-DELEIRIS commented on GitHub (May 18, 2022):

I remove all the line ?

<!-- gh-comment-id:1130039015 --> @Renaud-DELEIRIS commented on GitHub (May 18, 2022): I remove all the line ?
kerem commented 2026-02-27 11:18:09 +03:00
Author
Owner
Copy link

@tonioo commented on GitHub (May 18, 2022):

yes, the one with 9999. Just to check if it's a syntax issue

<!-- gh-comment-id:1130040061 --> @tonioo commented on GitHub (May 18, 2022): yes, the one with 9999. Just to check if it's a syntax issue
kerem commented 2026-02-27 11:18:09 +03:00
Author
Owner
Copy link

@Renaud-DELEIRIS commented on GitHub (May 18, 2022):

Oh that worked !!!!!
Thank you so much
Could you explain why it happen?

<!-- gh-comment-id:1130048643 --> @Renaud-DELEIRIS commented on GitHub (May 18, 2022): Oh that worked !!!!! Thank you so much Could you explain why it happen?
kerem commented 2026-02-27 11:18:09 +03:00
Author
Owner
Copy link

@tonioo commented on GitHub (May 18, 2022):

Postfix can be sometimes annoying with comments...
Ok, so the issue comes from the policy daemon but we don't know why.

<!-- gh-comment-id:1130054565 --> @tonioo commented on GitHub (May 18, 2022): Postfix can be sometimes annoying with comments... Ok, so the issue comes from the policy daemon but we don't know why.
kerem commented 2026-02-27 11:18:09 +03:00
Author
Owner
Copy link

@Renaud-DELEIRIS commented on GitHub (May 18, 2022):

Oh Do I have disabled something important ? Cause now I can send and receive mail

<!-- gh-comment-id:1130055635 --> @Renaud-DELEIRIS commented on GitHub (May 18, 2022): Oh Do I have disabled something important ? Cause now I can send and receive mail
kerem commented 2026-02-27 11:18:09 +03:00
Author
Owner
Copy link

@tonioo commented on GitHub (May 18, 2022):

The policy daemon is the component responsible for applying daily sending limits defined on your accounts

<!-- gh-comment-id:1130056996 --> @tonioo commented on GitHub (May 18, 2022): The policy daemon is the component responsible for applying daily sending limits defined on your accounts
kerem commented 2026-02-27 11:18:10 +03:00
Author
Owner
Copy link

@Renaud-DELEIRIS commented on GitHub (May 18, 2022):

I Don't use this feature so should be okay, Thanks for the help

<!-- gh-comment-id:1130165353 --> @Renaud-DELEIRIS commented on GitHub (May 18, 2022): I Don't use this feature so should be okay, Thanks for the help
kerem commented 2026-02-27 11:18:10 +03:00
Author
Owner
Copy link

@gi-yt commented on GitHub (Jun 7, 2022):

i am having a similar issue. when i try to send an email through the webmail i get

Jun  7 01:40:46 vern postfix/qmgr[1440]: 0244CA1CE2: from=<aryak@vern.cc>, size=1279, nrcpt=1 (queue active)
Jun  7 01:40:46 vern postfix/smtp[47007]: fatal: unknown service: smtp/tcp
Jun  7 01:40:47 vern postfix/qmgr[1440]: warning: private/smtp socket: malformed response
Jun  7 01:40:47 vern postfix/qmgr[1440]: warning: transport smtp failure -- see a previous warning/fatal/panic logfile record for the problem description
Jun  7 01:40:47 vern postfix/master[1432]: warning: process /usr/lib/postfix/sbin/smtp pid 47007 exit status 1
Jun  7 01:40:47 vern postfix/master[1432]: warning: /usr/lib/postfix/sbin/smtp: bad command startup -- throttling
Jun  7 01:40:47 vern postfix/error[47009]: 0244CA1CE2: to=<myoldgmail@gmail.com>, relay=none, delay=4701, delays=4700/1.1/0/0.01, dsn=4.3.0, status=deferred (unknown mail transport error)
Jun  7 01:43:41 vern postfix/anvil[46595]: statistics: max connection rate 1/60s for (smtpd:10.7.0.1) at Jun  7 05:40:20
Jun  7 01:43:41 vern postfix/anvil[46595]: statistics: max connection count 1 for (smtpd:10.7.0.1) at Jun  7 05:40:20
Jun  7 01:43:41 vern postfix/anvil[46595]: statistics: max cache size 1 at Jun  7 05:40:20
<!-- gh-comment-id:1148224197 --> @gi-yt commented on GitHub (Jun 7, 2022): i am having a similar issue. when i try to send an email through the webmail i get ``` Jun 7 01:40:46 vern postfix/qmgr[1440]: 0244CA1CE2: from=<aryak@vern.cc>, size=1279, nrcpt=1 (queue active) Jun 7 01:40:46 vern postfix/smtp[47007]: fatal: unknown service: smtp/tcp Jun 7 01:40:47 vern postfix/qmgr[1440]: warning: private/smtp socket: malformed response Jun 7 01:40:47 vern postfix/qmgr[1440]: warning: transport smtp failure -- see a previous warning/fatal/panic logfile record for the problem description Jun 7 01:40:47 vern postfix/master[1432]: warning: process /usr/lib/postfix/sbin/smtp pid 47007 exit status 1 Jun 7 01:40:47 vern postfix/master[1432]: warning: /usr/lib/postfix/sbin/smtp: bad command startup -- throttling Jun 7 01:40:47 vern postfix/error[47009]: 0244CA1CE2: to=<myoldgmail@gmail.com>, relay=none, delay=4701, delays=4700/1.1/0/0.01, dsn=4.3.0, status=deferred (unknown mail transport error) Jun 7 01:43:41 vern postfix/anvil[46595]: statistics: max connection rate 1/60s for (smtpd:10.7.0.1) at Jun 7 05:40:20 Jun 7 01:43:41 vern postfix/anvil[46595]: statistics: max connection count 1 for (smtpd:10.7.0.1) at Jun 7 05:40:20 Jun 7 01:43:41 vern postfix/anvil[46595]: statistics: max cache size 1 at Jun 7 05:40:20 ```
kerem commented 2026-02-27 11:18:10 +03:00
Author
Owner
Copy link

@gi-yt commented on GitHub (Jun 7, 2022):

smtp probably refers to

smtp      inet  n       -       -       -       1       postscreen

in master.cf indicating that there is something wrong with screening?

<!-- gh-comment-id:1148225754 --> @gi-yt commented on GitHub (Jun 7, 2022): smtp probably refers to ``` smtp inet n - - - 1 postscreen ``` in master.cf indicating that there is something wrong with screening?
kerem commented 2026-02-27 11:18:10 +03:00
Author
Owner
Copy link

@gi-yt commented on GitHub (Jun 7, 2022):

i cannot recieve mail either


Jun  7 01:56:42 vern postfix/postscreen[58391]: CONNECT from [10.7.0.1]:47416 to [10.7.0.2]:25
Jun  7 01:56:42 vern postfix/postscreen[58391]: PASS OLD [10.7.0.1]:47416
Jun  7 01:56:42 vern postfix/smtpd[58395]: fatal: in parameter smtpd_relay_restrictions or smtpd_recipient_restrictions, specify at least one working instance of: reject_unauth_destination, defer_unauth_destination, reject, defer, defer_if_permit or check_relay_domains
Jun  7 01:56:43 vern postfix/master[55868]: warning: process /usr/lib/postfix/sbin/smtpd pid 58395 exit status 1
Jun  7 01:56:43 vern postfix/master[55868]: warning: /usr/lib/postfix/sbin/smtpd: bad command startup -- throttling
<!-- gh-comment-id:1148228463 --> @gi-yt commented on GitHub (Jun 7, 2022): i cannot recieve mail either ``` Jun 7 01:56:42 vern postfix/postscreen[58391]: CONNECT from [10.7.0.1]:47416 to [10.7.0.2]:25 Jun 7 01:56:42 vern postfix/postscreen[58391]: PASS OLD [10.7.0.1]:47416 Jun 7 01:56:42 vern postfix/smtpd[58395]: fatal: in parameter smtpd_relay_restrictions or smtpd_recipient_restrictions, specify at least one working instance of: reject_unauth_destination, defer_unauth_destination, reject, defer, defer_if_permit or check_relay_domains Jun 7 01:56:43 vern postfix/master[55868]: warning: process /usr/lib/postfix/sbin/smtpd pid 58395 exit status 1 Jun 7 01:56:43 vern postfix/master[55868]: warning: /usr/lib/postfix/sbin/smtpd: bad command startup -- throttling ```
kerem commented 2026-02-27 11:18:10 +03:00
Author
Owner
Copy link

@gi-yt commented on GitHub (Jun 7, 2022):

Recipient restriction rules

smtpd_recipient_restrictions =
check_policy_service inet:127.0.0.1:9999
permit_mynetworks
permit_sasl_authenticated
check_recipient_access
proxy:pgsql:/etc/postfix/sql-maintain.cf
proxy:pgsql:/etc/postfix/sql-relay-recipient-verification.cf
reject_unverified_recipient
reject_unauth_destination
reject_non_fqdn_sender
reject_non_fqdn_recipient
reject_non_fqdn_helo_hostname

adding these back fixed the getting emails issue but i still cant send

<!-- gh-comment-id:1148229533 --> @gi-yt commented on GitHub (Jun 7, 2022): > # Recipient restriction rules > smtpd_recipient_restrictions = > check_policy_service inet:127.0.0.1:9999 > permit_mynetworks > permit_sasl_authenticated > check_recipient_access > proxy:pgsql:/etc/postfix/sql-maintain.cf > proxy:pgsql:/etc/postfix/sql-relay-recipient-verification.cf > reject_unverified_recipient > reject_unauth_destination > reject_non_fqdn_sender > reject_non_fqdn_recipient > reject_non_fqdn_helo_hostname adding these back fixed the getting emails issue but i still cant send
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
fix/sievefilters-allow-email-in-rule-name
dependabot/npm_and_yarn/frontend/axios-1.15.0
translations_04c0b653215cb5fa48ab101eae1a1917_ja_JP
translations_5d93982e9fd6dab991db4faf93ce9ded_ja_JP
fix/login-issue-3995
fix/sievefilters-issues
add-vitepress-openapi
2974-dmarc-empty-email
2.3.x
updated-doc-2.3.0
feature/OIDC
delete-all-alarms
translations_modoboa-admin-locale-en-lc-messages-djangojs-po--master_af_ZA
translations_modoboa-admin-locale-en-lc-messages-djangojs-po--master_ar
translations_modoboa-admin-locale-en-lc-messages-djangojs-po--master_ca
1.x
translations_modoboa-admin-locale-en-lc-messages-djangojs-po--master_sk
translations_modoboa-admin-locale-en-lc-messages-djangojs-po--master_tr
translations_modoboa-admin-locale-en-lc-messages-djangojs-po--master_es_ES
translations_modoboa-admin-locale-en-lc-messages-djangojs-po--master_uk
translations_modoboa-admin-locale-en-lc-messages-djangojs-po--master_zh_CN
translations_modoboa-admin-locale-en-lc-messages-djangojs-po--master_de_DE
translations_modoboa-admin-locale-en-lc-messages-djangojs-po--master_da_DK
1.8.x
1.7.x
1.6.x
1.4.x
1.3.x
1.2.x
2.8.2
2.8.1
2.8.0
2.7.2
2.7.1
2.7.0
2.6.5
2.6.4
2.6.3
2.6.2
2.6.1
2.6.0
2.5.1
2.5.0
2.4.11
2.4.10
2.4.9
2.4.8
2.4.7
2.4.6
2.4.5
2.4.4
2.4.3
2.4.2
2.4.1
2.4.0
2.3.6
2.3.5
2.3.4
2.3.3
2.3.2
2.3.1
2.3.0
2.3.0-beta.4
2.3.0-beta.3
2.3.0-beta.2
2.3.0-beta.1
2.2.4
2.2.3
2.2.2
2.2.1
2.2.0
2.1.2
2.1.1
2.1.0
2.0.5
2.0.4
2.0.3
2.0.2
2.0.1
2.0.0
2.0.0-beta.3
2.0.0-beta.2
2.0.0-beta.1
1.17.0
1.16.1
1.16.0
1.15.0
1.14.0
1.13.1
1.13.0
1.12.2
1.12.1
1.12.0
1.11.1
1.11.0
1.10.7
1.10.6
1.10.5
1.10.4
1.10.3
1.10.2
1.10.1
1.10.0
1.9.1
1.9.0
1.8.3
1.8.2
1.8.1
1.8.0
1.7.4
1.7.3
1.7.2
1.7.1
1.7.0
1.6.3
1.6.2
1.6.1
1.6.0
1.5.3
1.5.2
1.5.1
1.5.0
1.4.5
1.4.4
1.4.3
1.4.2
1.4.1
1.4.0
1.3.5
1.3.4
1.2.2
1.3.3
1.3.2
1.3.1
1.3.0
1.2.1
1.2.0
1.2.0-rc2
1.2.0-rc1
1.1.7
1.1.6
1.1.5
1.1.4
1.1.3
1.1.2
1.1.1
1.1.0
1.0.1
1.0.0
0.9.5
0.9.4
0.9.3
0.9.2
0.9.1
0.9
0.8.8
0.8.7
0.8.6.1
0.8.6
0.8.5
0.8.4
0.8.3
0.8.3-rc1
0.8.2
0.8.1
0.8
0.8-rc2
0.8-rc1
0.7.2
0.7.1
0.7
0.6.1
0.6
0.5
0.3
0.2
0.1
Labels
Clear labels   
bug

   
bug

   
dependencies

   
design

   
documentation

   
duplicate

   
enhancement

   
enhancement

   
enhancement

   
feedback-needed

   
help-needed

   
help-needed

   
installer

   
invalid

   
looking-for-sponsors

   
modoboa-contacts

   
new-ui

   
new-ui

   
pr

   
pull-request

Mirrored from GitHub Pull Request

  
pyconfr

   
python

   
question

   
security

   
stale

   
webmail

   
wontfix
No labels
bug
bug
dependencies
design
documentation
duplicate
enhancement
enhancement
enhancement
feedback-needed
help-needed
help-needed
installer
invalid
looking-for-sponsors
modoboa-contacts
new-ui
new-ui
pr
pull-request
pyconfr
python
question
security
stale
webmail
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/modoboa-modoboa#1618
No description provided.