Problem with users self-service password change

December 11, 2018, 11:04 pm

≫ Next: Re: Adding account dificult on iPad

≪ Previous: Re: Connection to IMAP server failed.

$

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): well, still Apache
- Manage mail accounts with iRedAdmin-Pro? yes
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

Hello,

users can't change their password anymore. Clicking on change password in iRedAdmin-Pro's self-service leads to an internal server error. No idea since when or why ... only apaches error.log shows something like this:

...[wsgi:error]... [remote x.x.x.x:50520] Traceback (most recent call last):
...[wsgi:error]... [remote x.x.x.x:50520]   File "/usr/lib/python2.7/dist-packages/web/application.py", line 239, in process
...[wsgi:error]... [remote x.x.x.x:50520]     return self.handle()
...[wsgi:error]... [remote x.x.x.x:50520]   File "/usr/lib/python2.7/dist-packages/web/application.py", line 230, in handle
...[wsgi:error]... [remote x.x.x.x:50520]     return self._delegate(fn, self.fvars, args)
...[wsgi:error]... [remote x.x.x.x:50520]   File "/usr/lib/python2.7/dist-packages/web/application.py", line 462, in _delegate
...[wsgi:error]... [remote x.x.x.x:50520]     return handle_class(cls)
...[wsgi:error]... [remote x.x.x.x:50520]   File "/usr/lib/python2.7/dist-packages/web/application.py", line 438, in handle_class
...[wsgi:error]... [remote x.x.x.x:50520]     return tocall(*args)
...[wsgi:error]... [remote x.x.x.x:50520]   File "/opt/www/iredadmin/controllers/decorators.py", line 120, in decorated
...[wsgi:error]... [remote x.x.x.x:50520]     return f(*args, **kw)
...[wsgi:error]... [remote x.x.x.x:50520]   File "/opt/www/iredadmin/controllers/decorators.py", line 100, in proxyfunc
...[wsgi:error]... [remote x.x.x.x:50520]     return func(self, *args, **kw)
...[wsgi:error]... [remote x.x.x.x:50520]   File "/opt/www/iredadmin/controllers/ldap/user.py", line 676, in POST
...[wsgi:error]... [remote x.x.x.x:50520]     conn=None)
...[wsgi:error]... [remote x.x.x.x:50520] TypeError: proxyfunc() takes at least 1 argument (0 given)

Any ideas - besides it is my own fault, still using apache?

Thanks

---

Re: Adding account dificult on iPad

December 12, 2018, 2:32 am

≫ Next: Re: Filter specific inbound mail by admin

≪ Previous: Problem with users self-service password change

$

0

0

ZhangHuangbin wrote:

Thomas B wrote:

Dec 11 09:40:15 sogod [1713]: [ERROR] <0x0x561cfa6b5ca0[WOWatchDog]> No child available to handle incoming request!

Update /etc/default/sogo, increase the prefork child processes, restart sogo service. That's it.

Thanks a lot ! I've changed the prefork to 80 and everything is now very quick.

You were very helpfull, so I hope you will enjoy the cup of coffee I sent to you ...

Re: Filter specific inbound mail by admin

December 12, 2018, 7:37 am

≫ Next: Re: White List of senders or domains

≪ Previous: Re: Adding account dificult on iPad

$

0

0

gabriel79 wrote:

Hello,
Go to /opt/iRedAPD-x.x/tools
(x.x is the greatest version that is installed)

run command: python greylisting_admin.py --list
to see domains that are filtered

run command: python greylisting_admin.py --from name@domain.xxx --enable
to enable the reject of name@domain.xxx

run command: python greylisting_admin.py --from name@domain.xxx --disable
to accept emails from name@domain.xxx without being filtered by the server

if you are using @domain.xxx all the emails from the domain.xxx will be accepted or rejected

Oh I see that tutorial, thanks for your help

Re: White List of senders or domains

December 12, 2018, 7:48 am

≫ Next: Re: tld based greylisting time ?

≪ Previous: Re: Filter specific inbound mail by admin

$

0

0

I think you've used the wrong file or syntax.

I would try moving your entries to "/etc/postfix/helo_whitelist", execute "postmap /etc/postfix/helo_whitelist" and check if "/etc/postfix/main.cf" contains under section "smtpd_helo_restrictions ="
   check_client_access hash:/etc/postfix/helo_whitelist

Re: tld based greylisting time ?

December 12, 2018, 8:04 am

≫ Next: SMTP settings for Discourse

≪ Previous: Re: White List of senders or domains

$

0

0

As intended before I've now extended the code to greylist certain top-level domains for a longer time, and have it running for a couple of days under Linux with success.
Following I share my approach with you, and would be thankful for any comments or useful changes:

1. create another table in (Maria)DB e.g. with:

