==== 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.
====

Server version 1.0
Manually update from .9.9
Backend MYSQL
Nginx
Manage with iredadmin pro

I can log in to the admin account with the web login just fine, but iredadmin pro with failed credentials error. I looked at the other thread regarding this matter and password hashes are all ssha512

Any suggestions ?

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

Since upgrading using the Easy installer the global SMTP relay was disabled - presume this is because main.cf was completely replaced.  So I thought I would just enter the server name at the Relay tab for each Domain, which I entered as per the attached screenshot.  However, after doing this, emails sent from this domain started bouncing with the error:

<user@icloud.com>: host mail.smtp2go.com[139.162.6.108] said: 550
   relay access denied - please authenticate (in reply to RCPT TO command)

The username and password is still stored in /etc/postfix/sasl_password and I also ran:
postmap hash:/etc/postfix/sasl_password
service postfix restart

but to no avail, as it doesn't appear to be picking up the authentication details from there.

How do we enter the authentication username and password in iRedAdmin Pro?

If this is not possible, what is the best practice to setup a global relay server.  In the docs I read that main.cf should be modified by editing /opt/iredmail/custom/postfix/custom.sh

Are you able to advise what should be added to 'custom.sh' to set the relay server as:
mail.smtp2go.com:2525

Thanks a lot,
Stephen

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

