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 | .... | 1370 | 1371 | (Page 1372) | 1373 | 1374 | .... | 1394 | newer

    0 0

    OK, did you test the issue on new server?


    0 0

    This is a bug of iRedAdmin 0.9.2. sad
    Please add one line in libs/default_settings.py:

    AMAVISD_CLEANUP_QUERY_SIZE_LIMIT = 100

    Then restart iredadmin service.


    0 0

    ZhangHuangbin wrote:

    If only the sql table "iredapd.greylisting_tracking" has this issue, the quickly solution might be:

    - Remove files of this table in MySQL database directory.
    - Start mysql service.
    - Re-create this table (you can copy the sql commands from /opt/iredapd/SQL/iredapd.mysql).

    If there're many sql tables with this issue, it's a different story.

    Thanks for the helping me! I fixed it by deleting greylisting_tracking.ibd in /var/lib/mysql/iredapd
    and then MySQL started right up.
    Marking this as solved


    0 0

    Is the netdata service running?


    0 0

    There're few comment lines in the upgrade script:

    # Notes:
    #
    #   * it uses sql username 'root' by default to connect to sql database. If you
    #     are using a remote SQL database which you don't have root privilege,
    #     please specify the sql username on command line with 'SQL_IREDADMIN_USER'
    #     parameter like this:
    #
    #       SQL_IREDADMIN_USER='iredadmin' bash upgrade_iredadmin.sh
    #
    #   * it reads sql password for given sql user from /root/.my.cnf by default.
    #     if you use a different file, please specify the file on command line with
    #     'MY_CNF' parameter like this:
    #
    #       MY_CNF='/root/.my.cnf-iredadmin' SQL_IREDADMIN_USER='iredadmin' bash upgrade_iredadmin.sh

    I suggest you write a my.cnf (with remote db server as server address) on iRedMail server, then run the iRedAdmin upgrade script with the MY_CNF= to specify my.cnf path, and optionally specify the sql user name.


    0 0

    Any error in Nginx / iRedAdmin-Pro log file?


    0 0

    It's "slapd", not sldap.


    0 0

    - Did you restart the server so that all required services are running after system start up?
    - Any error in Nginx log file (/var/log/nginx/)? and /var/log/maillog, /var/log/messages?
    - Maybe you can try our new deployment / upgrade / technical support platform instead: https://www.iredmail.org/easy.html


    0 0

    Try this:

    - Setup a fresh new server OS
    - Download iRedMail installer (https://www.iredmail.org/download.html )
    - run the installer

    iRedMail installer directory has a sub-directory named "runtime/", it contains installation progress and log, if you re-run the installer without remove installation progress file, it will skip almost all steps.

    Another way is try our new deployment / upgrade / technical support platform: iRedMail Easy.
    https://www.iredmail.org/easy.html


    0 0

    Please make sure you re-created removed sql table(s).


    0 0

    OMG sad What a stupid mistake! Thank you!


    0 0

    ZhangHuangbin wrote:

    Try this:

    - Setup a fresh new server OS
    - Download iRedMail installer (https://www.iredmail.org/download.html )
    - run the installer

    I cannot see the point in repeating exactly what I have done. Computers are deterministic, and it will produce the identical result if I repeat the same procedure.

    Thank you for trying.  I was impressed by the concept and the efficiency of the installer, but it is apparently not in a condition to succeed -- at least on a fresh Debian 9 server.  I will consider trying a different distro, although I prefer to run Debian on servers, as I find it easiest to administer.

    Another way is try our new deployment / upgrade / technical support platform: iRedMail Easy.
    https://www.iredmail.org/easy.html

    I saw that you have a new platform that is paid for.  This is not a commercial server, so I am minimizing expense.  I usually give donations to developers of software once it proves itself useful, but prefer to keep the costs on charity work low.


    0 0

    - Does file iRedMail-0.9.9/runtime/install.log contain any error?

    I think the problem is we don't have the console output for troubleshooting, although you claimed there's no error on console, but we're not sure about this claim. i understand you're an experience sysadmin, but that doesn't mean an experience sysadmin doesn't make any mistake or ignore something important. We just need relevant log for troubleshooting.

    Many users run Debian 9 + iRedMail smoothly, so Debian 9 is not a problem at all. We just need to figure out why it doesn't work for you, and we're here to help you out.


    0 0
  • 12/19/18--02:08: Maillist User Deletion Issue
  • ==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
    - iRedMail version (check /etc/iredmail-release): 0.9.9
    - Deployed with iRedMail Easy or the downloadable installer?
    - Linux/BSD distribution name and version: Centos 7 Minimal
    - 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.
    ====

    I upgraded my iRedMail-Pro and Admin to newest version. Admin Pro to 3.2.

    When I try to remove any new user or moderator from normal mail list (Not mlmmj list) it only shows successful message as "Profile has been updated". Actually it is not removing user from mail list. Message is also confusing where it should come as User had been remove from mail list or User has been removed successfully.

    Top search bar function is also having issue: When searching anything from top search bar it does not give results and only throws following error.

    Error: IndexError('list index out of range',)


    0 0

    Thanks for the rapid reply!

    ZhangHuangbin wrote:

    - Does file iRedMail-0.9.9/runtime/install.log contain any error?

    I think the problem is we don't have the console output ... We just need relevant log for troubleshooting.

    This really shows up an important omission in your script, or in the installation instructions. If the script does not log itself, you should instruct users to run ' # script -t 2>~/install-iredmail.time -a ~/install-iredmail.script' or something similar...

    For unconnected reasons, I am looking at possibility of running a further vm.  If I do, I will have a fresh server to try again.  Given the amount of time wasted on reinstating everything else after reimaging, installing and testing iredmail, I am not keen to simply do it over again.


    0 0

    ZhangHuangbin wrote:

    Any error in Nginx / iRedAdmin-Pro log file?

    Nginx access.log

    "GET /iredadmin/activities/quarantined/raw/JhsqVyjDOwzf HTTP/1.1" 504 578 "https://xxxxx.xx/iredadmin/activities/quarantined" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36"

    /var/log/messages

    Dec 19 12:05:48 mail uwsgi: mail.xxx.xxx [pid: 704|app: 1|req: 12/21] xx.xxx.xxx () {52 vars in 850 bytes} [Wed Dec 19 12:05:48 2018] GET /iredadmin/login => generated 5029 bytes in 234 msecs (HTTP/1.1 200) 2 headers in 146 bytes (2 switches on core 0)
    Dec 19 12:05:50 mail uwsgi: mail.xxx.xxx [pid: 703|app: 1|req: 3/22] xx.xxx.xxx () {64 vars in 1158 bytes} [Wed Dec 19 12:05:50 2018] POST /iredadmin/login => generate 0 bytes in 14 msecs (HTTP/1.1 303) 3 headers in 214 bytes (2 switches on core 0)
    Dec 19 12:05:51 mail uwsgi: mail.xxx.xxxh [pid: 704|app: 1|req: 13/23] xx.xxx.xxx () {58 vars in 1034 bytes} [Wed Dec 19 12:05:50 2018] GET /iredadmin/dashboard/checknew => generated 23804 bytes in 1478 msecs (HTTP/1.1 200) 2 headers in 146 bytes (2 switches on core 0)
    Dec 19 12:06:07 mail uwsgi: mail.xxx.xxx [pid: 704|app: 1|req: 14/24] xx.xxx.xxx () {56 vars in 1024 bytes} [Wed Dec 19 12:06:05 2018] GET /iredadmin/activities/quarantined => generated 26507 bytes in 1180 msecs (HTTP/1.1 200) 2 headers in 146 bytes (2 switches on core 0)

    What's worse, is now iredadmin become unresponsive. Reboot required.


    0 0

    ==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
    - iRedMail version (check /etc/iredmail-release): v0.9.9
    - Deployed with iRedMail Easy or the downloadable installer? previosuly installed by ZhangHuangbin
    - Linux/BSD distribution name and version: Ubuntu 18.04LTS
    - 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.
    ====

    After receiving the mail notification from iRedMail on Monday morning stating there was a new version of iRedMail, I followed all the instructions from https://docs.iredmail.org/upgrade.iredm … 0.9.9.html and in doing so saw that I also had to update iRedAdmin. I therefore followed the instructions in https://docs.iredmail.org/migrate.or.u … admin.html, tested it and it all seemed okay, at the time.

    Since then, I've had to reboot the server and am now getting an Internal Server Error on iRedAdmin.

    Here's the most recent relevant snippet from my syslog:

    Dec 19 10:18:33 mail uwsgi: Traceback (most recent call last):
    Dec 19 10:18:33 mail uwsgi:   File "/opt/www/iRedAdmin-0.9.2/iredadmin.py", line 9, in <module>
    Dec 19 10:18:33 mail uwsgi: 
    Dec 19 10:18:33 mail uwsgi: from libs import iredbase
    Dec 19 10:18:33 mail uwsgi:   File "/opt/www/iRedAdmin-0.9.2/libs/iredbase.py", line 18, in <module>
    Dec 19 10:18:33 mail uwsgi: 
    Dec 19 10:18:33 mail uwsgi: import iredutils
    Dec 19 10:18:33 mail uwsgi:   File "/opt/www/iRedAdmin-0.9.2/libs/iredutils.py", line 14, in <module>
    Dec 19 10:18:33 mail uwsgi: 
    Dec 19 10:18:33 mail uwsgi: import settings
    Dec 19 10:18:33 mail uwsgi: ImportError
    Dec 19 10:18:33 mail uwsgi: :
    Dec 19 10:18:33 mail uwsgi: No module named settings
    Dec 19 10:18:33 mail uwsgi: 
    Dec 19 10:18:33 mail uwsgi: unable to load app 0 (mountpoint='mail.mydomain.com|/iredadmin') (callable not found or import error)
    Dec 19 10:18:33 mail uwsgi: --- no python application found, check your startup logs for errors ---
    Dec 19 10:18:33 mail uwsgi: mail.mydomain.com [pid: 1090|app: -1|req: -1/4] 82.34.102.81 () {56 vars in 1334 bytes} [Wed Dec 19 10:18:33 2018] GET /iredadmin => generated 21 bytes in 8 msecs (HTTP/1.1 500) 2 headers in 83 bytes (0 switches on core 0)

    I can confirm that mail seems to be working okay, since I'm still successfully able to send and receive mail.

    Fortunately, I also have backups that I could recover to, but that would mean I'd have to start the whole upgrade process all over again.

    I'd appreciate any thoughts/suggestions as to how I'd go about resolving this iRedAdmin Internal Server Error.

    Thanks


    0 0

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

    Hello guys,

    I am new to this forum however i am using iRedMail for more then 2 years now.

    Now i got a small problem and i know this function exists before.

    Case: When a server logging in by using smtp program (Like: SSMTP) to send emails, the mail can get rejected because the FROM Email address does not match with the one thats listed. Recently i discovered that i am able to mail from noexistinguser@existingdomain.nl  while logging in via SSTMP with valid credentials (valid email + password). ).


    This is my main.cf
    # HELO restriction
    smtpd_helo_required = yes
    smtpd_helo_restrictions =
        permit_mynetworks
        permit_sasl_authenticated
        reject_non_fqdn_helo_hostname
        reject_invalid_helo_hostname
        check_helo_access pcre:/etc/postfix/helo_access.pcre

    # Sender restrictions
    smtpd_sender_restrictions =
        reject_unknown_sender_domain
        reject_non_fqdn_sender
        reject_unlisted_sender
        permit_sasl_authenticated
        permit_mynetworks
        reject_rbl_client zen.spamhaus.org=127.0.0.[2..11]
        reject_rbl_client b.barracudacentral.org=127.0.0.2
        check_sender_access pcre:/etc/postfix/reject_domain

    # Recipient restrictions
    smtpd_recipient_restrictions =
        reject_unknown_recipient_domain
        reject_non_fqdn_recipient
        reject_unlisted_recipient
        check_policy_service inet:127.0.0.1:7777
        permit_mynetworks
        permit_sasl_authenticated
        reject_unauth_destination
        reject_unlisted_sender
        reject_rbl_client zen.spamhaus.org=127.0.0.[2..11]
        reject_rbl_client b.barracudacentral.org=127.0.0.2
        check_sender_access pcre:/etc/postfix/reject_domains

    As far i my knowledge reaches i am getting the impression that some link is broken to the virtual user table.

    I searched en configured alot but i am not getting the impression that its working.

    Hopefully you guys can help me out.

    Thanks!


    0 0

    Just seen another new version 0.9.3 of iRedAdmin available today in https://dl.iredmail.org/yum/misc/?C=M;O=D

    Installed and now working again :-)


    0 0

    Dear all,

    We now have a perfect solution to fix this issue with the latest iRedAdmin release (either iRedAdmin or iRedAdmin-Pro):

    - iRedAdmin-0.9.3 (open source edition)
    - iRedAdmin-Pro-SQL-3.0
    - iRedAdmin-Pro-LDAP-3.2

    After you upgraded to either one, iRedAdmin(-Pro) will run as a standalone service named "iredadmin" and listening on port (127.0.0.1:)7791, it doesn't depend / rely on Apache mod_wsgi module although it still works with mod_wsgi. But if mod_wsgi doesn't work for you, here's another solution to fix it.

    - Upgrade iRedAdmin(-Pro) first
    - On Debian/Ubuntu, backup /etc/apache2/conf-enabled/iredadmin.conf first then replace its content by:

    Alias /iredadmin/static/ "/usr/share/apache2/iredadmin/static/"
    
    <Location "/iredadmin">
    RewriteEngine on
    RewriteCond %{REQUEST_URI} ^(.*)//(.*)$
    RewriteRule . %1/%2 [L]
    </Location>
    
    ProxyPass "/iredadmin/static/" "!"
    ProxyPass "/iredadmin" "uwsgi://127.0.0.1:7791"

    Note: some old Debian/Ubuntu system may use /etc/apache2/conf.d/iredadmin.conf instead, better move it to /etc/apache2/conf-available/ then enable it with command 'a2enconf iredadmin', do not use '/etc/apache2/conf.d/' anymore.

    - Install and enable required Apache modules, then restart Apache service:

    apt-get install libapache2-mod-proxy-uwsgi
    a2enmod rewrite proxy proxy_uwsgi
    service apache2 restart

    I fixed this issue on one client's server with this solution. Let me know whether or not it works for you.


older | 1 | .... | 1370 | 1371 | (Page 1372) | 1373 | 1374 | .... | 1394 | newer