Are you the publisher? Claim or contact us about this channel


Embed this content in your HTML

Search

Report adult content:

click to rate:

Account: (login)

More Channels


Showcase


Channel Catalog


Channel Description:

The most recent posts in iRedMail.

older | 1 | .... | 1335 | 1336 | (Page 1337) | 1338 | 1339 | .... | 1394 | newer

    0 0
  • 10/27/18--06:46: Re: Error on Debian 9
  • Did not use any third party packages in this installation.


    0 0

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


    i have problem with postfix, amavis (iredmail). I have 200 mail in queue at couple days. If i want flush i have i in log file:

    Oct 27 12:08:20  postfix/qmgr[20923]: CA731868F520: from=<mo@pppp.com>, size=12340, nrcpt=1 (queue active)
    Oct 27 12:08:20  postfix/smtp[21003]: fatal: garbage after numerical service in server description: [127.0.0.1]:10024?smtp-amavis_destination_recipient_limit = 1

    later:

    Oct 27 12:08:21 postfix/error[21038]: 9907983ABC4A: to=<biuppp@aaaa.com>, relay=none, delay=158805, delays=158804/1/0/0, dsn=4.3.0, status=deferred (unknown mail transport error)

        Oct 27 13:03:13  postfix/qmgr[23077]: warning: private/smtp-amavis socket: malformed response
    Oct 27 13:03:13  postfix/qmgr[23077]: warning: transport smtp-amavis failure -- see a previous warning/fatal/panic logfile record for the problem description

    In /etc/postfix/main.cf

    #
    # Amavisd + SpamAssassin + ClamAV
    #
    content_filter = smtp-amavis:[127.0.0.1]:10024
    smtp-amavis_destination_recipient_limit = 1

    With and without or coment smtp-amavis_destination_recipient_limit = 1 always is the same fatal error.


    I don't know what's goingon with this. Restart, amavis, postfix, double config check, update amavisd, clamav don't work. Still 200 in postfix queue like deferred sad

    systemctl status amavisd
    ● amavisd.service - Amavisd-new is an interface between MTA and content checkers.
       Loaded: loaded (/usr/lib/systemd/system/amavisd.service; enabled; vendor preset: disabled


    systemctl status postfix
    ● postfix.service - Postfix Mail Transport Agent
       Loaded: loaded (/usr/lib/systemd/system/postfix.service; enabled; vendor preset: disabled)
       Active: active (running) since sob 2018-10-27 12:07:27 CEST; 12min ago


    0 0
  • 10/27/18--08:32: Re: Error on Debian 9
  • gao wrote:

    Sat Oct 27 13:37:29 2018 -> WARNING: Clamd was NOT notified: Can't connect to clamd through /var/run/clamav/clamd.ctl: No such file or directory

    This is a known "issue", during iRedMail installation, clamav-daemon service is not running (and it can NOT start due to no clamav virus signature database). So after iRedMail calls 'freshclam' command to update signature database, freshclam tries to notify clamav-daemon process, but obviously it will fail.

    After iRedMail installation, iRedMail installer pints a message to remind you to reboot server to bring up all services (note: this is only required after installation).


    0 0
  • 10/27/18--08:33: Re: Error on Debian 9
  • ZhangHuangbin wrote:
    gao wrote:

    Sat Oct 27 13:37:29 2018 -> WARNING: Clamd was NOT notified: Can't connect to clamd through /var/run/clamav/clamd.ctl: No such file or directory

    This is a known "issue", during iRedMail installation, clamav-daemon service is not running (and it can NOT start due to no clamav virus signature database). So after iRedMail calls 'freshclam' command to update signature database, freshclam tries to notify clamav-daemon process, but obviously it will fail.

    After iRedMail installation, iRedMail installer pints a message to remind you to reboot server to bring up all services (note: this is only required after installation).

    Thank you. Does that mean no action is required? I can just boot up the server and it wont cause an issue?


    0 0
  • 10/27/18--11:14: Re: Error on Debian 9
  • No action required.


    0 0

    Confirmed it's a bug and fixed it. Here's the procedure of why it happened:

    1) Someone sends email to a mlmmj mailing list.
    2) mlmmj connects to Amavisd for DKIM signing (port 10027, without spam/virus/bad-header/banned checks). Using port 25 is not ok because Amavisd will not sign DKIM on it. Port 587 is not ok either because it requires SMTP AUTH.
    3) Amavisd re-injects the email back to Postfix through port 10025
    4) Postfix sends the email to final recipient

    The problem occurs at step #3 when Postfix accepts the email. With default iRedMail setting, in /etc/postfix/master.cf, there's a line for port 10025:

    10025 inet n  -   n   -   -  smtpd
        ...
        -o receive_override_options=no_header_body_checks,no_unknown_recipient_checks,no_address_mappings

    With option 'no_address_mappings', Postfix does not perform virtual aliad address expansion, so it doesn't know the final recipient address of your per-user alias address (craig1234@) is actually crag@, then it hands over the email to LDA (local deliver agent, it's Dovecot LDA in our case). But in Dovecot config file, the SQL query doesn't check virtual alias mapping.

    Since there're many kinds of address mappings, it's not ideal to handle this in Dovecot. Instead, we did some changes in Postfix and Amavisd config files to make it working perfectly.

    I will publish the fix soon in (DRAFT) iRedMail upgrade tutorial.


    0 0

    Here's the detailed fix.

    *) In /etc/amavsd/amavisd.conf, find existing config lines like below:

    $policy_bank{'MLMMJ'} = {
        ...
    };

    Add a new line inside the {} block:

    $policy_bank{'MLMMJ'} = {
        ...
        forward_method => 'smtp:[127.0.0.1]:10028',
    };

    Here we use a new smtp port 10028.

    *) Append new lines to file /etc/postfix/master.cf:

    10028 inet n  -   n   -   -  smtpd
        -o syslog_name=postfix/10028
        -o content_filter=
        -o mynetworks_style=host
        -o mynetworks=127.0.0.1
        -o local_recipient_maps=
        -o relay_recipient_maps=
        -o strict_rfc821_envelopes=yes
        -o smtp_tls_security_level=none
        -o smtpd_tls_security_level=none
        -o smtpd_restriction_classes=
        -o smtpd_delay_reject=no
        -o smtpd_client_restrictions=permit_mynetworks,reject
        -o smtpd_helo_restrictions=
        -o smtpd_sender_restrictions=
        -o smtpd_recipient_restrictions=permit_mynetworks,reject
        -o smtpd_end_of_data_restrictions=
        -o smtpd_error_sleep_time=0
        -o smtpd_soft_error_limit=1001
        -o smtpd_hard_error_limit=1000
        -o smtpd_client_connection_count_limit=0
        -o smtpd_client_connection_rate_limit=0
        -o receive_override_options=no_header_body_checks,no_unknown_recipient_checks

    It's very similar to existing transport '10025', but without option "no_address_mappings".

    Note: port 10025 is used BEFORE content filter, but 10028 is used AFTER content filter, so one needs 'no_address_mappings' and the other one doesn't, that's why we cannot use existing 10025.

    *) Restart both postfix and amavisd services.

    That's all. Please try it and let me know whether or not it works perfectly for you.


    0 0

    Seems you modified Postfix config files /etc/postfix/main.cf but it contains invalid value.
    Search '10024' in this file and double check that line.


    0 0

    Did you check Apache error log file? It has 2 log files, one for normal access, another for errors. /var/log/httpd/*error*

    I need relevant log for troubleshooting.


    0 0

    How about this:

    - Turn on plugin "acl" in Roundcube
    - Login to roundcube as user A, go to "Settings -> Folders" page to share a folder.
    - Login to roundcube as user B to verify the shared folder.


    0 0

    ZhangHuangbin wrote:

    Did you check Apache error log file? It has 2 log files, one for normal access, another for errors. /var/log/httpd/*error*

    I need relevant log for troubleshooting.

    Hi. No nothing comes up in the error log. When I go into a user and make a change, the only logs updated are ssl_access and ssl_request and those are both normal.


    0 0

    I really don't understand this.

    I chack.

    grep 10024 /etc/postfix/main.cf
    content_filter = smtp-amavis:[127.0.0.1]:10024

    cat /etc/postfix/main.cf
    postscreen_blacklist_action = enforce

    #
    # Amavisd + SpamAssassin + ClamAV
    #
    content_filter = smtp-amavis:[127.0.0.1]:10024

    # Concurrency per recipient limit.
    smtp-amavis_destination_recipient_limit = 1

    #
    # Dovecot SASL support.
    #


    Oct 27 22:44:40 poczta postfix/master[3799]: warning: process /usr/libexec/postfix/smtp pid 3836 exit status 1
    Oct 27 22:44:40 poczta postfix/qmgr[3801]: warning: private/smtp-amavis socket: malformed response
    Oct 27 22:44:40 poczta postfix/qmgr[3801]: warning: transport smtp-amavis failure -- see a previous warning/fatal/panic logfile record for the problem description


    Oct 27 22:44:39 poczta postfix/smtp[3809]: fatal: garbage after numerical service in server description: [127.0.0.1]:10024?smtp-amavis_destination_recipient_limit = 1
    Oct 27 22:44:39 poczta postfix/smtp[3814]: fatal: garbage after numerical service in server description: [127.0.0.1]:10024?smtp-amavis_destination_recipient_limit = 1
    Oct 27 22:44:39 poczta postfix/smtp[3816]: fatal: garbage after numerical service in server description: [127.0.0.1]:10024?smtp-amavis_destination_recipient_limit = 1
    Oct 27 22:44:39 poczta postfix/smtp[3817]: fatal: garbage after numerical service in server description: [127.0.0.1]:10024?smtp-amavis_destination_recipient_limit = 1
    Oct 27 22:44:39 poczta postfix/smtp[3818]: fatal: garbage after numerical service in server description: [127.0.0.1]:10024?smtp-amavis_destination_recipient_limit = 1


    0 0

    This is what I wrote in my opening post, that is how I did it.

    But as the IMAP commands LIST and LIST-EXTENDED doesn't show the shared folders, which is most likely because the folders aren't created in the physical mailbox by Dovecot, using every higher-level solution like roundcube or an email client is pointless, as they use those commands to retrieve the Mailbox folders.

    The problem is that Dovecot doesn't create the Shared/<shared-user@domain> directory in the Mailbox directory of the user shared to.


    0 0
  • 10/27/18--18:54: Cerbot SSL
  • Hello,
    I'm still having this SSL issue: Your connection is not secure.
    Of course I used Cerbot.

    ===
    iRedmail 0.9.8
    Debian9
    MySQL
    Nginx
    ===

    Best.


    0 0

    ZhangHuangbin wrote:

    That's all. Please try it and let me know whether or not it works perfectly for you.

    Thanks Zhang, it does indeed work perfectly. Excellent!

    Now, about those zombie processes. Mlmmj is not a systemd service, so restarting doesn't work. Any suggestions?

    Thanks.


    Craig


    0 0

    Sorry, let me clarify my last post. I know I can kill the zombie processes, of course, but what can I do to avoid them in the first place? Why are they happening?

    Thanks.


    0 0

    No idea yet, this is first report of the zombie process issue.
    Any way to reproduce it steadily?


    0 0
  • 10/28/18--03:48: Re: Cerbot SSL
  • Does this ssl warning appear when you access some https web site? if yes, what's the web domain name?
    The domain names supported by your ssl cert must contain your web domain name.


    0 0

    - Which Dovecot version are you running?
    - Would you like to compare your Dovecot config with the latest one (just the shared folder part)? https://bitbucket.org/zhb/iredmail/src/ … cot22.conf


    0 0

    shiver25 wrote:

    Oct 27 22:44:39 poczta postfix/smtp[3816]: fatal: garbage after numerical service in server description: [127.0.0.1]:10024?smtp-amavis_destination_recipient_limit = 1

    I suggest double check these 2 lines, seems there's no line break after '10024'.
    Maybe edit them manually again.


older | 1 | .... | 1335 | 1336 | (Page 1337) | 1338 | 1339 | .... | 1394 | newer