Jun 22 15:44:05 mail03 amavis[4160]: (04160-08) Blocked BANNED (.asc,highlight.js) {DiscardedInternal,Quarantined}, ORIGINATING LOCAL [##..##.##.##]:43064 [##.##.##.##] <user@domain> -> , quarantine: yp_QkTpmvJNa, Queue-ID: 36BA913821FC, Message-ID: <47BAA310-E55C-471D-9609-C520990F5A97@2030-kommunikation.de>, mail_id: yp_QkTpmvJNa, Hits: -, size: 856312, 1174 ms

Hi,

I got reports from a local user, that mail with an attachment does not reach destination on different mail servers. Sending user via SMTP does not receive a message that the mail will not be delivered.
Checking the logs on my side, it seems amavis does discard the message (see log above).
That may or may not be ok, but why does the sending user not receive an info, that the mail is discarded?

Thanks in advance, regards

Jochen
What's the best way to change this behaviour?

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

Hi Zhang,

Inbound emails from EIG servers (unifiedlayer.com) are rejected with the following error:

554 5.7.1 <1-2-3-4.unifiedlayer.com>: Helo command rejected: ACCESS DENIED. Your email was rejected because the sending mail server appears to be on a dynamic IP address that should not be doing direct mail delivery (1-2-3-4)

(Of course, the IP address is masked.)

There are these existing lines in /etc/postfix/helo_access.pcre, about half way down:

# bypass some HELOs which contains IP address
/^o\d{1,3}-\d{1,3}-\d{1,3}-\d{1,3}\.outbound-mail\.sendgrid\.net$/ DUNNO

So in order to accept emails from EIG/unifiedlayer.com servers I added this line immediately below the above two lines and restarted Postfix:

/^o\d{1,3}-\d{1,3}-\d{1,3}-\d{1,3}\.unifiedlayer\.com$/ DUNNO

However, the emails are still bounced with the same error message.

Do you have a suggestion for what is still causing the sending server to be blocked?

Thank-you.

Craig

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.0 MARIADB edition.
- Deployed with iRedMail Easy or the downloadable installer? Yes. Downloadable installer
- Linux/BSD distribution name and version: CentOS Linux release 7.8.2003 (Core)
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MARIADB
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? Yes
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====
Jun 24 10:22:12 email postfix/submission/smtpd[12662]: connect from c-24-18-149-33.hsd1.wa.comcast.net[24.18.149.33]
Jun 24 10:22:13 email postfix/submission/smtpd[12662]: SSL_accept error from c-24-18-149-33.hsd1.wa.comcast.net[24.18.149.33]: -1
Jun 24 10:22:13 email postfix/submission/smtpd[12662]: warning: TLS library problem: 12662:error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol:s23_srvr.c:640:
Jun 24 10:22:13 email postfix/submission/smtpd[12662]: lost connection after STARTTLS from c-24-18-149-33.hsd1.wa.comcast.net[24.18.149.33]
Jun 24 10:22:13 email postfix/submission/smtpd[12662]: disconnect from c-24-18-149-33.hsd1.wa.comcast.net[24.18.149.33]

If I need to upgrade to the latest version of iRedmail, how do I get the code to go from 1.0 to current Pro version? I do have the .tar to upgrade from 1.1 to 1.2, but not 1.0 to 1.1.

~ B

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

Hi ,
Need urgent help - LIve server , lots of clients. . After upgrading 1.1 ->1.2 , mail sending/receiving stopped working .

iredapd seems cannot start (updated to 4 )

systemctl status iredapd.service
● iredapd.service - iRedAPD (A simple posfix policy server)
   Loaded: loaded (/lib/systemd/system/iredapd.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2020-06-27 23:41:48 UTC; 47s ago
  Process: 4105 ExecStart=/usr/bin/python3 /opt/iredapd/iredapd.py (code=exited, status=1/FAILURE)

Jun 27 23:41:48 mxc systemd[1]: Starting iRedAPD (A simple posfix policy server)...
Jun 27 23:41:48 mxc python3[4105]: Traceback (most recent call last):
Jun 27 23:41:48 mxc python3[4105]:   File "/opt/iredapd/iredapd.py", line 20, in <module>
Jun 27 23:41:48 mxc python3[4105]:     from libs import __version__, daemon, utils
Jun 27 23:41:48 mxc python3[4105]:   File "/opt/iRedAPD-4.0/libs/utils.py", line 18, in <module>
Jun 27 23:41:48 mxc python3[4105]:     from web import sqlquote
Jun 27 23:41:48 mxc python3[4105]: ModuleNotFoundError: No module named 'web'
Jun 27 23:41:48 mxc systemd[1]: iredapd.service: Control process exited, code=exited status=1
Jun 27 23:41:48 mxc systemd[1]: iredapd.service: Failed with result 'exit-code'.
Jun 27 23:41:48 mxc systemd[1]: Failed to start iRedAPD (A simple posfix policy server).

mail.log:

Jun 27 23:54:58 mxc postfix/cleanup[3641]: warning: connect to TCP map 127.0.0.1:7778: Connection refused
Jun 27 23:54:58 mxc postfix/cleanup[3641]: warning: tcp:127.0.0.1:7778 lookup error for "netdata@MYSERVERDOMAINWASHERE"
Jun 27 23:54:58 mxc postfix/cleanup[3641]: warning: 49vVwn5Jbmz3wj1: sender_canonical_maps map lookup problem for netdata@MYSERVERDOMAINWASHERE -- message not accepted, try again later
Jun 27 23:54:58 mxc postfix/pickup[3049]: warning: maildrop/49vSdJ6pmkz3x24: error writing 49vVwn5Jbmz3wj1: queue file write error
Jun 27 23:54:58 mxc postfix/pickup[3049]: 49vVwy5LnXz3wj1: uid=0 from=<root>
Jun 27 23:54:58 mxc postfix/cleanup[3061]: warning: connect to TCP map 127.0.0.1:7778: Connection refused
Jun 27 23:54:59 mxc postfix/submission/smtpd[5731]: warning: connect to TCP map 127.0.0.1:7779: Connection refused
Jun 27 23:54:59 mxc postfix/cleanup[3061]: warning: connect to TCP map 127.0.0.1:7778: Connection refused
Jun 27 23:55:00 mxc postfix/postscreen[3583]: CONNECT from [114.237.188.198]:4294 to [MYSERVERIPWASHERE]:25
Jun 27 23:55:00 mxc postfix/dnsblog[4390]: addr 114.237.188.198 listed by domain zen.spamhaus.org as 127.0.0.11
Jun 27 23:55:00 mxc postfix/dnsblog[4390]: addr 114.237.188.198 listed by domain zen.spamhaus.org as 127.0.0.4
Jun 27 23:55:00 mxc postfix/dnsblog[4390]: addr 114.237.188.198 listed by domain zen.spamhaus.org as 127.0.0.3
Jun 27 23:55:00 mxc postfix/dnsblog[6011]: addr 114.237.188.198 listed by domain b.barracudacentral.org as 127.0.0.2
Jun 27 23:55:00 mxc postfix/submission/smtpd[5731]: warning: connect to TCP map 127.0.0.1:7779: Connection refused
Jun 27 23:55:00 mxc postfix/cleanup[3061]: warning: connect to TCP map 127.0.0.1:7778: Connection refused
Jun 27 23:55:01 mxc postfix/submission/smtpd[5731]: warning: connect to TCP map 127.0.0.1:7779: Connection refused
Jun 27 23:55:01 mxc postfix/cleanup[3061]: warning: connect to TCP map 127.0.0.1:7778: Connection refused
Jun 27 23:55:02 mxc postfix/postscreen[3583]: CONNECT from [49.88.64.179]:9207 to [MYSERVERIPWASHERE]:25
Jun 27 23:55:02 mxc postfix/dnsblog[3585]: addr 49.88.64.179 listed by domain zen.spamhaus.org as 127.0.0.11
Jun 27 23:55:02 mxc postfix/dnsblog[3585]: addr 49.88.64.179 listed by domain zen.spamhaus.org as 127.0.0.4
Jun 27 23:55:02 mxc postfix/dnsblog[3585]: addr 49.88.64.179 listed by domain zen.spamhaus.org as 127.0.0.3
Jun 27 23:55:02 mxc postfix/dnsblog[3584]: addr 49.88.64.179 listed by domain b.barracudacentral.org as 127.0.0.2
Jun 27 23:55:02 mxc postfix/submission/smtpd[5731]: warning: connect to TCP map 127.0.0.1:7779: Connection refused
Jun 27 23:55:02 mxc postfix/cleanup[3061]: warning: connect to TCP map 127.0.0.1:7778: Connection refused
Jun 27 23:55:03 mxc postfix/submission/smtpd[5731]: warning: connect to TCP map 127.0.0.1:7779: Connection refused
Jun 27 23:55:03 mxc postfix/cleanup[3061]: warning: connect to TCP map 127.0.0.1:7778: Connection refused
Jun 27 23:55:04 mxc postfix/submission/smtpd[5731]: warning: connect to TCP map 127.0.0.1:7779: Connection refused
Jun 27 23:55:04 mxc postfix/cleanup[3061]: warning: connect to TCP map 127.0.0.1:7778: Connection refused
Jun 27 23:55:05 mxc postfix/submission/smtpd[5731]: warning: connect to TCP map 127.0.0.1:7779: Connection refused
Jun 27 23:55:05 mxc postfix/cleanup[3061]: warning: connect to TCP map 127.0.0.1:7778: Connection refused
Jun 27 23:55:06 mxc postfix/postscreen[3583]: DNSBL rank 5 for [114.237.188.198]:4294
Jun 27 23:55:06 mxc postfix/postscreen[3583]: DISCONNECT [114.237.188.198]:4294
Jun 27 23:55:06 mxc postfix/submission/smtpd[5731]: warning: connect to TCP map 127.0.0.1:7779: Connection refused
Jun 27 23:55:06 mxc postfix/submission/smtpd[5731]: warning: tcp:127.0.0.1:7779 lookup error for "EMAILWASHERE@EMAILDOMAINWASHERE"
Jun 27 23:55:06 mxc postfix/submission/smtpd[5731]: NOQUEUE: reject: RCPT from MYSERVERDOMAINWASHERE[127.0.0.1]: 451 4.3.0 <EMAILWASHERE@EMAILDOMAINWASHERE>: Temporary lookup failure; from=<EMAILWASHERE@EMAILDOMAINWASHERE> to=<EMAILWASHERE@EMAILDOMAINWASHERE> proto=ESMTP helo=<localhost>
Jun 27 23:55:06 mxc roundcube: <gomelc8i> PHP Error: Invalid response code received from server (POST /mail/?_task=mail&_unlock=loading1593302097072&_framed=1&_lang=en&_action=send)
Jun 27 23:55:06 mxc roundcube: <gomelc8i> SMTP Error: Failed to add recipient 'EMAILWASHERE@EMAILDOMAINWASHERE'. 4.3.0 <EMAILWASHERE@EMAILDOMAINWASHERE>: Temporary lookup failure (Code: 451) in /opt/www/roundcubemail-1.3.8/program/lib/Roundcube/rcube.php on line 1689 (POST /mail/?_t
ask=mail&_unlock=loading1593302097072&_framed=1&_lang=en&_action=send)
Jun 27 23:55:06 mxc postfix/submission/smtpd[5731]: disconnect from MYSERVERDOMAINWASHERE[127.0.0.1] ehlo=2 starttls=1 auth=1 mail=1 rcpt=0/1 rset=1 quit=1 commands=7/8
Jun 27 23:55:06 mxc postfix/cleanup[3061]: warning: connect to TCP map 127.0.0.1:7778: Connection refused
Jun 27 23:55:07 mxc postfix/cleanup[3061]: warning: connect to TCP map 127.0.0.1:7778: Connection refused
Jun 27 23:55:07 mxc postfix/cleanup[3061]: warning: tcp:127.0.0.1:7778 lookup error for "root@MYSERVERDOMAINWASHERE"
Jun 27 23:55:07 mxc postfix/cleanup[3061]: warning: 49vVwy5LnXz3wj1: sender_canonical_maps map lookup problem for root@MYSERVERDOMAINWASHERE -- message not accepted, try again later
Jun 27 23:55:07 mxc postfix/pickup[3049]: warning: maildrop/49vSQd1vv2z3x1p: error writing 49vVwy5LnXz3wj1: queue file write error
Jun 27 23:55:07 mxc postfix/pickup[3049]: 49vVx75PVHz3wj1: uid=0 from=<root>
Jun 27 23:55:07 mxc postfix/cleanup[3641]: warning: connect to TCP map 127.0.0.1:7778: Connection refused
Jun 27 23:55:08 mxc postfix/postscreen[3583]: DNSBL rank 5 for [49.88.64.179]:9207
Jun 27 23:55:08 mxc postfix/postscreen[3583]: DISCONNECT [49.88.64.179]:9207
Jun 27 23:55:08 mxc postfix/cleanup[3641]: warning: connect to TCP map 127.0.0.1:7778: Connection refused
Jun 27 23:55:09 mxc postfix/cleanup[3641]: warning: connect to TCP map 127.0.0.1:7778: Connection refused
Jun 27 23:55:10 mxc postfix/cleanup[3641]: warning: connect to TCP map 127.0.0.1:7778: Connection refused
Jun 27 23:55:11 mxc postfix/cleanup[3641]: warning: connect to TCP map 127.0.0.1:7778: Connection refused
Jun 27 23:55:12 mxc postfix/cleanup[3641]: warning: connect to TCP map 127.0.0.1:7778: Connection refused
Jun 27 23:55:13 mxc postfix/postscreen[3583]: CONNECT from [49.68.145.22]:1442 to [MYSERVERIPWASHERE]:25
Jun 27 23:55:13 mxc postfix/dnsblog[3585]: addr 49.68.145.22 listed by domain zen.spamhaus.org as 127.0.0.4
Jun 27 23:55:13 mxc postfix/dnsblog[3585]: addr 49.68.145.22 listed by domain zen.spamhaus.org as 127.0.0.3
Jun 27 23:55:13 mxc postfix/dnsblog[3585]: addr 49.68.145.22 listed by domain zen.spamhaus.org as 127.0.0.11
Jun 27 23:55:13 mxc postfix/dnsblog[3897]: addr 49.68.145.22 listed by domain b.barracudacentral.org as 127.0.0.2
Jun 27 23:55:13 mxc postfix/cleanup[3641]: warning: connect to TCP map 127.0.0.1:7778: Connection refused
Jun 27 23:55:14 mxc postfix/cleanup[3641]: warning: connect to TCP map 127.0.0.1:7778: Connection refused
Jun 27 23:55:15 mxc postfix/cleanup[3641]: warning: connect to TCP map 127.0.0.1:7778: Connection refused

==== 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.
====

Centos 7
Test of new install about 2 weeks ago with updates applied today (kernel, sope49, sogo, rsyslog, python-perf).
Mysql

Have an unused domain with a test.user account and sends email out.  RoundCube shows red box stating interal server error though on interface (attached).  Appears from docs that RoundCube logs to: /var/log/maillog.

Does it in fact log there? 

Example: errors
Jun 27 23:50:51 m01 postfix/error[1835]: 49YnmH2prdzDy7: to=<postmaster@domain_name.com>, relay=none, delay=2490588, delays=2490588/0.15/0/0.08, dsn=4.3.0, status=deferred (address resolver failure)

Jun 27 23:50:51 m01 postfix/error[1835]: warning: proxy:mysql:/etc/postfix/mysql/relay_domains.cf: table lookup problem
Jun 27 23:50:51 m01 postfix/error[1835]: warning: 49YnmH2prdzDy7: flush service failure

Jun 27 23:50:51 m01 postfix/cleanup[1829]: warning: proxy:mysql:/etc/postfix/mysql/virtual_alias_maps.cf lookup error for "root@m01.domain.tld"

Jun 28 01:10:02 m01 postfix/trivial-rewrite[1882]: warning: proxy:mysql:/etc/postfix/mysql/transport_maps_maillist.cf lookup error for "*"

What is wrong and/or am I missing?

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.2.1
- Deployed with iRedMail Easy or the downloadable installer? installer
- Linux/BSD distribution name and version: centos 8
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): mysql
- Web server (Apache or Nginx): nginx
- Manage mail accounts with iRedAdmin-Pro? yes
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====
Setup:
iredmail-pro server with an address it@domain2.tld, all email to this address are set to forward to
user1@domain1.tdl and user2@dmain2.tld

if any user from domain1.tld send an email to it@domain2.tld we get the email refused with the error
REJECT SMTP AUTH is required for users under this sender domain

followed instruction on posting https://forum.iredmail.org/topic14387-s … -list.html

add a setting in /opt/iredapd/settings.py and restart iredapd service:

CHECK_SPF_IF_LOGIN_MISMATCH = True

..... it seemed to have worked for Craig    BUT NO JOY for me.

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

I have multiple CIDR Network blocks set up in my blacklist.

173.232.33.0/24  is working.
50.2.209.0/24 is not.   

I have to manually put in entries such as

50.2.209.156
50.2.209.164

The only thing that I can see obviously is that 50.0.0.0  is a class A network and 173.232.33.0 is a class C.  Since network classes are pretty much a thing of the past and only subnet masks really matter anymore, I doubt whether this is related, but it's the only thing I can see which could possibly be relevant.

I can see in my admin panel where specific IPs such as 50.2.209.156 are blocking.   Class C networks are blocking.   50.2.209.0/24 is not blocking.

Any ideas?

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

Hello,
after the upgrade of iRedAdmin-Pro-SQL to version 4.4 the top senders are no longer displayed in the dashboard.
After rolling back to version 4.3 they are displayed again

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

In the template templates/default/dashboard.html it literally says N/A:

<tr>
 86                     <td><i class="fa fa-ban fa-lg color-red"></i></td>
 87                     <th>{{ _('Banned IP Addresses') }}</th>
 88                     <td class="full"><a id="count_banned_ip" href="{{ ctx.homepath }}/activities/fail2ban/banned">N/A</a></td>
 89                 </tr>

Was this an oversight? Surely you could ask SQL to count the rows in the DB.

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.2.1
- Deployed with iRedMail Easy or the downloadable installer? download
- Linux/BSD distribution name and version: ubuntu 18.04 LTS
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): LDAP
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? Yes
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====
We have an antispam/virus mail gateway server and want to relay all mail through it before it hits the inbox of a user - so email sent internally and outside email. In the domain settings, under relay, I tried both:
[dfmx03.domain.com]
dfmx03.domain.com
I then sent an email to a user in domain.com and it was delivered to their mailbox right away instead of going out of the system to the antispam/virus scanner.
The only way I have gotten this to work is to have a second server setup for domain.com and set the "Relay received email to" to:
smtp:dfmx03.domain.com:25
Then the antispam server scans the email and delivers it to the real incoming server for domain.com.
Am I missing something?

