<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title><![CDATA[iRedMail — iRedMail Support]]></title>
		<link>https://forum.iredmail.org/</link>
		<atom:link href="https://forum.iredmail.org/feed-rss-forum2.xml" rel="self" type="application/rss+xml" />
		<description><![CDATA[The most recent topics at iRedMail.]]></description>
		<lastBuildDate>Fri, 07 Aug 2026 08:18:00 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Migrating from Dovecot deliver (LDA) to Dovecot LMTP]]></title>
			<link>https://forum.iredmail.org/topic21194-migrating-from-dovecot-deliver-lda-to-dovecot-lmtp-new-posts.html</link>
			<description><![CDATA[<p>==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====<br />- iRedMail version (check /etc/iredmail-release): 1.8.4 (newest one)<br />- Deployed with iRedMail Easy or the downloadable installer? installer<br />- Linux/BSD distribution name and version: Debian 13<br />- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MariaDB<br />- Web server (Apache or Nginx): Ngiinx<br />- Manage mail accounts with iRedAdmin-Pro? No<br />- [IMPORTANT] Related original log or error message is required if you&#039;re experiencing an issue.<br />====</p><p>Hey there,</p><p>after Upgrading to Trixie I have issues with the personal sieve filters (all mails appear in the inbox than in the designated folders). Due to the issues I checked my whole configs and saw that I still use LDA instead of the modern LMPT approach.</p><p>My iRedMail-installation is now 6 years old and I am really satisfied with it (Thank at the great team). I made all updates as described in the tutorials/relase notes.</p><p>have I missed something in case of LMTP. Is there any guide to migrate to LMTP?</p><p>Greets mike</p>]]></description>
			<author><![CDATA[null@example.com (mike175de)]]></author>
			<pubDate>Fri, 07 Aug 2026 08:18:00 +0000</pubDate>
			<guid>https://forum.iredmail.org/topic21194-migrating-from-dovecot-deliver-lda-to-dovecot-lmtp-new-posts.html</guid>
		</item>
		<item>
			<title><![CDATA[Testing 1.8.4 on FreeBSD 15.1, Python 3.12, PostGreSQL 18]]></title>
			<link>https://forum.iredmail.org/topic21192-testing-184-on-freebsd-151-python-312-postgresql-18-new-posts.html</link>
			<description><![CDATA[<p>==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====<br />- iRedMail version (check /etc/iredmail-release): 1.8.4 PGSQL<br />- Deployed with iRedMail Easy or the downloadable installer? Installer (Github code)<br />- Linux/BSD distribution name and version: FreeBSD 15.1<br />- Store mail accounts in which backend (LDAP/MySQL/PGSQL): PGSQL<br />- Web server (Apache or Nginx): Nginx<br />- Manage mail accounts with iRedAdmin-Pro? No<br />- [IMPORTANT] Related original log or error message is required if you&#039;re experiencing an issue.<br />====</p><p>Hi Zhang,</p><p>This is <strong>not</strong> a support ticket. I&#039;m sharing some testing notes after validating <strong>iRedMail 1.8.4</strong> on <strong>FreeBSD 15.1-RELEASE</strong>, which was released recently.</p><p>I&#039;ve been running iRedMail on FreeBSD since 2019, on a personal mail server, and perform periodic rebuild and migration exercises to keep my documentation current and validate the upgrade path.<br />The actual server is running quite old versions.<br />This test was performed entirely in a disposable VM environment using a fresh install of FreeBSD 15.1 and iRedMail 1.8.4.</p><p>Overall, the installation was successful, but I encountered a few issues related mainly to platform version drift since FreeBSD 15.1 has newer package baselines than the currently supported FreeBSD release. The fixes were straightforward and may be worth considering for inclusion before declaring FreeBSD 15.1 officially supported.</p><h5>Python Package Flavour</h5><p>The installer currently uses Python <strong>3.11</strong> package names while FreeBSD 15.1 repositories now provide Python <strong>3.12</strong> packages by default.</p><div class="codebox"><pre><code># ./functions/packages_freebsd.sh

# replace
export PY3_VER=&#039;3.11&#039;
export PY_FLAVOR=&#039;py311&#039;
# with
export PY3_VER=&#039;3.12&#039;
export PY_FLAVOR=&#039;py312&#039;</code></pre></div><p>Without this change the installer attempts to install packages which no longer exist in the repository, for example:<br /></p><div class="codebox"><pre><code>py311-sqlalchemy14
py311-passlib
py311-psycopg2
py311-requests
...</code></pre></div><p>After changing the flavour to py312, package installation proceeds normally.</p><h5>PostgreSQL Baseline</h5><p>The installer currently uses PostgreSQL 17. FreeBSD 15.1 repositories now provide PostgreSQL 18 as the default baseline.</p><div class="codebox"><pre><code># ./conf/postgresql

# replace
export PGSQL_VERSION=&#039;17&#039;
# with
export PGSQL_VERSION=&#039;18&#039;</code></pre></div><p>This avoids package version conflicts later in the installation process.</p><h5>Random Password Generation</h5><p>I (we) ran into an issue previously encountered on FreeBSD several years ago.<br />Check <a href="https://forum.iredmail.org/topic21040-not-a-support-ticket-sharing-tests-ideas-and-comments.html">Topic 21040 from 2025-Nov, under: Random Password Generator</a>. We came across that also back in 2020. So it is still linguering and bites me every time.</p><p>During installation PostgreSQL would eventually report:<br /></p><div class="codebox"><pre><code>FATAL: canceling authentication due to timeout</code></pre></div><p>The root cause is the random password generation method used on FreeBSD.</p><div class="codebox"><pre><code># ./conf/global

# replace
export RANDOM_STRING=&#039;eval &lt;/dev/urandom LC_CTYPE=C tr -dc a-zA-Z0-9 | head -c 32&#039;
# with
export RANDOM_STRING=&#039;openssl rand -base64 24&#039;</code></pre></div><p>This method has worked reliably in my testing and avoids the FreeBSD-specific issues that can occur with the existing command.</p><p>The generated passwords were correctly written to:<br /></p><div class="codebox"><pre><code>./config</code></pre></div><p>and PostgreSQL setup completed successfully afterwards.</p><h5>SpamAssassin Dependency (re2c)</h5><p>The installer completed package installation but later failed when compiling SpamAssassin rules.</p><div class="codebox"><pre><code>Error:
Can&#039;t exec &quot;re2c&quot;: No such file or directory</code></pre></div><p>This occurred during:</p><p>Compiling SpamAssassin rulesets (sa-compile)</p><p>Suggested update in:</p><div class="codebox"><pre><code># ./functions/packages_freebsd.sh

# replace
ALL_PKGS=&quot;${ALL_PKGS} spamassassin&quot;
# with
ALL_PKGS=&quot;${ALL_PKGS} re2c spamassassin&quot;</code></pre></div><p>After installing re2c, the SpamAssassin compilation step completed successfully.</p><h5>Optional Changes</h5><p>These are not required for successful installation but may be useful depending on deployment preferences. I <strong>do</strong> make these changes manually post-installation.</p><p><strong>PostgreSQL Login Class</strong><br /></p><div class="codebox"><pre><code># /etc/rc.conf.local

# add
postgresql_login_class=&quot;postgres&quot;</code></pre></div><p><strong>PHP-FPM Logging</strong><br /></p><div class="codebox"><pre><code># /usr/local/etc/php-fpm.conf

# Default: notice; reduce noise
log_level = warning</code></pre></div><p><strong>SOGo Not Installed</strong><br />If SOGo is not selected, remove it from the backup list:<br /></p><div class="codebox"><pre><code># /var/vmail/backup/backup_pgsql.sh

# if sogo not installed
# replace
export DATABASES=&#039;vmail roundcubemail amavisd iredadmin sogo iredapd&#039;
# with
export DATABASES=&#039;vmail roundcubemail amavisd iredadmin iredapd&#039;</code></pre></div><p><strong>PostFix server/domain</strong><br /></p><div class="codebox"><pre><code># /usr/local/etc/postfix/main.cf

# hostname
# server level
myhostname = server.domain.local
# domain level
myorigin = domain.local
# domain level (reuse, avoids issues)
mydomain = $myorigin</code></pre></div><h5>Summary</h5><p>After applying the following changes:</p><ul><li><p>Python flavor: py311 -&gt; py312</p></li><li><p>PostgreSQL: 17 -&gt; 18</p></li><li><p>Random password generation -&gt; openssl rand</p></li><li><p>Add re2c dependency</p></li></ul><br /><p>iRedMail 1.8.4 installed successfully on a fresh FreeBSD 15.1 VM.</p><p>Hopefully these notes help accelerate validation of FreeBSD 15.1 support and potentially reduce the work required for an upcoming release.</p><p>As always, thank you for continuing to support FreeBSD as a deployment platform for iRedMail.</p><p>Regards</p>]]></description>
			<author><![CDATA[null@example.com (angeloklin)]]></author>
			<pubDate>Mon, 03 Aug 2026 14:57:48 +0000</pubDate>
			<guid>https://forum.iredmail.org/topic21192-testing-184-on-freebsd-151-python-312-postgresql-18-new-posts.html</guid>
		</item>
		<item>
			<title><![CDATA[After Debian 12 to 13 Upgrade: unknown extension 'imapsieve']]></title>
			<link>https://forum.iredmail.org/topic21191-after-debian-12-to-13-upgrade-unknown-extension-imapsieve-new-posts.html</link>
			<description><![CDATA[<p>==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====<br />- iRedMail version (check /etc/iredmail-release): 1.8.4<br />- Deployed with iRedMail Easy or the downloadable installer? Downloadable installer<br />- Linux/BSD distribution name and version: Debian 13<br />- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL<br />- Web server (Apache or Nginx): Apache<br />- Manage mail accounts with iRedAdmin-Pro?no<br />- [IMPORTANT] Related original log or error message is required if you&#039;re experiencing an issue.<br />====</p><p>Did the Upgrade to Debian Trixie today an now the (personal?) sieve filters wont work. Did the Fix tutorial for Trixie but still get there error messages, when an e-mail comes in. Aparrently startet with iRedMail 0.9.4 way back and did all the Upgrade tutorials bit by bit</p><div class="codebox"><pre><code>: Error: sieve: binary /media/data/vmail/sieve/report_ham.svbin: open: binary requires unknown extension &#039;imapsieve&#039;
: Error: sieve: report_ham: line 1: require command: unknown Sieve capability &#039;imapsieve&#039;
: Error: sieve: report_ham: validation failed
: Error: sieve: Failed to compile script &#039;before/report_ham&#039;</code></pre></div><p>sanitized dovecot.conf:<br /></p><div class="codebox"><pre><code>dovecot_config_version = 2.4.0
dovecot_storage_version = 2.4.0

#
# Default limits
#
default_client_limit = 4096
default_process_limit = 500

# Limit the process&#039;s address space. When the space is reached, some memory
# allocations may start failing with &quot;Out of memory&quot;, or the kernel may kill
# the process with signal 9. This setting is mainly intended to prevent memory
# leaks from eating up all of the memory, but there can be also legitimate
# reasons why the process reaches this limit. For example a huge mailbox may
# not be accessed if this limit is too low.
# The default value (18446744073709551615 = 2^64-1) sets the limit to
# `default_vsz_limit`, while 0 disables the limit entirely.
default_vsz_limit = unlimited

# Listen addresses.
#   - &#039;*&#039; means all available IPv4 addresses.
#   - &#039;[::]&#039; means all available IPv6 addresses.
# Listen on all available addresses by default
listen = * [::]
   
# Enabled mail protocols.
protocols = pop3 imap sieve lmtp
   
# Plugins
mail_plugins {
    acl = yes
    mail_log = yes
    notify = yes
    quota = yes
    quota_clone = yes
}  
   
# Required by OpenBSD
base_dir = /run/dovecot
   
# User/group who owns the message files:
mail_uid = 2000
mail_gid = 2000
   
# Assign uid to virtual users.
first_valid_uid = 2000
last_valid_uid = 2000
   
# Debug
# Enables logging all failed authentication attempts.
#auth_verbose = yes
   
# Enables all authentication debug logging. Passwords are logged as `&lt;hidden&gt;`.
#log_debug = category=auth
   
# Removes password hiding.
#auth_debug_passwords = yes
   
# If authentication fails, this setting logs the used password.
# If you don&#039;t really need to know what the password itself was, but are more
# interested in knowing if the user is simply trying to use the wrong password
# every single time or if it&#039;s a brute force attack, you can set this to sha1
# and only the SHA1 of the password is logged. That&#039;s enough to know if the
# password is same or different between login attempts.
#auth_verbose_passwords = no
#auth_verbose_passwords = plain
#auth_verbose_passwords = sha1
   
# Enables all kinds of mail related debug logging, such as showing where
# Dovecot is looking for mails.
#log_debug = category=mail

# Enables logging SSL errors and warnings.
# Even without this setting if connection is closed because of an SSL error,
# the error is logged as the disconnection reason.
#verbose_ssl = category=ssl
   
#log_debug = category=fts
#log_debug = category=ldap
   
# logging
log_path = syslog
syslog_facility = local5
   
# Login log elements.
# Add &#039;%k&#039; for detailed SSL protocol and cipher information.
# e.g. &quot;TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)&quot;
#login_log_format_elements = user=&lt;%{user}&gt; method=%m rip=%r lip=%l %c %k
   
# Mail delivery log format
#deliver_log_format = from=%{from}, envelope_sender=%{from_envelope}, subject=%{subject}, msgid=%m, size=%{size}, delivery_time=%{delivery_time}ms, %$
   
# Authentication mechanisms.
auth_mechanisms = PLAIN LOGIN
   
# Authentication related settings.
# Append this domain name if client gives empty realm.
#auth_default_domain =
   
auth_allow_cleartext = no
   
# IP addresses/ranges specified by login_trusted_networks setting are assumed
# to be secure.
login_trusted_networks =
   
# Mailbox format and path.
mail_driver = %{userdb:mail_driver | default(&quot;maildir&quot;) | lower}
mail_path = %{userdb:mail_path | default(&quot;~/Maildir&quot;)}
   
# The maximum number of IMAP connections allowed for a user from each IP address.
# Maximum number of IMAP connections allowed for a user from each IP address.
# NOTE: The username is compared case-sensitively.
# Default is 10.
mail_max_userip_connections = 30
   
   
# SSL: Global settings.
# Refer to wiki site for per protocol, ip, server name SSL settings:
ssl = required
   
ssl_min_protocol = TLSv1.2
# log_debug = category=ssl
   
ssl_server_cert_file = /
ssl_server_key_file = /
ssl_server_dh_file = /etc/ssl/dhparam2048.pem
ssl_server_prefer_ciphers = server
ssl_cipher_list = EECDH+CHACHA20:EECDH+AESGCM:EDH+AESGCM:AES256+EECDH
   
# Master user.
# Master users are able to log in as other users. It&#039;s also possible to
# directly log in as any user using a master password, although this isn&#039;t
# recommended.
auth_master_user_separator = *
   
passdb passwd-file {
    master = yes
    passwd_file_path = /etc/dovecot/dovecot-master-users
    result_success = continue
}  

# `mailbox_list_index = yes` can help a lot by replying to IMAP STATUS (and
# similar) lookups from a single index without having to open each mailbox
# index separately.
# This is the default in v2.3+.
mailbox_list_index = yes
   
# Assume that the list index is up-to-date.
mailbox_list_index_very_dirty_syncs = yes
   
# Maximum IMAP command line length. Some clients generate very long command
# lines with huge mailboxes, so you may need to raise this if you get
# &quot;Too long argument&quot; or &quot;IMAP command line too large&quot; errors often.
# Defaults to 64k.
imap_max_line_length = 2m
   
sql_driver = mysql
   
mysql 127.0.0.1 {
    port = 3306
    dbname = vmail
    user = vmailadmin
    password = 
}  
   
   
dict_server {
    dict quota_clone {
        driver = sql
   
        dict_map priv/quota/messages {
            sql_table = used_quota
            username_field = username
            value_field messages {
            }
        }
   
        dict_map priv/quota/storage {
            sql_table = used_quota
            username_field = username
            value_field bytes {
            }
        }
    }
   
    dict acl {
        driver = sql
   
        dict_map shared/shared-boxes/user/$to/$from {
            sql_table = share_folder
            value_field dummy {
            }
   
            key_field from_user {
                value = $from
            }
            key_field to_user {
                value = $to
            }
        }
   
        dict_map shared/shared-boxes/anyone/$from {
            sql_table = anyone_shares
            value_field dummy {
            }
   
            key_field from_user {
                value = $from
            }
        }
    }
   
    dict lastlogin {
        driver = sql
   
        dict_map shared/last-login/imap/$user/$domain {
            sql_table = last_login
            value_field imap {
                type = uint
            }
   
            key_field username {
                value = $user
            }
   
            key_field domain {
                value = $domain
            }
        }
   
        dict_map shared/last-login/pop3/$user/$domain {
            sql_table = last_login
            value_field pop3 {
                type = uint
            }
   
            key_field username {
                value = $user
            }
   
            key_field domain {
                value = $domain
            }
        }
   
        dict_map shared/last-login/lda/$user/$domain {
            sql_table = last_login
            value_field lda {
                type = uint
            }
   
            key_field username {
                value = $user
            }
   
            key_field domain {
                value = $domain
            }
        }
   
        # Treat lmtp as lda
        dict_map shared/last-login/lmtp/$user/$domain {
            sql_table = last_login
            value_field lda {
                type = uint
            }
   
            key_field username {
                value = $user
            }
   
            key_field domain {
                value = $domain
            }
        }
    }
}  
   
#  
# Virtual mail accounts.
#  
   
userdb sql {
    iterate_query = SELECT username AS user FROM mailbox
   
    # Use COALESCE(NULLIF(...)) to prevent empty value.
    query = SELECT \
            LOWER(&#039;%{user | lower}&#039;) AS master_user, \
            LOWER(CONCAT(mailbox.storagebasedirectory, &#039;/&#039;, mailbox.storagenode, &#039;/&#039;, mailbox.maildir)) AS home, \
            COALESCE(NULLIF(mailbox.mailboxformat, &#039;&#039;), &#039;maildir&#039;) AS mail_driver, \
            CONCAT(&quot;~/&quot;, COALESCE(NULLIF(mailbox.mailboxfolder, &#039;&#039;), &#039;Maildir&#039;)) AS mail_path, \
            mailbox.quota * 1048576 AS quota_storage_size \
        FROM mailbox,domain \
       WHERE mailbox.username=&#039;%{user | lower}&#039; \
             AND mailbox.domain=&#039;%{user | domain | lower}&#039; \
             AND mailbox.`enable%{protocol | lower}%{secured | lower}`=1 \
             AND mailbox.domain=domain.domain \
             AND domain.backupmx=0 \
             AND domain.active=1 \
             AND mailbox.active=1
}  
   
passdb sql {
    query = SELECT mailbox.password, mailbox.allow_nets \
        FROM mailbox,domain \
       WHERE mailbox.username=&#039;%{user | lower}&#039; \
             AND mailbox.`enable%{protocol | lower}%{secured | lower}`=1 \
             AND mailbox.active=1 \
             AND mailbox.domain=domain.domain \
             AND domain.active=1
}  
   
#  
# Namespaces
#  
namespace inbox {
    type = private
    separator = /
    prefix =
    inbox = yes
   
    # Sent
    mailbox Sent {
        auto = subscribe
        special_use = \Sent
    }
    mailbox &quot;Sent Messages&quot; {
        auto = no
        special_use = \Sent
    }
    mailbox &quot;Sent Items&quot; {
        auto = no
        special_use = \Sent
    }
   
    mailbox Drafts {
        auto = subscribe
        special_use = \Drafts
    }
   
    # Trash
    mailbox Trash {
        auto = subscribe
        special_use = \Trash
    }
   
    mailbox &quot;Deleted Messages&quot; {
        auto = no
        special_use = \Trash
    }
   
    # Junk
    mailbox Junk {
        auto = subscribe
        special_use = \Junk
        fts_autoindex = no
    }

    mailbox Spam {
        auto = no
        special_use = \Junk
        fts_autoindex = no
    }

    mailbox &quot;Junk E-mail&quot; {
        auto = no
        special_use = \Junk
        fts_autoindex = no
    }
}

namespace shared {
    type = shared
    separator = /
    prefix = Shared/$user/
    mail_driver = maildir
    mail_path = %{owner_home}/Maildir
    mail_index_private_path = ~/Maildir/shared/%{owner_user}
    # not share the index files between users
    mail_index_path = ~/Maildir/shared/%{owner_user}

    # this namespace should handle its own subscriptions or not.
    subscriptions = no
    list = children
}

# Public mailboxes.
#namespace {
#    type = public
#    separator = /
#    prefix = Public/
#    mail_driver = maildir
#    mail_path = /var/vmail/public
#    subscriptions = no
#
#    # Per-user \Seen Flag
#    mail_index_private_path = ~/Maildir/public
#}

#
# Protocols
#
# Store METADATA information within user&#039;s Maildir directory
mail_attribute {
    dict file {
        path = ~/dovecot-attributes
    }
}

# Avoid spending excessive time waiting for the quota calculation to finish
# when mails&#039; vsizes aren&#039;t already cached. If this many mails are opened,
# finish the quota calculation on background in indexer-worker process. Mail
# deliveries will be assumed to succeed, and explicit quota lookups will
# return internal error.
protocol !indexer-worker {
    mail_vsize_bg_after_count = 100
}

protocol imap {
    mail_plugins {
        imap_quota = yes
        imap_acl = yes

        # This will only enable support for administrator scripts.
        imap_sieve = yes
        last_login = yes
    }

    imap_client_workarounds = tb-extra-mailbox-sep
    imap_metadata = yes
}  

protocol pop3 {
    mail_plugins {
        last_login = yes
    }

    pop3_client_workarounds = outlook-no-nuls oe-ns-eoh
    pop3_uidl_format = %{uid | hex(8)}%{uidvalidity | hex(8)}

    # POP3 logout format string:
    #  %i - total number of bytes read from client
    #  %o - total number of bytes sent to client
    #  %t - number of TOP commands
    #  %p - number of bytes sent to client as a result of TOP command
    #  %r - number of RETR commands
    #  %b - number of bytes sent to client as a result of RETR command
    #  %d - number of deleted messages
    #  %m - number of messages (before deletion)
    #  %s - mailbox size in bytes (before deletion)
    # Default format doesn&#039;t have &#039;in=%i, out=%o&#039;.
    #pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s, in=%i, out=%o
}

protocol lda {
    mail_plugins {
        sieve = yes
        last_login = yes
    }

    lda_mailbox_autocreate = yes
    lda_mailbox_autosubscribe = yes
}

protocol lmtp {
    mail_plugins {
        sieve = yes
        last_login = yes
    }

    # Address extension delivery
    lmtp_save_to_detail_mailbox = yes
    recipient_delimiter = +
}

#
# Services
#
# FYI: 
# Dovecot anvil process tracks authentication penalties for different IPs to
# slow down brute force login attempts.
service anvil {
    # there can be only one master process.
    #process_limit = 1

    unix_listener anvil-auth-penalty {
        user = vmail
        group = vmail
        # Set mode to 0 to completely disable penalty.
        mode = 0660
    }
}

service auth {
    # should be large enough to handle all the simultaneous connections.
    # Typically only login processes use long lasting auth connections, while
    # other processes do only quick lookups and disconnect afterwards.
    #client_limit = 4096

    # there can be only one auth master process
    #process_limit = 1

    # Auth socket
    unix_listener /var/spool/postfix/private/dovecot-auth {
        user = vmail
        group = vmail
        mode = 0666
    }

    unix_listener auth-master {
        user = vmail
        group = vmail
        mode = 0666
    }

    unix_listener auth-userdb {
        user = vmail
        group = vmail
        mode = 0660
    }
}

service dict {
    unix_listener dict {
        mode = 0660
        user = vmail
        group = vmail
    }
}

# Login processes. Refer to Dovecot wiki for more details:
service imap-login {
    # Maximum number of simultaneous client connections per process. Once this
    # number of connections is received, the next incoming connection will
    # prompt Dovecot to spawn another process.
    # If set to 0, default_client_limit is used instead.
    #client_limit = 0

    # vsz_limit should be fine at its default 64MB value
    #vsz_limit = 64M
    inet_listener imap {
        name = imap
        port = 143
    }

    inet_listener imaps {
        name = imaps
        port = 993
        ssl = yes
    }
}

service imap {
    #process_limit = 4096

    # required by imap-hibernate
    unix_listener imap-master {
        user = vmail
        group = vmail
        mode = 0666
    }
}

service pop3 {
    #process_limit = 4096
}

# LMTP server (Local Mail Transfer Protocol).
# Reference: 
service lmtp {
    user = vmail

    # For higher volume sites, it may be desirable to increase the number of
    # active listener processes. A range of 5 to 20 is probably good for most
    # sites.
    process_min_avail = 5

    # Logging.
    # Require &#039;log_path =&#039; in &#039;protocol lmtp {}&#039; block.
    executable = lmtp -L

    # Listening on socket file and TCP
    unix_listener /var/spool/postfix/private/dovecot-lmtp {
        user = vmail
        group = vmail
        mode = 0666
    }

    inet_listener lmtp {
        listen = 127.0.0.1
        port = 24
    }
}

service managesieve-login {
    inet_listener sieve {
        listen = 127.0.0.1
        port = 4190
    }
}

service pop3-login {
    #client_limit = 0
    #process_limit = 0
    #process_min_avail =

    inet_listener pop3 {
        name = pop3
        port = 110
    }

    inet_listener pop3s {
        name = pop3s
        port = 995
        ssl = yes
    }
}

service quota-warning {
    executable = script /usr/local/bin/dovecot-quota-warning.sh
    user = vmail

    unix_listener quota-warning {
        user = vmail
        group = vmail
        mode = 0660
    }
}

quota_status_success = DUNNO
quota_status_nouser = DUNNO
quota_status_overquota = &quot;552 5.2.2 Mailbox is full&quot;
service quota-status {
    executable = quota-status -p postfix
    inet_listener quota-status {
        listen = 127.0.0.1
        port = 12340
    }
    client_limit = 1
}

# quota plugin: count
# `count` driver doesn&#039;t have any additional parameters.
quota &quot;User quota&quot; {
}
# Allows message deliveries to exceed quota once by this amount.
# After the quota is already over the limit, the grace no longer applies.
quota_storage_grace = 30M

# Quota warning.
# Configure the highest limits first.
quota user {
  warning warn-95 {
    quota_storage_percentage = 95
    execute quota-warning {
      args = 95 %{user}
    }
  }
  warning warn-90 {
    quota_storage_percentage = 90
    execute quota-warning {
      args = 90 %{user}
    }
  }
  warning warn-85 {
    quota_storage_percentage = 85
    execute quota-warning {
      args = 85 %{user}
    }
  }
  warning warn-under {
    quota_storage_percentage = 100
    # user is no longer over quota
    threshold = under
    execute quota-warning {
      args = below %{user}
    }
  }
}

# plugin: quota_clone.
quota_clone {
    dict proxy {
        name = quota_clone
    }
}

# The maximum number of redirect actions that can be performed during a single
# script execution.
sieve_max_redirects = 30

# Use recipient as vacation message sender instead of null sender (&lt;&gt;).
sieve_vacation_send_from_recipient = yes

# Specifies what envelope sender address is used for redirected messages.
# Requires pigeonhole v0.4.4+.
#
# Normally, the Sieve &quot;redirect&quot; command copies the sender address for the
# redirected message from the processed message. So, the redirected message
# appears to originate from the original sender.
sieve_redirect_envelope_from = recipient

sieve_duplicate_default_period = 1h
sieve_duplicate_max_period = 1d

sieve_script global {
    type = global
    driver = file
    path = /media/data/vmail/sieve
}

sieve_script before {
    type = before
    driver = file
    path = /media/data/vmail/sieve
    active_path = /media/data/vmail/sieve/dovecot.sieve
}

sieve_script personal {
    type = personal
    driver = file
    path = ~/sieve
    active_path = ~/sieve/dovecot.sieve
}

sieve_plugins {
  sieve_extprograms = yes
}

sieve_extensions {
   vnd.dovecot.pipe = yes
    editheader = yes
}

# plugin: mail_log
# 
mail_log_events = delete undelete expunge copy save mailbox_create mailbox_delete mailbox_rename
mail_log_fields = uid box msgid size from subject flags
#mail_log_cached_only = yes

# plugin: acl
# 
# ACL and share folder
acl_driver = vfile
acl_globals_only = no

acl_sharing_map {
    dict proxy {
        name = acl
    }
}

# By default Dovecot doesn&#039;t allow using the IMAP &quot;anyone&quot; or
# &quot;authenticated&quot; identifier, because it would be an easy way to spam
# other users in the system. If you wish to allow it,
#imap_acl_allow_anyone = no

# plugin: last-login.
# 
last_login {
    dict proxy {
        name = lastlogin
    }
    key = last-login/%{service}/%{user}/%{user | domain}
}</code></pre></div>]]></description>
			<author><![CDATA[null@example.com (ccgx)]]></author>
			<pubDate>Sun, 02 Aug 2026 14:28:09 +0000</pubDate>
			<guid>https://forum.iredmail.org/topic21191-after-debian-12-to-13-upgrade-unknown-extension-imapsieve-new-posts.html</guid>
		</item>
		<item>
			<title><![CDATA[MySQL error after Debian 12 to 13 upgrade]]></title>
			<link>https://forum.iredmail.org/topic21189-mysql-error-after-debian-12-to-13-upgrade-new-posts.html</link>
			<description><![CDATA[<p>==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====<br />- iRedMail version (check /etc/iredmail-release): 1.8.4<br />- Deployed with iRedMail Easy or the downloadable installer? downloadable installer<br />- Linux/BSD distribution name and version: Debian 13.6<br />- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL <br />- Web server (Apache or Nginx): nginx<br />- Manage mail accounts with iRedAdmin-Pro? no<br />- [IMPORTANT] Related original log or error message is required if you&#039;re experiencing an issue.<br />====</p><p>My server was originally on Debian 12 and iRedMail version 1.6.8. I upgraded to Debian 13 today (I had already upgraded to iRedMail 1.8.4 prior). Everything went really smoothly and I followed the guide to fix what needed to be fixed and all went without incident.</p><p>The only issue I have, which might not even be an issue and I only noticed it from journald, is with MySQL. (MariaDB version 11.8.6):</p><div class="codebox"><pre><code>Jul 28 19:05:02 *DOMAIN* debian-start[1459]: Could not open required defaults file: /etc/mysql/debian.cnf
Jul 28 19:05:02 *DOMAIN* debian-start[1459]: Fatal error in defaults handling. Program aborted</code></pre></div><p>To be clear, MariaDB is active and running and ready for connections/is functional. I see the same error on another mail server I deployed about two months ago and upgraded from Debian 12 to 13 as well today (it was originally on iRedMail 1.8.2).</p>]]></description>
			<author><![CDATA[null@example.com (dice)]]></author>
			<pubDate>Tue, 28 Jul 2026 23:44:17 +0000</pubDate>
			<guid>https://forum.iredmail.org/topic21189-mysql-error-after-debian-12-to-13-upgrade-new-posts.html</guid>
		</item>
		<item>
			<title><![CDATA[sieve path issue with dovecot 2.4 on debian 13]]></title>
			<link>https://forum.iredmail.org/topic21186-sieve-path-issue-with-dovecot-24-on-debian-13-new-posts.html</link>
			<description><![CDATA[<p>==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====<br />- iRedMail version (check /etc/iredmail-release):&nbsp; 1.8.3<br />- Deployed with iRedMail Easy or the downloadable installer? installer<br />- Linux/BSD distribution name and version: Debian 13<br />- Store mail accounts in which backend (LDAP/MySQL/PGSQL): mariadb<br />- Web server (Apache or Nginx): nginx<br />- Manage mail accounts with iRedAdmin-Pro? yes<br />- [IMPORTANT] Related original log or error message is required if you&#039;re experiencing an issue.<br />====</p><p>A fresh install on debian 13, then restore config and data</p><p>This is the error we get :<br /></p><div class="codebox"><pre><code>dovecot: sieve(name@domaine.tld)&lt;16329&gt;&lt;mBy5ACZXnsB/AAAB&gt;: Error: sieve: file storage: Sieve storage path &#039;/var/vmail/vmail1/domaine.tld/n/a/m/name-
2021.04.15.10.29.46//sieve/dovecot.sieve&#039; is not a directory, but it is to be opened for write access </code></pre></div><p>To solve this problem we had to change dovecot.conf from this :<br /></p><div class="codebox"><pre><code>sieve_script personal {
    type = personal
    driver = file
    path = ~/sieve/dovecot.sieve
}</code></pre></div><p>to this :<br /></p><div class="codebox"><pre><code>sieve_script personal {
    type = personal
    driver = file
    path = ~/sieve
    active_path = ~/sieve/dovecot.sieve
}</code></pre></div><p>It&#039;s the second server on debian 13 that has this issue.</p><p>Is this normal ? did I find a bug ?</p>]]></description>
			<author><![CDATA[null@example.com (b.cherrier)]]></author>
			<pubDate>Tue, 21 Jul 2026 22:48:36 +0000</pubDate>
			<guid>https://forum.iredmail.org/topic21186-sieve-path-issue-with-dovecot-24-on-debian-13-new-posts.html</guid>
		</item>
		<item>
			<title><![CDATA[Question about Spider archiver]]></title>
			<link>https://forum.iredmail.org/topic21182-question-about-spider-archiver-new-posts.html</link>
			<description><![CDATA[<p>==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====<br />- iRedMail version (check /etc/iredmail-release): <br />- Deployed with iRedMail Easy or the downloadable installer?<br />- Linux/BSD distribution name and version: <br />- Store mail accounts in which backend (LDAP/MySQL/PGSQL): <br />- Web server (Apache or Nginx):<br />- Manage mail accounts with iRedAdmin-Pro?<br />- [IMPORTANT] Related original log or error message is required if you&#039;re experiencing an issue.<br />====</p><p>Hey guys! I know I submitted a forum post yesterday about Spider, but I have a few more questions. My apologies for the double post.</p><p>1.) Does Spider need to be installed on a server running iRedMail or can it just be installed on any Unix server as a stand-alone? I&#039;m asking because I want to give it a try, but I want to install it on a test server that is not running iRedMail.</p><p>2.) What other remote storage platforms are supported besides S3? We use BackBlaze as our online storage provider. Can i use that with Spider? If yes, do you have instructions on how to set it up?</p><p>3.) I read a post back from 2023 that said you guys no longer offer free trials for Spider. Is that true? If not, will I need to purchase it for a minimum of 5 users just to try it out?</p><p>Thanks!</p>]]></description>
			<author><![CDATA[null@example.com (lindapagillo13)]]></author>
			<pubDate>Wed, 15 Jul 2026 16:20:24 +0000</pubDate>
			<guid>https://forum.iredmail.org/topic21182-question-about-spider-archiver-new-posts.html</guid>
		</item>
		<item>
			<title><![CDATA[Question about Spider archiver]]></title>
			<link>https://forum.iredmail.org/topic21180-question-about-spider-archiver-new-posts.html</link>
			<description><![CDATA[<p>Hi. Does the Spider archiver work with other mail server software besides iRedMail?</p>]]></description>
			<author><![CDATA[null@example.com (lindapagillo13)]]></author>
			<pubDate>Tue, 14 Jul 2026 19:04:39 +0000</pubDate>
			<guid>https://forum.iredmail.org/topic21180-question-about-spider-archiver-new-posts.html</guid>
		</item>
		<item>
			<title><![CDATA[Location of Incremental iRedMail and iRedAdmin Installers]]></title>
			<link>https://forum.iredmail.org/topic21176-location-of-incremental-iredmail-and-iredadmin-installers-new-posts.html</link>
			<description><![CDATA[<p>==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====<br />- iRedMail version (check /etc/iredmail-release): 0.9.7 MARIADB to 1.7.4 MARIADB.<br />- Deployed with iRedMail Easy or the downloadable installer? Downloadable for both.<br />- Linux/BSD distribution name and version: CentOS 7 to Ubuntu 24.04.<br />- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL for both.<br />- Web server (Apache or Nginx): Nginx for both.<br />- Manage mail accounts with iRedAdmin-Pro? Yes, for both.<br />- [IMPORTANT] Related original log or error message is required if you&#039;re experiencing an issue.<br />====</p><p>As I understand it, to migrate our old 0.9.7 iRedMail and old 2.8.0 iRedAdmin-Pro server to the new server, we have to update the old server&#039;s iRedAdmin to the build on the new server and do the same iRedAdmin-Pro on the old server, that is, update it to the version on the new server.&nbsp; Then we can migrate.</p><p>Where can I download these many incremental builds?</p>]]></description>
			<author><![CDATA[null@example.com (mbaker)]]></author>
			<pubDate>Wed, 08 Jul 2026 20:36:03 +0000</pubDate>
			<guid>https://forum.iredmail.org/topic21176-location-of-incremental-iredmail-and-iredadmin-installers-new-posts.html</guid>
		</item>
		<item>
			<title><![CDATA[v. 2 to v. 5 and Mailbox Migration]]></title>
			<link>https://forum.iredmail.org/topic21172-v-2-to-v-5-and-mailbox-migration-new-posts.html</link>
			<description><![CDATA[<p>==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====<br />- iRedMail version (check /etc/iredmail-release): 0.9.7 MARIADB to 1.7.4 MARIADB.<br />- Deployed with iRedMail Easy or the downloadable installer? Downloadable for both.<br />- Linux/BSD distribution name and version: CentOS 7 to Ubuntu 24.04<br />- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL for both.<br />- Web server (Apache or Nginx): Nginx for both.<br />- Manage mail accounts with iRedAdmin-Pro?<br />- [IMPORTANT] Related original log or error message is required if you&#039;re experiencing an issue.<br />====</p><p>We have an older server running an older iredmail, which want to migrate to a new server running a newer version of iredmail.&nbsp; I have two questions in that regard&gt;</p><p>1) Do you have any caveats or issues in migrating from those versions to the newer versions?</p><p>2) Is this still the best mailbox migration KB, given those versions, old and new?<br /><a href="https://docs.iredmail.org/migrate.to.new.iredmail.server.html#migrate-mailboxes-maildir-format">https://docs.iredmail.org/migrate.to.ne … dir-format</a></p>]]></description>
			<author><![CDATA[null@example.com (mbaker)]]></author>
			<pubDate>Mon, 06 Jul 2026 19:56:22 +0000</pubDate>
			<guid>https://forum.iredmail.org/topic21172-v-2-to-v-5-and-mailbox-migration-new-posts.html</guid>
		</item>
		<item>
			<title><![CDATA[Spamassasin learning when move to spam and out]]></title>
			<link>https://forum.iredmail.org/topic21170-spamassasin-learning-when-move-to-spam-and-out-new-posts.html</link>
			<description><![CDATA[<p>==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====<br />- iRedMail version (check /etc/iredmail-release): latest<br />- Deployed with iRedMail Easy or the downloadable installer? download<br />- Linux/BSD distribution name and version: Debian 13<br />- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL<br />- Web server (Apache or Nginx): Nginx<br />- Manage mail accounts with iRedAdmin-Pro? No<br />- [IMPORTANT] Related original log or error message is required if you&#039;re experiencing an issue.<br />====</p><p>&quot;This tutorial is NOT applicable for Dovecot 2.4 due to incompatible config syntax.&quot;</p><p>I did ask AI, but there is a way, but is there also a official way to do this by you guys?</p>]]></description>
			<author><![CDATA[null@example.com (BliXem)]]></author>
			<pubDate>Fri, 03 Jul 2026 07:26:35 +0000</pubDate>
			<guid>https://forum.iredmail.org/topic21170-spamassasin-learning-when-move-to-spam-and-out-new-posts.html</guid>
		</item>
		<item>
			<title><![CDATA[SOGo per-user flags (Webmail/ActiveSync) ignored — ModulesConstraints]]></title>
			<link>https://forum.iredmail.org/topic21168-sogo-peruser-flags-webmailactivesync-ignored-modulesconstraints-new-posts.html</link>
			<description><![CDATA[<p>==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====<br />- iRedMail version (check /etc/iredmail-release): 1.7.3 MARIADB edition<br />- Deployed with iRedMail Easy or the downloadable installer? Downloadable installer<br />- Linux/BSD distribution name and version: Debian GNU/Linux 12 (Bookworm)<br />- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL/MariaDB<br />- Web server (Apache or Nginx): Nginx<br />- Manage mail accounts with iRedAdmin-Pro? Yes, iRedAdmin-Pro-SQL 5.8<br />- [IMPORTANT] Related original log or error message is required if you&#039;re experiencing an issue.</p><p>SOGo log extract confirming successful login despite enablesogowebmail = &#039;n&#039; in vmail.mailbox:</p><p>Jun 30 20:11:25 sogod [15240]: SOGoRootPage successful login from &#039;172.16.x.x&#039; for user &#039;user@domain.tld&#039; - expire = -1&nbsp; grace = -1<br />Jun 30 20:11:25 sogod [15240]: 172.16.x.x &quot;POST /SOGo/connect HTTP/1.0&quot; 200 84/94 0.044 - - 0 - 13<br />====</p><p>---</p><p>**[Bug Report] iRedAdmin-Pro SOGo per-user flags (enablesogowebmail, enablesogocalendar, enablesogoactivesync) have no effect on SOGo behavior**</p><p>**Description:**</p><p>iRedAdmin-Pro exposes three per-user toggles under SOGo Groupware:<br />- SOGo Webmail<br />- SOGo Calendar<br />- SOGo ActiveSync</p><p>These map to columns `enablesogowebmail`, `enablesogocalendar` and `enablesogoactivesync` in `vmail.mailbox`, which are exposed via the `sogo.users` view as `c_webmail`, `c_calendar` and `c_activesync` respectively.</p><p>Disabling any of these flags in iRedAdmin-Pro has no effect on SOGo behavior. Users with `enablesogowebmail = &#039;n&#039;` can still log in to the SOGo webmail interface. Users with `enablesogoactivesync = &#039;n&#039;` and `enablesogocalendar = &#039;n&#039;` can still authenticate via EAS (HTTP 200) and CalDAV (HTTP 207 Multi-Status).</p><p>**Verification:**</p><p>Confirmed that the `sogo.users` view correctly exposes the columns:</p><p>```sql<br />SHOW CREATE VIEW sogo.users\G<br />-- Result includes:<br />-- enablesogowebmail AS c_webmail<br />-- enablesogocalendar AS c_calendar<br />-- enablesogoactivesync AS c_activesync<br />```</p><p>Confirmed column type in `vmail.mailbox`:<br />```sql<br />SELECT COLUMN_NAME, DATA_TYPE, CHARACTER_MAXIMUM_LENGTH<br />FROM information_schema.COLUMNS<br />WHERE TABLE_SCHEMA = &#039;vmail&#039; AND TABLE_NAME = &#039;mailbox&#039;<br />AND COLUMN_NAME = &#039;enablesogowebmail&#039;;<br />-- Result: varchar(1)<br />```</p><p>Added `ModulesConstraints` to `/etc/sogo/sogo.conf` inside the SQL `SOGoUserSources` block, using the syntax from the official iRedMail sample:</p><p>```<br />ModulesConstraints = {<br />&nbsp; &nbsp; Mail = { c_webmail = y; };<br />&nbsp; &nbsp; Calendar = { c_calendar = y; };<br />&nbsp; &nbsp; ActiveSync = { c_activesync = y; };<br />};<br />```</p><p>After restarting SOGo, users with `enablesogowebmail = &#039;n&#039;` can still log in successfully. SOGo log confirms:</p><p>```<br />SOGoRootPage successful login from &#039;172.16.x.x&#039; for user &#039;user@domain.tld&#039; - expire = -1&nbsp; grace = -1<br />POST /SOGo/connect HTTP/1.0&quot; 200<br />```</p><p>**Root cause (suspected):**</p><p>This appears to be related to SOGo bug #5390 (ModulesConstraints and SQL column type VARCHAR(1)), which was reported as resolved but the behavior persists in SOGo 5.9.0 with MySQL/MariaDB backend. The `ModulesConstraints` directive does not appear to be enforced for SQL authentication sources in this version.</p><p>**Impact:**</p><p>The per-user SOGo service flags in iRedAdmin-Pro are effectively non-functional. Administrators who disable SOGo Webmail, Calendar or ActiveSync for specific users via iRedAdmin-Pro will see no actual restriction applied. This is a silent failure with no warning in the UI or logs.</p><p>**Workaround currently in use:**</p><p>Blocking SOGo web access at the nginx level by redirecting `/SOGo`, `/SOGo/` and `/SOGo/connect` to `/mail` (Roundcube). This is a global block and does not allow per-user granularity.</p><p>**Question:**</p><p>Is there a supported way to enforce per-user SOGo service restrictions (webmail, calendar, ActiveSync) with a MySQL/MariaDB SQL backend in iRedAdmin-Pro 5.8 / SOGo 5.9.0? If `ModulesConstraints` is not functional for SQL sources, should the iRedAdmin-Pro UI reflect this limitation?</p>]]></description>
			<author><![CDATA[null@example.com (oscarfp)]]></author>
			<pubDate>Tue, 30 Jun 2026 18:54:41 +0000</pubDate>
			<guid>https://forum.iredmail.org/topic21168-sogo-peruser-flags-webmailactivesync-ignored-modulesconstraints-new-posts.html</guid>
		</item>
		<item>
			<title><![CDATA[Enterprise Edition Installer only listens on IPv6, even when disabled]]></title>
			<link>https://forum.iredmail.org/topic21166-enterprise-edition-installer-only-listens-on-ipv6-even-when-disabled-new-posts.html</link>
			<description><![CDATA[<p>==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====<br />- iRedMail version (latest): <br />- Deployed with iRedMail Easy or the downloadable installer? EE Installer<br />- Linux/BSD distribution name and version: Debian Trixie <br />- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MariaDB intended<br />- Web server (Apache or Nginx): Nginx Intended<br />- Manage mail accounts with iRedAdmin-Pro? EE/Yes<br />- [IMPORTANT] Related original log or error message is required if you&#039;re experiencing an issue.<br />====</p><p>root@mail:~# iredmail -debug<br />Seems server doesn&#039;t have iRedMail Enterprise Edition installed, launch installer on port 8080.<br />HTTP Basic Authentication:<br />- Username: xxxxxxxxxxxxxxxxxxx<br />- Password: xxxxxxxxxxxxxxxxxxxx</p><p>root@mail:/opt/iredmail/conf# netstat -ano | grep 8080<br />tcp6&nbsp; &nbsp; &nbsp; &nbsp;0&nbsp; &nbsp; &nbsp; 0 :::8080&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;:::*&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; LISTEN&nbsp; &nbsp; &nbsp; off (0.00/0/0)</p><p>root@mail:/opt/iredmail/conf# ip a<br />1: lo: &lt;LOOPBACK,UP,LOWER_UP&gt; mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000<br />&nbsp; &nbsp; link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00<br />&nbsp; &nbsp; inet 127.0.0.1/8 scope host lo<br />&nbsp; &nbsp; &nbsp; &nbsp;valid_lft forever preferred_lft forever<br />2: enp1s0: &lt;BROADCAST,MULTICAST,UP,LOWER_UP&gt; mtu 1500 qdisc mq state UP group default qlen 1000<br />&nbsp; &nbsp; link/ether 56:00:06:4b:b2:db brd ff:ff:ff:ff:ff:ff<br />&nbsp; &nbsp; altname enx5600064bb2db<br />&nbsp; &nbsp; inet x.x.x.x/23 brd x.x.x.x scope global dynamic noprefixroute enp1s0<br />&nbsp; &nbsp; &nbsp; &nbsp;valid_lft 85611sec preferred_lft 74811sec</p><p>root@mail:/opt/iredmail/conf# cat /proc/sys/net/ipv6/conf/all/disable_ipv6 <br />1</p><p>All the files under /opt/iredmail appear to be binaries, I can&#039;t find anything to edit to force IPv4.</p><p>Please advise.</p>]]></description>
			<author><![CDATA[null@example.com (familyguy)]]></author>
			<pubDate>Thu, 25 Jun 2026 19:13:11 +0000</pubDate>
			<guid>https://forum.iredmail.org/topic21166-enterprise-edition-installer-only-listens-on-ipv6-even-when-disabled-new-posts.html</guid>
		</item>
		<item>
			<title><![CDATA[amavis connection to MySQL server error]]></title>
			<link>https://forum.iredmail.org/topic21165-amavis-connection-to-mysql-server-error-new-posts.html</link>
			<description><![CDATA[<p>==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====<br />- iRedMail version (check /etc/iredmail-release): 1.8.2<br />- Deployed with iRedMail Easy or the downloadable installer? downloadable installer<br />- Linux/BSD distribution name and version: Ubuntu 24.04<br />- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL<br />- Web server (Apache or Nginx):nginx<br />- Manage mail accounts with iRedAdmin-Pro?<br />- [IMPORTANT] Related original log or error message is required if you&#039;re experiencing an issue.<br />====</p><p>2026-06-22T07:07:32.576925+00:00 mail postfix/smtpd[388043]: connect from bg1.exmail.qq.com[114.132.73.137]<br />2026-06-22T07:07:32.620463+00:00 mail postfix/smtpd[388043]: discarding EHLO keywords: CHUNKING<br />2026-06-22T07:07:32.819446+00:00 mail postfix/smtpd[388043]: Anonymous TLS connection established from bg1.exmail.qq.com[114.132.73.137]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)<br />2026-06-22T07:07:32.967670+00:00 mail postfix/smtpd[388043]: discarding EHLO keywords: CHUNKING<br />2026-06-22T07:07:33.409815+00:00 mail postfix/smtpd[388043]: 4gkK5d2rXVzWg98: client=bg1.exmail.qq.com[114.132.73.137]<br />2026-06-22T07:07:33.547703+00:00 mail postfix/cleanup[388066]: 4gkK5d2rXVzWg98: message-id=&lt;mis_33F71FEF4DF9EA35360F6619@exmail.weixin.qq.com&gt;<br />2026-06-22T07:07:33.553916+00:00 mail postfix/qmgr[278081]: 4gkK5d2rXVzWg98: from=&lt;10000@exmail.weixin.qq.com&gt;, size=17755, nrcpt=1 (queue active)<br />2026-06-22T07:07:33.582693+00:00 mail postfix/smtpd[388043]: disconnect from bg1.exmail.qq.com[114.132.73.137] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7<br />2026-06-22T07:07:33.600267+00:00 mail amavis[2470]: (02470-02) NOTICE: reconnecting in response to: err=2013, HY000, DBD::mysql::st execute failed: Lost connection to MySQL server during query at /usr/share/perl5/Amavis/Out/SQL/Connection.pm line 175.</p>]]></description>
			<author><![CDATA[null@example.com (charwavid)]]></author>
			<pubDate>Tue, 23 Jun 2026 01:13:41 +0000</pubDate>
			<guid>https://forum.iredmail.org/topic21165-amavis-connection-to-mysql-server-error-new-posts.html</guid>
		</item>
		<item>
			<title><![CDATA[roundcube Oops... something went wrong!]]></title>
			<link>https://forum.iredmail.org/topic21164-roundcube-oops-something-went-wrong-new-posts.html</link>
			<description><![CDATA[<p>==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====<br />- iRedMail version (check /etc/iredmail-release):&nbsp; 1.8.0 MARIADB edition.<br />- Deployed with iRedMail Easy or the downloadable installer? downloadable installer<br />- Linux/BSD distribution name and version: Rocky 8.10<br />- Store mail accounts in which backend (LDAP/MySQL/PGSQL): mariadb<br />- Web server (Apache or Nginx):Nginx<br />- Manage mail accounts with iRedAdmin-Pro?No<br />- [IMPORTANT] Related original log or error message is required if you&#039;re experiencing an issue.<br />====<br />I have made mistakes while upgrading iredmail to 1.8.0<br />Everything seems OK now, except accessing roundcube gives to message: Oops... something went wrong!</p><p>My initial mistake was that I missed the instruction to upgrade php from v8.0 to v8.2, and I tried v8.5 (which is not compatible).&nbsp; After I got that sorted out (installed php v8.2), I don&#039;t see any relevant error message in any log, but the problem continues.</p><p>If I replace the roundcube index.php with a test .php file, that is served correctly, so nginx and php-fpm are working, and mariadb is running.</p><p>Can you give some hints as to where to look, or how to enable more logging?</p>]]></description>
			<author><![CDATA[null@example.com (redcar)]]></author>
			<pubDate>Sat, 20 Jun 2026 14:30:47 +0000</pubDate>
			<guid>https://forum.iredmail.org/topic21164-roundcube-oops-something-went-wrong-new-posts.html</guid>
		</item>
		<item>
			<title><![CDATA[how install Sogo with 1.8.2]]></title>
			<link>https://forum.iredmail.org/topic21163-how-install-sogo-with-182-new-posts.html</link>
			<description><![CDATA[<p>==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====<br />- iRedMail version (check /etc/iredmail-release): 1.8.2<br />- Deployed with iRedMail Easy or the downloadable installer? Installer<br />- Linux/BSD distribution name and version: Ubuntu 26.04<br />- Store mail accounts in which backend (LDAP/MySQL/PGSQL): LDAP<br />- Web server (Apache or Nginx): Nginx<br />- Manage mail accounts with iRedAdmin-Pro? No<br />- [IMPORTANT] Related original log or error message is required if you&#039;re experiencing an issue.<br />====</p><p>Hello !<br />How are you? <br />we Love iredmail ! Thanks for your job </p><p>I&#039;ve just try to install new one for upgrade but installer does not ask for SOGO at the last screen just before execute.<br />just roundCube iRedAdmin and Fail2Ban :0( </p><p>Best regards</p>]]></description>
			<author><![CDATA[null@example.com (Tonton)]]></author>
			<pubDate>Fri, 19 Jun 2026 16:26:16 +0000</pubDate>
			<guid>https://forum.iredmail.org/topic21163-how-install-sogo-with-182-new-posts.html</guid>
		</item>
	</channel>
</rss>
