Displaying 6 results from an estimated 6 matches for "buzon1".
Did you mean:
buzon
2019 Feb 05
0
problem using different dovecot versions
...index files when a RHEL7 dovecot service write to the filesystem of
a user (the first log line corresponds to RHEL7 and the others to RHEL6):
Feb? 5 09:33:05 listas3 dovecot: lda(user at domain): sieve:
msgid=<007bxxxxxxx at uam.es>: stored mail into mailbox 'INBOX'
Feb? 5 09:33:25 buzon1 dovecot: imap(user at domain): Error: Corrupted
transaction log file /.../Maildir/dovecot.index.log seq 1610: Invalid
transaction log size (28408 vs 28528): /.../Maildir/dovecot.index.log
(sync_offset=28408)
Feb? 5 09:33:25 buzon1 dovecot: imap(user at domain): Panic: file
mail-index-sync-keywo...
2014 Oct 29
1
different mail location in different namespace
...r:/buzon/archivo/%u/_ARCHIVO
prefix = _ARCHIVO.
hidden = yes
separator = .
type = private
}
We take the attribute "home directory" from the LDAP in the userdb attributes.
We would like to modify this attribute for the Namespace ARCHIVO.
For example, if a home directory is /buzon/buzon1/11111111, the mail location for ARCHIVO would be /buzon/archivo1/11111111.
Is this modification possible without adding another attribute at the LDAP (just editing the attribute)?
Thank you very much in advanced.
Kind regards.
H?ctor Moreno.
P Please consider the environment before printing th...
2019 Feb 15
4
index problems after update
...r sympa) processed a message for a user, its indexes were
> corrupted, and the user could't access his inbox through webmail, so I
> had to delete dovecot.* files from the user mail path to get it
> working again. This is the error shown at the dovecot log:
>
> Feb? 5 09:33:25 buzon1 dovecot: imap(user at domain): Panic: file
> mail-index-sync-keywords.c: line 227 (keywords_update_records):
> assertion failed: (data_offset >= sizeof(struct mail_index_record))
> Feb? 5 09:33:25 buzon1 dovecot: imap(user at domain): Error: Raw
> backtrace: /usr/lib64/dovecot/lib...
2019 Feb 15
0
index problems after update
...RHEL7 servers (used
for sympa) processed a message for a user, its indexes were corrupted,
and the user could't access his inbox through webmail, so I had to
delete dovecot.* files from the user mail path to get it working again.
This is the error shown at the dovecot log:
Feb? 5 09:33:25 buzon1 dovecot: imap(user at domain): Panic: file
mail-index-sync-keywords.c: line 227 (keywords_update_records):
assertion failed: (data_offset >= sizeof(struct mail_index_record))
Feb? 5 09:33:25 buzon1 dovecot: imap(user at domain): Error: Raw backtrace:
/usr/lib64/dovecot/libdovecot.so.0() [0x37...
2019 Feb 18
0
index problems after update
...message for a user, its indexes were
>> corrupted, and the user could't access his inbox through webmail, so
>> I had to delete dovecot.* files from the user mail path to get it
>> working again. This is the error shown at the dovecot log:
>>
>> Feb? 5 09:33:25 buzon1 dovecot: imap(user at domain): Panic: file
>> mail-index-sync-keywords.c: line 227 (keywords_update_records):
>> assertion failed: (data_offset >= sizeof(struct mail_index_record))
>> Feb? 5 09:33:25 buzon1 dovecot: imap(user at domain): Error: Raw
>> backtrace: /usr/l...
2019 Feb 15
2
index problems after update
Hello,
Am 11.02.2019 um 09:12 schrieb Hajo Locke via dovecot:
> Hello,
> Am 08.02.2019 um 09:25 schrieb Hajo Locke via dovecot:
>> Hello List,
>>
>> i have a problem with index-files which is separated in 2
>> subproblems. May be these problems are connected.
>> Currently we use Ubuntu 18.04 LTS which is bundled with dovecot 2.2.33.2
>> These servers are