Thanks

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): v1.3
- Deployed with iRedMail Easy or the downloadable installer? dowload installer
- Linux/BSD distribution name and version: ubuntu 20.04 LTS
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx):Nginx
- Manage mail accounts with iRedAdmin-Pro? yes
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====
我安装新系统 ubuntu 20.04, 然后安装 iRedMail v1.3, 检查连接iRedadmin 正常， 再装上iRedmail Pro 就出这问题。
用户连接web mail 可以， 但是不能连接 iRedadmin 了。显示 "404 Not Found nginx".
请问是什么问题？

my dovecot server does not accept connections with TLSv1.2, however 1, 1.1 & 1.3 are working

openssl s_client -crlf -connect ripley.calvi.de:993 -tls1_2 -> fails

postfix is working fine on all protocols

any idea what might be wrong ?

====
iRedMail version: 1.1 MYSQL edition
Deployed with downloadable installer
Ubuntu 18.04.4 LTS
ApacheiRedAdmin-Pro
====

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

After upgrade to iRedMail 1.3 and iRedAdmin-Pro 4.4 I'm not able to edit any account profile in iRedAdmin-Pro. When clicking on the name to edit, I'm getting error message:

Error: ConnectionError(ProtocolError('Connection aborted.', BadStatusLine('No status line received - the server has closed the connection',)),)

