similar to: allow_nets

Dear list, I am having a problem with openvpn. I have the following arrangement, running two instances of openvpn on "home fw". I want to protect my WLAN in back of the home fw and that works fine. I can see "Peer connection initiated with 192.168.1.3:5000" in daemon.log on homefw. Nothing gets initiated with officefw, nor can I ping the other end of the tunnel at officefw.

Hello, I'am trying to efi-netboot a HP ProLiant DL120 Gen9[1], that has multiple NICs, one embedded 2-port and an extra 4-port, so I got to the HP/EFI/multinic problem. I read through the multinic mailthreads and using current master[2], it booted successfully to syslinux but then another problem manifested: Syslinux for some reason asks the gateway and not next-server about ldlinux.e64 (I

I am trying to get Samba 3.4.0 (on an Ubuntu 9.10 box) set up as a file server for my home. The router is 10.1.10.1; the Ubuntu box ("chronicles") is 10.1.10.2; the OS X box I'm using for testing purposes ("job") is 10.1.10.3. From job, I can see ports 139 and 445 on chronicles are open. Neither box has 'chronicles' or 'job' listed in its /etc/hosts file.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I use the allow_nets password extra field [0] for my users. Is there a way to use this functionality for ALL users, and not to edit my passwd-file every time a new user is added ? The alternative i am working for this is the TCP Wrappers. [0]: http://wiki.dovecot.org/PasswordDatabase/ExtraFields/AllowNets -----BEGIN PGP SIGNATURE----- Version: GnuPG

Hi, I'm wanting to implement allow_nets so that some users can be limited to only use webmail while others can use client or webmail access. Adding the sql to pull a list of IPs/ranges for webmail only users was easy enough. For the users that are allowed to access from anywhere, do I need to specify 0.0.0.0/0 or something or can I just let the sql query return a blank field? Thanks Guy --

Hello! I'm trying to restrict imap logins to our internal network for several users, but this breaks dovecot delivery too Even if i set allow_nets to NULL or 0.0.0.0/0 deliver exits with "Error: Auth lookup returned failure" i'm running it as 'command = /usr/lib/dovecot/deliver -e -d "$local_part@$domain" -s' in exim.conf i guess delivery lookups should

Hello, i am running dovevot 2.0.5 using ldap authentication with the allow_nets paramter to limit access to some local networks. The problem is, when i want to use the local lmtp socket from postfix *virtual_transport = lmtp:unix:private/dovecot-lmtp * i get the follwing error: *Oct 21 15:48:03 auth: Info: passdb(username): allow_nets check failed: Remote IP not known *When using the TCP

Hello, I'm playing with allow_nets function. It is really cool! In a filebased passwd backend you simply add "allow_nets=192.0.2.143/32" as mentioned in http://wiki2.dovecot.org/PasswordDatabase/ExtraFields/AllowNets But if I use an LDAP backend it looks different. Following http://wiki2.dovecot.org/AuthDatabase/LDAP/AuthBinds and

This was brought up in 2014, and left without conclusion, so I thought it would be time to bump it :) I would love a way to do allow_nets based on an RBL check, could this be added to the feature-list? https://wiki2.dovecot.org/PasswordDatabase/ExtraFields/AllowNets Thanks -- Tom

On 29 Apr 2019, at 19:56, Zhang Huangbin via dovecot <dovecot at dovecot.org> wrote: > Recently we need to allow some users to login from everywhere except some IP/networks, Can you use firewall rules for this? > how can we accomplish this with "allow_nets"? Allow_nets specifies allowed networks. Doesn't say anything else about any other use. "The allow_nets

Hello, Zhang. You can easily do this without a new feature in Dovecot. - Create a post login script, for instance, in bash. - install grepcidr on your server. Your post login script can use grepcidr to check for white or black list. https://wiki.dovecot.org/PostLoginScripting I have implemented this myself on a small open source project, I can send you the links of you want. Andr?. Tue Apr

On 4/29/2019 11:20 PM, Zhang Huangbin via dovecot wrote: > I understand what "allow" means. But it will be very handy to > support something like "!a.b.c.d" to allow all but just exclude few > IPs/networks. Isn't it? :) I'm not sure why: iptables -A INPUT -p tcp --match multiport --syn ! -s a.b.c.d/netmask \ --dports 110,143,993,995 -j REJECT doesn't do

> On 30 Apr 2019, at 4.56, Zhang Huangbin via dovecot <dovecot at dovecot.org> wrote: > > Dear all, > > We use `allow_nets`[1] to restrict login clients, it works fine. > Recently we need to allow some users to login from everywhere except some IP/networks, how can we accomplish this with "allow_nets"? > > Tried allow_nets="!a.b.c.d", but

Hi, I have the following configuration in my dovecot.conf for Dovecot 2.2.21: passdb { driver = ldap args = /etc/dovecot/dovecot-ldap.conf.ext default_fields = allow_nets=local,127.0.0.1,10.255.1.0/24 } This triggers "auth: Panic" on POP3/IMAP logins as the below: Dec 22 14:57:39 localhost dovecot: auth: ldap(u0000,::1,<oiF8SHYngqsAAAAAAAAAAAAAAAAAAAAB>): allow_nets:

I use Dovecot for SASL authentication from Postfix. In Postfix main.cf I have: smtpd_sasl_type = dovecot It works good, but now I need to allow users to connect by IMAP only from given IP adresses. I've added extra field allow_nets to passdb in Dovecot, and IMAP authentication works fine. But now I can't connect to my SMTP server because when smtpd ask dovecot about user

Hi. I want to use allow_nets in my configuration, but i have some troubles which i cant resolve. To use allow_nets i creates `allow_nets` text field in my mysql users table. My query is: from: dovecot/sql.conf: password_query = SELECT crypt as password, maildir as userdb_mail, 6 AS userdb_uid,6 AS userdb_gid, allow_nets FROM users WHERE id = '%u' from dovecot.conf: auth default {

> On Apr 30, 2019, at 11:21 AM, @lbutlr via dovecot <dovecot at dovecot.org> wrote: > > On 29 Apr 2019, at 19:56, Zhang Huangbin via dovecot <dovecot at dovecot.org> wrote: >> Recently we need to allow some users to login from everywhere except some IP/networks, > > Can you use firewall rules for this? I suppose not. We don't restrict ALL users this way,

Hi, When using dovecot for authentication of an SASL (postfix) request, i cannot use the allow_nets parameter. The IP-address of the requester is not known in dovecot. I would like to allow sasl for certain users, others are not allowed to access via SASL. Some users can have access to imap and pop3 from certain IP-addresses. How could i combine this in then dovecot configuration? -- Best

Hi, I'm using dovecot on debian etch: ||/ Name Version ii dovecot-common 1.0.rc15-2etch1 ii dovecot-imapd 1.0.rc15-2etch1 ii dovecot-pop3d 1.0.rc15-2etch1 # dovecot --version 1.0.rc15 Now here is my question. Some of the mail users may only login from the LAN, while others can login from the LAN and the internet. I've read about

Hello all, I am testing my dovecot installation in order to restrict access via POP3 for IPs outside my network. I have read and understood the instructions in the wiki and I have reached a configuration that works ONLY when single IPs are listed in allow_nets but not when ranges in the notation x.x.x.x/y are listed. Some examples should be more explanatory. I am using 1.0.rc15 patched as