Hi Eric - just added auth_debug=yes to the end of
/etc/dovecot/toaster.conf. The dovecot log is showing auth: Debug
Let me know when you test - thanks - Jeff
On 9/3/2021 10:25 AM, Eric Broch wrote:
When you get advanced logging for dovecot done let me know I'll test
again.
Here are my settings for squirrelmail in
/etc/squirrelmail/config_local.php
# imap server options
$imapServerAddress = 'localhost';
$imap_server_type = 'dovecot';
# SM doesn't support starttls until v1.5.1, so we'll use digest-md5
til then
$imap_auth_mech = 'login';
On 9/2/2021 5:47 PM, Eric Broch wrote:
You can change squirrelmail config
On Sep 2, 2021, at 5:11 PM, Jeff Koch <jeffk...@intersessions.com
<mailto:jeffk...@intersessions.com>> wrote:
Hi Eric - tried removing digest-md5 and cram-md5. Found out
squirrelmail webmail won't work unless digest-md5 is in the
auth_mechanisms
Jeff
On 9/2/2021 10:31 AM, Eric Broch wrote:
both have
auth_mechanisms = plain login
On 9/2/2021 8:29 AM, Eric Broch wrote:
I have a 2 QMT 7 servers and they both work with
dovecot-2.3.11.3-12.qt.el7.x86_64
On 9/2/2021 7:55 AM, Jeff Koch wrote:
Hi Eric:
We'll try doing that but is this a problem with only our
mailserver or all QMT 7 mailservers?
Jeff
On 9/2/2021 9:44 AM, Eric Broch wrote:
Next to the check when entering the settings there is a
question mark circled to the left. Clicking that gives a menu
with 'Collect Diagnostics' & 'Contact Support'
On 9/2/2021 7:42 AM, Eric Broch wrote:
When the popup indicates a connection issue I push 'support'
button and error suggests a certificate issue. Two options
appear at this point: 'Talk to Agent' & 'OK'. If you 'talk
to an agent' you can do more advanced troublshooting like
sending an Outlook error log file to them. You might try this.
Eric
On 9/2/2021 7:11 AM, Jeff Koch wrote:
I could be wrong but I think Outlook for Android must be
very sensitive to the encryption ciphers being used and the
SSL/TLS versions. We use Let's Encrypt certificates - I
wonder if it's anything to do with that.
Jeff
On 9/2/2021 1:16 AM, Remo Mattei wrote:
I just found out to have the same issue from one of my
client.
Il giorno 2 set 2021, alle ore 02:49, Eric Broch
<ebr...@whitehorsetc.com> ha scritto:
Try this script (replace with relevant user, password, &
host) from the command line of the server. It will yield
what version of TLS you're running.
<script>
#!/bin/bash
function imapscript () {
echo "a login $1 $2"
echo 'a logout'
sleep 1
echo 'quit'
}
user=some...@mydomain.com
pass=***********
host=mail.mydomain.com
imapscript "$user" $pass | openssl s_client -crlf
-connect $host:993
</script>
On 9/1/2021 6:29 PM, Eric Broch wrote:
Does your web mail work?
On Sep 1, 2021, at 5:12 PM, Jeff Koch <
jeffk...@intersessions.com
<mailto:jeffk...@intersessions.com>> wrote:
Neither IMAP or IMAPS will connect - Jeff
On 9/1/2021 6:16 PM, Eric Broch wrote:
What protocol, IMAP, IMAPS, SMTPS...?
On 9/1/2021 2:36 PM, Jeff Koch wrote:
We have a customer trying to connect to his
qmail-toaster email account using the MicroSoft
Outlook app on an Android phone. He keeps getting
bounced off with the message 'can't connect to
server' or 'can't login'. I did some research on
the MS forums and apparently this Outlook app only
connects with SSL (no STARTTLS) and TLS 1.2 or
higher. If the mailserver tries anything else
first the connection is dropped.
Is there any known work-around or configuration
adjustment needed to get this Android Outlook app
to work with the toaster.
We're running qmail-1.03-2.2.qt.cdb.el7.x86_64.rpm
Thanks, Jeff
