==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 0.9.9
- Deployed with iRedMail Easy or the downloadable installer?
- Linux/BSD distribution name and version: Ubuntu 18.04
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MariaDB
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro?
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

I have two test installations of iRedMail 0.9.9. Both on Ubuntu 18.04 and Nginx.
In one of these devices have set the automatic update. I receive information about updates every day by email.
"Cron <root@mail> test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )"
Why this option is installed only on one server? Is this correct or something is wrong?

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release):  0.9.7
- Deployed with iRedMail Easy or the downloadable installer?
- Linux/BSD distribution name and version:  CentOS 7
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):  LDAP
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? no
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

Today, I learned that Greylisting doesn't quite do what I thought.  Today, we had a remote host hammer us on supposedly returned-mail to 4 of our users:

[root@voyageur ~]# egrep 188.213.140.179 /var/log/maillog | head
Feb  4 14:43:33 voyageur postfix/postscreen[12014]: CONNECT from [188.213.140.179]:60726 to [64.111.99.245]:25
Feb  4 14:43:33 voyageur postfix/postscreen[12014]: CONNECT from [188.213.140.179]:40664 to [64.111.99.245]:25
Feb  4 14:43:39 voyageur postfix/postscreen[12014]: PASS OLD [188.213.140.179]:60726
Feb  4 14:43:39 voyageur postfix/postscreen[12014]: PASS OLD [188.213.140.179]:40664
Feb  4 14:43:39 voyageur postfix/smtpd[24199]: connect from o21.royalpalace.club[188.213.140.179]
Feb  4 14:43:39 voyageur postfix/smtpd[24199]: NOQUEUE: reject: RCPT from o21.royalpalace.club[188.213.140.179]: 451 4.7.1 <USER1@mailbag.com>: Recipient address rejected: Intentional policy rejection, please try again later; from=<> to=<greglusk@mailbag.com> proto=ESMTP helo=<o21.royalpalace.club>
Feb  4 14:43:40 voyageur postfix/smtpd[24199]: NOQUEUE: reject: RCPT from o21.royalpalace.club[188.213.140.179]: 451 4.7.1 <USER2@mailbag.com>: Recipient address rejected: Intentional policy rejection, please try again later; from=<> to=<alewis@mailbag.com> proto=ESMTP helo=<o21.royalpalace.club>
Feb  4 14:43:40 voyageur postfix/smtpd[5826]: connect from o21.royalpalace.club[188.213.140.179]
Feb  4 14:43:40 voyageur postfix/smtpd[24199]: NOQUEUE: reject: RCPT from o21.royalpalace.club[188.213.140.179]: 451 4.7.1 <USER3@mailbag.com>: Recipient address rejected: Intentional policy rejection, please try again later; from=<> to=<rfalci@mailbag.com> proto=ESMTP helo=<o21.royalpalace.club>
Feb  4 14:43:40 voyageur postfix/smtpd[24199]: disconnect from o21.royalpalace.club[188.213.140.179]
Feb  4 14:43:40 voyageur postfix/smtpd[5826]: NOQUEUE: reject: RCPT from o21.royalpalace.club[188.213.140.179]: 451 4.7.1 <USER4@mailbag.com>: Recipient address rejected: Intentional policy rejection, please try again later; from=<> to=<artwebb@mailbag.com> proto=ESMTP helo=<o21.royalpalace.club>

Normal right?  Well, what I didn't expect is that this host would continue to beat up my server until the 15 minute period expired:

Feb  4 14:58:41 voyageur amavis[1927]: (01927-14) Passed CLEAN {RelayedInbound}, [188.213.140.179]:56787 [188.213.140.179] <> -> <USER4@mailbag.com>, Queue-ID: 04C289BC6, Message-ID: <167561732655753455460.oqiflqsdsrjevymzbzuhjmo4tw77i99@5923224nb.myself.com>, mail_id: mKQaj46pokmk, Hits: 4.515, size: 6874, queued_as: 922818438, 488 ms, Tests: [BASE64_LENGTH_79_INF=1.502,BAYES_00=-1.9,FROM_LOCAL_NOVOWEL=0.5,HTML_FONT_SIZE_HUGE=0.001,HTML_MESSAGE=0.001,MPART_ALT_DIFF=0.79,MPART_ALT_DIFF_COUNT=1.112,TO_NO_BRKTS_PCNT=2.499,T_HTML_TAG_BALANCE_CENTER=0.01]
Feb  4 15:03:59 voyageur postfix/anvil[19203]: statistics: max connection rate 60/60s for (smtpd:188.213.140.179) at Feb  4 14:57:43
Feb  4 15:03:59 voyageur postfix/anvil[19203]: statistics: max connection count 2 for (smtpd:188.213.140.179) at Feb  4 14:54:41

