Am 21.02.2010 um 07:16 schrieb Timo Sirainen:
> Yes, that's intentional. imaps isn't a protocol.
Thanks Timo. Has the specific logging option for the LDA been dropped? I see it
logging to 'info_log_path=' only.
Regards
Thomas
On Sat, 2010-02-20 at 23:41 +0100, Thomas Leuxner wrote:
> this is the first 2.0 build I tested, and I haven't been following the 2.0
> threads very closely. This said I'm puzzled whether 'protocols = imap' does
> what it should. It also enables a listener for IMAPS on port 993, different
> to
Hi,
this is the first 2.0 build I tested, and I haven't been following the 2.0
threads very closely. This said I'm puzzled whether 'protocols = imap' does
what it should. It also enables a listener for IMAPS on port 993, different to
what 1.2 series did. I had to manually disable the IMAPS part
On Sáb, 2010-02-20 at 18:59 +, Spyros Tsiolis wrote:
> Sir, you are one busy bee !
> :-)
>
> You make the rest of us look like lazy sobs :-)
>
Most likely because we are :)
-- Jose Celestino SAPO.pt::Systems http://www.sapo.pt
---
Timo,
Thanks for clearing things up. I have finally figured it out (I hope)
INBOX is a special mailbox. Setting inbox=yes changes nothing except
where INBOX's location is looked up from. No other mailboxes are
affected. Listing/opening RealMails/INBOX might or might not work,
depending on config
On Sat, 2010-02-20 at 20:02 +0100, e-frog wrote:
> I'm playing around with the new Dovecot v2.0.beta3 and don't seem to be
> able to get quotas working from userdb. I didn't change the SQL query
> which was working for 1.2.10.
I guess I broke it with the recent config changes. Or maybe earlier.
I
Hello Timo,
I'm playing around with the new Dovecot v2.0.beta3 and don't seem to be
able to get quotas working from userdb. I didn't change the SQL query
which was working for 1.2.10.
Feb 20 19:34:06 ubuntu-test dovecot: auth: sql(test,192.168.156.99):
SELECT home, mail, uid, gid, concat('*:stora
Sir, you are one busy bee !
:-)
You make the rest of us look like lazy sobs :-)
s.
--- On Fri, 19/2/10, Timo Sirainen wrote:
> From: Timo Sirainen
> Subject: [Dovecot] Dovecot blog
> To: dovecot-n...@dovecot.org, "Dovecot Mailing List"
> Date: Friday, 19 February, 2010, 16:20
> http://blog
Hi Timo,
>> 2010-02-17 17:52:21 deliver(wer...@example.com): Error: Corrupted
>> transaction log file /mailhome/wernertest/dovecot.index.log seq 24: Invalid
>> transaction log size (67988 vs 68080):
>> /mailhome/wernertest/dovecot.index.log (sync_offset=67988)
>>
>> Is this something to worry ab
http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta3.tar.gz
http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta3.tar.gz.sig
I had to break a few APIs in this release to get some other stuff
implemented and fixed. And since I had to break some of them, I decided
it could be a good time to do so
Dear List,
I have a few questions regarding dovecot sasl authentication that are
somewhat related to each other.
I have a working dovecot config with
--
ssl_verify_client_cert = yes
..
.
ssl_require_client_cert = yes
ssl_username_from_cert = yes
---
(With this set up I need
Hi,
I got problem whith CRAM-MD5 auth (works fine with PLAIN):
--
Feb 20 13:15:02 auth(default): Info: new auth connection: pid=5026
Feb 20 13:15:06 auth(default): Info: client in: AUTH 1 CRAM-MD5
service=imap secured l
On Sat, 2010-02-20 at 11:55 +0100, Kamil Jońca wrote:
> > deliver -m your_mailbox_name
> >
> > (With Sieve that actually only specifies the default mailbox, which is
> > used only if Sieve doesn't decide to save it elsewhere.)
>
> Yes, I know about this switch. Maybe I should tourned off sieve (So
Timo Sirainen writes:
> On Fri, 2010-02-12 at 14:42 +0100, Kamil Jońca wrote:
>> Is any posibility to pass parameters/environment variables to deliver
>> with sieve plugin?
>>
>> I have some procmail rules to decide where mail should go, which
>> can't be migrated to sieve (uses external program
Timo Sirainen wrote:
> On Fri, 2010-02-12 at 14:42 +0100, Kamil Jońca wrote:
>> Is any posibility to pass parameters/environment variables to deliver
>> with sieve plugin?
>>
>> I have some procmail rules to decide where mail should go, which
>> can't be migrated to sieve (uses external programs)
On Fri, 2010-02-12 at 14:42 +0100, Kamil Jońca wrote:
> Is any posibility to pass parameters/environment variables to deliver
> with sieve plugin?
>
> I have some procmail rules to decide where mail should go, which
> can't be migrated to sieve (uses external programs). So far I write it
> to mail
Steffen Kaiser writes:
> On Fri, 12 Feb 2010, Kamil Jońca wrote:
>
>> Is any posibility to pass parameters/environment variables to deliver
>> with sieve plugin?
>
> No. But you could check the "extdata" extension posted by Stephan Bosch
> lately.
But, if I understand, this plugin can store onl
17 matches
Mail list logo