Hij Voytek,
if the connection becomes stale, it might well be a network-related or
client-side issue.
Have you ever heard of the ADSL MTU problem? If some router/firewall inbetween
drops ICMP messages related to path-MTU-discovery, then the maximum transfer
unit (MTU) might be wrong and larger
Le 28 mai 2014 à 16:41, Stanislas SABATIER a écrit :
> [...]
> I tried to explain my specific case in my first post to the list (first
> mail of this thread, may 24) :
> [...]
> To sum up, here are the headers : (CASE 1)
>
>*from : user1@mydomain1*
>to: some...@yahoo.com
>CC: user2@my
Unfortunately, I'm still getting the same errors post upgrade to 2.2.13.
I'm coming from 2.1.12, so perhaps there is some slight incompatibility
in some circumstances with the index files? I'm continuing to delete
them as this arises, and so far I've no repeat problem accounts.
Andy
---
Andy
I actually submitted the PR's. I'm waiting for the real maintainer to
approve or for the 2 week timeout.
As I said, it's doing great for me :)
On Fri, May 30, 2014 at 3:01 PM, Andy Dills wrote:
> Thanks to the suggestion by Larry off-list, I snagged an official patch
> from the FreeBSD PR an
Thanks to the suggestion by Larry off-list, I snagged an official patch
from the FreeBSD PR and now the ports are compiling cleanly.
I'll report back if I get the errors again.
Thanks,
Andy
---
Andy Dills
Xecunet, Inc.
www.xecu.net
301-682-9972
---
On 05/30/2014 15:34, Andy Dills wrote:
Hi t
Hi there,
We recently upgraded to 2.2.12 (the current version in FreeBSD's port
tree), and are seeing these errors in our logs (not super frequently,
but it happens):
May 30 13:20:57 mail1 kernel: pid 15752 (imap), uid 1005: exited on
signal 6
May 30 13:20:57 mail1 dovecot: imap(xxx): Fatal:
thebighonker.lerctr.org /home/ler $ gdb -c doveadm.core `which doveadm`
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions
Hi,
we use attachment dedup with lots of emails (still migrating to it
from maildir).
We use netapp storage with wafl filesystem over nfs.
Problem is that netapp has hard limit of 100k hardlinks to one file.
And we encountered it.
Problem is that dovecot start do segfault (lmtp,dsync,pop3 etc) wh
Hello
We have migrated our email services from a server, which did not support IMAP
and folders, therefore threated the plus sign + as a normal character in a
part of an email address.
Our new server delivers the emails via lmtp to dovecot.
the few users which got a + character in the username
El 30/05/14 08:28, voy...@sbt.net.au escribió:
I have a user with with W7/TBird/IMAP to my dovecot 2.1.17 server, the
user complains whilst he is composing lengthy emails (with multiple
fowrds/replies quoted in the message) he gets 'hour glass' over compose
windows with some message about not bei
> -Ursprüngliche Nachricht-
> Von: dovecot [mailto:dovecot-boun...@dovecot.org] Im Auftrag von Arthur
> Dent
> Gesendet: Freitag, 30. Mai 2014 11:25
> An: dovecot@dovecot.org
> Betreff: Re: [Dovecot] Change to Maildir format (Was:Corrupted Mail?)
>
> Well, with thanks to everyone on this
Well, with thanks to everyone on this list I have now successfully (I
hope) switched from mbox to Maildir format. Moreover I am now using
dovecot-lda to deliver.
I went step by step, and tested it with just one account before opening
up the whole system.
I had to rewrite my procmail recipes twice
Just to give it a shot, I took a look into my SELinux log. Problem solved,
SELinux blocked it. I added a rule to allow the access and that's it.
Thanks for your help
Chris
On Fri, May 30, 2014 at 2:46 AM, Larry Rosenman wrote:
> Can you check all the auth-* process(es) running and make sure th
13 matches
Mail list logo