Re: [qmailtoaster]Fixed - Outlook users get "unsupported encryption type" error after Windows update

2022-10-20 Thread Eric Broch 

it should

On 10/20/2022 1:36 AM, Tommi Järvilehto wrote:

yum update gives newer version from qmt-current repo
2.3.11.3-12.qt.el7
Does this have the fix?

On 17.10.2022 19.07, Jeff Koch wrote:
Eric - good news - upgrading Dovecot to the latest CDB version fixed 
the problem. Outlook users with the current updates can now get their 
IMAP (and I guess POP3) mail.


Thanks as always for your help.

Jeff Koch



On 10/15/2022 10:15 AM, Eric Broch wrote:


wget 
http://repo.whitehorsetc.com/7/spl/cdb/testing/x86_64/dovecot-2.3.7.2-9.qt.cdb.el7.x86_64.rpm


yum update 
http://repo.whitehorsetc.com/7/spl/cdb/testing/x86_64/dovecot-2.3.7.2-9.qt.cdb.el7.x86_64.rpm



On 10/15/2022 7:45 AM, Jeff Koch wrote:

Hi Eric - thanks for the rpm - can I just install it as is?

I'll configure my Windows 10 laptop today to run Outlook, advanced 
logging and see if I can trace a connection.


Jeff



On 10/15/2022 6:50 AM, Eric Broch wrote:


Actually, this is the latest one for cdb:

http://repo.whitehorsetc.com/7/spl/cdb/testing/x86_64/dovecot-2.3.7.2-9.qt.cdb.el7.x86_64.rpm

But if you're seeing nothing in the dovecot log, it means that 
there is no connection being made to the server from the PC which 
indicates something going on on the PC not the server.


Can you use tcpdump to see if any connection is being made. Tailor 
the command for the remote host and port.


You could also turn on advanced logging in Dovecot to troubleshoot.

Again, if nothing is in the Dovecot log, is a connection even 
being attempted by Outlook. If it is, is it being blocked by some 
Windows issue?


It'd be nice to know, if any traffic from the PC is even going 
across the network.



On 10/14/2022 9:10 PM, Jeff Koch wrote:

Hi Eric:

We're using dovecot-2.2.32-22.qt.el7.cdb.x86_64.rpm but I see the 
lastest qmt release is 2.3.11.3-12.qt.el7.  Would it do any good 
to upgrade?


Jeff

On 10/14/2022 7:38 PM, Eric Broch wrote:


What is in the Dovecot log?


On 10/13/2022 12:04 PM, Jeff Koch wrote:

Hi Eric:

Has anyone figured out what's going on and is this a good short 
term fix? We also have Outlook users that say they are not 
connecting to IMAP. However we use Dovecot IMAP and the SSL 
connection on port 993 says its using TLSv1.2


Jeff

On 10/12/2022 9:21 PM, Eric Broch wrote:


What version of qmt

On 10/12/2022 2:16 PM, Quinn Comendant wrote:


Today we received several complaints from Outlook users who 
are unable to connect to QMT servers. They get this error:


Task "u...@example.com - Sending: reported error
(Ox800CCC1A) :
'Your server does not support the connection encryption
type you have
specified. Try changing the encryption method. Contact
your mail server
administrator or internet service provider (ISP) for
additional assistance.'

The error began after installing Windows 10 servicing stack 
update - 19042.1940, 19043.1940, and 19044.1940 
, 
and the problem was fixed by uninstalling the update.


Has anyone else experienced this, or know what the problem 
could be? I hope there is a config change I can make on QMT 
servers so that users will not need to uninstall the update.


Quinn











--
Tommi Järvilehto
DataVahti Oy
040 732 8032

Re: [qmailtoaster]Fixed - Outlook users get "unsupported encryption type" error after Windows update

2022-10-20 Thread Tommi Järvilehto 

yum update gives newer version from qmt-current repo
2.3.11.3-12.qt.el7
Does this have the fix?