CREATE TABLE iredapd.greylisting_ext (id BIGINT UNSIGNED AUTO_INCREMENT PRIMARY KEY, tld VARCHAR(64) );

2. add one or more tlds with:

INSERT INTO iredapd.greylisting_ext SET tld='loan';

    see also most used tlds by spammers: https://www.spamhaus.org/statistics/tlds/

3. add variables to /opt/iredapd/settings.py:

    # settings for extended greylisting for certain tlds
    # allow after 1 day (1440min), forget without retrying after 2 days
    GREYLISTING_BLOCK_EXPIRE_EXT = 1440
    GREYLISTING_UNAUTH_TRIPLET_EXPIRE_EXT = 2

4. change some code in /opt/iredapd/plugins/greylisting.py:

--- greylisting.py      2018-02-07 03:16:56.000000000 +0100
+++ greylisting.py.ext  2018-12-01 11:14:46.974074092 +0100
@@ -178,12 +178,30 @@
                                       recipient,
                                       recipient_domain,
                                       client_address):
+
+    # check if extented greylisting should be applied
+    sender_tld_domain = sender_domain.split('.')[-1]
+    sql = """SELECT id
+              FROM greylisting_ext
+              WHERE tld='%s'
+              LIMIT 1""" % (sender_tld_domain)
+    logger.debug('[SQL] query tlds: \n%s' % sql)
+    qr = conn.execute(sql)
+    sql_record = qr.fetchone()
+
     # Time of now.
     now = int(time.time())

-    # timeout in seconds
-    block_expired = now + int(settings.GREYLISTING_BLOCK_EXPIRE) * 60
-    unauth_triplet_expire = now + int(settings.GREYLISTING_UNAUTH_TRIPLET_EXPIRE) * 24 * 60 * 60
+    if sql_record:
+        logger.debug('Client tld (%s) will be greylisted extra long.')
+        # timeout in seconds
+        block_expired = now + int(settings.GREYLISTING_BLOCK_EXPIRE_EXT) * 60
+        unauth_triplet_expire = now + int(settings.GREYLISTING_UNAUTH_TRIPLET_EXPIRE_EXT) * 24 * 60 * 60
+    else:
+        # timeout in seconds
+        block_expired = now + int(settings.GREYLISTING_BLOCK_EXPIRE) * 60
+        unauth_triplet_expire = now + int(settings.GREYLISTING_UNAUTH_TRIPLET_EXPIRE) * 24 * 60 * 60
+
     auth_triplet_expire = now + int(settings.GREYLISTING_AUTH_TRIPLET_EXPIRE) * 24 * 60 * 60

     sender = sqlquote(sender)

5. restart iredappd deamon:

systemctl restart iredapd

For my personal usage I've increased the values of GREYLISTING_BLOCK_EXPIRE_EXT and GREYLISTING_UNAUTH_TRIPLET_EXPIRE_EXT

Have Fun

SMTP settings for Discourse

December 12, 2018, 1:18 pm

≫ Next: Autodiscover not working

≪ Previous: Re: tld based greylisting time ?

$

0

0

What would the smtp settings for Discourse? I have tried with many settings but none works.

smtp.example.com
postmaster@in.example.com
password

smtp start TLS should be True or False?

How do i decide Which is going to be my smtp address, User ID and User password?

I have used my subdomain for my iredmail server, so what should be my DNS settings in cloudflare DNS?

Autodiscover not working

December 13, 2018, 1:57 am

≫ Next: Re: Connection to IMAP server failed.

≪ Previous: SMTP settings for Discourse

$

0

0

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): v0.9.8
- Linux/BSD distribution name and version: centos 7.4
- 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.
====

Hello,
Based on these logs:
2018/12/13 11:01:59 [error] 62821#0: *188 open() "/var/www/html/autodiscover/autodiscover.json" failed (2: No such file or directory), client: 5.2.130.224, server: _, request: "GET /autodiscover/autodiscover.json?Email=postmaster%40appclouds.eu&Protocol=ActiveSync&RedirectCount=1 HTTP/1.1", host: "autodiscover.appclouds.eu"
2018/12/13 11:02:08 [error] 62821#0: *190 open() "/var/www/html/Autodiscover/Autodiscover.xml" failed (2: No such file or directory), client: 5.2.130.224, server: _, request: "POST /Autodiscover/Autodiscover.xml HTTP/1.1", host: "autodiscover.appclouds.eu"
2018/12/13 11:02:08 [error] 62821#0: *191 open() "/var/www/html/Autodiscover/Autodiscover.xml" failed (2: No such file or directory), client: 5.2.130.224, server: _, request: "POST /Autodiscover/Autodiscover.xml HTTP/1.1", host: "autodiscover.appclouds.eu"