[root@voyageur ~]# egrep 188.213.140.179 /var/log/maillog | grep reject: | wc -l
1752

1752 submission rejections between 14:43 and 14:58.  Should the greylisting timer reset with every submission attempt within the 15 minute interval?  Thinking about it, I could see this as problematic if a site were to have a 10 minute queue run interval they may never have their email accepted but certainly 1700 attempts should trigger some inverse reaction on the email score - on top of everything else, it wasn't even marked as SPAM despite the empty from:<>.

After poking around in the iredapd database, here's the record for that IP:

MariaDB [iredapd]> select * from greylisting_tracking where client_address='188.213.140.179';
+---------+--------+----------------------+-----------------+---------------+-------------+------------+---------------+----------------+---------------+--------+
| id      | sender | recipient            | client_address  | sender_domain | rcpt_domain | init_time  | block_expired | record_expired | blocked_count | passed |
+---------+--------+----------------------+-----------------+---------------+-------------+------------+---------------+----------------+---------------+--------+
| 1381799 |        | USER1@mailbag.com | 188.213.140.179 |               | mailbag.com | 1549313019 |    1549313919 |     1551905921 |           441 |      1 |
+---------+--------+----------------------+-----------------+---------------+-------------+------------+---------------+----------------+---------------+--------+

Shouldn't there have been 4 records, one for each user being emailed?

So I guess to summarize, this behavior in my opinion should not be rewarded.  But what do you suppose would help?

Is this worthy of setting up another fail2ban jail - after say X "Intentional policy rejections" from the same IP, block them for Y hours. where X is say 10-20 and Y is > 1 hour since we are dealing with a legitimate mail server who has proved it can queue messages.

Is there a spamassassin rule I should tweak to get this email marked as spam?

Is there anything else which should be considered?

Note:  I  *really* love the 0.9.8 pregreet jail - it made a huge performance improvement to block anyone who speaks before the SMTP banner is sent.

-James

Yes you are right, it is not a big concern right now. I was not familiar these kind of things but as i understand it is smooth for now. Thank you.

If anyone else is having deliverability issues, I can confirm that Postmark is working great for me, and it's free up to 100 sent emails per day, which is more than enough for a personal email server.

Thanks for the reply.

Because the server is blocking for an hour after every attempt, testing is not convenient. I have spent all my spare time for the last week trying various alternatives on a different server where at least I can work continuously. I have now abandoned the project as neither sogo nor any of four alternatives could be installed without an in-depth knowledge of Caldav/Carddav and of Postfix and Dovecot. I will have to try again in a year or two, when perhaps the default configuration for some of these may run without manual configuration.  Meanwhile google will continue to benefit from my data.

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (0.9.9):
- Deployed with downloadable installer?
- Linux/BSD distribution name and version: centos7
- Store mail accounts in which backend (mysql):
- Web server (Nginx):
- Manage mail accounts with iRedAdmin-Pro? No
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

Hi
i am using a sophos spam box for protecting an internal mail server. Due to no facility to enable DKIM on the box, I have setup another Iredmail in DMZ for acting as a relay for all mails received by this box.

but whenever my sophos box relays any mail to iredmail server i get "client host rejected message in the maillog". i want to know if i can relay all mails coming from this sophos box to outside world while block any other source.

Secondly how do i relay all incoming mails from my dmz mailserver to sophos box for scanning and then to my internal mail server

Please assist

Regards

morethanlazy: my profile is changed, you can contact me via the forums now.

Zhang: I understand your points. It makes sense. I will work on a list of binary packages and get back to you.

Hi ZhangHuangbin

I had already seen and used that page.