On 17.10.2022 19.07, Jeff Koch wrote:
Eric - good news - upgrading Dovecot to the latest CDB version fixed 
the problem. Outlook users with the current updates can now get their 
IMAP (and I guess POP3) mail.


Thanks as always for your help.

Jeff Koch



On 10/15/2022 10:15 AM, Eric Broch wrote:


wget 
http://repo.whitehorsetc.com/7/spl/cdb/testing/x86_64/dovecot-2.3.7.2-9.qt.cdb.el7.x86_64.rpm


yum update 
http://repo.whitehorsetc.com/7/spl/cdb/testing/x86_64/dovecot-2.3.7.2-9.qt.cdb.el7.x86_64.rpm



On 10/15/2022 7:45 AM, Jeff Koch wrote:

Hi Eric - thanks for the rpm - can I just install it as is?

I'll configure my Windows 10 laptop today to run Outlook, advanced 
logging and see if I can trace a connection.


Jeff



On 10/15/2022 6:50 AM, Eric Broch wrote:


Actually, this is the latest one for cdb:

http://repo.whitehorsetc.com/7/spl/cdb/testing/x86_64/dovecot-2.3.7.2-9.qt.cdb.el7.x86_64.rpm

But if you're seeing nothing in the dovecot log, it means that 
there is no connection being made to the server from the PC which 
indicates something going on on the PC not the server.


Can you use tcpdump to see if any connection is being made. Tailor 
the command for the remote host and port.


You could also turn on advanced logging in Dovecot to troubleshoot.

Again, if nothing is in the Dovecot log, is a connection even being 
attempted by Outlook. If it is, is it being blocked by some Windows 
issue?


It'd be nice to know, if any traffic from the PC is even going 
across the network.



On 10/14/2022 9:10 PM, Jeff Koch wrote:

Hi Eric:

We're using dovecot-2.2.32-22.qt.el7.cdb.x86_64.rpm but I see the 
lastest qmt release is 2.3.11.3-12.qt.el7.  Would it do any good 
to upgrade?


Jeff

On 10/14/2022 7:38 PM, Eric Broch wrote:


What is in the Dovecot log?


On 10/13/2022 12:04 PM, Jeff Koch wrote:

Hi Eric:

Has anyone figured out what's going on and is this a good short 
term fix? We also have Outlook users that say they are not 
connecting to IMAP. However we use Dovecot IMAP and the SSL 
connection on port 993 says its using TLSv1.2


Jeff

On 10/12/2022 9:21 PM, Eric Broch wrote:


What version of qmt

On 10/12/2022 2:16 PM, Quinn Comendant wrote:


Today we received several complaints from Outlook users who 
are unable to connect to QMT servers. They get this error:


Task "u...@example.com - Sending: reported error
(Ox800CCC1A) :
'Your server does not support the connection encryption
type you have
specified. Try changing the encryption method. Contact
your mail server
administrator or internet service provider (ISP) for
additional assistance.'

The error began after installing Windows 10 servicing stack 
update - 19042.1940, 19043.1940, and 19044.1940 
, 
and the problem was fixed by uninstalling the update.


Has anyone else experienced this, or know what the problem 
could be? I hope there is a config change I can make on QMT 
servers so that users will not need to uninstall the update.


Quinn











--
Tommi Järvilehto
DataVahti Oy
040 732 8032

[qmailtoaster] imapd 100% cpu please help me

2022-10-20 Thread Giuseppe Perna 
Hello,
i have the server freez becouse the imapd process (vpopmail) allocate 100%
CPU e small RAM.
Please help me.
thanks