I can't figure out how to setup autodiscover for this domain. None of my domain has working autodiscover.
Any idea?

Re: Connection to IMAP server failed.

December 13, 2018, 2:08 am

≫ Next: My License marked as expired while expire year is 2099

≪ Previous: Autodiscover not working

$

0

0

Can anyone help me with the above? I finished all the setup. But not able to login now.

Thanks
Arun

---

My License marked as expired while expire year is 2099

December 13, 2018, 7:14 am

≫ Next: Re: My License marked as expired while expire year is 2099

≪ Previous: Re: Connection to IMAP server failed.

$

0

0

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

Hello,
We are having our iRedAdmin-Pro bought since 2013 as lifetime licence but recently it has been marked as expired.
More details as seen in the panel.

License status Expired
Product nameiRedAdmin-Pro-LDAP
Purchase dateAug 10, 2013
Expire date Dec 31, 2099
Contacts  [...hidden...]
Latest version3.1 (You are running version 2.5.0)

Our version is older than the current one and now we can't even get the link option to request new version for upgrade.

Kindly assist what is the issue.

Regard,

Re: My License marked as expired while expire year is 2099

December 13, 2018, 7:27 am

≫ Next: Re: Connection to IMAP server failed.

≪ Previous: My License marked as expired while expire year is 2099

$

0

0

Dear Kambey,

Your license is running on multiple servers, this violates our license terms (one license can be ran on only one server at the same time).

Please contact us if there's some mistake on our side: https://www.iredmail.org/contact.html

Re: Connection to IMAP server failed.

December 13, 2018, 7:29 am

≫ Next: Re: autodiscover for activesync

≪ Previous: Re: My License marked as expired while expire year is 2099

$

0

0

Check file /opt/www/roundcubemail/config/config.inc.php, use 127.0.0.1 as your IMAP server address, like this:

$config['default_host'] = '127.0.0.1';

Re: autodiscover for activesync

December 13, 2018, 11:24 am

≫ Next: Re: autodiscover for activesync

≪ Previous: Re: Connection to IMAP server failed.

$

0

0

bayardis wrote:

Hmm ok. Do you know if anyone has used z-push and sogo together? Sogo's documentation seems to imply I need to use ocsmanager but from what I see Iredadmin didn't use openxchange with sogo so I'm a little confused how the Activesync is working

I've managed to make Autodiscover work with z-push with the following configuration: Centos7, iRedMail-0.9.8, SOGo nightly build. Install and configure iRedMail first and setup SSL certificate.

Get latest tarball release of z-push (I used 2.3.9) and put the files in the usual location /usr/share/z-push.
Create log folder /var/log/z-push.
Configure z-push: in the main configuration file /usr/share/z-push/config.php set define('BACKEND_PROVIDER', 'BackendIMAP');
In autodiscover/config.php - define('ZPUSH_HOST', 'mailhost.yourdomain.com');
Create /etc/nginx/templates/autodiscover.tmpl with:
include         fastcgi_params;
fastcgi_index   index.php;
fastcgi_param   SCRIPT_FILENAME $document_root$fastcgi_script_name;
fastcgi_param   REQUEST_URI $1;
fastcgi_param   PHP_FLAG "magic_quotes_gpc=off \n register_globals=off \n magic_quotes_runtime=off \n short_open_tag=on";
fastcgi_param   PHP_VALUE "post_max_size=20M \n upload_max_filesize=20M \n max_execution_time=3660";
fastcgi_param   HTTP_PROXY ""; # Mitigate https://httpoxy.org/ vulnerabilities
fastcgi_read_timeout 3660; # Z-Push Ping might run 3600s, but to be safe

location ~* /AutoDiscover/AutoDiscover.xml {
    alias       /usr/share/z-push/autodiscover/autodiscover.php;

    access_log  /var/log/nginx/z-push-autodiscover-access.log;
    error_log   /var/log/nginx/z-push-autodiscover-error.log;

    fastcgi_pass    unix:/var/run/php-fpm.socket;

    fastcgi_index   autodiscover.php;
}
Edit /etc/nginx/sites-enabled/00-default-ssl.conf adding a line:
include /etc/nginx/templates/autodiscover.tmpl;
Don't forget the autodiscover DNS record and you should be all set.

Re: autodiscover for activesync

December 13, 2018, 12:39 pm

≫ Next: Re: Emails recieved and shown as delivered in log but not on server

≪ Previous: Re: autodiscover for activesync

$

0

0

radonm wrote:

bayardis wrote:

Hmm ok. Do you know if anyone has used z-push and sogo together? Sogo's documentation seems to imply I need to use ocsmanager but from what I see Iredadmin didn't use openxchange with sogo so I'm a little confused how the Activesync is working