Is there an error log somewhere I can look to debug what is going wrong?

Cheers
Chris

It is like Google Mail is blocked from accessing the server. I have also found I cannot get it to send from my server either.

All other mail clients (like Thunderbird) connect to the server fine!

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 0.9.9
- Deployed with iRedMail Easy or the downloadable installer?
- Linux/BSD distribution name and version: Centos 7.6
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): LDAP
- Web server (Apache or Nginx):nginx
- Manage mail accounts with iRedAdmin-Pro?
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

Today I proceeded to updating my mail server in CENTOS 7, updating everything, and among themselves I update the dovecot to the version 2.3.4.1, but when I try to deposit the webclient you give me error of connection: You appear to me in the dovecot's log:

Feb  5 13:09:17 correo dovecot: master: Dovecot v2.3.4.1 (3c0b8769e) starting up for pop3, imap, sieve, lmtp (core dumps disabled)
Feb  5 13:09:17 correo dovecot: doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -Pn > dovecot-new.conf
Feb  5 13:09:17 correo dovecot: doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:43: ssl_protocols has been replaced by ssl_min_protocol
Feb  5 13:09:17 correo dovecot: doveconf: Error: Could not find a minimum ssl_min_protocol setting from ssl_protocols = !SSLv2 !SSLv3: Unrecognized protocol 'SSLv2'
Feb  5 13:09:17 correo dovecot: config: Warning: NOTE: You can get a new clean config file with: doveconf -Pn > dovecot-new.conf
Feb  5 13:09:17 correo dovecot: config: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:43: ssl_protocols has been replaced by ssl_min_protocol
Feb  5 13:09:17 correo dovecot: config: Error: Could not find a minimum ssl_min_protocol setting from ssl_protocols = !SSLv2 !SSLv3: Unrecognized protocol 'SSLv2'
Feb  5 13:09:28 correo dovecot: stats: Error: (stats-reader): didn't reply with a valid VERSION line: EXPORT#011global
Feb  5 13:09:28 correo dovecot: stats: Error: (stats-reader): didn't reply with a valid VERSION line: EXPORT#011global
Feb  5 13:13:21 correo dovecot: master: Warning: Killed with signal 15 (by pid=1309 uid=0 code=kill)
Feb  5 13:14:29 correo dovecot: master: Dovecot v2.3.4.1 (3c0b8769e) starting up for pop3, imap, sieve, lmtp (core dumps disabled)
Feb  5 13:14:29 correo dovecot: doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -Pn > dovecot-new.conf
Feb  5 13:14:29 correo dovecot: doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:43: ssl_protocols has been replaced by ssl_min_protocol
Feb  5 13:14:29 correo dovecot: doveconf: Error: Could not find a minimum ssl_min_protocol setting from ssl_protocols = !SSLv2 !SSLv3: Unrecognized protocol 'SSLv2'
Feb  5 13:14:29 correo dovecot: config: Warning: NOTE: You can get a new clean config file with: doveconf -Pn > dovecot-new.conf
Feb  5 13:14:29 correo dovecot: config: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:43: ssl_protocols has been replaced by ssl_min_protocol
Feb  5 13:14:29 correo dovecot: config: Error: Could not find a minimum ssl_min_protocol setting from ssl_protocols = !SSLv2 !SSLv3: Unrecognized protocol 'SSLv2'
Feb  5 13:14:41 correo dovecot: stats: Error: (stats-reader): didn't reply with a valid VERSION line: EXPORT#011global
Feb  5 13:14:41 correo dovecot: stats: Error: (stats-reader): didn't reply with a valid VERSION line: EXPORT#011global
Feb  5 13:16:42 correo dovecot: auth: Error: LDAP: Connection lost to LDAP server, reconnecting
Feb  5 13:16:42 correo dovecot: auth: Error: LDAP: Can't connect to server: 127.0.0.1:389
Feb  5 13:16:42 correo dovecot: master: Warning: Killed with signal 15 (by pid=1262 uid=0 code=kill)
Feb  5 13:29:29 correo dovecot: master: Dovecot v2.3.4.1 (3c0b8769e) starting up for pop3, imap, sieve, lmtp (core dumps disabled)
Feb  5 13:29:29 correo dovecot: doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -Pn > dovecot-new.conf
Feb  5 13:29:29 correo dovecot: doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:43: ssl_protocols has been replaced by ssl_min_protocol
Feb  5 13:29:29 correo dovecot: doveconf: Error: Could not find a minimum ssl_min_protocol setting from ssl_protocols = !SSLv2 !SSLv3: Unrecognized protocol 'SSLv2'
Feb  5 13:29:29 correo dovecot: config: Warning: NOTE: You can get a new clean config file with: doveconf -Pn > dovecot-new.conf
Feb  5 13:29:29 correo dovecot: config: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:43: ssl_protocols has been replaced by ssl_min_protocol
Feb  5 13:29:29 correo dovecot: config: Error: Could not find a minimum ssl_min_protocol setting from ssl_protocols = !SSLv2 !SSLv3: Unrecognized protocol 'SSLv2'
Feb  5 13:29:41 correo dovecot: stats: Error: (stats-reader): didn't reply with a valid VERSION line: EXPORT#011global
Feb  5 13:29:41 correo dovecot: stats: Error: (stats-reader): didn't reply with a valid VERSION line: EXPORT#011global