Editing anything else, e.g. Domains, Aliases, etc. works fine…

Thanks for the help!

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

Hello,

in our server we receive the next messages in the sogo.log and its look related to a case when the users try to access to the webmail and doesnt load the folders or messages:

Jul 01 16:55:58 sogod [2143362]: 190.252.226.186 "POST /SOGo/so/director1@gyomedical.com.co/Mail/unseenCount HTTP/1.0" 200 21/31 0.116 - - 0
Jul 01 16:55:58 sogod [2143362]: <0x0x563de53b9d40[NGImap4Client]> ERROR(-[NGImap4Client _handleShutdownDuringCommandException:]): IMAP4 socket was shut down by server NGSocketShutdownDuringReadException: the socket was shutdown
Jul 01 16:55:58 sogod [2143362]: [ERROR] <0x0x563de3b39910[NGImap4ConnectionManager]> IMAP4 login failed:
Jul 01 16:55:58 sogod [2143362]: <0x563de5a8f8b0[SOGoMailAccount]:0> renewing imap4 password
Jul 01 16:55:58 sogod [2143362]: <0x0x563de530fb00[NGImap4Client]> ERROR(-[NGImap4Client _handleShutdownDuringCommandException:]): IMAP4 socket was shut down by server NGSocketShutdownDuringReadException: the socket was shutdown
Jul 01 16:55:58 sogod [2143362]: [ERROR] <0x0x563de3b39910[NGImap4ConnectionManager]> IMAP4 login failed:
Jul 01 16:55:58 sogod [2143362]: [ERROR] <0x563de5a8f8b0[SOGoMailAccount]:0> Could not connect IMAP4

