Discussion:
GMail reports "(Your ISP) did not encrypt this message"
(too old to reply)
alan@pengers.co.uk [blat]
2018-07-08 21:23:46 UTC
Permalink
Security: "(Your ISP) did not encrypt this message"
The email went straight to junk folder.


My blat.log indicates STARTTLS is initiated which I thought WAS encryption, but that might just be my ignorance. It seems quite a few club emails are going to junk mail despite me requesting inclusion in safe senders lists (which they may not bother to do of course).


Anything I should do to try and improve things, is it a stunnel type of thing? (been using Blat for a looooong time now, without.


2018.07.08 21:48:57 (Sun)------------Start of Session-----------------
Blat v3.2.19 (build : Nov 18 2017 03:14:40)
32-bit Windows, Full, Unicode
superDebug: init_winsock(), WSAStartup() returned 0 (NO_ERROR)
superDebug: Hostname <smtp.ISP_Hosting.co.uk> resolved to ip address 83.999.124.83
superDebug: Official hostname is smtp.ISP.co.uk
superDebug: Attempting to connect to ip address 83.999.124.83, on port 25
superDebug: Received 32 bytes:
superDebug: 00000 32 32 30 20 73 6D 74 70 32 2E 69 6E 74 65 72 64 220 mtp2.ISP_d
superDebug: 00010 6E 73 2E 63 6F 2E 75 6B 20 45 53 4D 54 50 0D 0A ns.co.uk ESMTP..
<<<getline<<< 220 smtp2.ISP_dns.co.uk ESMTP
superDebug: Attempting to send 14 bytes:
superDebug: 00000 45 48 4C 4F 20 70 65 6E 67 65 72 73 0D 0A EHLO pengers..
putline>>> EHLO pengers
superDebug: Received 111 bytes:
superDebug: 00000 32 35 30 2D 73 6D 74 70 32 2E 69 6E 74 65 72 64 250-smtp2.ISP_dnserd
superDebug: 00010 6E 73 2E 63 6F 2E 75 6B 0D 0A 32 35 30 2D 53 54 ns.co.uk..250-ST
superDebug: 00020 41 52 54 54 4C 53 0D 0A 32 35 30 2D 50 49 50 45 ARTTLS..250-PIPE
superDebug: 00030 4C 49 4E 49 4E 47 0D 0A 32 35 30 2D 38 42 49 54 LINING..250-8BIT
superDebug: 00040 4D 49 4D 45 0D 0A 32 35 30 2D 53 49 5A 45 20 34 MIME..250-SIZE 4
superDebug: 00050 31 39 34 33 30 34 30 0D 0A 32 35 30 20 41 55 54 1943040..250 AUT
superDebug: 00060 48 20 4C 4F 47 49 4E 20 50 4C 41 49 4E 0D 0A H LOGIN PLAIN..
<<<getline<<< 250-smtp2.ISP_dns.co.uk
<<<getline<<< 250-STARTTLS
<<<getline<<< 250-PIPELINING
<<<getline<<< 250-8BITMIME
<<<getline<<< 250-SIZE 41943040
<<<getline<<< 250 AUTH LOGIN PLAIN
Sending C:\APPS\BUJFC\THISBODY.TXT to ***@gmail.com, ***@MyDomain.co.uk
Subject: Bollington United: Team message



Many thanks for the program, your attention and any response.


Regards Alan
Chip chip.programmer@att.net [blat]
2018-07-08 23:28:15 UTC
Permalink
Going to users' junk folder is usually out of our control.  However, how the message is formatted, the verbage used, and/or if BCC is used can impact whether it is treated as junk or not.
Did your ISP recently change their configuration to require SSL or TLS connections?  Check your ISP's support pages for email settings, look for a requirement to use port number 465 or 587 for SMTP connections.  If this is the case, you may need to use stunnel or similar program.
STARTTLS is just an indicator of your server's ability to support encrypted connections, not that an encrypted connection is actually in effect.
Chip
-------- Original message --------From: "***@pengers.co.uk [blat]" <***@yahoogroups.com> Date: 7/8/18 3:23 PM (GMT-07:00) To: ***@yahoogroups.com Subject: [blat] GMail reports "(Your ISP) did not encrypt this message"













Security: "(Your ISP) did not encrypt this message"The email went straight to junk folder.
My blat.log indicates STARTTLS is initiated which I thought WAS encryption, but that might just be my ignorance. It seems quite a few club emails are going to junk mail despite me requesting inclusion in safe senders lists (which they may not bother to do of course).
Anything I should do to try and improve things, is it a stunnel type of thing? (been using Blat for a looooong time now, without.
2018.07.08 21:48:57 (Sun)------------Start of Session-----------------
Blat v3.2.19 (build : Nov 18 2017 03:14:40)
32-bit Windows, Full, Unicode
superDebug: init_winsock(), WSAStartup() returned 0 (NO_ERROR)
superDebug: Hostname <smtp.ISP_Hosting.co.uk> resolved to ip address 83.999.124.83
superDebug: Official hostname is smtp.ISP.co.uk
superDebug: Attempting to connect to ip address 83.999.124.83, on port 25
superDebug: Received 32 bytes:
superDebug: 00000  32 32 30 20 73 6D 74 70 32 2E 69 6E 74 65 72 64  220 mtp2.ISP_d
superDebug: 00010  6E 73 2E 63 6F 2E 75 6B 20 45 53 4D 54 50 0D 0A  ns.co.uk ESMTP..
<<<getline<<< 220 smtp2.ISP_dns.co.uk ESMTP
superDebug: Attempting to send 14 bytes:
superDebug: 00000  45 48 4C 4F 20 70 65 6E 67 65 72 73 0D 0A        EHLO pengers.. 
putline>>> EHLO pengers
superDebug: Received 111 bytes:
superDebug: 00000  32 35 30 2D 73 6D 74 70 32 2E 69 6E 74 65 72 64  250-smtp2.ISP_dnserd
superDebug: 00010  6E 73 2E 63 6F 2E 75 6B 0D 0A 32 35 30 2D 53 54  ns.co.uk..250-ST
superDebug: 00020  41 52 54 54 4C 53 0D 0A 32 35 30 2D 50 49 50 45  ARTTLS..250-PIPE
superDebug: 00030  4C 49 4E 49 4E 47 0D 0A 32 35 30 2D 38 42 49 54  LINING..!
250-8BIT
superDebug: 00040  4D 49 4D 45 0D 0A 32 35 30 2D 53 49 5A 45 20 34  MIME..250-SIZE 4
superDebug: 00050  31 39 34 33 30 34 30 0D 0A 32 35 30 20 41 55 54  1943040..250 AUT
superDebug: 00060  48 20 4C 4F 47 49 4E 20 50 4C 41 49 4E 0D 0A     H LOGIN PLAIN..
<<<getline<<< 250-smtp2.ISP_dns.co.uk
<<<getline<<< 250-STARTTLS
<<<getline<<< 250-PIPELINING
<<<getline<<< 250-8BITMIME
<<<getline<<< 250-SIZE 41943040
<<<getline<<< 250 AUTH LOGIN PLAIN
Sending C:\APPS\BUJFC\THISBODY.TXT to ***@gmail.com, ***@MyDomain.co.uk
Subject: Bollington United: Team message

Many thanks for the program, your attention and any response.
Regards Alan

Continue reading on narkive:
Loading...