I've managed to make Autodiscover work with z-push with the following configuration: Centos7, iRedMail-0.9.8, SOGo nightly build. Install and configure iRedMail first and setup SSL certificate.

Get latest tarball release of z-push (I used 2.3.9) and put the files in the usual location /usr/share/z-push.
Create log folder /var/log/z-push.
Configure z-push: in the main configuration file /usr/share/z-push/config.php set define('BACKEND_PROVIDER', 'BackendIMAP');
In autodiscover/config.php - define('ZPUSH_HOST', 'mailhost.yourdomain.com');
Create /etc/nginx/templates/autodiscover.tmpl with:
include         fastcgi_params;
fastcgi_index   index.php;
fastcgi_param   SCRIPT_FILENAME $document_root$fastcgi_script_name;
fastcgi_param   REQUEST_URI $1;
fastcgi_param   PHP_FLAG "magic_quotes_gpc=off \n register_globals=off \n magic_quotes_runtime=off \n short_open_tag=on";
fastcgi_param   PHP_VALUE "post_max_size=20M \n upload_max_filesize=20M \n max_execution_time=3660";
fastcgi_param   HTTP_PROXY ""; # Mitigate https://httpoxy.org/ vulnerabilities
fastcgi_read_timeout 3660; # Z-Push Ping might run 3600s, but to be safe

location ~* /AutoDiscover/AutoDiscover.xml {
    alias       /usr/share/z-push/autodiscover/autodiscover.php;

    access_log  /var/log/nginx/z-push-autodiscover-access.log;
    error_log   /var/log/nginx/z-push-autodiscover-error.log;

    fastcgi_pass    unix:/var/run/php-fpm.socket;

    fastcgi_index   autodiscover.php;
}
Edit /etc/nginx/sites-enabled/00-default-ssl.conf adding a line:
include /etc/nginx/templates/autodiscover.tmpl;
Don't forget the autodiscover DNS record and you should be all set.

Thanks for that info. If I go back to iredadmin I will try it but I switched to mailcow now for evaluation and so far unlikely to go back.

Re: Emails recieved and shown as delivered in log but not on server

December 13, 2018, 1:14 pm

≫ Next: Re: Emails recieved and shown as delivered in log but not on server

≪ Previous: Re: autodiscover for activesync

$

0

0

I'm going to build a new server from ground up and start over. how do i import the emails from the old server over to the new one when its ready?

Re: Emails recieved and shown as delivered in log but not on server

December 13, 2018, 4:54 pm

≫ Next: Re: autodiscover for activesync

≪ Previous: Re: Emails recieved and shown as delivered in log but not on server

$

0

0

justinr wrote:

I'm going to build a new server from ground up and start over. how do i import the emails from the old server over to the new one when its ready?

With same iRedMail-0.9.8 version, you can simply export/import SQL databases, then copy mailboxes with "rsync" to same directory.

justinr wrote:

I'm going to build a new server from ground up and start over. how do i import the emails from the old server over to the new one when its ready?

Have to dive into Postfix+Dovecot log files to figure it out.

---

Re: autodiscover for activesync

December 13, 2018, 4:56 pm

≫ Next: Re: Autodiscover not working

≪ Previous: Re: Emails recieved and shown as delivered in log but not on server

$

0

0

radonm wrote:

I've managed to make Autodiscover work with z-push with the following configuration:

Thanks for sharing.

Re: Autodiscover not working

December 13, 2018, 4:59 pm

≫ Next: Re: SMTP settings for Discourse

≪ Previous: Re: autodiscover for activesync

$

0

0

iRedMail doesn't support autodiscover by default.

Maybe you can try this:
https://forum.iredmail.org/post66700.html#p66700

Re: SMTP settings for Discourse

December 13, 2018, 4:59 pm

≫ Next: Re: SMTP settings for Discourse

≪ Previous: Re: Autodiscover not working

$

0

0

FYI:

- MUA settings: https://docs.iredmail.org/#mua
- DNS: https://docs.iredmail.org/setup.dns.html

Re: SMTP settings for Discourse

December 13, 2018, 5:03 pm

≫ Next: Re: tld based greylisting time ?

≪ Previous: Re: SMTP settings for Discourse

$

0

0

ZhangHuangbin wrote:

FYI:

- MUA settings: https://docs.iredmail.org/#mua
- DNS: https://docs.iredmail.org/setup.dns.html

I tried all, but this documentation does not say anything about SMTP settings like smtp@example.com, email ID and password. Nothing is working. But my usual iredmail is working fine.

Re: tld based greylisting time ?

December 13, 2018, 5:04 pm

≫ Next: Re: White List of senders or domains

≪ Previous: Re: SMTP settings for Discourse

$

0

0

Did you every try this without modifying iredapd source code?

cd /opt/iredapd/tools/
python greylisting_admin.py --enable --from '@.loan'