in de loging whit rouncubemail:

tail -f /var/log/maillog
Feb  5 13:37:26 correo roundcube: <fq0pqecb> IMAP Error: Login failed for postmaster@rubia.alinet.cu from 192.168.0.1. LOGIN: Internal error occurred. Refer to server log for more information. in /opt/www/roundcubemail-1.3.8/program/lib/Roundcube/rcube_imap.php on line 196 (POST /mail/?_task=login&_action=login)

Apparently exists a change of protocol ssl of SSLv2 to ssl min protocol TLSv1 that is not contemplated in Iredmail's versions.

When the Iredmail's developer the fact that this bringing up to date modifies something of what installed for the Iredmail that now yields error with the servant IMAP, that is, to say it the connection SSl between the servant LDAP and the mail server.

Any help with regard to this matter.

How can I add additional SMTP users (to allow) without creating an account for username?

Latest version, installer, MySQL
==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release):
- Deployed with iRedMail Easy or the downloadable installer?
- Linux/BSD distribution name and version:
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):
- Web server (Apache or Nginx):
- Manage mail accounts with iRedAdmin-Pro?
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 0.9.9
- Deployed with iRedMail Easy or the downloadable installer? Downloaded
- Linux/BSD distribution name and version: ubuntu 18.04.1
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): PGSQL
- Web server (Apache or Nginx): NGINX
- Manage mail accounts with iRedAdmin-Pro? No
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

Hi again, i was just checking syslog and realised an error

“Feb  6 01:09:51 mail postfix/dnsblog[Feb  6 01:09:51 mail postfix/dnsblog[28913]: warning: dnsblog_query: lookup error for DNS query 78.116.119.45.zen.spamhaus.org: Host or domain name not found. Name service error for name=78.116.119.45.zen.spamhaus.org type=A: Host not found, try again]: warning: dnsblog_query: lookup error for DNS query 78.116.119.45.zen.spamhaus.org: Host or domain name not found. Name service error for name=78.116.119.45.zen.spamhaus.org type=A: Host not found, try again”

Can someone pls enligten me about this error and corrective action? Thank you

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 0.9.9
- Deployed with iRedMail Easy or the downloadable installer?
- Linux/BSD distribution name and version: Centos 7
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): LDAP
- Web server (Apache or Nginx):Nginx
- Manage mail accounts with iRedAdmin-Pro?
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====
I have a problem with the iredadmin: I have recently installed the version 0,9,9, the rouncubemail it works and good in the voyager, perocuandointento turns on accessing iredadmin https://10.0.0.2/iredadmin this appears to 502 Bad Gateway of the NGIX in the NGINX's log and with error put salt in the sigiuente error:

exit for /var/log/nginx/error.log

