Closed mq2195 closed 2 years ago
There's no trick to it - you specify username, password, and CRAM-MD5 and it should just work. I'm confused by how you refer to "Encrypted password", are you providing swaks the plaintext version of your password or something else? It needs to be the plaintext version, which, when using CRAM-MD5, swaks will encrypt before sending over the network.
It's possible that swaks is doing something wrong. For instance, maybe your password has special characters in it, etc, but I'm not going to be able to troubleshoot it without knowing your actual username and password, sorry. Are you in a position to set up a test account so that you could share the test account's unimportant credentials with me? To be clear, I don't need to log into anything, I just can't debug the CRAM-MD5 transaction without knowing what the inputs are
I'm confused by how you refer to "Encrypted password"
There are two of us... It came from Thunderbird... In the server settings, there is Authentication method
. Available choices are: Normal password
, Encrypted password
and others. Now I know it has nothing to do with SMTP PLAIN or SMTP CRAM-MD5 authentications.
My initial testing was done with postmaster account, which as it turned out has a special (mis)configuration. After proper testing I was able to make it work.
My problem was: -au user1
vs -au user1@example.org
Sorry for wasting your time...
How to set it up?
Why I think it is CRAM-MD5? Because server replies:
50-AUTH=LOGIN PLAIN CRAM-MD5
Where it works: Thunderbird with settings: SSL/TLS and "Encrypted password"
For swaks -ap argument I am using the same string as for "Encrypted password" in Thunderbird
How can I use "Encrypted password" from Thunderbird (that is what I have) with swaks?