Please help us to validate the origin of the issue

Many thanks

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

   Hello,

After upgrading iRedAPD from 3.6 to 4.1 version, I started to find many warning messages in maillog:

Jul  3 10:30:20 mail postfix/submission/smtpd[1070]: connect from unknown[x.x.x.x]
Jul  3 10:30:20 mail postfix/submission/smtpd[1070]: Anonymous TLS connection established from unknown[x.x.x.x]: TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)
Jul  3 10:30:20 mail postfix/submission/smtpd[1070]: 548C3200B732: client=unknown[x.x.x.167], sasl_method=LOGIN, sasl_username=user@domain.ltd
Jul  3 10:30:20 mail postfix/cleanup[16290]: 548C3200B732: message-id=<014701d6510b$ce2faf50$6a8f0df0$@domain.ltd>
Jul  3 10:30:21 mail postfix/submission/smtpd[1070]: warning: problem talking to server 127.0.0.1:7777: Success
Jul  3 10:30:21 mail postfix/submission/smtpd[1070]: 548C3200B732: reject: END-OF-MESSAGE from unknown[x.x.x.x]: 451 4.3.5 Server configuration problem; from=<user@domain.ltd> to=<user1@domain1.ltd> proto=ESMTP helo=<hostname>
Jul  3 10:30:23 mail postfix/submission/smtpd[1070]: disconnect from unknown[x.x.x.x]

