similar to: building on cygwin

http://dovecot.org/test/ - Fixed APPEND hanging in some situations. Didn't happen with mail_save_crlf=yes. - Added pop3_uidl_format setting. No need to patch sources anymore if you don't want the default. Does anyone want pop3_uidl_xuidl_header yes/no setting, with fallbacking to pop3_uidl_format if X-UIDL header isn't found? Shouldn't be difficult to do.. - Added

I am looking for PHP functions that implement passwords that much the dovecotpw implementation. I downloaded one from PEAR, Crypt_HMAC, but the passwords it generates look nothing like the dovecotpw passwords, which could be my fault because I know nothing about the field. Is there a guide or some library that implements them to match dovecotpw?

The idea of salted hash algorithms is to generate a different hash even if the same text is entered. That can be easily seen with dovecotpw: using NON-salted SHA256, same hash is generated for a given password [root at correio ~]# dovecotpw -s SHA256 -p 123 {SHA256}pmWkWSBCL51Bfkhn79xPuKBKHz//H6B+mY6G9/eieuM= [root at correio ~]# dovecotpw -s SHA256 -p 123

Platform is Solaris 8 on a 280R. I'm setting up a new installation of Dovecot, and I ran into some troubles that I've partly tracked down. I setup auth/user dbs with LDAP initially, and things worked well. Passwords are stored as "{crypt}zxcv..." in LDAP. I setup SQL, and began getting this: dovecot: Jan 23 16:37:47 Error: child 8718 (auth-worker) killed with signal 11

Is there any other mechanism than using passwd files with md5-hashed passwords created by dovecotpw that will support cram-md5 authentication? Has anyone created setups where the passwd databases reside in the individual users home directories? Is it possible to persuade dovecotpw to update the passwd databases automatically. Having to use a text editor to paste in the passwords sets a high

Hi, please apply the following patch to dovecotpw. Without this, it will be unusable on powerpc and (maybe) other architectures where the char is unsigned by default. --- dovecot-1.0/src/util/dovecotpw.c (revisione 2066) +++ dovecot-1.0.new/src/util/dovecotpw.c (copia locale) @@ -40,7 +40,7 @@ const char *user = NULL; char *scheme = NULL; char *plaintext = NULL; - char ch; +

Hi again, I`m a bit confused how to store a SSHA256 password in the database and I can`t find any information in the wiki. Do I have to store the SHA256 hash and the salt separately (what would the password_query be like in this way) or just the final SSHA256 hash? Regards Patrick

Hello, Is this the proper place to suggest an enhancement for the stock dovecot package ? The enhancement would be the following: For the time being, the dovecotpw utility offers a standardised way to interactively encode a user password in a certain scheme, say: dovecotpw -s CRYPT Enter new passord: Re-enter new password: etc. Given a *valid* /etc/imap.passwd file (passwd-file

Hi, I'm just in the middle of setting up dovecot to serve IMAPS -- Actually I've finished apart from one thing: CRAM-MD5 passwords. I'm using SQL as a backend for the password storage, and I don't want to store the passwords in plaintext. I've also configured dovecot to be rather restrictive when it comes to authentication methods (only CRAM-MD5 is allowed). To generate the

Hello, I want to use PostgreSQL to store my Dovecot users. I setup a very basic configuration, following word for word this page http://wiki.dovecot.org/DovecotPostgresql and it works ... almost. In fact, it works if I use PLAIN password scheme in my database. However, I would like to store them encrypted. But, if I replace the password field for my user with {HMAC-MD5}-... (the password

Where do you think the following binaries should be installed to? The possible locations are: - bin/ - sbin/ - libexec/dovecot/ (or lib/dovecot/ in most Linux distros) So the binaries are: 1) These probably belong to bin/ or sbin/ or both: - authtest - dovecotpw - doveadm 2) Binaries that you might want to call from mail_executable setting: - rawlog - gdbhelper 3) Index file dumping

If you have time, please test http://dovecot.org/nightly/dovecot-latest.tar.gz If nothing big comes up, I'll release it as 1.0beta1 tomorrow evening. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url :

Hello, I just installed dovecot version 2.0.8 from the source tarball. After doing ./configure, make, and make install, I don't have the dovecotpw binary anywhere. It is not in /usr/local/bin or /usr/local/sbin where the other binaries are; I also did a find / for it and don't see it. Is there some configuration flag I'm missing? I read the flags in ./configure --help and nothing

Hi all, Got a question on configuring dovecot, I'm still new at this so I might be doing this all wrong. I want dovecot to authenticate the mail client using CRAM-MD5 so I've setup the config in dovecot.conf: auth default { mechanisms = cram-md5 passdb sql { # Path for SQL configuration file, see doc/dovecot-sql-example.conf args = /etc/dovecot/dovecot-sql.conf

Hi guys, Anyone know what this error with deliver is (v1.1.1)? 2008-07-03T09:45:19+01:00 mail4 deliver(alexander): Panic: file mail-index-transaction.c: line 642 (mail_index_transaction_lookup): assertion failed: (seq >= t->first_new_seq && seq <= t->last_new_seq) Seen a few of these this morning. Mark -- Mark Zealey -- Shared Hosting Team Leader Product Development *

Hi Timo, Awhile back I'd written about making changes to some of the log levels that dovecot writes to to stop the process from writing these to monitor. I wanted to run a few changes by you for this, just to make sure these won't cause problems somewhere else. And to send this to the list, in case anyone else wants to make similar changes in the future. In the file

On 2/20/19 5:09 AM, Yassine Chaouche via dovecot wrote: > On 2/12/19 5:05 PM, Robert Moskowitz via dovecot wrote: >> I have trying to find how to set the dovecot-sql.conf for using >> SHA256/512.? I am going to start clean with the stronger format, not >> migrate from the old MD5.? It seems all I need is: >> [...] default_pass_scheme = SHAxxx-CRYPT [...] > > How

Hi there, We are living dangerously and using the test versions on our production servers which are migrated from 3 different older servers (about 5000 accounts) therefore we have 3 different MySQL auths. All seems to be ok, but a guy in the office is using Thunderbird as pop3 access. The auth is saying: auth(sql): plain(?,xx.xxx.xx.xxx): invalid input I have hidden his IP for security

We uograded our dovecot from version 2.1.10 -> 2.10.12, but within the first hour of use, dovecot-lda would segfault during delivery. This left a lock file lying around causing the user's mail readers to hang; much hilarity ensues. All further deliveries to the same user will result in a crash. The only thing that fixes this condition is to blow away the user's INBOX cache index.

Hi, I patched dovecot-1.1.beta14 to compile under gcc 2.95. __builtin_expect and __attribute__((malloc)) are only available since gcc 3.0, and __builtin_types_compatible_p since 3.1. Also the flexible array members (char a[]) are not available for gcc 2.95. So I replaced them with zero-extent arrays (char a[0]), which should also work, but that is gcc specific. A general pointer (char* a) should