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&pasting 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 ar