#top
18711 vpopmail  18   0  3504 1188  676 D  1.7  0.0   0:04.71 imapd
20619 vpopmail  17   0  3556 1264  696 D  1.7  0.0   0:01.11 imapd
16117 vpopmail  18   0  4428 2096  696 D  1.3  0.0   0:26.84 imapd
17188 vpopmail  18   0  3892 1664  692 D  1.3  0.0   0:12.45 imapd
17146 vpopmail  18   0  3760 1476  676 D  1.0  0.0   0:21.32 imapd
17488 vpopmail  18   0  4356 2124  688 D  1.0  0.0   0:08.45 imapd
17491 vpopmail  18   0  5264 2984  740 D  1.0  0.0   0:08.70 imapd
17495 vpopmail  18   0  4356 2124  688 D  1.0  0.0   0:08.48 imapd
17728 vpopmail  18   0  3676 1404  680 D  1.0  0.0   0:07.16 imapd
18262 vpopmail  18   0  4360 2152  704 D  1.0  0.0   0:07.55 imapd
18364 vpopmail  18   0  3424 1068  680 D  1.0  0.0   0:07.53 imapd
18766 vpopmail  18   0  3284 1028  700 D  1.0  0.0   0:05.21 imapd
18851 vpopmail  18   0  3424 1068  680 D  1.0  0.0   0:07.23 imapd
15960 vpopmail  18   0  3760 1516  696 D  0.7  0.0   0:55.24 imapd
17096 vpopmail  18   0  3688 1456  700 D  0.7  0.0   0:17.46 imapd
17614 vpopmail  18   0  4360 2104  708 D  0.7  0.0   0:07.52 imapd
17616 vpopmail  18   0  3676 1436  688 D  0.7  0.0   0:06.25 imapd
17686 vpopmail  18   0  3476 1288  708 D  0.7  0.0   0:11.40 imapd
17783 vpopmail  18   0  3676 1400  680 D  0.7  0.0   0:06.71 imapd
18354 vpopmail  18   0  4364 2076  688 D  0.7  0.0   0:06.98 imapd
18361 vpopmail  18   0  3280 1016  680 D  0.7  0.0   0:05.11 imapd
18510 vpopmail  18   0  3148  928  688 D  0.7  0.0   0:07.66 imapd
18680 vpopmail  18   0  3664 1352  676 D  0.7  0.0   0:06.21 imapd
18800 vpopmail  18   0  3364 1068  676 D  0.7  0.0   0:02.88 imapd
18850 vpopmail  18   0  3892 1560  692 D  0.7  0.0   0:06.17 imapd
18880 vpopmail  18   0  3280 1032  700 D  0.7  0.0   0:04.76 imapd
18890 vpopmail  18   0  4012 1788  680 D  0.7  0.0   0:02.72 imapd


I have this old version CentOS release 5.8 (Final):

ucspi-tcp-toaster-0.88-1.3.9
maildrop-toaster-2.0.3-1.3.8
control-panel-toaster-0.5-1.4.0
libdomainkeys-toaster-0.68-1.3.6
qmail-pop3d-toaster-1.03-1.3.22
squirrelmail-toaster-1.4.20-1.3.17
qmailtoaster-plus.repo-0.2-2
vpopmail-toaster-5.4.33-1.4.0
daemontools-toaster-0.76-1.3.6
libsrs2-toaster-1.0.18-1.3.6
courier-authlib-toaster-0.59.2-1.3.10
ripmime-toaster-1.4.0.6-1.3.6
autorespond-toaster-2.0.5-1.4.0
courier-imap-toaster-4.1.2-1.3.10
isoqlog-toaster-2.1-1.3.7
maildrop-toaster-devel-2.0.3-1.3.8
qmailmrtg-toaster-4.2-1.3.7
send-emails-toaster-0.5-1.4.0
spamassassin-toaster-3.3.2-1.4.3
vqadmin-toaster-2.3.7-1.4.1
qmailtoaster-plus-0.3.2-1.4.19
ezmlm-toaster-0.53.324-1.3.6
qmail-toaster-1.03-1.3.22
ezmlm-cgi-toaster-0.53.324-1.3.6
qmailadmin-toaster-1.2.16-1.4.0
simscan-toaster-1.4.0-1.4.0
clamav-toaster-0.97.6-1.4.2