similar to: dovecot + LDAP-SASL ?

Hi, I would like to setup an IMAP server with SASL and LDAP support. As far as I can see dovecot supports SASL and LDAP, but not the way I need it. If I understand dovecot correctly, it has it's own set of SASL mechnisms and uses the LDAP server just to store the plaintext password. In case of authentication dovecot fetches the plaintext password from LDAP and then performs the SASL

Hi, I am trying to deal with the problem, that under regular mbox format a path can lead to either a file or a directory, but not both, while under IMAP, a path is usually both, a message folder containing subfolders. I found dovecot's approach to this problem, the Maildir++ layout described under http://wiki2.dovecot.org/MboxChildFolders , and was astonished to see, what problems come with

https://bugzilla.mindrot.org/show_bug.cgi?id=3648 Bug ID: 3648 Summary: ssh client blocks itself by leaving unix domain socket alive after user Product: Portable OpenSSH Version: 9.3p1 Hardware: Other OS: Linux Status: NEW Severity: normal Priority: P5 Component: ssh

> Sounds more like you just introduced a new self-created problem that would require yet another workaround.. ;-) Definitely wrong. Appending .dir to directories and .folder to folder files keeps files completely distinct and name collissions are not possible. > But what was not clear from your mail, is what exactly you identified as "the problems" with standard Maildir++

Hi, just a simple question about dovecot: The mbox file format contains the SMTP envelope sender and transmission date in a FROM ... line preceding the RFC822 mail header and body. As far as I see at the moment, the IMAP protocol does not support transmission of that SMTP envelope data in either way, but confusingly uses the term ?envelope? for a structure describing the RFC822 mail header.

Hi, it becomes more and more common to have machines with dynamically assigned IP addresses online (e.g. DSL), which can be found through dynamic DNS entries. Unfortunately, the "Known Hosts" mechanism doesn't work for these machines: Since the entry is made for the IP address, there's a new entry every time the address changes. Therefore, an option should be invented

Hello, I've just installed dovecot to replace courier-imap and I've found out it didn't support some of the typical LDAP userPassword schemes, so I've written some based on OpenSSL API. Furthermore I noticed that the MD5 one seems broken. If it isn't a requirement to ship its own implementation of a crypto algorithm, I would send in a patch to replace schema checks with

Hi, I'd like to suggest a new feature to rsync. Problem: Currently, rsync generates a recursive list of file existing a the source directory, modifies this list by includes and excludes, and then copies these files. That's pretty good in most, but not all cases. I am mirroring a debian archive, but unfortunately, debian mixes all files of several distributions in a subtree /pool.

Hallo. First of all I'm sorry for my bad english. I have a question about how dovecot use passwords. I have all my mail accounts in a ldap database. The user password are stored in form: {crypt}mypasswd. In dovecot-ldap.conf I have default_pass_scheme = CRYPT. All is working fine. The problem in the crypt scheme is that I can't have passwords more than 8 characters long. So I've tried

Hello, am I right, that dovecot can't cope with ldap so authentification is handled by ldap itself? And, for that I have to use {CRYPT} and cannot use other mechanisms as {SMD5} Are there any other possibilities? A --

Hi, dovecot provides POP and IMAP services. Proposal: Would be nice if it also could offer an RSS-Feed for a mailbox, giving a summery of sender/subject/date and maybe the first lines of text. regards Hadmut

on a FreeBSD 11.2 amd64 machine, I am trying to get Dovecot 2.3.4 to play nice with "argonid" encryption. In the "10-auth.conf" file, I tried: auth_mechanisms = plain argon2id Upon restarting dovecot, I received an error message when attempting to actually it: auth: FATAL: Unknown authentication mechanism "ARGON2ID" Output from doveadm pw -l doveadm pw -l SHA1

Hi, I'm looking for a hint about what has changed in syslinux 6.03. Some years ago I had written a script that configures a bootable USB pen drive with syslinux and some boot images, which still worked well under Ubuntu 14.04 LTS and previous versions, but does not work anymore under Ubuntu 15.10 with syslinux 6.03. I've boiled this down to a test-script that isolates the problem:

Dear friends, We have samba-3.0.21c-1 under RH9 + openldap 2.3.11 under FC4. When a windows user changes his password using Ctrl-Alt-Del the password is stored on ldap in SSHA format but we need to work with CRYPT because we have some apps that don't support SSHA. These are the lines related with authentication defined in smb.conf: encrypt passwords = yes ldap passwd sync = Yes

I am using a FreeBSD 11-2 amd/64 system with dovecot version 2.3.4 installed. I was playing around with different encryption schemes. doveadm pw -l SHA1 SSHA512 BLF-CRYPT PLAIN HMAC-MD5 OTP SHA512 SHA RPA DES-CRYPT CRYPT SSHA MD5-CRYPT SKEY PLAIN-MD4 PLAIN-MD5 SCRAM-SHA-1 LANMAN SHA512-CRYPT CLEAR CLEARTEXT SSHA256 NTLM MD5 PBKDF2 SHA256 CRAM-MD5 PLAIN-TRUNC SHA256-CRYPT SMD5 DIGEST-MD5

Hi, today I tried to migrate an old NT4 PDC to Samba 3 as described in http://samba.org/samba/docs/man/Samba-HOWTO-Collection/NT4Migration.html but with the Samba databases on LDAP: Whenever I tried that net rpc vampire -S NT4PDC -U administrator%passwd I received error messages that the users cannot be created. When I set debugging to level 2, it told me about Found bogus group

(I subscribed to a daily digest for this list and can?t figure out how to reply to a reply.) Anyway, Aki Tuomi replied to my feature request saying: > We support in latest 2.2 release > > MD5 MD5-CRYPT SHA SHA1 SHA256 SHA512 SMD5 SSHA SSHA256 SSHA512 PLAIN > CLEAR CLEARTEXT PLAIN-TRUNC CRAM-MD5 SCRAM-SHA-1 HMAC-MD5 DIGEST-MD5 > PLAIN-MD4 PLAIN-MD5 LDAP-MD5 LANMAN NTLM OTP SKEY

On 2/13/19 1:23 AM, Matthias Fechner via dovecot wrote: > > > Am 13. Februar 2019 00:34:15 schrieb Robert Moskowitz > <rgm at htt-consult.com>: > >> On 2/12/19 6:03 PM, Matthias Fechner via dovecot wrote: >>> Am 12.02.2019 um 17:05 schrieb Robert Moskowitz via dovecot: >>>> I have trying to find how to set the dovecot-sql.conf for using

Hi, I have a problem with the host verification of ssh in several networks of the same structure: In all cases there is a router or a firewall with an official IP address, making the ssh-ports of several hosts with RFC1918-addresses available through NAT or TCP forwarding. Thus, different hosts appear on the same IP address, just with different ports. Since SSH uses the IP address but not

Hi, I was just using ssh to access an IPv6 machine. ssh root at 2002:1234::1 (example address) works, while scp root at 2002:1234::1:/etc/motd . works not, scp parses this as hostname 2002 and file path 1234::1:/etc/motd It's a syntax problem. The manpage addresses this problem for -L and -R arguments, but not for scp arguments. Any idea how to deal with this problem? regards