Jul  3 10:30:20 mail journal: iredapd Whitelisted: wblist=(19, 1740, 'W')
Jul  3 10:30:20 mail journal: iredapd [x.x.x.x] RCPT, user@domain.ltd => user1@domain1.ltd, OK [sasl_username=user@domain.ltd, sender=user@domain.ltd, client_name=unknown, reverse_client_name=unknown, helo=hostname, encryption_protocol=TLSv1.2, encryption_cipher=DHE-RSA-AES256-GCM-SHA384, server_port=, process_time=0.0073s]

Regards
Marius

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

Hello,
I install iredadmin 4.4 last monday, and I have this error when I try to edit a profile:

Error: ConnectionError(ProtocolError('Connection aborted.', BadStatusLine('No status line received - the server has closed the connection',)),)

If I run  python mlmmjadmin.py everythin is OK

api_auth_tokens is the same  mlmmjadmin_api_auth_token but in /opt/www/iredadmin/settings.py it appears twice

cat /opt/www/iredadmin/settings.py | grep api_auth
mlmmjadmin_api_auth_token = ''
mlmmjadmin_api_auth_token = 'RQrI2McJsAN7dYfOGYFseYTaPlKejs'

I have this error in mlmmjadmin.log

Jul  3 13:56:38 esperanto mlmmjadmin: !!!!!!!!!!!!!! WARNING !!!!!!!!!!!!!!
Jul  3 13:56:38 esperanto mlmmjadmin: no request plugin is loaded, you will not be able to manage requests.
Jul  3 13:56:38 esperanto mlmmjadmin: you may need to install the package for your language of choice, or simply load it with --plugin.
Jul  3 13:56:38 esperanto mlmmjadmin: !!!!!!!!!!! END OF WARNING !!!!!!!!!!