2019/02/06 10:34:58 [error] 723#0: *19 upstream prematurely closed connection while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET /iredadmin HTTP/1.1", upstream: "uwsgi://127.0.0.1:7791", host: "10.0.0.2"
2019/02/06 10:35:37 [error] 723#0: *19 upstream prematurely closed connection while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET /iredadmin/ HTTP/1.1", upstream: "uwsgi://127.0.0.1:7791", host: "10.0.0.2"
2019/02/06 10:35:43 [error] 723#0: *24 upstream prematurely closed connection while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET /iredadmin/ HTTP/1.1", upstream: "uwsgi://127.0.0.1:7791", host: "10.0.0.2"
2019/02/06 10:36:12 [error] 1347#0: *3 upstream prematurely closed connection while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET /iredadmin/ HTTP/1.1", upstream: "uwsgi://127.0.0.1:7791", host: "10.0.0.2"
2019/02/06 10:36:13 [error] 1347#0: *3 upstream prematurely closed connection while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET /iredadmin/ HTTP/1.1", upstream: "uwsgi://127.0.0.1:7791", host: "10.0.0.2"
2019/02/06 10:36:13 [error] 1347#0: *3 upstream prematurely closed connection while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET /iredadmin/ HTTP/1.1", upstream: "uwsgi://127.0.0.1:7791", host: "10.0.0.2"
2019/02/06 10:36:13 [error] 1347#0: *3 upstream prematurely closed connection while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET /iredadmin/ HTTP/1.1", upstream: "uwsgi://127.0.0.1:7791", host: "10.0.0.2"
2019/02/06 10:36:14 [error] 1347#0: *3 upstream prematurely closed connection while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET /iredadmin/ HTTP/1.1", upstream: "uwsgi://127.0.0.1:7791", host: "10.0.0.2"
2019/02/06 10:36:15 [error] 1347#0: *3 upstream prematurely closed connection while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET /iredadmin/ HTTP/1.1", upstream: "uwsgi://127.0.0.1:7791", host: "10.0.0.2"
2019/02/06 10:36:16 [error] 1347#0: *3 upstream prematurely closed connection while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET /iredadmin/ HTTP/1.1", upstream: "uwsgi://127.0.0.1:7791", host: "10.0.0.2"
2019/02/06 10:36:17 [error] 1347#0: *3 upstream prematurely closed connection while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET /iredadmin/ HTTP/1.1", upstream: "uwsgi://127.0.0.1:7791", host: "10.0.0.2"
2019/02/06 10:36:17 [error] 1347#0: *3 upstream prematurely closed connection while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET /iredadmin/ HTTP/1.1", upstream: "uwsgi://127.0.0.1:7791", host: "10.0.0.2"
2019/02/06 10:36:17 [error] 1347#0: *3 upstream prematurely closed connection while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET /iredadmin/ HTTP/1.1", upstream: "uwsgi://127.0.0.1:7791", host: "10.0.0.2"
2019/02/06 10:36:22 [error] 1347#0: *3 upstream prematurely closed connection while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET /iredadmin/ HTTP/1.1", upstream: "uwsgi://127.0.0.1:7791", host: "10.0.0.2"
2019/02/06 10:36:24 [error] 1347#0: *3 upstream prematurely closed connection while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET /iredadmin/ HTTP/1.1", upstream: "uwsgi://127.0.0.1:7791", host: "10.0.0.2"
2019/02/06 10:36:24 [error] 1347#0: *3 upstream prematurely closed connection while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET /iredadmin/ HTTP/1.1", upstream: "uwsgi://127.0.0.1:7791", host: "10.0.0.2"
2019/02/06 10:38:38 [error] 1347#0: *66 upstream prematurely closed connection while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET /iredadmin/ HTTP/1.1", upstream: "uwsgi://127.0.0.1:7791", host: "10.0.0.2"
2019/02/06 10:42:04 [error] 1347#0: *137 upstream prematurely closed connection while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET /iredadmin/ HTTP/1.1", upstream: "uwsgi://127.0.0.1:7791", host: "10.0.0.2"
2019/02/06 10:42:05 [error] 1347#0: *137 upstream prematurely closed connection while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET /iredadmin/ HTTP/1.1", upstream: "uwsgi://127.0.0.1:7791", host: "10.0.0.2"
2019/02/06 10:42:05 [error] 1347#0: *137 upstream prematurely closed connection while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET /iredadmin/ HTTP/1.1", upstream: "uwsgi://127.0.0.1:7791", host: "10.0.0.2"
2019/02/06 10:42:06 [error] 1347#0: *137 upstream prematurely closed connection while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET /iredadmin/ HTTP/1.1", upstream: "uwsgi://127.0.0.1:7791", host: "10.0.0.2"
2019/02/06 10:47:29 [error] 1539#0: *3 upstream prematurely closed connection while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET /iredadmin/ HTTP/1.1", upstream: "uwsgi://127.0.0.1:7791", host: "10.0.0.2"
2019/02/06 10:47:30 [error] 1539#0: *3 upstream prematurely closed connection while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET /iredadmin/ HTTP/1.1", upstream: "uwsgi://127.0.0.1:7791", host: "10.0.0.2"
2019/02/06 10:48:39 [error] 455#0: *26 upstream prematurely closed connection while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET /iredadmin/ HTTP/1.1", upstream: "uwsgi://127.0.0.1:7791", host: "10.0.0.2"
2019/02/06 10:48:44 [error] 455#0: *26 upstream prematurely closed connection while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET /iredadmin/ HTTP/1.1", upstream: "uwsgi://127.0.0.1:7791", host: "10.0.0.2"
2019/02/06 10:52:31 [error] 1371#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: _, request: "GET /status?full&json HTTP/1.1", upstream: "fastcgi://127.0.0.1:9999", host: "localhost"
2019/02/06 10:52:34 [error] 1371#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: _, request: "GET /status?full&json HTTP/1.1", upstream: "fastcgi://127.0.0.1:9999", host: "localhost"
2019/02/06 10:52:37 [error] 1371#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: _, request: "GET /status?full&json HTTP/1.1", upstream: "fastcgi://127.0.0.1:9999", host: "localhost"
2019/02/06 10:52:40 [error] 1371#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: _, request: "GET /status?full&json HTTP/1.1", upstream: "fastcgi://127.0.0.1:9999", host: "localhost"
2019/02/06 10:52:43 [error] 1371#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: _, request: "GET /status?full&json HTTP/1.1", upstream: "fastcgi://127.0.0.1:9999", host: "localhost"
2019/02/06 10:52:53 [error] 1371#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: _, request: "GET /status?full&json HTTP/1.1", upstream: "fastcgi://127.0.0.1:9999", host: "localhost"
2019/02/06 10:53:02 [error] 1371#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: _, request: "GET /status?full&json HTTP/1.1", upstream: "fastcgi://127.0.0.1:9999", host: "localhost"
2019/02/06 10:53:11 [error] 1371#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: _, request: "GET /status?full&json HTTP/1.1", upstream: "fastcgi://127.0.0.1:9999", host: "localhost"
2019/02/06 10:53:20 [error] 1371#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: _, request: "GET /status?full&json HTTP/1.1", upstream: "fastcgi://127.0.0.1:9999", host: "localhost"
2019/02/06 10:53:29 [error] 1371#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: _, request: "GET /status?full&json HTTP/1.1", upstream: "fastcgi://127.0.0.1:9999", host: "localhost"
2019/02/06 10:53:46 [error] 1371#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: _, request: "GET /status?full&json HTTP/1.1", upstream: "fastcgi://127.0.0.1:9999", host: "localhost"
2019/02/06 10:54:04 [error] 1371#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: _, request: "GET /status?full&json HTTP/1.1", upstream: "fastcgi://127.0.0.1:9999", host: "localhost"
2019/02/06 10:54:22 [error] 1371#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: _, request: "GET /status?full&json HTTP/1.1", upstream: "fastcgi://127.0.0.1:9999", host: "localhost"
2019/02/06 10:54:40 [error] 1371#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: _, request: "GET /status?full&json HTTP/1.1", upstream: "fastcgi://127.0.0.1:9999", host: "localhost"
2019/02/06 10:54:58 [error] 1371#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: _, request: "GET /status?full&json HTTP/1.1", upstream: "fastcgi://127.0.0.1:9999", host: "localhost"
2019/02/06 10:55:23 [error] 1371#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: _, request: "GET /status?full&json HTTP/1.1", upstream: "fastcgi://127.0.0.1:9999", host: "localhost"
2019/02/06 10:55:48 [error] 1616#0: *3 upstream prematurely closed connection while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET /iredadmin/ HTTP/1.1", upstream: "uwsgi://127.0.0.1:7791", host: "10.0.0.2"
2019/02/06 10:55:51 [error] 1616#0: *3 upstream prematurely closed connection while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET /iredadmin/ HTTP/1.1", upstream: "uwsgi://127.0.0.1:7791", host: "10.0.0.2"
2019/02/06 10:56:07 [error] 1616#0: *3 upstream prematurely closed connection while reading response header from upstream, client: 192.168.0.1, server: _, request: "GET /iredadmin/ HTTP/1.1", upstream: "uwsgi://127.0.0.1:7791", host: "10.0.0.2"

