search for: lukashaase

Hi, I have the following problem: My structure is stored in LDAP that way: dc=example,dc=com + ou=groups | + cn=Account Operators | + ... + ou=machines | + uid=workstation1$ | + uid=workstation2$ | + ... + ou=users + ou=int | + uid=user1 | + uid=user2 | + ... + ou=ext + uid=user3 + uid=user4 + ... ... Only internal

Hi, Simple Scenario: Shared namespace and a specific UNIX group should have access to it. System is Debian lenny (stable). # cat /etc/dovecot/dovecot.conf [...] namespace public { separator = . prefix = Shared. location = maildir:/var/mail/shared } mail_executable = /usr/local/sbin/dovecot-imap-fix.sh mail_drop_priv_before_exec = no #just to make sure [...] # dpkg -l | grep dovecot ii

Hi, I successfully configured dovecot using virtual users (and LDAP/AD). deliver is the LDA and verifies if the user exists (as recommended in the WIKI). However, the howtos in the Wiki say *nothing* about the case that the recipients should be verified *before* receiving the messages (prevent backscatter, ...). All configurations in the dovecot-Wiki (postfix and exim) just accept the mails

Hi, I always had problems that my Smart-UPS 1500 had "hickups" with nut: Connection would get lost, just to get restored seconds later again. This resulted in annoying log entried and console messages but wasn't too critical. For a few days, nut doesn't detect my UPS at all any more. I get the console messages: Broadcast message from nut at server (somewhere) (Tue Oct 29

Hi, I always had problems that my Smart-UPS 1500 had "hickups" with nut: Connection would get lost, just to get restored seconds later again. This resulted in annoying log entried and console messages but wasn't too critical. For a few days, nut doesn't detect my UPS at all any more. I get the console messages: Broadcast message from nut at server (somewhere) (Tue Oct 29

Hi, I have activated only imaps and managesieve. As sieve is running on a different port/protocol: Can I make sure that sieve can ONLY be used with SSL/TLS? As the credentials are transmitted I only offer services with SSL (IMAPS, SMTP over SSL, ...). For sieve I am not sure about this. If there is the possibility that user's credentials are transmitted in plain text I would block the

Hi, I have a problem when migrating from dovecot 1.0 to dovecot 1.2 (Debian lenny to Debian squeeze). In my dovecot-ldap.conf I have: user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid,uid=system_groups_user I use the last parameter for the groups which I need for shared folders. If I only use this, everything works. However, I also use LDAP as passdb with prefetch: pass_attrs =

Hi, In Debian lenny I used the following in upsd.conf: ACL all 0.0.0.0/0 ACL localhost 127.0.0.1/32 ACL webinterface 192.168.0.2/32 ACL slave 192.168.50.22/32 ACCEPT localhost ACCEPT webinterface ACCEPT slave REJECT all and in upsd.users: [monmaster] password = secret0 allowfrom = localhost upsmon master [monslave] password = secret1 allowfrom =

Hi, On the local machine I have running samba (3.5.6) as PDC for Windows XP using the LDAP backend. This works great; however, for one service running on the *same* machine I need ntlm_auth for SSO and therefore winbind. I do *not* need winbind for NSS etc. since all users are resolved by plain LDAP anyway. ONLY to get ntlm_auth working! I just installed winbind and it works - more or less.

Hi, After using dovecot for several years now, today happend something which makes me really feel unconfortable: An email received was just not delivered properly, or, is lost! The mail (from an external server) was sent to two local mailboxes, user1 and user2. user1 received the message but for user2, it *magically* disappeared. MTA is exim4 which definitely processed the messages and handed

Hi, Some time ago my dovecot started to become BUGgy: Evertime I restart the system, dovecot is started but I cannot login. I see the following information in the logs: Jul 4 04:04:36 mail dovecot: auth: passwd-file(user,127.11.91.218,<nfkQjFT9vwCADFra>): no passwd file: /etc/dovecot/imap.passwd Jul 4 04:04:36 mail dovecot: auth: Error: BUG: Authentication client sent unknown handshake

Hi, I have been running a Debian 3 server without problems for a long time. Now, after upgrading to Debian jessie (Debian 4.2.14) I cannot log in any more: smbclient -U admin -L //localhost/ Enter admin's password: session setup failed: NT_STATUS_UNSUCCESSFUL In the logs: [2017/01/14 23:37:21.636022, 2] ../source3/auth/auth.c:305(auth_check_ntlm_password) check_ntlm_password:

Hi, I read the Wiki about dovecot-shared a few times but it is not 100% clear to me (at least for 1.2). First, if I want shared keywords I *must* have a dovecot-shared. In this case, the permissions are not taken any longer from the parent folder (what is exactly this parent folder?) but from the dovecot-shared file. So in some sense dovecot-shared is always required (since everyone would

Hi, On my mail server I want to implement shared folders for each workgroup where there are many workgroups. One way would be to create a separate namespace for each workgroup. However, this does not scale well so I decided to use a single Shared mailbox and use ACLs: namespace public { separator = . prefix = Shared. location = maildir:/var/mail/shared:CONTROL=~/Maildir/shared } Each

Hi, I have been running a Debian 3 server without problems for a long time. Now, after upgrading to Debian jessie (Debian 4.2.14) I cannot log in any more: smbclient -U admin -L //localhost/ Enter admin's password: session setup failed: NT_STATUS_UNSUCCESSFUL In the logs: [2017/01/14 23:37:21.636022, 2] ../source3/auth/auth.c:305(auth_check_ntlm_password) check_ntlm_password: