We don’t have Cpanel. Sent from my iPhone
> On Mar 9, 2021, at 6:47 PM, John Tulp <johnt...@tulpholdings.com> 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=<user>, >> method=PLAIN, rip=10.5.1.77, lip=10.5.1.17, mpid=97537, TLS, >> session=<AvLvkCC9w9kKBQFN> >> 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=<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 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. >> #base_dir = /var/run/dovecot/ >> >> # Name of this instance. In multi-instance setup doveadm and other commands >> # can use -i <instance_name> to select which instance is used (an >> alternative >> # to -c <config_path>). The instance name is also added to Dovecot processes >> # in ps output. >> #instance_name = dovecot >> >> # Greeting message for clients. >> #login_greeting = Dovecot ready. >> >> # Space separated list of trusted network ranges. Connections from these >> # IPs are allowed to override their IP addresses and ports (for logging and >> # for authentication checks). disable_plaintext_auth is also ignored for >> # these networks. Typically you'd specify your IMAP proxy servers here. >> #login_trusted_networks = >> login_trusted_networks = 10.5.1.0/24 >> # Space separated list of login access check sockets (e.g. tcpwrap) >> #login_access_sockets = >> >> # With proxy_maybe=yes if proxy destination matches any of these IPs, >> don't do >> # proxying. This isn't necessary normally, but may be useful if the >> destination >> # IP is e.g. a load balancer's IP. >> #auth_proxy_self = >> >> # Show more verbose process titles (in ps). Currently shows user name and >> # IP address. Useful for seeing who are actually using the IMAP processes >> # (eg. shared mailboxes or if same uid is used for multiple accounts). >> #verbose_proctitle = no >> >> # Should all processes be killed when Dovecot master process shuts down. >> # Setting this to "no" means that Dovecot can be upgraded without >> # forcing existing client connections to close (although that could also be >> # a problem if the upgrade is e.g. because of a security fix). >> #shutdown_clients = yes >> >> # If non-zero, run mail commands via this many connections to doveadm >> server, >> # instead of running them directly in the same process. >> #doveadm_worker_count = 0 >> # UNIX socket or host:port used for connecting to doveadm server >> #doveadm_socket_path = doveadm-server >> >> # Space separated list of environment variables that are preserved on >> Dovecot >> # startup and passed down to all of its child processes. You can also give >> # key=value pairs to always set specific settings. >> #import_environment = TZ >> >> ## >> ## Dictionary server settings >> ## >> >> # Dictionary can be used to store key=value lists. This is used by several >> # plugins. The dictionary can be accessed either directly or though a >> # dictionary server. The following dict block maps dictionary names to URIs >> # when the server is used. These can then be referenced using URIs in format >> # "proxy::<name>". >> >> dict { >> #quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext >> #expire = sqlite:/etc/dovecot/dovecot-dict-sql.conf.ext >> } >> >> # Most of the actual configuration gets included below. The filenames are >> # first sorted by their ASCII value and parsed in that order. The >> 00-prefixes >> # in filenames are intended to make it easier to understand the ordering. >> !include conf.d/*.conf >> >> # A config file can also tried to be included without giving an error if >> # it's not found: >> !include_try local.conf >> ----------- >> >> I need assistance. I appreciate the help. >> >> Chris >> >> >> >> -- >> Christopher Wensink >> IS Administrator >> Five Star Plastics, Inc >> 1339 Continental Drive >> Eau Claire, WI 54701 >> Office: 715-831-1682 >> Mobile: 715-563-3112 >> Fax: 715-831-6075 >> cwens...@five-star-plastics.com >> www.five-star-plastics.com >> >> > > For what it's worth... I know less than nothing, but a quick search > turned up an apparent issue with cpanel which sounds similar: > > https://forums.cpanel.net/threads/dovecot-errors.626131/ > > John Tulp > >