http://dovecot.org/releases/1.1/dovecot-1.1.3.tar.gz
http://dovecot.org/releases/1.1/dovecot-1.1.3.tar.gz.sig
This fixes several mbox problems previous v1.1 releases have had.
* mail_max_userip_connections limit no longer applies to master user
logins.
+ login_log_forma
I try to cinfigure dovecot run sieve scripts on incoming mail.
In my dovecot.conf:
<...>
protocol lda {
# Address to use when sending rejection mails.
postmaster_address = [EMAIL PROTECTED]
# Hostname to use in various parts of sent mails,
Stewart Dean escreveu:
> IBM recently changed both its delivery package for OpenSSL and the locations
> it
> put things. Luckily, I have a second machine other than my mail server that
> I
> can test things on and DC 1.0.15 seems to be be running OK (thus I got all
> the
> configure/compilat
IBM recently changed both its delivery package for OpenSSL and the locations it
put things. Luckily, I have a second machine other than my mail server that I
can test things on and DC 1.0.15 seems to be be running OK (thus I got all the
configure/compilation tweaks right), but.is there anyw
Would you recommend a set of reasonable settings for this? I kind of
struggle to put these together...
R.
Timo Sirainen wrote:
On Sep 1, 2008, at 7:02 PM, Radomir Zoltowski wrote:
Imagine an NFS mounted read-only file system containing directories
full of plain mboxes. Any recommendations on
Chris Wakelin wrote:
> I've been testing zlib again in Dovecot 1.1.1 (plus assert-crash fix)
> and 1.1.2 and I'm beginning to think it may be some sort of race
> condition (the Solaris 8 box is significantly slower than the SuSE one!).
>
> If I leave a few seconds pause between the "FETCH BODY[]
On Sep 1, 2008, at 7:02 PM, Radomir Zoltowski wrote:
Imagine an NFS mounted read-only file system containing directories
full of plain mboxes. Any recommendations on how to approach the
access with dovecot?
I believe all NFS recommended options apply, how about index/cache
files though? C
Hi all,
Imagine an NFS mounted read-only file system containing directories full
of plain mboxes. Any recommendations on how to approach the access with
dovecot?
I believe all NFS recommended options apply, how about index/cache files
though? Can I switch them off deliberately for good? Perf
It appears so far that the problem I was having with Trash not emptying
and other strange random Thunderbird problem with message counts not
being right appears to have been fixed.
So far it's working well.
On Mon, 01 Sep 2008 15:35:56 +0300, Timo Sirainen <[EMAIL PROTECTED]> wrote:
> Oh, one guess: Do you store passwords in CRAM-MD5 or plaintext format?
> If not, maybe your clients are trying to use CRAM-MD5 and it's failing
> because of that? Logs would show that anyway.
All passwords are hashed
On Sep 1, 2008, at 6:42 PM, Marc Perkel wrote:
If however I restart dovecot then the message count goes to 0 and
everyhing works for a few more hours.
Restarting dovecot fixes the problem. Hope this gives you enought
info to find the bug. 1.0.x didn't have this problem.
I'm pretty sure yo
Hi Timo,
Spoke too soon about everything working.
I have some directories that I use to report spam by dragging messages
into them. I'm using maildir. Once a minute any message in these
directories are cleaned out and deleted.
In Thunderbird if I drag a message into the directory and wait a
On Mon, 01 Sep 2008 17:17:27 +0300, Timo Sirainen <[EMAIL PROTECTED]> wrote:
>> Extracts of /var/log/mail.log attached below. Nothing new in mail.err.
>
> Those are only Postfix's logs. See Dovecot's logs.
> http://wiki.dovecot.org/Logging
Sorry, I pulled these from syslog:
Sep 1 13:52:36 lo
Hi
This sounds to me like the failing Outlook clients might fall over to
CRAM-MD5
and you need to use the %m to map out the method sasl uses to return the
right
password.
Then you need to either use the source packet from ubuntu intrepid
and apply this patch
http://hg.dovecot.org/dovecot-1.1/rev/
On Mon, 2008-09-01 at 16:50 +0200, Edgar Fuß wrote:
> > Is this not working with you?
> Ouch. I should have read the log more carefully.
> The problem was that for this particular test user, the mail directory didn't
> exist and of course deliver was unable to create cur in that non-existing
> di
> Is this not working with you?
Ouch. I should have read the log more carefully.
The problem was that for this particular test user, the mail directory didn't
exist and of course deliver was unable to create cur in that non-existing
directory.
Sorry for the noise.
On Mon, 2008-09-01 at 15:19 +0200, Edgar Fuß wrote:
> I would like deliver not to automatically create subfolders for mails
> addressed to [EMAIL PROTECTED], but nevertheless
> automatically create INBOX for new users. I'm not sure whether a new
> option like -M or -m -m would be appropriate,
I would like deliver not to automatically create subfolders for mails
addressed to [EMAIL PROTECTED], but nevertheless
automatically create INBOX for new users. I'm not sure whether a new
option like -M or -m -m would be appropriate, i.e., whether anyone
needs the current -m behaviour.
It
Or actually that log doesn't show anything since both mail and
sAMAccountName are the same. :) But I'm pretty sure the user gets
ignored..
On Mon, 2008-09-01 at 15:46 +0300, Timo Sirainen wrote:
> Your log shows that "home" is working but "user" is ignored, just as I
> thought..
>
> On Mon, 2008-
Your log shows that "home" is working but "user" is ignored, just as I
thought..
On Mon, 2008-09-01 at 15:42 +0300, Petri Asikainen wrote:
> Works for me (tm). Maybe some of ldap servers does not like that result
> attributes are specified multiple times. But current active directory
> server th
Works for me (tm). Maybe some of ldap servers does not like that result
attributes are specified multiple times. But current active directory
server this not seems be an issue.
Log shows that quory is working:
Sep 1 15:00:52 domainlx6 dovecot: auth(default):
ldap(petasi,172.21.89.69): user s
On Mon, 2008-09-01 at 13:29 +0100, Rodti MacLeary wrote:
> auth default:
> mechanisms: plain login cram-md5
> passdb:
> driver: sql
> args: /etc/dovecot/dovecot-sql.conf
Oh, one guess: Do you store passwords in CRAM-MD5 or plaintext format?
If not, maybe your clients are trying to use
On Mon, 2008-09-01 at 13:29 +0100, Rodti MacLeary wrote:
> In this install Postfix passes SASL authentication to Dovecot. For most
> clients using SSL this works fine, but as soon as SSL is off it fails.
> This is despite having disable_plaintext_auth set to 'no'. Furthermore it
> appears that s
On Mon, 2008-09-01 at 15:15 +0300, Petri Asikainen wrote:
> user_attrs =
> sAMAccountName=user,sAMAccountName=home=/var/spool/vmail/%$,=gid=12,=uid=1001
Hmm. Does that really return both "user" and "home"? I've in TODO that
it's not working..
signature.asc
Description: This is a digitally signe
Hi there, I'm in a bit of a dilemma and wonder if anyone can help.
Over the weekend I bought a new dedicated server and moved my mail/web over
to it. I'd used the Sarge[1] tutorial at workaround.org for the old server
and as I'd wanted to move to Dovecot for a while I decided to use their
Etch[2
Thanks I got it working.
my dovecot-ldap.conf is end of mail in case anyone is interested.
Couple of notes, I have to leave uid and gid mappings here (user_filter)
or I got setuid related error messages.
userdb is queried with email address when lda got mail to deliver. and
with username whe
On Mon, 2008-09-01 at 13:07 +0300, Petri Asikainen wrote:
> Still having some problems.
> Is there way to query user db to see what values dovecot is returning
> after ldap query?
Not really, but auth_debug=yes shows what it returns.
signature.asc
Description: This is a digitally signed messag
Still having some problems.
Is there way to query user db to see what values dovecot is returning
after ldap query?
Timo Sirainen kirjoitti:
On Sep 1, 2008, at 7:51 AM, Petri Asikainen wrote:
I added dovecot-ldap-userdb.conf and it's in auth default, but now
it does lookup users at all. Acc
We do it the same and it works fine, however we do it by inbound port
(because we're behind some loadbalancers that can do port translation.
We create a port -> domain mapping table and then you can just do the
join with "where port = '%a'" (dovecot 1.1 only). Seems a little neater
than the per-ip
I've recently replaced courier-imap with dovecot - mainly for
performance benefits. All of my users in the office use Outlook
Express. It appears that dovecot has no facility to move deleted
messages to a Trash folder - where they can be removed after a
specified time with a cronjob.
Other mail
My existing pop3/imap environment is courier imap + vpopmail + qmail with MySQL
backend. I'm looking at migrating this to Dovecot.
Currently I have multiple instances of Courier bound to different loopback IPs
(the IPs correspond with the virtual IPs on a server load balancer). When a
user auth
Hello, i upgraded dovecot to 1.1.2 this weekend and i get those errors:
grep dovecot /var/log/net/maillog |grep Panic | cut -d " " -f 11-100|
sort | uniq -c | sort -rn
7368 file index-sync.c: line 39: assertion failed:
(seq_range_exists(&ibox->recent_flags, uid))
71 file index-mail.c: line
32 matches
Mail list logo
