1 Topic by moreni

  • moreni
  • Member
  • Offline
  • Registered: 2011-08-19
  • Posts: 40

Topic: User Control IMAP external

==== Required information ====
- iRedMail version: 1.8.0
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):
- Linux/BSD distribution name and version:
- Related log if you're reporting an issue:
====

LDAP-PRO
Centos 6.0

Hello.
It is possible to create an enabling User Control who can or can not connect to IMAP?

I would use this to limit connections to external users.

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,090

Re: User Control IMAP external

You can manage per-user service control in user profile page, under tab "Advanced". Screenshot for your reference:

http://iredmail.org/images/iredadmin/user_profile_advanced.png

3 Reply by moreni

  • moreni
  • Member
  • Offline
  • Registered: 2011-08-19
  • Posts: 40

Re: User Control IMAP external

Hello,

I not only found to block external.
Ex: User test @ example can connect internal and external
user @ example teste001 concetar can only internal (192.168.xx)

IMAP and SMTP

4 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,090

Re: User Control IMAP external

For per-user restriction in your case, you can try to restrict it with Dovecot post login script.

- For Dovecot-1.x: http://wiki.dovecot.org/PostLoginScripting
- For Dovecot-2.x: http://wiki2.dovecot.org/PostLoginScripting

If you just want to restrict all users, how about add rules in firewall?

5 Reply by moreni

  • moreni
  • Member
  • Offline
  • Registered: 2011-08-19
  • Posts: 40

Re: User Control IMAP external

Hi

Thanks for the tip.

Got what I wanted!


dovecot.conf

}
service imap-postlogin {
  # all post-login scripts are executed via script-login binary
    executable = script-login /usr/local/bin/postlogin.sh
  #
  #     # the script process runs as the user specified here (v2.0.14+):
    user = $default_internal_user
  #         # this UNIX socket listener must use the same name as given to imap executable
    unix_listener imap-postlogin {
    }
}