Hi,
I've had the following appear in my logfile, and am just wondering
what the warning means?
dovecot: managesieve-login: Warning: SSL alert: where=0x4008, ret=256:
warning close notify [a.b.c.d]
dovecot: imap-login: Warning: SSL alert: where=0x4004, ret=256:
warning close notify [w.x.y.z]
Shou
Hi,
Anyone else experiencing this (Dovecot 2.2.4, attachments stored
separately):
dovecot: imap(u...@kamdha.com): Error: file_istream.open(/home/
example.com/user/attachments/f5/f0/f5f0f2c08c4311fa404d090a703c3b492f2ea718-a52388285a04eb51820cd485234e-c92f64f79f0d1ed01e6d5b314f04886c-42501)
fa
Hi,
I've noticed that the redirect sieve extension is placing an extra space
before the headers of email when the 'redirect' command is used.
Unfortunately this break gmail, yahoo, and most other email programs.
I am using pigeonhole 0.4.0-14 with Dovecot 2.2.4.3; I see change
1781:e439789e3211
24 July 2013 07:12, Stephan Bosch wrote:
> On 7/24/2013 3:55 AM, Anand Kumria wrote:
>
>> I've noticed that the redirect sieve extension is placing an extra space
>> before the headers of email when the 'redirect' command is used.
>>
>> Unfortunately
Hi Stephan,
On 24 July 2013 11:52, Stephan Bosch wrote:
> Op 7/24/2013 12:32 PM, Anand Kumria schreef:
>
> Hi Stephan,
>>
>> Attached is the configuration and both the original message as received
>> (sieve redirect test.eml) and what it was like at the locatio
upgrade to that version might help?
Regards,
Anand
On 24 July 2013 15:10, Stephan Bosch wrote:
> Op 7/24/2013 3:30 PM, Stephan Bosch schreef:
>
> Op 7/24/2013 1:04 PM, Anand Kumria schreef:
>>
>>>
>>> As I said, my suspicions are on 'mail_crlf_save =
Hi,
I have been (attempting) to transition a company from in-house dovecot 1.x
to a hosted dovecot 2.2 setup.
I am running the doveadm sync command, and for the four mailboxes have been
blocked -- sync'ing seem to be copying the same mails, over and over (note,
initially I was using doveadm backu
Hi Timo,
On 5 August 2013 19:19, Timo Sirainen wrote:
> On 21.7.2013, at 17.12, Anand Kumria wrote:
>
> > Anyone else experiencing this (Dovecot 2.2.4, attachments stored
> > separately):
> >
> > dovecot: imap(u...@kamdha.com): Error: file_istream.open(/home/
>
Hi Stephen,
I finally had a chance to re-test this and confirm that v4.1 of the plugin
does fix the problem.
Thanks for your assistance.
Regards,
Anand
On 25 July 2013 17:11, Stephan Bosch wrote:
> On 7/25/2013 8:06 AM, Anand Kumria wrote:
>
> Hi Stephan,
>
> I'm
I've now upgraded my server to Dovecot v2.2.5 - and the same problem still
occurs.
Has anyone else had Dovecot consistently fail to sync remote users?
I've been trying this essentially daily for the last month to finish this
migration off, with no success. :-(
A
On 3 August 2013 11
Hi,
I am beginning to see many entries like:
Sep 10 21:32:06 mail1 dovecot: imap(us...@example1.com): Warning:
read(/var/run/dovecot/dict): dict lookup took 20 seconds
Sep 10 21:32:11 mail1 dovecot: imap(us...@example2.com): Warning:
read(/var/run/dovecot/dict): dict lookup took 25 seconds
Sep 10
Hi,
Another day, another dysnc attempt. Using Dovecot v2.2.5.4; I see:
# doveadm -v -o imapc_user=u...@example.com -o imapc_password=password -o
imapc_host=imap.example.com -o imapc_port=993 -o imapc_ssl=imaps -o
imapc_ssl_dir=/etc/ssl -o imapc_feature=rfc822.size -o imapc_ssl_verify=no
sync -1 -
Hi,
Using dovecot v2.2.5.5, I get the following:
$ doveadm -v backup -R -u u...@example.com maildir:/home/rsync/
example.com/user/Maildir/
[...]
dsync(u...@example.com): Panic: file dsync-mailbox-export.c: line 228
(export_save_change_get): assertion failed: (change->type ==
DSYNC_MAIL_CHANGE_T
Thanks,
Anand
On 22 September 2013 01:03, Timo Sirainen wrote:
>
> On 17.9.2013, at 6.25, Anand Kumria wrote:
>
> > Another day, another dysnc attempt. Using Dovecot v2.2.5.4; I see:
>
> Is it still duplicating mails? So if you first delete everything from
> destination
nt the
original contents anonymized.
Also, the issue might be related to the folder structure, the original is
using Maildir within Maildir (what Dovecot 1.x creates actually).
So you might need the full structure?
Regards,
Anand
On 26 October 2013 16:23, Timo Sirainen wrote:
> On 20.10.2013, at 1
creates actually).
>
> So you might need the full structure?
>
> Regards,
> Anand
>
>
> On 26 October 2013 16:23, Timo Sirainen wrote:
>
>> On 20.10.2013, at 19.24, Anand Kumria wrote:
>>
>> > Using dovecot v2.2.5.5, I get the following:
>> >
Hi,
After upgrading to v2.2.7 yesterday, I am starting to get a larger number
of bugs occurring -- unfortunately I hadn't configured things to save core
dumps (now done).
But I am seeing things like:
dovecot: imap(u...@example.com): Fatal: master: service(imap): child
27931 killed with signal 1
Hi Timo,
As a follow-up to my earlier email, I've managed to get a few backtraces
now.
#305439 o_stream_close (stream=0x1680c10) at ostream.c:85
#305440 0x7ff222f70f3c in o_stream_zlib_send_outbuf (zstream=0x1680b80)
at ostream-zlib.c:97
#305441 0x7ff222f70fef in o_stream_zlib_send_flush
Yes, it appears that that might be the issue.
A
On 5 November 2013 18:02, Timo Sirainen wrote:
> On 5.11.2013, at 16.12, Anand Kumria wrote:
>
> > After upgrading to v2.2.7 yesterday, I am starting to get a larger number
> > of bugs occurring -- unfortunately I hadn'
Hi,
I am seeing occasional log entries like:
Feb 4 06:20:01 mail1 dovecot: imap(u...@example.com): Error: read() failed: zlib.read(): unexpected EOF at 894774
Feb 4 06:20:01 mail1 dovecot: imap(u...@example.com): Disconnected in
APPEND (1 msgs, 201 secs, 0/5180550 bytes) in=894774 out=643701
I
20 matches
Mail list logo
