I can not reproduce this issue.

I have changed to:
            proxy_buffer_size          1024k;
            proxy_buffers              8 512k;
            proxy_busy_buffers_size    1024k;

Unfortunately without result.
The server terminates the connection.

All this happened after updating SOGo to version 5.7. What other recommendations are there for setting up a proxy. The problem is, but I don't know what to do.

I suppose you mean /etc/postfix/mysql/*.cf file because there is no conf file inside that folder. The contents of the cf file is below.

Is there a log that states where iRedAdmin-Pro is doing/not doing things? It is not changing memberOfGroup attribute in the LDAP database, and it is also not removing member from mailLists when you unclick the checkbox on the user.

To be clear, the web UI shows the user being added or removed, but the actual LDAP entries do not change. It will add a user if they are not already in the group, but it will not remove them from it ever. Using the checkbox under Domain->User-> or the drop down menu in Domain->Mailing List->Member->Remove Selected Members does not remove a user from the group in LDAP. The Web UI shows it as removed (the user no longer shows up in the mailing list under Members) but the LDAP attribute is not changed.

The Web UI also does not update if the changes are made via LDAP. If I make a change to LDAP (ie, remove the member attribute from a mailList) the WebUI does not show this change (the user will still appear to belong in the group; unchecking or deleting the user will remove the user from the WebUI without any error in the webpage but they are already removed). memberOf overlay will update the user when I add them via LDAP, but the WebUI does not show them added to the mailList.

Run a chron script to restart all processes involved.

Why? Users see weird expired ssl certificate errors on a roughly monthly basis. Email clients claim the date does not match any of the expiry dates of the cert bot issued certificates.

This is something of a hack but I’ve found no way to even diagnose the issue server-side.

From what I have done on my own vm, I have installed 1.4.0 and upgrade it to current version. According to the upgrade notes, you have to edit to /etc/iredmail-release and whatever you put in that file it will display as the version in the iRedAdmin.

Thanks for your help. I was able to get this working by implementing the following step on top of my installation

Source: https://github.com/gearrington/acme-dns-certbot-joohoi

After some reading I got the following result

Successfully received certificate.
Certificate is saved at: /etc/letsencrypt/live/mydomain.com/fullchain.pem
Key is saved at:         /etc/letsencrypt/live/mydomain.com/privkey.pem
This certificate expires on 2022-10-02.
These files will be updated when the certificate renews.
Certbot has set up a scheduled task to automatically renew this certificate in the background.

Case closed

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.5.1 MARIADB edition.
- Deployed with iRedMail Easy or the downloadable installer? yes
- Linux/BSD distribution name and version: CENTOS STREAM 8
- 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.
=====

Iredmail is working as designed (I hope ;-) ) but have a question about accessing message sent via a 3rd party app using this email account to sent notifications to different email addresses. When these emails are sent, these don't show up in the SoGo sentbox of this account.

Question: How can I check if these emails are indeed stored in the Iredmail database for this email account ?
Question 2: Any idea where this can go wrong ?

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.6.0
- Deployed with iRedMail Easy or the downloadable installer? downloadable installer
- Linux/BSD distribution name and version: Debian 11
- 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.
====

I have a new iRedmail installation.   I have the mx record for my domain pointing to a standalone server that scans emails for spam and virus before delivery to iRedmail.  I use this same server with a number of other email servers with no issues.  When it tries to deliver mail to the iRedmail server, the messages are rejected with a " Recipient address rejected: unverified address: Recipient address lookup failed" and a return error 554 5.7.1 Relay access denied.

If I point the mx record direct at the redmail server then messages are properly received and processed.

The spam server is in the same subnet and I have tried using the local and pubic address to connect to iRedmail and placed the public and private ip addresses of the spam server in the mynetwork parameter in opt/iredapd/settings.py and main.cf to no avail.   Is there another parameter I should use to allow message relay?

Hello I am having the same issue. Some of our emails are being placed into the recipients junk mail. After checking the tools in mxtoolbox website, the only issue that was identified was DKIM Signature Not Verified. I have a DKIM key for every domain setup on the server. Below is the output from the MXtoolbox test. 

Your help would be highly appreciated

dkim:7h.holdings:dkim
Public Record:
v=DKIM1; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDWplKaNiDDr2msH/lQiYTJ3FrBqXxeAu3LgVrhDNkklycC2G5+mbVxA/J/kmGlv3/mP/T3l1u5On80VgRfuSpS2XXxm4APZclkLwOdNA34p7fxqK7Q3nkSAqCVLkR/qmH9xSPBUPnY9rZ6dY0Aa3+SQ37ADRAQWsLdkAmzRrMURQIDAQAB

Dkim Signature:
v=1; a=rsa-sha256; c=relaxed/simple; d=7h.holdings; h= x-mailer:to:date:message-id:subject:mime-version :content-transfer-encoding:content-type:from; s=dkim; t= 1657131787; x=1657995788; bh=frcCV1k9oG9oKj3dpUqdJg1PxRT2RSN/XKd LCPjaYaY=; b=ivddVxZol73gCZ31tQrRWaM9SslVhn9H3rgktOvY7VNPSaD2dTw Ga/toy6+Iiitt2OObw8Fm70e//DmKForB01jcxwiqyh/26EGMsDIMzwQqD1Emsoo qQmHGIx4rU0sc3I72fbKRfDxeOZeISCr+VO32eFMFf3UOtf5uaIv5VSk=

Email is sent via SMTP protocol, SMTP server doesn't store a copy of sent email at all.

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

Hello.

Freshly installed (maybe 2 weeks ago) iredmail 1.6.0. Installed using the downloadable .sh script.

Everything seems to be fine. I seem to receive / send e-mails as expected. However. On the occasion I see this:

● amavis.service - Interface between MTA and virus scanner/content filters
     Loaded: loaded (/lib/systemd/system/amavis.service; enabled; vendor preset: enabled)
     Active: inactive (dead) since Thu 2022-07-07 20:06:42 IST; 1h 2min ago
       Docs:
    Process: 3438 ExecStartPre=/usr/bin/find /var/lib/amavis -maxdepth 1 -name amavis-* -type d -exec rm -rf {} ; (code=exited, status=0/SUCCESS)
    Process: 3443 ExecStartPre=/usr/bin/find /var/lib/amavis/tmp -maxdepth 1 -name amavis-* -type d -exec rm -rf {} ; (code=exited, status=0/SUCCESS)
    Process: 3445 ExecStart=/usr/sbin/amavisd-new foreground (code=exited, status=0/SUCCESS)
   Main PID: 3445 (code=exited, status=0/SUCCESS)
        CPU: 5.416s

Jul 07 19:46:44 mail.williwonka.eu amavis[3445]: (03445-13) Passed CLEAN {RelayedInternal}, ORIGINATING LOCAL [66.77.88.99]:48068 [66.77.88.99] ESMTP/ESMTP <williwonka@williwonka.eu> -> <williwonka@williwonka.eu>, (ESMTPSA://[66.77.88.99]:48068), Queue-ID: 4Lf53m3f8Hz1dL, Message-ID: <20220707184644.51E62232C@an>
Jul 07 20:01:39 mail.williwonka.eu amavis[3445]: (03445-14) Passed CLEAN {RelayedInternal}, ORIGINATING LOCAL [66.77.88.99]:47468 [66.77.88.99] ESMTP/ESMTP <williwonka@williwonka.eu> -> <williwonka@williwonka.eu>, (ESMTPSA://[66.77.88.99]:47468), Queue-ID: 4Lf0b15fY2z240, Message-ID: <20220707152501.870A3230C@an>
Jul 07 20:01:46 mail.williwonka.eu amavis[3445]: (03445-15) Passed CLEAN {RelayedInternal}, ORIGINATING LOCAL [66.77.88.99]:55258 [66.77.88.99] ESMTP/ESMTP <williwonka@williwonka.eu> -> <williwonka@williwonka.eu>, (ESMTPSA://[66.77.88.99]:55258), Queue-ID: 4Lf5P61vqNz1dD, Message-ID: <20220707190146.0C7862456@an>
Jul 07 20:06:39 mail.williwonka.eu amavis[3445]: (03445-16) Passed CLEAN {RelayedInternal}, ORIGINATING LOCAL [66.77.88.99]:51764 [66.77.88.99] ESMTP/ESMTP <williwonka@williwonka.eu> -> <williwonka@williwonka.eu>, (ESMTPSA://[66.77.88.99]:51764), Queue-ID: 4Ldz4T1VFJz22Q, Message-ID: <20220707141657.03F3E593@pri>
Jul 07 20:06:39 mail.williwonka.eu amavis[3445]: (03445-17) Passed CLEAN {RelayedInternal}, ORIGINATING LOCAL [66.77.88.99]:57786 [66.77.88.99] ESMTP/ESMTP <williwonka@williwonka.eu> -> <williwonka@williwonka.eu>, (ESMTPSA://[66.77.88.99]:57786), Queue-ID: 4Ldz4C0MNhz22J, Message-ID: <20220707141642.CFD6E23C3@an>
Jul 07 20:06:39 mail.williwonka.eu amavis[3445]: (03445-17-2) Passed CLEAN {RelayedInternal}, ORIGINATING LOCAL [66.77.88.99]:52650 [66.77.88.99] ESMTP/ESMTP <williwonka@williwonka.eu> -> <williwonka@williwonka.eu>, (ESMTPSA://[66.77.88.99]:52650), Queue-ID: 4Ldz820kscz22T, Message-ID: <20220707142001.DF21723C3@>
Jul 07 20:06:40 mail.williwonka.eu amavis[3445]: (03445-17-3) Passed CLEAN {RelayedInternal}, ORIGINATING LOCAL [66.77.88.99]:39958 [66.77.88.99] ESMTP/ESMTP <williwonka@williwonka.eu> -> <williwonka@williwonka.eu>, (ESMTPSA://[66.77.88.99]:39958), Queue-ID: 4Lf0hn3Gxjz244, Message-ID: <20220707153001.3345E23C3@>
Jul 07 20:06:40 mail.williwonka.eu amavis[3445]: (03445-17-4) Passed CLEAN {RelayedInternal}, ORIGINATING LOCAL [66.77.88.99]:39956 [66.77.88.99] ESMTP/ESMTP <williwonka@williwonka.eu> -> <williwonka@williwonka.eu>, (ESMTPSA://[66.77.88.99]:39956), Queue-ID: 4Lf0hn39t8z243, Message-ID: <20220707153001.311ED23E2@>
Jul 07 20:06:42 mail.williwonka.eu systemd[1]: amavis.service: Succeeded.
Jul 07 20:06:42 mail.williwonka.eu systemd[1]: amavis.service: Consumed 5.416s CPU time.

I am unable to figure out why amavis dies but then when restarted I seem to be getting a lot of backlogged e-mails.

Can you please try and help?

Ask for any additional info like command outputs or logs and you shall receive it.

Kindest regards.

AndrzejL

how much vram do you have?

Excellent question. This virtual machine has 4GB of RAM allocated to it.

I will increase it to 6 and see if behaviour persists.

Thank you for your reply! I appreciate it.

Kindest regards.

AndrzejL

You should check why amavis crashed, since it starts up normally, but i guess it uses too much vram for spam and virus scanning so it shuts down

I also would suggest this:
https://docs.iredmail.org/completely.di … assin.html

MYNETWORKS in main.cf
and if fail2ban installed, add whitelist range(s).

Hi!

Unfortunately the service crashed last night around 2:30 again:

root@mail:~# systemctl status amavis
● amavis.service - Interface between MTA and virus scanner/content filters
     Loaded: loaded (/lib/systemd/system/amavis.service; enabled; vendor preset: enabled)
     Active: inactive (dead) since Fri 2022-07-08 02:31:41 IST; 5h 30min ago
.
.
Jul 08 02:31:41 mail.williwonka.eu systemd[1]: amavis.service: Succeeded.
Jul 08 02:31:41 mail.williwonka.eu systemd[1]: amavis.service: Consumed 5.351s CPU time.

I will up the ram for the vm to 8 see if it happens again.

I would rather not disable the mentioned above services. Its scary...

Edit: Disabled clamav. Left amavis and spam assassin running. Lets see how that goes.

Kindest regards.

AndrzejL

Thanks for clarifying this. I've added a BCC towards the sending email account, so I expect a copy being sent to this email address. If this works well, I will create a rule to move these to the sent box based on the sending email address.

Unfortunately it keeps happening every now and then so I created a cron job to restart amavis every hour... Its a silly solution I know but I need this working.

Last time I was able to "catch it" was today at 16:46:42

Jul 08 16:46:42 mail.williwonka.eu postfix/submission/smtpd[9770]: connect from 66-77-88-99-hostname [66.77.88.99]
Jul 08 16:46:42 mail.williwonka.eu postfix/submission/smtpd[9770]: Anonymous TLS connection established from 66-77-88-99-hostname [66.77.88.99]: TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256
Jul 08 16:46:42 mail.williwonka.eu python3[882]: iredapd [51.171.4.95] RCPT, williwonka@williwonka.eu => root@williwonka.eu, DUNNO [sasl_username=williwonka@williwonka.eu, sender=williwonka@williwonka.eu, client_name=51-171-4-95-dynamic.agg9.chf.chf-qkr.eircom.net, reverse_client_name=51-171-4-95-dynamic.agg9.chf.chf-qkr.eircom.net, helo=williwonka.eu, encryption_protocol=TLSv1.3, encryption_cipher=TLS_AES_256_GCM_SHA384, server_port=587, process_time=0.0067s]
Jul 08 16:46:42 mail.williwonka.eu postfix/submission/smtpd[9770]: 4Lfd1Z3HRKz1dJ: client=66-77-88-99-hostname [66.77.88.99], sasl_method=PLAIN, sasl_username=williwonka@williwonka.eu
Jul 08 16:46:42 mail.williwonka.eu python3[882]: iredapd [51.171.4.95] END-OF-MESSAGE, williwonka@williwonka.eu => root@williwonka.eu, DUNNO [recipient_count=1, size=688, process_time=0.0008s]
Jul 08 16:46:42 mail.williwonka.eu postfix/cleanup[9771]: 4Lfd1Z3HRKz1dJ: prepend: header Content-Transfer-Encoding: 8bit from 66-77-88-99-hostname [66.77.88.99]; from=<williwonka@williwonka.eu> to=<root@williwonka.eu> proto=ESMTP helo=<williwonka.eu>: List-Unsubscribe: mailto:<sender-email-address>?subject=unsubscribe>"
Jul 08 16:46:42 mail.williwonka.eu postfix/cleanup[9771]: 4Lfd1Z3HRKz1dJ: message-id=<20220708154642.43197243B@williwonka.eu>
Jul 08 16:46:42 mail.williwonka.eu postfix/qmgr[1626]: 4Lfd1Z3HRKz1dJ: from=<williwonka@williwonka.eu>, size=978, nrcpt=1 (queue active)
Jul 08 16:46:42 mail.williwonka.eu postfix/submission/smtpd[9770]: disconnect from 66-77-88-99-hostname [66.77.88.99] ehlo=2 starttls=1 auth=1 mail=1 rcpt=1 data=1 quit=1 commands=8
Jul 08 16:46:42 mail.williwonka.eu postfix/10025/smtpd[9775]: connect from mail.williwonka.eu[127.0.0.1]
Jul 08 16:46:42 mail.williwonka.eu postfix/10025/smtpd[9775]: 4Lfd1Z57tKz1dK: client=mail.williwonka.eu[127.0.0.1]
Jul 08 16:46:42 mail.williwonka.eu postfix/cleanup[9771]: 4Lfd1Z57tKz1dK: message-id=<20220708154642.43197243B@williwonka.eu>
Jul 08 16:46:42 mail.williwonka.eu postfix/10025/smtpd[9775]: disconnect from mail.williwonka.eu[127.0.0.1] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5
Jul 08 16:46:42 mail.williwonka.eu postfix/qmgr[1626]: 4Lfd1Z57tKz1dK: from=<williwonka@williwonka.eu>, size=2247, nrcpt=1 (queue active)
Jul 08 16:46:42 mail.williwonka.eu amavis[2034]: (02034-20) Passed CLEAN {RelayedInternal}, ORIGINATING LOCAL [51.171.4.95]:49106 [51.171.4.95] ESMTP/ESMTP <williwonka@williwonka.eu> -> <williwonka@williwonka.eu>, (ESMTPSA://[51.171.4.95]:49106), Queue-ID: 4Lfd1Z3HRKz1dJ, Message-ID: <20220708154642.43197243B@williwonka.eu>, mail_id: TrTAnwdtc5W4, b: i-JpaJPjB, Hits: -1.01, size: 990, queued_as: 4Lfd1Z57tKz1dK, Subject: "Cron <root@williwonka> /root/.bin/Fix_WWW_Permissions.sh", From: <williwonka.eu@williwonka.eu>, helo=williwonka.eu, Tests: [ALL_TRUSTED=-1,T_SCC_BODY_TEXT_LINE=-0.01], autolearn=ham autolearn_force=no, autolearnscore=-0.01, dkim_new=dkim:williwonka.eu, 253 ms
Jul 08 16:46:42 mail.williwonka.eu postfix/amavis/smtp[9773]: 4Lfd1Z3HRKz1dJ: to=<williwonka@williwonka.eu>, orig_to=<root@williwonka.eu>, relay=127.0.0.1[127.0.0.1]:10026, delay=0.3, delays=0.03/0.01/0/0.26, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 4Lfd1Z57tKz1dK)
Jul 08 16:46:42 mail.williwonka.eu postfix/qmgr[1626]: 4Lfd1Z3HRKz1dJ: removed
Jul 08 16:46:42 mail.williwonka.eu dovecot[9777]: lda(williwonka@williwonka.eu)<9777><TaIJLWJRyGIxJgAAFXfAmQ>: sieve: from=williwonka.eu@williwonka.eu, envelope_sender=williwonka@williwonka.eu, subject=Cron <root@williwonka> /root/.bin/Fix_WWW_Permissions.sh, msgid=<20220708154642.43197243B@williwonka.eu>, size=2275, delivery_time=19ms, stored mail into mailbox 'INBOX'
Jul 08 16:46:42 mail.williwonka.eu postfix/pipe[9776]: 4Lfd1Z57tKz1dK: to=<williwonka@williwonka.eu>, relay=dovecot, delay=0.05, delays=0.01/0.01/0/0.04, dsn=2.0.0, status=sent (delivered via dovecot service)
Jul 08 16:46:42 mail.williwonka.eu postfix/qmgr[1626]: 4Lfd1Z57tKz1dK: removed
Jul 08 16:46:42 mail.williwonka.eu systemd[1]: amavis.service: Succeeded.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: Link removed.
░░
░░ The unit amavis.service has successfully entered the 'dead' state.
Jul 08 16:46:42 mail.williwonka.eu systemd[1]: amavis.service: Consumed 4.566s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: Link removed.
░░
░░ The unit amavis.service completed and consumed the indicated resources.

I have 6 gigs of ram attached to the VM and it wasn't using even 1/3 of it when amavis crashed.

Kindest regards.

AndrzejL

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

Hello.

Freshly installed (maybe 2 weeks ago) iredmail 1.6.0. Installed using the downloadable .sh script.

Everything seems to be fine. I seem to receive / send e-mails as expected. However on every boot I see this:

root@mail:~# journalctl -b -l -x --no-pager -p 3
-- Journal begins at Fri 2022-07-08 11:16:02 IST, ends at Fri 2022-07-08 19:06:11 IST. --
Jul 08 19:05:50 mail.williwonka.eu dovecot[677]: stats: Error: conn stats-reader (127.0.0.1:53616): didn't reply with a valid VERSION line: EXPORT        global
Jul 08 19:05:50 mail.williwonka.eu dovecot[677]: stats: Error: conn stats-reader (127.0.0.1:53618): didn't reply with a valid VERSION line: EXPORT        global
root@mail:~#

I did see this post... 1.0-beta1 Report: dovecot stats-reader - Sorry I cannot link it. I am not allowed to add links.

When I tried the solution from that post:

/etc/dovecot/dovecot.conf

service stats {
#    fifo_listener stats-mail {
#    user = vmail
#    mode = 0644
#  }

    unix_listener stats-writer {
        user = vmail
        group = vmail
        mode = 0660
    }

    inet_listener {
        address = 127.0.0.1
        port = 24242
    }
}

I get the same thing (port number changes) during the next boot. I tried also hashing out the stats-writer bit but also no effect.

Can you please try and help?

Ask for any additional info like command outputs or logs and you shall receive it.

Kindest regards.

AndrzejL