• Resolved graeuk

    (@graeuk)


    Hi, I am wondering if there is a way around this. My host (kualo) doesn’t allow me to authenticate by plaintext. Is there a way of changing that?
    I am using sockets because cURL had the error that @ was seen to be sending the email and thus the post was rejected ….

    Is there a way around this?

    Many thanks

    G

    • This topic was modified 7 years, 7 months ago by graeuk.
Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Wayne Allen

    (@wayneallen-1)

    What kind of authentication do you need? All the Kualo docs I could find indicate it should work with user name and password.

    Thread Starter graeuk

    (@graeuk)

    Hi Wayne,
    Thanks for the response. The support guys say –

    “The server has been hardened for PCI compliance. As such only connections via the SSL ports (993 for POP, 995 for IMAP, and 465 for SMTP) are opened. Also, only the latest authentication method is supported (TLS1.2). For example, users of Outlook on Windows 7/8 require a Windows update to allow support for TLS1.2.”

    Does that help?
    Thanks
    G

    Plugin Author Wayne Allen

    (@wayneallen-1)

    Postie supports SSL on both POP and IMAP. TLS support depends on what is installed on your web server.
    Just set up Postie for IMAP-SSL on port 995 and you should be good to go.

    Thread Starter graeuk

    (@graeuk)

    Hi Wayne, Thanks. So have tried POP and IMAP SSL .. get the following error: (i’ve removed the domain name for the post here, there isn’t normally a space there! πŸ™‚ )

    Connect to Mail Host
    Postie connection: sockets
    Postie protocol: pop3-ssl
    Postie server: mail.domain removed.co.uk
    Postie port: 995
    pConnection: mailbox: INBOX
    Connecting via Socket
    Socket: tls://mail.domain removed.co.uk:995
    Socket error: 0 –
    Unable to connect. The server said:
    There was an error connecting to the server
    Test complete

    ###############################

    Then the server log says:
    Oct 20 18:37:48 servernamehere dovecot: pop3-login: Disconnected (tried to use disallowed plaintext auth): user=<[email protected]>, rip=192.168.0.1, lip=192.168.0.1, session=<23YQUa14/Ju5tXSq>

    Any ideas on why it is failing ?

    Many thanks

    G

    Plugin Author Wayne Allen

    (@wayneallen-1)

    You should be using port 993 for POP.

    Thread Starter graeuk

    (@graeuk)

    ah, thanks. You might want to update the text under that field that says:
    Standard Ports:
    POP3: 110
    IMAP: 143
    IMAP-SSL: 993
    POP3-SSL: 995

    πŸ˜‰

    I now have a password not accepted error .. I will discuss with the host and see where I go from there.

    Thanks for your help.

    Thread Starter graeuk

    (@graeuk)

    Actually, scrap that, I had it set to POP not POP3-SSL .. urgh. Slowly giving up

    Plugin Author Wayne Allen

    (@wayneallen-1)

    I was basing the port number off of the information your host provided. The ports listed on the Postie settings page are the typical port assignments.

    Thread Starter graeuk

    (@graeuk)

    They use the standard ports .. so not sure what made you think that?
    Anyway, we managed to get it working with cURL. Connection was easy and the problem where it would reject the message because it was sent by @ seems to have gone away, hopefully it won’t come back πŸ™‚
    Thanks for your help
    G

Viewing 9 replies - 1 through 9 (of 9 total)

The topic ‘Connection Issue – authenticating via plaintext’ is closed to new replies.