> "Herbert J. Skuhra" :
> On Thu, Feb 15, 2024 at 11:28:04AM -0600, Brad Koehn via dovecot wrote:
>> Just wondering how/if JMAP support is coming along. It seems to offer major
>> protocol advantages to a connection-oriented protocol like IMAP; I’m curious
>> to
>> see how it performs in the
>>>>> Steinar Bang :
>>>>> Steinar Bang :
>> I am transitioning between servers (both debian 11.6 with dovecot
>> 2.3.13) and I'm seeing some strange behaviour after the transition: it
>> seems like dovecot is listing the correct subject for t
>>>>> Steinar Bang :
> I am transitioning between servers (both debian 11.6 with dovecot
> 2.3.13) and I'm seeing some strange behaviour after the transition: it
> seems like dovecot is listing the correct subject for the test messages
> I'm sending in what&#x
I am transitioning between servers (both debian 11.6 with dovecot
2.3.13) and I'm seeing some strange behaviour after the transition: it
seems like dovecot is listing the correct subject for the test messages
I'm sending in what's shown in my MUA's summary.
But the body of the message is an old me
> Aki Tuomi :
> We are working on including JMAP support to Dovecot. At this moment I
> cannot give any promise for exact version, but hopefully it will be
> part of v2.3
Any updates on jmap support in dovecot?
I tried searching the git repo for "jmap" yesterday, so I'm guessing the
answer i
>>>>> Aki Tuomi :
> On 13.09.2017 23:59, Steinar Bang wrote:
>> When a message is copied to a folder on dovecot with maildir storage, is
>> the mtime of the saved maildir file set to the time of the save?
> It's the file ctime.
Is there a way to get the I
>>>>> Aki Tuomi :
> On 09.09.2017 12:33, Steinar Bang wrote:
>> When a message is copied to a folder on dovecot with mbox storage, is
>> the mtime of the saved mbox file set to the time of the save?
[snip!]
> Internaldate is picked from the separating &#x
When a message is copied to a folder on dovecot with mbox storage, is
the mtime of the saved mbox file set to the time of the save?
Or is the mtime set to the Date: field of the source message that is
saved?
If there is a difference in the behaviour, do someone know the dovecot
version number w
> Aki Tuomi :
> Is there some reason you cannot protect your users with TLS/SSL?
I do use SSL. I don't understand what that have to do with the
preference of CRAM-MD5 over plain text auth?
> Using CRAM-MD5 is not very secure option, since you have to store the
> password in clear text. Plai
>>>>> Aki Tuomi :
> On 2017-03-25 17:54, Steinar Bang wrote:
>> This is a PAM module that listens for password changes, and will update
>> the MD5 password for a user, in a file that dovecot can read, when the
>> user's password is changed:
>>
This is a PAM module that listens for password changes, and will update
the MD5 password for a user, in a file that dovecot can read, when the
user's password is changed:
https://github.com/steinarb/pam_dovecotmd5pwd
Caveat emptor! (Works for me...! :-) )
> Felix Zielcke :
> Are you talking about wheezy or jessie?
Well I looked on a jessie system, but the fail2ban was pulled in when it
was wheezy (or maybe even easier).
> jessie has rules. But they need to be enabled like this:
> # cat /etc/fail2ban/jail.d/local.conf
> [exim]
> enabled = tr
> Edward Betts :
> Jorge Bastos wrote:
>> What do you see in the logs?
>> My guess is that someone is trying a brute force auth against you,
> Thanks Jorge, I think this is the answer. I'm using dovecot for exim4 SMTP
> authentication. The exim4 logs show brute force attacks.
A little late
> /dev/rob0 :
> On Thu, May 23, 2013 at 04:10:01PM -0700,
>Dan Mahoney, System Admin wrote:
>> I'd love to hear about any other ways people have thought about
>> to do this. Any ideas?
> Are you familiar with the mutt(1) MUA? I use it with a:
> set tunnel="MAILDIR=~/Mail/ /usr/libexe
> Daniel Parthey :
> The PAM documentation can be found at:
> http://www.linux-pam.org/Linux-PAM-html/
This one I have already visited, if the link colour in the browser is to
be belived. However it didn't make much of an impression at the time.
Now, however, after actually writing a PAM mo
>>>>> Steinar Bang :
>>>>> Professa Dementia :
>>> There are plugins that allow you to call some glue logic (Perl,
>>> Python, shell scripts, etc) which enables you to interface to pretty
>>> much any method (SQL, LDAP, shadow files, etc)
>>>>> Steinar Bang :
>>>>> Professa Dementia :
>> There are plugins that allow you to call some glue logic (Perl, Python,
>> shell scripts, etc) which enables you to interface to pretty much any
>> method (SQL, LDAP, shadow files, etc) you have c
> Professa Dementia :
> Also note that MD5, the basis for CRAM-MD5, is considered weak and no
> longer recommended. Thus, if you face an attacker that is sophisticated
> enough to crack the SSL / TLS connection, they very likely will have
> little problem with the CRAM-MD5 mechanism.
Well, y
I prefer not to use clear text passwords, even over an encrypted
connection. With IMAP, the only such mechanism with widespread client
support is CRAM-MD5 (please correct my if I'm wrong... I'd love to be
corrected here...).
On the dovecot 2 wiki, the only way I've found to implement CRAM-MD5
sup
> Reindl Harald :
> and deb-packages does not support Obsoletes/Provides like RPM or only
> the packager too stupid not break upgrades?
There isn't an "obsolete"-concept, AFAIK. But there is a way to handle
upgrades that switch implementations, through a mechanism called virtual
packages.
W
>>>>> Steinar Bang :
> Could the culprit be the syslogd? Could the syslogd have gone AWOL
> during the debian upgrade? That's a point of investigation, at least...
Indeed...
rainey:~# dpkg -S /etc/syslog.conf
sysklogd: /etc/syslog.conf
rainey:~# dpkg -l sysklog
>>>>> Pascal Volk :
> On 05/09/2013 02:02 PM Steinar Bang wrote:
>> After upgrading my IMAP server to the new debian stable, and upgrading
>> dovecot from 1.x to 2.1.7 in the process, dovecot no longer logs
>> anything to /var/log/mail.*. The last entries there
After upgrading my IMAP server to the new debian stable, and upgrading
dovecot from 1.x to 2.1.7 in the process, dovecot no longer logs
anything to /var/log/mail.*. The last entries there are from before the
upgrade, and no starts or error messages or failed login attempts, since
then, have been l
When I upgraded my debian-based imap server from squeeze to wheezy
yesterday, SSL stopped working.
I am using a http://cacert.org signed server sertificate, and I am
reusing the certificates that were used on the 1.x dovecot of debian
squeeze.
My three MUAs that worked against the previous 1.x do
> Timo Sirainen :
> Thoughts?
How about:
a) Dropping into a command prompt where it's possible to give commands?
b) Making it possible to feed commands through a pipe (ie reading lines
from stdin)?
> Timo Sirainen :
> I'm not as much against git anymore as I was when I switched to hg,
> but I don't see much benefits in switching to git either. I highly
> doubt I'd get even a single patch more if I used git instead of hg.
FWIW the distingushing feature of git isn't that it is a ditribute
>>>>> Steinar Bang :
>>>>> Timo Sirainen :
>> I don't know if I'm doing something wrong, but I can't even cause a
>> DoS. Even while all imap-login processes are eating 100% CPU (almost
>> 500 handshakes/second), I can successfully
> Timo Sirainen :
> I don't know if I'm doing something wrong, but I can't even cause a
> DoS. Even while all imap-login processes are eating 100% CPU (almost
> 500 handshakes/second), I can successfully log in with another client.
Are you using the tool linked to in the article, to stress th
> Timo Sirainen :
> Yes, SSL handshakes are extra. Although SSL supports some kind of
> quick renegotiation too, but Dovecot doesn't support that yet. No
> one's ever requested it..
Hum... this article (in Norwegian)
http://www.digi.no/881186/skrekkverktoy-slaar-ut-%ABsikre%BB-servere
addres
> Phil Howard :
> And I fully accept that as a sufficient reason to make a choice. I
> made the choice of Dovecot, having zero experience with it, because of
> my experience with Courier. Sadly, making such a choice with zero
> experience and zero knowledge of either options is the really ha
> Phil Howard :
> I abandoned sendmail many years ago and haven't looked back. I tried
> qmail and postfix, and was a lot happier with postfix. I overlooked
> exim at the time, but from what little I've seen and heard, it should
> be up there with postfix, making for a tough choice if you di
> Timo Sirainen :
> Do you think I'd break a lot of people's filters if I removed the
> prefix? :) Anyone strongly for/against removing it? It seems kind of
> annoying to me whenever I happen to think about it.
FWIW I read the lit in prefix-stripped form, via NNTP to news.gmane.org,
so I neve
> "L.M.J" :
> Unfortunately, I'm using mbox :-/ In that case, --fuzzy got less
> interest but --delete-after is definitely a good one.
If you're talking mbox then -fuzzy has no interest, that's right. But
rsync is still a good match, actually a better match than with maildir.
The rsync progr
> "L.M.J" :
...
> rsync -a --delete $i ${PATHTOSAFEPLACE}/$(date +%u)/${i}/
...
The downside to not using --fuzzy, is that the entire article is
transferred again if a message names changes slightly (ie. if we're
talking maildir here), as a result of status change.
Note if you decide to
> Timo Sirainen :
> The main potential problem with that is that if a message's flag is
> changed, the filename changes so it's now stored twice in the backup
> server. So when restoring mails, be sure not to restore duplicates.
I use the --fuzzy flag to handle the renaming issue. Here's my
> Andrzej Adam Filip :
> You can use mda option provided in fetchmail as SMTP alternative.
> -
> I recommend using procmail as mda in ~/.fetchmailrc e.g.:
Heh... I'm an old procmail user, and was happy to be able to switc
Samba has pam_smbpass which is a PAM module that hooks into password
changing, and changes the users' samba password (presumably used for
NTLM auth?), when the users change their ordinary unix/linux password.
http://gitweb.samba.org/?p=samba.git;a=tree;f=source3/pam_smbpass;h=c230a1b239719
>>>>> Steinar Bang <[EMAIL PROTECTED]>:
> I can see one issue with it, when using rsync to back up the mailboxes
> to a different machine:
> since the file names of the articles change when they are read, and when
> the state changes, rsync may ending up transfer
> CJ Keist <[EMAIL PROTECTED]>:
[On why mbox and not maildir]
> It's to do with how our current file services are setup and a personal
> preference and familiarity with the mbox format.
FWIW it was familiarity with mbox, and that maildir was a big unknown
for me, that almost made me choose mb
> CJ Keist <[EMAIL PROTECTED]>:
> Anyone out there know of a tool that can convert a Cyrus MailDir format
> to Dovecot mbox? I have a user that I need to move over from a mail
> server running cyrus using MailDir format. At first I told him to setup
> second account with Thunderbird to our m
> Holger Weiss <[EMAIL PROTECTED]>:
> However, for our conversion, we've written our own "cyrus2dovecot"
> which also supports skiplist databases (amongst another few features
> not provided by the other tools):
> http://cyrus2dovecot.sw.fu-berlin.de/
The wiki page says "cyrus2dovecot
The transition was quick, and also (so far) seemingly painless.
The server is an old Pentium II 233 machine that sits between my home
LAN and the internet, and have sitting there, and running night and day
since 1999. For the first two years it was running SuSE linux, but
since 2001 it has been r
> Timo Sirainen <[EMAIL PROTECTED]>:
> You can use shadow, but only if you can put the passwords there as
> {cram-md5}password. That of course means that only Dovecot is able to
> use such passwords. Also you can't modify the passwords with passwd
> utility because it doesn't write compatible
>>>>> Timo Sirainen <[EMAIL PROTECTED]>:
> On Fri, 2008-09-12 at 20:17 +0200, Steinar Bang wrote:
>> Is there any other mechanism than using passwd files with md5-hashed
>> passwords created by dovecotpw that will support cram-md5
>> authentication?
>
>>>>> Timo Sirainen <[EMAIL PROTECTED]>:
> On Fri, 2008-09-12 at 20:17 +0200, Steinar Bang wrote:
>> Is it possible to persuade dovecotpw to update the passwd databases
>> automatically. Having to use a text editor to paste in the passwords
>> sets
>>>>> Steinar Bang <[EMAIL PROTECTED]>:
> Is there any other mechanism than using passwd files with md5-hashed
> passwords created by dovecotpw that will support cram-md5
> authentication?
It would have been really neat if there had been a pam_crammd5.so that
wo
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
> Kyle Wheeler <[EMAIL PROTECTED]>:
> The flag information is stored in the index, and for Maildir backends
> the first 26 flags are stored in the filename as well. In other words,
> access to flags is pretty dang fast, and for Maildir storage, never
> requires opening the message or parsing h
Gnus use a lot of custom flags to represent the messages state
wrt. Gnus.
How well are these flags supported in dovecot? How fast are access to
them? (Ie. will dovecot have to open the message and parse the headers)
Are they supported when using imapsync to transfer messages from a
different I
> Timo Sirainen <[EMAIL PROTECTED]>:
> cyrus2courier does everything, but it requires a supported Cyrus
> version.
Right. I tried that one first, but I wasn't able to figure out what
arguments to give it. Eg. what to tell it the courierdir was, and what
the mailbox should be named.
Eg. if
What's the best utility to use to convert mail folders from a cyrus
2.2.13-10, on a debian 4.0 Etch system, to folders that can be used by
dovecot?
The http://wiki.dovecot.org/Migration/Cyrus page isn't too clear on
what's the difference.
cyrus2courier says "It should be able to preserve message
51 matches
Mail list logo
