Re: SpamBayes & TLS/SSL

Achim Königs <[email protected]> Mon, 26 Mar 2018 21:53:47 +0200
Newsgroups gmane.mail.spam.spambayes.general
Message-ID <[email protected]>
This is a multi-part message in MIME format.
--===============8636928165517399944==
Content-Type: multipart/alternative;
 boundary="------------6F748535078F9FB0A303EE69"
Content-Language: de-DE

This is a multi-part message in MIME format.
--------------6F748535078F9FB0A303EE69
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Hi,

your setup is not correct. You'll have to leave the connection 
Thunderbird to spambayes as is, i.e. no SSL (which is probably OK for 
localhost anyway). Then you'd need to setup the connection spambayes to 
the server to use SSL. This should be possible by adding :995 to the 
mailhost (not sure I did not try this in a long time).

Best of luck.
Achim

Am 26. März 2018 18:03:20 MESZ schrieb Carl Colijn <[email protected]>:

    Hi group,

    Is it possible to use TLS/SSL POP3 when the mail is being proxied
    via SpamBayes?

    I'm using the 1.1b2 version of sb_server on Windows 10 with
    Thunderbird as the mail client.  I've configured SpamBayes to listen
    on port 53100, proxying to my mail provider.

    When pointing Thunderbird to localhost:53100 without any security
    set, in combination with SpamBayes proxying to port 110 at my mail
    provider, everything works OK.

    When pointing Thunderbird directly to my mail provider on port 995
    with TLS/SSL checked, it can connect fine.

    When in turn pointing Thunderbird to localhost:53100 with TLS/SSL
    checked, in combination with SpamBayes proxying to the same mail
    provider settings used above, fetching mails results in a time out
    after 30 seconds in Thunderbird.

    Updating the SpamBayes advanced setting "Retrieval timeout" from
    it's default of 30 seconds to 15 seconds didn't make a difference
    (Thunderbird still times out after 30 seconds), so it's not directly
    related to that I assume.

    Looking if Thunderbird attaches anything significant to the port
    used (here 53100), I configured SpamBayes and Thunderbird to use the
    default port 995, but that made no difference either.

    I've shut down both the SpamBayes server and Thunderbird between
    applying changes as well, but that didn't magically solve anything.

    Is TLS/SSL supported by the SpamBayes proxy?

    Thanks in advance!


--------------6F748535078F9FB0A303EE69
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="content-type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Hi,<br>
    <br>
    your setup is not correct. You'll have to leave the connection
    Thunderbird to spambayes as is, i.e. no SSL (which is probably OK
    for localhost anyway). Then you'd need to setup the connection
    spambayes to the server to use SSL. This should be possible by
    adding :995 to the mailhost (not sure I did not try this in a long
    time).<br>
    <br>
    Best of luck.<br>
    Achim<br>
    <br>
    <div class="gmail_quote">Am 26. März 2018 18:03:20 MESZ schrieb Carl
      Colijn <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]">&lt;[email protected]&gt;</a>:
      <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex;
        border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
        <p><font face="Arial">Hi group,</font></p>
        <p><font face="Arial">Is it possible to use TLS/SSL POP3 when
            the mail is being proxied via SpamBayes?</font></p>
        <p><font face="Arial">I'm using the 1.1b2 version of sb_server
            on Windows 10 with Thunderbird as the mail client.  I've
            configured SpamBayes to listen on port 53100, proxying to my
            mail provider.<br>
          </font></p>
        <p><font face="Arial">When pointing Thunderbird to
            localhost:53100 without any security set, in combination
            with SpamBayes proxying to port 110 at my mail provider,
            everything works OK.</font></p>
        <p><font face="Arial">When pointing Thunderbird directly to my
            mail provider on port 995 with TLS/SSL checked, it can
            connect fine.</font></p>
        <p><font face="Arial">When in turn pointing Thunderbird to
            localhost:53100 with TLS/SSL checked, in combination with
            SpamBayes proxying to the same mail provider settings used
            above, fetching mails results in a time out after 30 seconds
            in Thunderbird.</font></p>
        <p><font face="Arial">Updating the SpamBayes advanced setting
            "Retrieval timeout" from it's default of 30 seconds to 15
            seconds didn't make a difference (Thunderbird still times
            out after 30 seconds), so it's not directly related to that
            I assume.<br>
          </font></p>
        <p><font face="Arial">Looking if Thunderbird attaches anything
            significant to the port used (here 53100), I configured
            SpamBayes and Thunderbird to use the default port 995, but
            that made no difference either.<br>
          </font></p>
        <p><font face="Arial">I've shut down both the SpamBayes server
            and Thunderbird between applying changes as well, but that
            didn't magically solve anything.</font></p>
        <p><font face="Arial">Is TLS/SSL supported by the SpamBayes
            proxy?</font></p>
        <p><font face="Arial">Thanks in advance!</font><br>
        </p>
      </blockquote>
    </div>
  </body>
</html>

--------------6F748535078F9FB0A303EE69--

--===============8636928165517399944==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
[email protected]
https://mail.python.org/mailman/listinfo/spambayes
Info/Unsubscribe: http://mail.python.org/mailman/listinfo/spambayes
Check the FAQ before asking: http://spambayes.sf.net/faq.html

--===============8636928165517399944==--