many thanks

Hi!

I would like to add a new partition to store new mail data and I found the following part in settings.py:

# Base directory used to store all mail data.
# iRedMail uses '/var/vmail/vmail1' as default storage directory.
# Tip: You can set a per-domain storage directory in domain profile page.
storage_base_directory = "/var/vmail/vmail1"

My plan is to mount the new storage to /var/vmail/vmail2 and i set the per-domain storage directory parameter on the related new domains according to the tip in the comment section. But unfortunately i can't find the per-domain storage directory setting in domain profile page. On the user profile page i can find the path to mailbox parameter but I would prefer to separate the storage between whole domains instead of users.
Can you help me where can I find this option please?

Thank you for your answer!
Regards,
Adam

Hello!

We are monitoring all of the scheduled scripts and their exit codes in our mail server and we realized that the sogo backup script (/var/vmail/backup/backup_sogo.sh) sometimes exits with exit code 1 which generates an alert for us.

The reason of the error is the following lines from the end of the script:

# Try to remove empty directory.
rmdir ${REMOVED_BACKUP_MONTH_DIR} 2>/dev/null
rmdir ${REMOVED_BACKUP_YEAR_DIR} 2>/dev/null

When the related directories are empty there is no problem but if the rmdir can't remove the non-empty directory it returns with 1 and there is no additional exit code after that in the script so it will exit with exit code 1 too.

We temporary corrected this in our instance but could you fix this in the next release please? We would prefer to use the original scripts to avoid any problems.

Thank you for your help!
Best regards,
Adam