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 | .... | 1367 | 1368 | (Page 1369) | 1370 | 1371 | .... | 1394 | newer

    0 0

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

    Error: mysql(192.168.1.50): Connect failed to database (vmail): Access denied for user 'vmail'@'mail.lxd'

    I have installed iredmail inside a LXC container and after a reboot of my container i get the SQL error.

    It is strange cause the issue is that it changed the host to 'mail.lxd', it should be the ipaddress.

    in settings.py eveything looks okay, im wondering if there is somewhere else a config file making this changes?


    0 0
  • 12/16/18--06:44: webmail not connecting
  • ==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
    - iRedMail version (check /etc/iredmail-release):
    - Linux/BSD distribution name and version:
    - Store mail accounts in which backend (LDAP/MySQL/PGSQL):
    - Web server (Apache or Nginx):
    - Manage mail accounts with iRedAdmin-Pro?
    - [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
    ====
    System Information
    iRedMail:  v0.9.8
    iRedAdmin: v0.9.1(MySQL) 
    Hostname: mx.geeksmail.com
    O/S Ubuntu 18.04
    Web Server: Apache
    Domain name: Justourmail.com

    I am able to  send and receive email via Gmail, yahoo, etc..
    but the web based RoundCube will not connect from internet, it works locally by using 192.168.0.41/mail
    My email server is on a different server then the webserver


    0 0

    ==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
    - iRedMail version (check /etc/iredmail-release):
    - Linux/BSD distribution name and version:
    - Store mail accounts in which backend (LDAP/MySQL/PGSQL):
    - Web server (Apache or Nginx):
    - Manage mail accounts with iRedAdmin-Pro?
    - [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
    ====
    iRedMail-0,9,8, fresh Vultr Ubuntu 18.04, mySQL mail storage, Nginx, not using Pro

    When the installation is in its final steps, my terminal window includes the following error message:
    [ INFO ] Updating ClamAV database (freshclam), please wait ...
    ERROR: /var/log/clamav/freshclam.log is locked by another process
    ERROR: Problem with internal logger (UpdateLogFile = /var/log/clamav/freshclam.log).

    It doesn't seem to affect installation, which goes to completion with no more errors. I haven't yet started using iRedMail so I can't comment on any usability issues.

    Just wanted to give you an alert that this error is being thrown.


    0 0

    ==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
    - iRedMail version (check /etc/iredmail-release):       0.9.8
    - Linux/BSD distribution name and version:               Debian stretch
    - Store mail accounts in which backend (LDAP/MySQL/PGSQL):   LDAP
    - 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.
    ====
    Just tried to install.  System is not a new install, but I removed all mail related packages. 
    Got an error message during installation:

    ...
    Setting up php-ldap (1:7.0+49) ...
    Setting up postfix-ldap (3.1.8-0+deb9u1) ...
    Adding ldap map entry to /etc/postfix/dynamicmaps.cf
    Setting up uwsgi-plugin-python (2.0.14+20161117-3+deb9u2) ...
    Setting up nginx-full (1.10.3-1+deb9u2) ...
    Job for nginx.service failed because the control process exited with error code.
    See "systemctl status nginx.service" and "journalctl -xe" for details.
    invoke-rc.d: initscript nginx, action "start" failed.
    * nginx.service - A high performance web server and a reverse proxy server
       Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
       Active: failed (Result: exit-code) since Sun 2018-12-16 17:52:47 UTC; 9ms ago
         Docs: man:nginx(8)
      Process: 17837 ExecStart=/usr/sbin/nginx -g daemon on; master_process on; (code=exited, status=1/FAILURE)
      Process: 17835 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=0/SUCCESS)
    
    Dec 16 17:52:45 carotid nginx[17837]: nginx: [emerg] bind() to [::]:80 fail…use)
    Dec 16 17:52:46 carotid nginx[17837]: nginx: [emerg] bind() to 0.0.0.0:80 f…use)
    Dec 16 17:52:46 carotid nginx[17837]: nginx: [emerg] bind() to [::]:80 fail…use)
    Dec 16 17:52:46 carotid nginx[17837]: nginx: [emerg] bind() to 0.0.0.0:80 f…use)
    Dec 16 17:52:46 carotid nginx[17837]: nginx: [emerg] bind() to [::]:80 fail…use)
    Dec 16 17:52:47 carotid nginx[17837]: nginx: [emerg] still could not bind()
    Dec 16 17:52:47 carotid systemd[1]: nginx.service: Control process exited, …us=1
    Dec 16 17:52:47 carotid systemd[1]: Failed to start A high performance web …ver.
    Dec 16 17:52:47 carotid systemd[1]: nginx.service: Unit entered failed state.
    Dec 16 17:52:47 carotid systemd[1]: nginx.service: Failed with result 'exit…de'.
    Hint: Some lines were ellipsized, use -l to show in full.
    dpkg: error processing package nginx-full (--configure):
     subprocess installed post-installation script returned error exit status 1
    Setting up php-mbstring (1:7.0+49) ...
    ...

    and of course at the end:

    ...
    Errors were encountered while processing:
     nginx-full
    E: Sub-process /usr/bin/dpkg returned an error code (1)
    << ERROR >> Installation failed, please check the terminal output.

    Perhaps this is because apache2 was still installed, or because I forgot to stop it before installing?
    (I chose nginx in spite of being familiar with apache2, because it was the only option given, and because I thought the two could be installed side by side as long as they are not run simultaneously.)

    In any case, do I now need to uninstall everything in order to start again, or is there a method to repair the nearly complete installation?

    TIA


    0 0

    Apache is listening on port 80/443, but Nginx is trying to bind to same ports. This is the cause.
    It's recommended to use a fresh new server OS for iRedMail installation.


    0 0

    It's safe to ignore, at this stage ClamAV daemon is not running, so freshclam can not talk to its socket to notify ClamAV to reload the virus signature database.


    0 0
  • 12/16/18--22:58: Re: webmail not connecting
  • keith.miller wrote:

    but the web based RoundCube will not connect from internet

    Seems a network relevant issue: is port 80/443 open in firewall?


    0 0

    Did LXC change server hostname automatically after reboot?


    0 0

    MattHo wrote:

    May I know I should follow the upgrade guide to upgrade my iRedmail from 0.9.7 to 0.9.8 first, then upgrade the iRedAdmin-Pro to 2.9.0? Or I can just upgrade my iRedAdmin-Pro to 2.9.0?

    1: upgrade iRedMail from 0.9.7 to 0.9.8. upgrade tutorials: https://docs.iredmail.org/iredmail.releases.html
    2: upgrade iRedAdmin-Pro from any old version to the latest one. upgrade tutorials: https://docs.iredmail.org/migrate.or.up … admin.html

    NOTE: You must upgrade iRedMail to the latest stable release BEFORE upgrading iRedAdmin-Pro.


    0 0

    Thanks


    0 0

    Dear all,

    iRedMail-0.9.9 stable release has been released, also a new web-based deployment, upgrade and support platform, iRedMail Easy, https://www.iredmail.org/easy.html.

    About "iRedMail Easy" - the new deployment, upgrade and support platform

    This is a new web-based deployment, (one-click) upgrade and technical support platform. We rewrite iRedMail installer with Ansible for this platform, also a web interface for ease of use. It's strongly recommended to deploy NEW iRedMail server with iRedMail Easy instead of classic downloadable iRedMail installer.

    For more details, please read our website, the comparison of iRedMail Easy and classic downloadable installer is available too: https://www.iredmail.org/easy.html



    Below are changes since iRedMail-0.9.8, and planned changes in next release.

    Supports new distribution release
    • OpenBSD 6.4[*/]

    • Ubuntu 18.10. WARNING: It receives only 9 months of security and maintenance updates, until July 2019. NOT RECOMMENDED FOR PRODUCTION SERVER.

    Improvements
    • netdata is able to monitor OpenLDAP.

    • SOGo now supports resource management with OpenLDAP backend.

    • Add rc script and rules for ip6tables on Debian/Ubuntu.

    • iRedAdmin is now running as a standalone uwsgi instance (service name 'iredadmin'), not controlled by 'uwsgi' service anymore.

    • For new iRedMail installation, it uses /opt/www to store web applications on all Linux distros and OpenBSD.

    • Able to set per-user mailbox format (e.g. mdbox) and mailbox folder appended to maildir path in SQL/LDAP.

    • Switch to utf8mb4 as default character set in MySQL.

    • Set file/directory permission to 0400 for dumpped SQL backup files.

    • OpenLDAP log file has been moved to /var/log/openldap/openldap.log (was /var/log/openldap.log).

    Fixed issues
    • Not correctly generate/update firewall rules if ssh is listening on 2 network ports.

    • Not index ldap attribute `mobile`.

    • Not always specify a plain text footer file for altermime to update email sent to mlmmj mailing list.

    • Use accurate Nginx url match for Roundcube.

    • mlmmjadmin:

      • Not set correct owner/group for config file.

      • Not use correct syslog socket path on FreeBSD.

    • SQL backends: Not handle alias domains for relay in Postfix.

    Updated packages
    • Roundcube -> 1.3.8

    • iRedAdmin -> 0.9.2

    • iRedAPD -> 2.3

    • mlmmjadmin -> 1.9

    • uwsgi -> 2.0.17.1 (OpenBSD only)

    • netdata -> 1.11.1


    0 0

    Thanks , it works again!


    0 0

    Dear all,

    iRedAdmin-Pro-LDAP-3.2 (iRedAdmin-Pro for OpenLDAP and OpenBSD ldapd(8) backends) is now available for upgrading and purchasing.

    How to download the latest iRedAdmin-Pro

    iRedAdmin-Pro customers can get download link of this new release by following steps below:

    • Login to iRedAdmin-Pro as global admin

    • Click "License" on the top-right corner, it will show you basic license info and a "Download" button if new version is available for upgrading.

    If above steps don't work for you, please send an email to support @ iredmail.org to get download link of the latest release.

    Below are detailed changes since iRedAdmin-Pro-LDAP-3.1:

    RESTful API

    API Document: https://docs.iredmail.org/iredadmin-pro … l.api.html

    • Able to add subscribers while creating (subscribeable) mailing list.

    • Able to add/remove subscribers while updating (subscribeable) mailing list.

    • Able to get all subscribers of given mailing list with optional parameter `with_subscribers=yes`:

      • URI: `GET /api/ml/<mail>?with_subscribers=yes`

    • Able to list all mailing lists in given domain:

      • URI: `GET /api/mls/<domain>`

      • Optional parameters: `email_only=yes`. if present, return a list of mailing list email addresses. Otherwise return a list of mailing list profiles.

    • Able to set mailbox format, mailbox folder name, full maildir path while creating/updating user:

      • URIS:

        • `POST /api/user/<mail>`

        • `PUT  /api/user/<mail>`

      • Parameters: `mailboxFormat`, `mailboxFolder`, `maildir`.

    • Show mailbox size and number of stored messages while getting user profile:

      • URI: GET /api/user/<mail>

      • New parameter names: stored_bytes, stored_messages.

    • Show assigned mail alias groups and mailing lists while getting user profile:

      • URI: GET /api/user/<mail>

      • New parameter names: mailing_aliases, mailing_lists.

    • Able to reset user password by submitting a password hash (`PUT /api/user/<mail>`, parameter `password_hash`).

    • Fixed issues:

      • Cannot verify password: `POST /api/verify_password/user/<mail>`.

    Improvements
    • Able to export statistics of admins.

    • 2 LDAP attributes for mail user are deprecated: storageBaseDirectory, mailMessageStore.

    • If new password doesn't match policies, display error messages of all unmatched policies.

    • Allow multiple title attributes for mail user.

    • Spam policy: able to set score for blocking/quarantining detected spam.

    • In mailing list profile page, it's able to control whether or not to display mailing list in global address book.

    • On search result page, now able to set days to keep mailbox of removed domain and user accounts.

    • Able to define days to keep removed mailbox for normal domain admin and global admin. With default settings, normal admin can keep mailbox for 1 day, 1/2/3 weeks, 1/2/3/6/12 months. Global admin can keep mailbox for 1 day, 1/2/3 weeks, 1/2/3/6/12 months, 2/3 years, and 'forever'.

    • Display user password last change date on user list page and user profile page.

    • Able to set mailbox format while creating new user.

    • New: tools/dump_quarantined_mails.py, used to dump quarantined emails to the directory given on command line. It's useful if you want to train SpamAssassin by calling `sa-learn`.

    Fixed issues
    • self-service: User can not update preferences.

    • Not correctly revoke admin privilege while removing user.

    • Cannot correctly add new user when there's alias domain.

    • Cannot automatically assign newly created user to unsubscribeable mailing list.

    • Normal domain admin can create unlimied domains.

    • Normal domain admin should not be able to update max user quota.

    • Cannot correctly sort domain names on domain list page.

    • Cannot send email to mailing list which is migrated from old-style mailing list.

    • Cannot filter admin log.

    • Incorrect url of mailing list profile page in search result page.

    • Cannot correctly subscribe user to or unsubscribe user from mailing list in user profile page when domain has alias domains.

    • Cannot set throttle setting to inherit from lower priority account.

    • While deleting (old style) mailing list, not remove all alias domain addresses from internal members.

    • Renaming mailing list doesn't remove old mail address from member account.

    • Not strip leading and ending spaces in search string.

    • Cannot disable imap service per user.

    • Not correctly set spam policy to deliver detected spam/virus/badheader/banned mail to mailbox while quarantining is disabled.

    • Not delete all emails of selected quarantined type (e.g. spam, virus). It deleted all emails no matter which quarantined type you are viewing.

    • Update library used to delete LDAP tree. This causes iRedAdmin cannot be started on Ubuntu 18.04 with python-ldap-3.0.

    • Not handle service name 'pop3tls' and 'imaptls' for Dovecot-2.3.

    • Not use AMAVISD_QUARANTINE_HOST as mlmmj relay host if a remote Amavisd server is used.

    • tools/notify_quarantined_recipients.py:

      • Cannot generate email message if quarantined mail subject contains non-ascii characters.

      • Not correctly handle mail subject in some case.

    Translations
    • New: Danish (da_DK). Thanks Søren Mortensen <sm _at_ upnavigator.dk>.

    • Updated: German (de_DE). Thanks lug-gh on github.


    0 0

    ZhangHuangbin wrote:

    Apache is listening on port 80/443, but Nginx is trying to bind to same ports. This is the cause.
    It's recommended to use a fresh new server OS for iRedMail installation.

    OK thanks.  I guessed it might be that.  I decided the install script starts by using dpkg or apt to install packages, so it should be safe to simply re-run `bash iRedMail.sh` rather than uninstalling the 204 packages...

    I stopped apache and re-ran the script.  It seems to have completed, but

    • gave a series of error messages:  ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2 "No such file or directory")

    • subsequently, nginx fails to run: nginx: [emerg] could not build map_hash, you should increase map_hash_bucket_size: 32 \ nginx: configuration file /etc/nginx/nginx.conf test failed .

    I tried swapping the file nginx.conf.2018.12.16.19.58.36 into nginx.conf, but now get a new error xwhen I start nginx: 'nginx: [emerg] no port in upstream "php_workers" in /etc/nginx/templates/fastcgi_php.tmpl:13'

    I have now removed the apache2 installation, and am wondering whether it is safe to try re-running the iRedMail.sh install script.  I suppose it cannot do any harm...


    0 0

    Dear all,

    iRedAdmin-Pro-SQL-3.0 (iRedAdmin-Pro for MySQL, MariaDB and PostgreSQL backends) is now available for upgrading and purchasing.

    How to download the latest iRedAdmin-Pro

    iRedAdmin-Pro customers can get download link of this new release by following steps below:

    • Login to iRedAdmin-Pro as global admin

    • Click "License" on the top-right corner, it will show you basic license info and a "Download" button if new version is available for upgrading.

    If above steps don't work for you, please send an email to support @ iredmail.org to get download link of the latest release.

    Below are detailed changes since iRedAdmin-Pro-SQL-2.9.0:

    RESTful API

    API Document: https://docs.iredmail.org/iredadmin-pro … l.api.html

    • Able to add subscribers while creating (subscribeable) mailing list.

    • Able to add/remove subscribers while updating (subscribeable) mailing list.

    • Able to get all subscribers of given mailing list with optional parameter `with_subscribers=yes`:

      • URI: `GET /api/ml/<mail>?with_subscribers=yes`

    • Able to list all mailing lists in given domain:

      • URI: `GET /api/mls/<domain>`

      • Optional parameters: `email_only=yes`. if present, return a list of mailing list email addresses. Otherwise return a list of mailing list profiles.

    • Able to set mailbox format, mailbox folder name, full maildir path while creating/updating user:

      • URIS:

        • `POST /api/user/<mail>`

        • `PUT  /api/user/<mail>`

      • Parameters: `mailboxFormat`, `mailboxFolder`, `maildir`.

    • Show mailbox size and number of stored messages while getting user profile:

      • URI: GET /api/user/<mail>

      • New parameter names: stored_bytes, stored_messages.

    • Show assigned mail alias groups and mailing lists while getting user profile:

      • URI: GET /api/user/<mail>

      • New parameter names: mailing_aliases, mailing_lists.

    • Able to reset user password by submitting a password hash (`PUT /api/user/<mail>`, parameter `password_hash`).

    • Fixed issues:

      • Cannot verify password: `POST /api/verify_password/user/<mail>`.

      • Not correctly set date to deleted mailboxes while deleting a domain (`DELETE /api/domain/<domain>/keep_mailbox_days/<number>`). Thanks Wes Cossick <wes _at_ hoa-express.com> for the report.

    Improvements
    • Able to export statistics of admins.

    • If new password doesn't match policies, display error messages of all unmatched policies.

    • Spam policy: able to set score for blocking/quarantining detected spam.

    • On search result page, now able to set days to keep mailbox of removed domain and user accounts.

    • Able to define days to keep removed mailbox for normal domain admin and global admin. With default settings, normal admin can keep mailbox for 1 day, 1/2/3 weeks, 1/2/3/6/12 months. Global admin can keep mailbox for 1 day, 1/2/3 weeks, 1/2/3/6/12 months, 2/3 years, and 'forever'.

    • Display user password last change date on user list page and user profile page.

    • Able to set mailbox format while creating new user.

    • New: tools/dump_quarantined_mails.py, used to dump quarantined emails to the directory given on command line. It's useful if you want to train SpamAssassin by calling `sa-learn`.

    Fixed issues
    • While deleting a domain, it removes all forwarding destinations addresses under this domain, but it should be kept for those forwarding source addresses which don't belong to removed domain.

    • When login as normal admin, it lists global admins in the per-domain admin list page.

    • Normal domain admin should not be able to update max user quota.

    • Cannot correctly sort domain names on domain list page.

    • Cannot unassign user from external mail aliases on user profile page.

    • Cannot filter admin log.

    • Cannot set throttle setting to inherit from lower priority account.

    • Not strip leading and ending spaces in search string.

    • Incorrectly delete assigned external mail alias groups while updating mail user profile.

    • Cannot disable imap service per user.

    • Not correctly set spam policy to deliver detected spam/virus/badheader/banned mail to mailbox while quarantining is disabled.

    • Not delete all emails of selected quarantined type (e.g. spam, virus). It deleted all emails no matter which quarantined type you are viewing.

    • Not handle service name 'pop3tls' and 'imaptls' for Dovecot-2.3.

    • Not use AMAVISD_QUARANTINE_HOST as mlmmj relay host if a remote Amavisd server is used.

    • tools/notify_quarantined_recipients.py:

      • Cannot generate email message if quarantined mail subject contains non-ascii characters.

      • Not correctly handle mail subject in some case.

    Updated translations
    • German (de_DE). Thanks Peter <info _at_ nuw.biz>.

    • Italian (it_IT). Thanks Francesco <frankonet _at_ infinito.it>.


    0 0

    I suggest rebuild a fresh new server OS for installation, you will realize how easy it is. smile


    0 0

    ==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
    - iRedMail version (check /etc/iredmail-release): v0.9.8
    - Deployed with iRedMail Easy or the downloadable installer?
    - Linux/BSD distribution name and version:
    - 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 configured DNSlike:
    server on which iredmail is running: mail2.example.com
    First virtudal domain: demo.example.dom

    dns setup:

        hostname                                         Type                       Value
    
    mail2.example.com                               TXT      v=spf1 mx mx:mail2.example.com -all
    dkim._domainkey.demo.example.com    TXT     "v=DKIM1; p=(BLABLA......)"
    example.com                                         MX       IP address of mail2.example.com

    the problem i am facing is emails from my mail server are always marked as spam by gmail even though i have specified DKIM and SPF records, how can i resolve this?


    0 0

    Dear ZhangHuangbin,

    As per your advice, we would like to buy the license for the other servers and retain the original because we don't like to disturb our setup at-least for now.
    Kindly advice how to get the invoice that include license for 2-4 servers (i saw the discount option) for one year.
    Also we would like to register a new contact email for the new license as ictsupport(at)gov.go.tz


    0 0

    @zhangHuagbin  thanks.

    I would like to share a small script which I've found from ired doc china.

    #!/bin/bash
    for vService in mysql nginx postfix dovecot iredapd \
                    amavis clamav-daemon clamav-freshclam
    do
        service $vService status || service $vService start
    done

    if want to just restart regardless the status of services


    #!/bin/bash
    for vService in mysql nginx postfix dovecot iredapd \
                    amavis clamav-daemon clamav-freshclam
    do
        service $vService restart
    done

    Regards


    0 0

    I regenerated a new key using

    amavisd-new genrsa /var/lib/dkim/mydomain.pem 1024

    chown amavis.amavis /var/lib/dkim/mydomain.com.pem
    chmod 0400 /var/lib/dkim/mydomain.com.pem

    amavisd-new testkeys

    TESTING#1 mydomain: dkim._domainkey.mydomain.com => invalid (public key: DNS error: SERVFAIL)

    keep getting above message I dont know what is wrong. One more thing I've have not update the key on my dns provider server. Do I need to update it first there and then test keys?

    Regards


older | 1 | .... | 1367 | 1368 | (Page 1369) | 1370 | 1371 | .... | 1394 | newer