I eat to correct the same in order that the console come out of the iredadmin

And also getting this one:

managed-keys-zone: Unable to fetch DNSKEY set '.': timed out

Does restarting "iredadmin" service fix this issue?

9.9
downloadble install
centos
mariadb
apache
dont know.
none.

We have many businesses with even more domains that need to send email with dkim. Here is my issue, We are using a program that will be the go between to send out email from the individual sending domains. It acts as mailchimp and mailgun does in providing templates and outbound email and connects with all of our other services. Can IRedMail act as the smtp server so that the actual sending domain can send with dkim emails. We cant really individually add each domain or email address.

Explanation of our system

Multiple businesses each with multiple Sending domain with multiple email addresses

Our mailchimp like server program

Actual SMTP server that sends the email

How do I set this up or does someone have a guide? Any way to make this relay server, like get the transferred dkim from the sending domain.

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 0.9.9
- Deployed with iRedMail Easy or the downloadable installer? downloadable installer
- Linux/BSD distribution name and version: Ubuntu 18.04
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? No
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

Hi,

i've set up a 2 node iRedMail cluster with mariadb and dovecot replication.
I tested a failover und shutdown node 2 all fine, i started node 2 backup and shutdown node 1 and i have "DB Error: SQLSTATE[HY000] [1045] Access denied for user" in all services.

