Re: invalid vsize-hdr
On Tue, 2021-03-09 at 19:03 -0600, Chris Wensink wrote: > We don’t have Cpanel. > > Sent from my iPhone > > > On Mar 9, 2021, at 6:47 PM, John Tulp wrote: > > > > > >> On Tue, 2021-03-09 at 16:26 -0600, Christopher Wensink wrote: > >> Good afternoon everyone, > >> > >> I have one account on our internal dovecot server that keeps throwing > >> the same repeated error: > >> > >> The user is on a Windows 10 computer running the latest version of > >> Thunderbird. Here's the log: > >> > >> > >> Mar 9 13:03:16 mario2 dovecot: imap(pstrangfeld): Error: vsize-hdr has > >> invalid size: 36 > >> Mar 9 13:09:53 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > >> size: 36 > >> Mar 9 13:18:57 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > >> size: 36 > >> Mar 9 13:25:09 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > >> size: 36 > >> Mar 9 13:29:07 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > >> size: 36 > >> Mar 9 13:31:03 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > >> size: 36 > >> Mar 9 13:37:20 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > >> size: 36 > >> Mar 9 13:42:26 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > >> size: 36 > >> Mar 9 13:47:21 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > >> size: 36 > >> Mar 9 13:50:11 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > >> size: 36 > >> Mar 9 13:53:46 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > >> size: 36 > >> Mar 9 13:59:40 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > >> size: 36 > >> Mar 9 14:03:52 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > >> size: 36 > >> Mar 9 14:08:54 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > >> size: 36 > >> Mar 9 14:11:53 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > >> size: 36 > >> Mar 9 14:17:02 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > >> size: 36 > >> Mar 9 14:21:14 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > >> size: 36 > >> Mar 9 14:24:00 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > >> size: 36 > >> Mar 9 14:28:43 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > >> size: 36 > >> Mar 9 14:33:00 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > >> size: 36 > >> Mar 9 14:38:24 mario2 dovecot: imap(user): Connection closed (IDLE > >> running for 0.001 + waiting input for 0.001 secs, 2 B in + 10+10 B out, > >> state=wait-input) in=1578244 out=2878370 > >> Mar 9 14:40:51 mario2 dovecot: imap-login: Login: user=, > >> method=PLAIN, rip=10.5.1.77, lip=10.5.1.17, mpid=97537, TLS, > >> session= > >> Mar 9 14:41:30 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > >> size: 36 > >> Mar 9 14:44:14 mario2 dovecot: imap(user): Connection closed (IDLE > >> running for 0.002 + waiting input for 0.001 secs, 2 B in + 10+10 B out, > >> state=wait-input) in=319541 out=1272761 > >> Mar 9 14:44:14 mario2 dovecot: imap-login: Login: user=, > >> method=PLAIN, rip=10.5.1.77, lip=10.5.1.17, mpid=97671, TLS, > >> session=<85YInSC95NkKBQFN> > >> Mar 9 14:46:37 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > >> size: 36 > >> --- > >> > >> I have tried the following: > >> -Restarting the workstation > >> - Compacting folders in Thunderbird > >> - Repaired the Inbox Folder in Thunderbird > >> - Restarting the dovecot service > >> - Set the connections in Thunderbird Account settings to not check for > >> messages automatically (manual only) > >> - Set the user to own all folders and sub-folders in his home > >> directory on the server > >> > >> I found old message in the archives from 2017 that had the same error > >> but I did not see a posted solution. > >> > >> dovecot --version 2.2.36 (lfl0bfa63) > >> > >> config file: > >> > >> [root@mario2 dovecot]# cat dovecot.conf > >> ## Dovecot configuration file > >> > >> # If you're in a hurry, see http://wiki2.dovecot.org/QuickConfiguration > >> > >> # "doveconf -n" command gives a clean output of the changed settings. Use > >> it > >> # instead of copy files when posting to the Dovecot mailing list. > >> > >> # '#' character and everything after it is treated as comments. Extra > >> spaces > >> # and tabs are ignored. If you want to use either of these explicitly, > >> put the > >> # value inside quotes, eg.: key = "# char and trailing whitespace " > >> > >> # Most (but not all) settings can be overridden by different protocols > >> and/or > >> # source/destination IPs by placing the settings inside sections, for > >> example: > >> # protocol imap { }, local 127.0.0.1 { }, remote 10.0.0.0/8 { } > >> > >> # Default values are shown for each setting, it's not required to uncomment >
Re: invalid vsize-hdr
> On 10/03/2021 00:26 Christopher Wensink > wrote: > > > Good afternoon everyone, > > I have one account on our internal dovecot server that keeps throwing > the same repeated error: > > The user is on a Windows 10 computer running the latest version of > Thunderbird. Here's the log: > > > Mar 9 13:03:16 mario2 dovecot: imap(pstrangfeld): Error: vsize-hdr has > invalid size: 36 > Mar 9 13:09:53 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 13:18:57 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 13:25:09 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 13:29:07 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 13:31:03 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 13:37:20 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 13:42:26 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 13:47:21 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 13:50:11 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 13:53:46 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 13:59:40 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 14:03:52 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 14:08:54 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 14:11:53 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 14:17:02 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 14:21:14 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 14:24:00 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 14:28:43 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 14:33:00 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 14:38:24 mario2 dovecot: imap(user): Connection closed (IDLE > running for 0.001 + waiting input for 0.001 secs, 2 B in + 10+10 B out, > state=wait-input) in=1578244 out=2878370 > Mar 9 14:40:51 mario2 dovecot: imap-login: Login: user=, > method=PLAIN, rip=10.5.1.77, lip=10.5.1.17, mpid=97537, TLS, > session= > Mar 9 14:41:30 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 14:44:14 mario2 dovecot: imap(user): Connection closed (IDLE > running for 0.002 + waiting input for 0.001 secs, 2 B in + 10+10 B out, > state=wait-input) in=319541 out=1272761 > Mar 9 14:44:14 mario2 dovecot: imap-login: Login: user=, > method=PLAIN, rip=10.5.1.77, lip=10.5.1.17, mpid=97671, TLS, > session=<85YInSC95NkKBQFN> > Mar 9 14:46:37 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > --- > > I have tried the following: > -Restarting the workstation > - Compacting folders in Thunderbird > - Repaired the Inbox Folder in Thunderbird > - Restarting the dovecot service > - Set the connections in Thunderbird Account settings to not check for > messages automatically (manual only) > - Set the user to own all folders and sub-folders in his home > directory on the server > > I found old message in the archives from 2017 that had the same error > but I did not see a posted solution. > > dovecot --version 2.2.36 (lfl0bfa63) > > config file: > > [root@mario2 dovecot]# cat dovecot.conf > ## Dovecot configuration file > > # If you're in a hurry, see http://wiki2.dovecot.org/QuickConfiguration > > # "doveconf -n" command gives a clean output of the changed settings. Use it > # instead of copy files when posting to the Dovecot mailing list. > > # '#' character and everything after it is treated as comments. Extra spaces > # and tabs are ignored. If you want to use either of these explicitly, > put the > # value inside quotes, eg.: key = "# char and trailing whitespace " > > # Most (but not all) settings can be overridden by different protocols > and/or > # source/destination IPs by placing the settings inside sections, for > example: > # protocol imap { }, local 127.0.0.1 { }, remote 10.0.0.0/8 { } > > # Default values are shown for each setting, it's not required to uncomment > # those. These are exceptions to this though: No sections (e.g. > namespace {}) > # or plugin settings are added by default, they're listed only as examples. > # Paths are also just examples with the real defaults being based on > configure > # options. The paths listed here are for configure --prefix=/usr > # --sysconfdir=/etc --localstatedir=/var > > # Protocols we want to be serving. > #protocols = imap pop3 lmtp > protocols = imap pop3 > # A comma separated list of IPs or hosts
Re: JMAP support?
On 8. Mar 2021, at 8.11, Mark Constable wrote: > Two years on so what is the status of JMAP support in Dovecot now? Lots of work, and nobody really seems to want it that much, so we're not actively working on it. There are also some generic optimization and code cleanup steps along the way that are slowly happening, and after those it should be easier to implement JMAP (or some other HTTP based protocol).
Re: invalid vsize-hdr
On 9. Mar 2021, at 23.26, Christopher Wensinkwrote:Mar 9 13:29:07 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36Looks like the index file is a bit broken for whatever reason. You could delete it (which would lose flags if you're using dbox) or you could use the attached script to run:dovecot-index-log.py --file /path/to/broken/folder/dovecot.index.log --ext_hdr_shrink --add_ext_intro hdr-vsize --add_ext_hdr Of course at some point we'll need to fix the code to fix it automatically..#!/usr/bin/env python3 from struct import unpack, unpack_from, pack from collections import namedtuple from optparse import OptionParser import binascii def pad4(payload): pad = 4 - (len(payload) % 4) if pad == 4: return payload return payload.ljust(len(payload)+pad, b'\x00') class DovecotIndexSect(object): ExtIntroHeader = namedtuple("IntroHeader", "ext_id reset_id hdr_size record_size record_align flags name_size name") KIND_TO_TEXT = { 0x0001 | 0xcd90: "EXPUNGE", 0x0002: "APPEND", 0x0004: "FLAG_UPDATE", 0x0020: "HEADER_UPDATE", 0x0040: "EXT_INTRO", 0x0080: "EXT_RESET", 0x0100: "EXT_HDR_UPDATE", 0x0200: "EXT_REC_UPDATE", 0x0400: "KEYWORD_UPDATE", 0x0800: "KEYWORD_RESET", 0x1000: "EXT_ATOMIC_INC", 0x2000 | 0xcd90: "EXPUNGE_GUID", 0x8000: "MODSEQ_UPDATE", 0x0001: "EXT_HDR_UPDATE32", 0x0002: "INDEX_DELETED", 0x0004: "INDEX_UNDELETED", 0x0008: "BOUNDARY", 0x0010: "ATTRIBUTE_UPDATE", } def __init__(self, log, kind): self.log = log self.kind = kind self.mod = kind & ~(0x0fff) self.type = kind & 0x0fff self.ext_id = 0 self.name = "" self.str = "" def __str__(self): return self.KIND_TO_TEXT[self.type] + " " + self.str def parse_EXPUNGE(self): (self.uid1, self.uid2) = unpack_from("II", self.data) def ext_get_name(self): if self.ext_id > 0 and len(self.log.ext_names) >= self.ext_id: self.name = self.log.ext_names[self.ext_id-1] else: self.name = "" def parse_EXT_INTRO(self): self.hdr = self.ExtIntroHeader._make(unpack_from("III", self.data) + ("",)) name = self.data[20:20+self.hdr.name_size].decode() self.hdr = self.hdr._replace(name = name) self.ext_id = self.hdr.ext_id if self.ext_id == 4294967295: self.ext_id = -1 self.name = name if self.ext_id < 0: if name in self.log.ext_names: self.ext_id = self.log.ext_names.index(name)+1 else: self.ext_id = len(self.log.ext_names)+1 self.log.ext_names += [name] elif self.ext_id > 0: self.ext_get_name() self.log.last_ext_id = self.ext_id self.str = "(name=%s, ext_id=%u)" % (self.name, self.ext_id) def parse_EXT_HDR_UPDATE32(self): self.ext_id = self.log.last_ext_id self.ext_get_name() (self.offset, self.len) = unpack_from("II", self.data) self.str = "(name=%s, ext_id=%u, offset=%u, len=%u, data=%s" % (self.name,self.ext_id,self.offset,self.len,binascii.hexlify(self.data[8:8+self.len]).decode()) def parse_EXT_HDR_UPDATE(self): self.ext_id = self.log.last_ext_id self.ext_get_name() (self.offset, self.len) = unpack_from("HH", self.data) self.str = "(name=%s, ext_id=%u, offset=%u, len=%u, data=%s)" % (self.name,self.ext_id,self.offset,self.len,binascii.hexlify(self.data[4:4+self.len]).decode()) def parse_EXT_REC_UPDATE(self): self.ext_id = self.log.last_ext_id self.ext_get_name() (self.uid,) = unpack_from("I", self.data) self.str = "(name=%s, ext_id=%u, uid=%u)" % (self.name,self.ext_id,self.uid) def parse(self): meth = "parse_%s" % (self.KIND_TO_TEXT[self.type]) meth = getattr(self, "parse_%s" % (self.KIND_TO_TEXT[self.type]), None) if meth and callable(meth): meth() class DovecotIndexLog(object): LogHeader = namedtuple("LogHeader", "major minor hdr_size indexid file_seq prev_file_seq prev_file_offset create_stamp initial_modseq compat_flags unused unused2") def __init__(self, fn): self.fn = fn self.ext_names = [] self.sections = {} self.parse() def uint32_to_offset(self, offset): offset >>= 2 offset = 0x0080 | (offset & 0x007f) | 0x8000 | ((offset & 0x3f80) >> 7 << 8) | 0x0080 | ((offset & 0x001fc000) >> 14 << 16) | 0x8000 | ((offset & 0x0fe0) >> 21 << 24) return offset def offset_to_uint32(self, offset): if ((offset & 0x80808080) != 0x80808080): return 0 return
Re: invalid vsize-hdr
We don’t have Cpanel. Sent from my iPhone > On Mar 9, 2021, at 6:47 PM, John Tulp wrote: > > >> On Tue, 2021-03-09 at 16:26 -0600, Christopher Wensink wrote: >> Good afternoon everyone, >> >> I have one account on our internal dovecot server that keeps throwing >> the same repeated error: >> >> The user is on a Windows 10 computer running the latest version of >> Thunderbird. Here's the log: >> >> >> Mar 9 13:03:16 mario2 dovecot: imap(pstrangfeld): Error: vsize-hdr has >> invalid size: 36 >> Mar 9 13:09:53 mario2 dovecot: imap(user): Error: vsize-hdr has invalid >> size: 36 >> Mar 9 13:18:57 mario2 dovecot: imap(user): Error: vsize-hdr has invalid >> size: 36 >> Mar 9 13:25:09 mario2 dovecot: imap(user): Error: vsize-hdr has invalid >> size: 36 >> Mar 9 13:29:07 mario2 dovecot: imap(user): Error: vsize-hdr has invalid >> size: 36 >> Mar 9 13:31:03 mario2 dovecot: imap(user): Error: vsize-hdr has invalid >> size: 36 >> Mar 9 13:37:20 mario2 dovecot: imap(user): Error: vsize-hdr has invalid >> size: 36 >> Mar 9 13:42:26 mario2 dovecot: imap(user): Error: vsize-hdr has invalid >> size: 36 >> Mar 9 13:47:21 mario2 dovecot: imap(user): Error: vsize-hdr has invalid >> size: 36 >> Mar 9 13:50:11 mario2 dovecot: imap(user): Error: vsize-hdr has invalid >> size: 36 >> Mar 9 13:53:46 mario2 dovecot: imap(user): Error: vsize-hdr has invalid >> size: 36 >> Mar 9 13:59:40 mario2 dovecot: imap(user): Error: vsize-hdr has invalid >> size: 36 >> Mar 9 14:03:52 mario2 dovecot: imap(user): Error: vsize-hdr has invalid >> size: 36 >> Mar 9 14:08:54 mario2 dovecot: imap(user): Error: vsize-hdr has invalid >> size: 36 >> Mar 9 14:11:53 mario2 dovecot: imap(user): Error: vsize-hdr has invalid >> size: 36 >> Mar 9 14:17:02 mario2 dovecot: imap(user): Error: vsize-hdr has invalid >> size: 36 >> Mar 9 14:21:14 mario2 dovecot: imap(user): Error: vsize-hdr has invalid >> size: 36 >> Mar 9 14:24:00 mario2 dovecot: imap(user): Error: vsize-hdr has invalid >> size: 36 >> Mar 9 14:28:43 mario2 dovecot: imap(user): Error: vsize-hdr has invalid >> size: 36 >> Mar 9 14:33:00 mario2 dovecot: imap(user): Error: vsize-hdr has invalid >> size: 36 >> Mar 9 14:38:24 mario2 dovecot: imap(user): Connection closed (IDLE >> running for 0.001 + waiting input for 0.001 secs, 2 B in + 10+10 B out, >> state=wait-input) in=1578244 out=2878370 >> Mar 9 14:40:51 mario2 dovecot: imap-login: Login: user=, >> method=PLAIN, rip=10.5.1.77, lip=10.5.1.17, mpid=97537, TLS, >> session= >> Mar 9 14:41:30 mario2 dovecot: imap(user): Error: vsize-hdr has invalid >> size: 36 >> Mar 9 14:44:14 mario2 dovecot: imap(user): Connection closed (IDLE >> running for 0.002 + waiting input for 0.001 secs, 2 B in + 10+10 B out, >> state=wait-input) in=319541 out=1272761 >> Mar 9 14:44:14 mario2 dovecot: imap-login: Login: user=, >> method=PLAIN, rip=10.5.1.77, lip=10.5.1.17, mpid=97671, TLS, >> session=<85YInSC95NkKBQFN> >> Mar 9 14:46:37 mario2 dovecot: imap(user): Error: vsize-hdr has invalid >> size: 36 >> --- >> >> I have tried the following: >> -Restarting the workstation >> - Compacting folders in Thunderbird >> - Repaired the Inbox Folder in Thunderbird >> - Restarting the dovecot service >> - Set the connections in Thunderbird Account settings to not check for >> messages automatically (manual only) >> - Set the user to own all folders and sub-folders in his home >> directory on the server >> >> I found old message in the archives from 2017 that had the same error >> but I did not see a posted solution. >> >> dovecot --version 2.2.36 (lfl0bfa63) >> >> config file: >> >> [root@mario2 dovecot]# cat dovecot.conf >> ## Dovecot configuration file >> >> # If you're in a hurry, see http://wiki2.dovecot.org/QuickConfiguration >> >> # "doveconf -n" command gives a clean output of the changed settings. Use it >> # instead of copy files when posting to the Dovecot mailing list. >> >> # '#' character and everything after it is treated as comments. Extra spaces >> # and tabs are ignored. If you want to use either of these explicitly, >> put the >> # value inside quotes, eg.: key = "# char and trailing whitespace " >> >> # Most (but not all) settings can be overridden by different protocols >> and/or >> # source/destination IPs by placing the settings inside sections, for >> example: >> # protocol imap { }, local 127.0.0.1 { }, remote 10.0.0.0/8 { } >> >> # Default values are shown for each setting, it's not required to uncomment >> # those. These are exceptions to this though: No sections (e.g. >> namespace {}) >> # or plugin settings are added by default, they're listed only as examples. >> # Paths are also just examples with the real defaults being based on >> configure >> # options. The paths listed here are for
Re: invalid vsize-hdr
On Tue, 2021-03-09 at 16:26 -0600, Christopher Wensink wrote: > Good afternoon everyone, > > I have one account on our internal dovecot server that keeps throwing > the same repeated error: > > The user is on a Windows 10 computer running the latest version of > Thunderbird. Here's the log: > > > Mar 9 13:03:16 mario2 dovecot: imap(pstrangfeld): Error: vsize-hdr has > invalid size: 36 > Mar 9 13:09:53 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 13:18:57 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 13:25:09 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 13:29:07 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 13:31:03 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 13:37:20 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 13:42:26 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 13:47:21 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 13:50:11 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 13:53:46 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 13:59:40 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 14:03:52 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 14:08:54 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 14:11:53 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 14:17:02 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 14:21:14 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 14:24:00 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 14:28:43 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 14:33:00 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 14:38:24 mario2 dovecot: imap(user): Connection closed (IDLE > running for 0.001 + waiting input for 0.001 secs, 2 B in + 10+10 B out, > state=wait-input) in=1578244 out=2878370 > Mar 9 14:40:51 mario2 dovecot: imap-login: Login: user=, > method=PLAIN, rip=10.5.1.77, lip=10.5.1.17, mpid=97537, TLS, > session= > Mar 9 14:41:30 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > Mar 9 14:44:14 mario2 dovecot: imap(user): Connection closed (IDLE > running for 0.002 + waiting input for 0.001 secs, 2 B in + 10+10 B out, > state=wait-input) in=319541 out=1272761 > Mar 9 14:44:14 mario2 dovecot: imap-login: Login: user=, > method=PLAIN, rip=10.5.1.77, lip=10.5.1.17, mpid=97671, TLS, > session=<85YInSC95NkKBQFN> > Mar 9 14:46:37 mario2 dovecot: imap(user): Error: vsize-hdr has invalid > size: 36 > --- > > I have tried the following: > -Restarting the workstation > - Compacting folders in Thunderbird > - Repaired the Inbox Folder in Thunderbird > - Restarting the dovecot service > - Set the connections in Thunderbird Account settings to not check for > messages automatically (manual only) > - Set the user to own all folders and sub-folders in his home > directory on the server > > I found old message in the archives from 2017 that had the same error > but I did not see a posted solution. > > dovecot --version 2.2.36 (lfl0bfa63) > > config file: > > [root@mario2 dovecot]# cat dovecot.conf > ## Dovecot configuration file > > # If you're in a hurry, see http://wiki2.dovecot.org/QuickConfiguration > > # "doveconf -n" command gives a clean output of the changed settings. Use it > # instead of copy files when posting to the Dovecot mailing list. > > # '#' character and everything after it is treated as comments. Extra spaces > # and tabs are ignored. If you want to use either of these explicitly, > put the > # value inside quotes, eg.: key = "# char and trailing whitespace " > > # Most (but not all) settings can be overridden by different protocols > and/or > # source/destination IPs by placing the settings inside sections, for > example: > # protocol imap { }, local 127.0.0.1 { }, remote 10.0.0.0/8 { } > > # Default values are shown for each setting, it's not required to uncomment > # those. These are exceptions to this though: No sections (e.g. > namespace {}) > # or plugin settings are added by default, they're listed only as examples. > # Paths are also just examples with the real defaults being based on > configure > # options. The paths listed here are for configure --prefix=/usr > # --sysconfdir=/etc --localstatedir=/var > > # Protocols we want to be serving. > #protocols = imap pop3 lmtp > protocols = imap pop3 > # A comma separated list of IPs or hosts
invalid vsize-hdr
Good afternoon everyone, I have one account on our internal dovecot server that keeps throwing the same repeated error: The user is on a Windows 10 computer running the latest version of Thunderbird. Here's the log: Mar 9 13:03:16 mario2 dovecot: imap(pstrangfeld): Error: vsize-hdr has invalid size: 36 Mar 9 13:09:53 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 13:18:57 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 13:25:09 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 13:29:07 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 13:31:03 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 13:37:20 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 13:42:26 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 13:47:21 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 13:50:11 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 13:53:46 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 13:59:40 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 14:03:52 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 14:08:54 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 14:11:53 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 14:17:02 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 14:21:14 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 14:24:00 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 14:28:43 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 14:33:00 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 14:38:24 mario2 dovecot: imap(user): Connection closed (IDLE running for 0.001 + waiting input for 0.001 secs, 2 B in + 10+10 B out, state=wait-input) in=1578244 out=2878370 Mar 9 14:40:51 mario2 dovecot: imap-login: Login: user=, method=PLAIN, rip=10.5.1.77, lip=10.5.1.17, mpid=97537, TLS, session= Mar 9 14:41:30 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 Mar 9 14:44:14 mario2 dovecot: imap(user): Connection closed (IDLE running for 0.002 + waiting input for 0.001 secs, 2 B in + 10+10 B out, state=wait-input) in=319541 out=1272761 Mar 9 14:44:14 mario2 dovecot: imap-login: Login: user=, method=PLAIN, rip=10.5.1.77, lip=10.5.1.17, mpid=97671, TLS, session=<85YInSC95NkKBQFN> Mar 9 14:46:37 mario2 dovecot: imap(user): Error: vsize-hdr has invalid size: 36 --- I have tried the following: -Restarting the workstation - Compacting folders in Thunderbird - Repaired the Inbox Folder in Thunderbird - Restarting the dovecot service - Set the connections in Thunderbird Account settings to not check for messages automatically (manual only) - Set the user to own all folders and sub-folders in his home directory on the server I found old message in the archives from 2017 that had the same error but I did not see a posted solution. dovecot --version 2.2.36 (lfl0bfa63) config file: [root@mario2 dovecot]# cat dovecot.conf ## Dovecot configuration file # If you're in a hurry, see http://wiki2.dovecot.org/QuickConfiguration # "doveconf -n" command gives a clean output of the changed settings. Use it # instead of copy files when posting to the Dovecot mailing list. # '#' character and everything after it is treated as comments. Extra spaces # and tabs are ignored. If you want to use either of these explicitly, put the # value inside quotes, eg.: key = "# char and trailing whitespace " # Most (but not all) settings can be overridden by different protocols and/or # source/destination IPs by placing the settings inside sections, for example: # protocol imap { }, local 127.0.0.1 { }, remote 10.0.0.0/8 { } # Default values are shown for each setting, it's not required to uncomment # those. These are exceptions to this though: No sections (e.g. namespace {}) # or plugin settings are added by default, they're listed only as examples. # Paths are also just examples with the real defaults being based on configure # options. The paths listed here are for configure --prefix=/usr # --sysconfdir=/etc --localstatedir=/var # Protocols we want to be serving. #protocols = imap pop3 lmtp protocols = imap pop3 # A comma separated list of IPs or hosts where to listen in for connections. # "*" listens in all IPv4 interfaces, "::" listens in all IPv6 interfaces. # If you want to specify non-default ports or anything more complex, # edit conf.d/master.conf. #listen = *, :: listen = *, :: # Base directory where to store runtime data.
Re: Virtual users @ virtual domains / better documentation?
> I have configured postfix so it will deliver mail to virtual mailboxes. For > some reason, the mail is not delivered to the virtual mailboxes unless both > $virtual_alias_domains and $virtual_alias_maps are left undefined: these > directives are apparently for aliasing virtual users "@" virtual domains to > "real" unix users on the local system. > > --%%== > # ADDRESS REDIRECTION (VIRTUAL DOMAIN) > # > # The VIRTUAL_README document gives information about the many forms > # of domain hosting that Postfix supports. > virtual_mailbox_domains = domain1.example.org domain2.example.com > virtual_transport = virtual > #virtual_alias_domains = domain1.example.org domain2.example.com > virtual_mailbox_base = /var/mail/vhosts > virtual_mailbox_maps = hash:/etc/postfix/vmailbox > virtual_minimum_uid = 100 > virtual_uid_maps = static:5000 > virtual_gid_maps = static:5000 > #virtual_alias_maps = hash:/etc/postfix/virtual > ==%-- First of all I won't recommend using native postfix 'virtual' delivery agent, if you already have dovecot as the mailbox server. It will work ok, as long as you use standard mailbox or maildir store in dovecot, but does not allow to use some dovecot-specific options, does not allow more modern storage formats (dbox), does not update indexes at delivery time and does not allow to run sieve scripts. IMO it's better to use either dovecot-lda configured as a postfix 'pipe' service, or LMTP. > If the $virtual_alias_maps directive invalidates virtual mailboxes, then "the > usual" aliases (postmaster@, etc.) for the virtual domains would have to be > listed in > /etc/aliases > along with the non-virtual aliases, but this does not work either, and > generates a warning when "newaliases" is run. > > postalias: warning: /etc/aliases, line 99: name must be local > > So as far as I can tell, no aliasing at all is available for > "virtual_mailbox_domains" in postfix Yes, there's no easy way to do aliases in postfix for a domain that's declared as virtual_mailbox. You can alias virtual_mailbox domain addresses to local adresses, virtual_alias to virtual_mailbox, but not virtual_mailbox to virtual_mailbox, if I am correct. If you switch to dovecot-lda or LMTP, the aliases are best handled on the dovecot side by appropriate userdb setup. Using a database is handy. You could also setup virtual_mailbox_maps in postfix to use the same database so you have the same source of data. For my small setup I use sqlite, but one could use mysql. > I am still unsure how to authenticate the virtual users on postfix. PAM > authentication works fine for non-virtual users. The following command > gives two options for authentication: cyrus-sasl and dovecot-sasl. > > # postconf -a > cyrus > dovecot > Use smtpd_sasl_* settings and configure dovecot to provide auth listener socket (either UNIX or TCP). -- Piotr "Malgond" Auksztulewicz firstn...@lastname.net
Virtual users @ virtual domains / better documentation?
I have configured postfix so it will deliver mail to virtual mailboxes. For some reason, the mail is not delivered to the virtual mailboxes unless both $virtual_alias_domains and $virtual_alias_maps are left undefined: these directives are apparently for aliasing virtual users "@" virtual domains to "real" unix users on the local system. --%%== # ADDRESS REDIRECTION (VIRTUAL DOMAIN) # # The VIRTUAL_README document gives information about the many forms # of domain hosting that Postfix supports. virtual_mailbox_domains = domain1.example.org domain2.example.com virtual_transport = virtual #virtual_alias_domains = domain1.example.org domain2.example.com virtual_mailbox_base = /var/mail/vhosts virtual_mailbox_maps = hash:/etc/postfix/vmailbox virtual_minimum_uid = 100 virtual_uid_maps = static:5000 virtual_gid_maps = static:5000 #virtual_alias_maps = hash:/etc/postfix/virtual ==%-- If the $virtual_alias_maps directive invalidates virtual mailboxes, then "the usual" aliases (postmaster@, etc.) for the virtual domains would have to be listed in /etc/aliases along with the non-virtual aliases, but this does not work either, and generates a warning when "newaliases" is run. postalias: warning: /etc/aliases, line 99: name must be local So as far as I can tell, no aliasing at all is available for "virtual_mailbox_domains" in postfix I am still unsure how to authenticate the virtual users on postfix. PAM authentication works fine for non-virtual users. The following command gives two options for authentication: cyrus-sasl and dovecot-sasl. # postconf -a cyrus dovecot Postfix also works with cyrus-sasl if the passwords are set in "/etc/sasldb2" via the "saslpasswd2" command, but dovecot doesn't seem to work with cyrus-sasl, and has its own type of sasl authentication. I realize this is not a postfix list, so my real question here is, What do I need in order for dovecot to authenticate the virtual users and allow them to read their mail and obtain authorization to send mail via postfix on the same system? signature.asc Description: This is a digitally signed message part.
Re: JMAP support?
Em 09/03/2021 05:43, Jean-Daniel escreveu: Hi. The HTTP API is just for doveadm and is not related in anyway to JMAP AFAIK. Are there any web-admin for dovecot/doveadm? Thanks -- _Engº Julio Cesar Covolato 0v0 /(_)\ F: 55-11-99175-9260 ^ ^ PSI INTERNET --
Re: DMARC problems with some emails from the list
On 09.03.21 17:00, Benny Pedersen wrote: > ARC test can be skipped if ORIGINATING dkim signed DKIM signature gives > PASS > > your mail here gives DKIM PASS in perl Mail::DKIM > > but > > ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; > d=dovecot.org; > s=arc; t=1615272934; > h=from:from:reply-to:subject:subject:date:date:message-id:message-id: > to:to:cc:mime-version:mime-version:content-type:content-type: > content-transfer-encoding:content-transfer-encoding: > in-reply-to:in-reply-to:references:references:dkim-signature; > > is with double headers sign in ARC :( > > is owners listen here ? Again, there is and should be no problem with double header signing. And even if there would be a problem with it, the ARC-Message-Signature will be ignored by 99% of mail handling applications... I really don't get your point and it seems to me you didn't understand the OP's problem. Cheers, Juri
Re: DMARC problems with some emails from the list
On 2021-03-09 07:55, Ángel L. Mateo wrote: I don't know the exact details of the antispam configuration. But I have asked and the administrator told me that we are not doing ARC tests. He told me that the emails are marked as spam because of dkim failures. ARC test can be skipped if ORIGINATING dkim signed DKIM signature gives PASS your mail here gives DKIM PASS in perl Mail::DKIM but ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=dovecot.org; s=arc; t=1615272934; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; is with double headers sign in ARC :( is owners listen here ?
Re: DMARC problems with some emails from the list
On 2021-03-08 13:21, Juri Haberland wrote: On 08.03.21 11:38, Benny Pedersen wrote: On 2021-03-08 10:34, Juri Haberland wrote: checked your dkim signing, it have signed 2 Date headers, 2 From, 2 Subject, solve this :=) Benny, it's not about *my* DKIM signature. And it is perfectly legal and has a special purpose to double sign some headers, called oversigning. h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; double header signing on top of that C= with simple it could be a bug in perl Mail::DKIM, but so far spamassassin give dkim invalid eof my help with it
Re: JMAP support?
The HTTP API is just for doveadm and is not related in anyway to JMAP AFAIK. > Le 8 mars 2021 à 23:52, Philip a écrit : > > Didn't JMAP get included with v2.3 with the HTTP API? > > https://www.dovecot.org/list/dovecot-news/2016-March/000313.html > > Or maybe that was just for admin things. > > Phil > > On 09/03/2021 11:26, @lbutlr wrote: >> On 08 Mar 2021, at 14:04, Leonardo Rodrigues >> wrote: >>> Em 08/03/2021 16:43, @lbutlr escreveu: On 08 Mar 2021, at 02:15, Mark Constable wrote: There doesn't seem to be much interest in JMAP ou there, which means it is going to be pretty hard to get something working well unless you write it yourself. >>> Or sponsor its development, if the OP is so interested on it! >> I checked and Roundcube-next appears to be a dead project, so I'd really not >> hold out much hope. >>