The passwords and grants on both nodes are the same, can't figure out whats causing the error.

Regards

i think figured out the problem, during the mariadb replication setup i move a mysqldump from node 1 to node 2 i selected all databases, therefore the users in the mysql db have the same passwords. But on node 2, for example, the postfix config had a other password.

I think i need to reinstall the second node.

regards

*** Update ***
i found all the users and passwords in the installation folder under iRedMail(version).tips and changed the passwords in the mariadb and all is working fine.

Something schould be wrong i my replication configuration at mariadb. Sometimes my service users get the passwords of the other node.

this is my rep configuration:
[mariadb]
server_id=2
log-basename=slave1
log_bin
auto_increment_increment=10
auto_increment_offset=1
binlog_do_db='amavisd'
binlog_do_db='iredadmin'
binlog_do_db='roundcubemail'
binlog_do_db='sogo'
binlog_do_db='vmail'
binlog_ignore_db='test'
binlog_ignore_db='information_schema'
binlog_ignore_db='mysql'
binlog_ignore_db='iredapd'
replicate_ignore_db='test'
replicate_ignore_db='information_schema'
replicate_ignore_db='mysql'
replicate_ignore_db='iredapd'
slave-parallel-threads=5

someone a idea why this happen?

Thanks.

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 0.9.9
- Deployed with iRedMail Easy or the downloadable installer? Downloadable Installer
- Linux/BSD distribution name and version:  Ubuntu 18.04 (current)
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):  MariaDB 10.1.34
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? No
====

Greetings! Thank you Zhang Huangbin for creation and for ongoing support of iRedMail. I have used it for several years and love the completeness and security of the whole suite.

A couple years ago I tried to run a web site along with iRedAdmin and RoundCube on the same Nginx instance. I have since given up trying to configure that. Now, although the iRedAdmin web pages render fine, nginx cannot find RoundCube. After re-directing from the base URL to https://hostname/mail/ it simply returns 404. I have enabled "debug" in the logs, but that does not help me understand.

I have attached the full nginx configuration (via

nginx -T

).

I very much appreciate any help folks can offer. I would be happy to provide nginx logs as well.

Thanks!

David Klann