On Mon, 19 Apr 2021 21:43:06 +0200, Bernd Rose posted for all of us to
digest...

>
> On Mon, 19th Apr 2021 19:40:57 +0100, Jim S wrote:
>
> [Program PlonkWithAddress; //v0.4 24/Gennaio/2005, by MLC]
>
> It is a bit late for testing, hereabouts. I'll look into it tomorrow
> evening. But if you are adventurous, you can try to replace the last
> Begin/End block of the script with this version:
>
> Begin
> myForm := tForm.Create(nil);
> lockdisplay;
> try
> BuildContainers;
> ADo('ShowHeaders');
> GetMsgBody;
> ADo('ShowHeaders');
> mail:=GetAddress;
> if (mail='') then myMemo.text:=' '
> else myMemo.text:=' +"'+mail+'"';
> myMemo.SelectAll;
> myMemo.CopyToClipboard;
> ADoLater('AddPlonkFilter');
> PostKey(35, false, false, false, false, false, false, false, false);
> //end
> PostKey(86, false, false, true, false, false, false, false, false);
> //Ctrl+V
> PostKey(79, false, true, false, false, false, false, false, false);
> //Alt+O
> finally
> unlockdisplay;
> myForm.free;
> ADoLater('Ignore');
> ADoLater('RefreshView');
> end;
> End.

Hello Bernd, this is completely unrelated to this topic. I use Microplanet
Gravity as my newsreader. I use Comcast as my email server. Gravity allows me
to forward posts to my email, which I used quite often until Comcast changed
something in the SMTP server. Several people have tried to help me with an
stunnel script to allow me to do this but I have been unsuccessful in every
instance. Would you help me write a conf that works? I would very much
appreciate it. Thank you!

--
Tekkie

On Tue, 20th Apr 2021 14:23:15 -0400, Tekkie© wrote:

> I use Microplanet
> Gravity as my newsreader. I use Comcast as my email server. Gravity allows me
> to forward posts to my email, which I used quite often until Comcast changed
> something in the SMTP server. Several people have tried to help me with an
> stunnel script to allow me to do this but I have been unsuccessful in every
> instance. Would you help me write a conf that works? I would very much
> appreciate it. Thank you!

Try this with sTunnel.conf:

[Comcast_SMTP]
client = yes
accept = localhost:25
connect = smtp.comcast.net:587
protocol = smtp
ProtocolAuthentication = login
verifyChain = yes
CAfile = ca-certs.pem
checkHost = smtp.comcast.net
OCSPaia = yes

In Gravity you set
"Mail server (SMTP)": localhost
"Server ports SMTP": 25
and provide your login credentials (Name/Password).

If you use local port 25 with another program, already, change *both*
occurrences of 25 to an unused port number (e.g. 250).

Don't forget to reload the *.conf file in stunnel after changing the
settings.

Maybe, this works.
Bernd

On Tue, 20 Apr 2021 22:28:56 +0200, Bernd Rose posted for all of us to
digest...

>
> On Tue, 20th Apr 2021 14:23:15 -0400, Tekkie© wrote:
>
> > I use Microplanet
> > Gravity as my newsreader. I use Comcast as my email server. Gravity allows me
> > to forward posts to my email, which I used quite often until Comcast changed
> > something in the SMTP server. Several people have tried to help me with an
> > stunnel script to allow me to do this but I have been unsuccessful in every
> > instance. Would you help me write a conf that works? I would very much
> > appreciate it. Thank you!
>
> Try this with sTunnel.conf:
>
> [Comcast_SMTP]
> client = yes
> accept = localhost:25
> connect = smtp.comcast.net:587
> protocol = smtp
> ProtocolAuthentication = login
> verifyChain = yes
> CAfile = ca-certs.pem
> checkHost = smtp.comcast.net
> OCSPaia = yes
>
> In Gravity you set
> "Mail server (SMTP)": localhost
> "Server ports SMTP": 25
> and provide your login credentials (Name/Password).
>
> If you use local port 25 with another program, already, change *both*
> occurrences of 25 to an unused port number (e.g. 250).
>
> Don't forget to reload the *.conf file in stunnel after changing the
> settings.
>
> Maybe, this works.
> Bernd

Thanks for your very rapid response!

The first attempt did not work, giving me the same old error messages.

The second time I read your post I noticed I should change the Gravity SMTP
server setting to localhost. I did that but again it failed but I got this
error message out of Gravity:
The attempt to connect failed. The target server is not running the required
service

Any hints? I did reload the config.

This is the stunnel log:
2021.04.21 17:32:52 LOG5[main]: stunnel 5.59 on x64-pc-mingw32-gnu platform
2021.04.21 17:32:52 LOG5[main]: Compiled/running with OpenSSL 1.1.1k 25 Mar
2021
2021.04.21 17:32:52 LOG5[main]: Threading:WIN32 Sockets:SELECT,IPv6
TLS:ENGINE,OCSP,PSK,SNI
2021.04.21 17:32:52 LOG5[main]: Reading configuration from file stunnel.conf
2021.04.21 17:32:52 LOG5[main]: UTF-8 byte order mark detected
2021.04.21 17:32:52 LOG5[main]: FIPS mode disabled
2021.04.21 17:32:52 LOG5[main]: Configuration successful

I feel we on the road to success!
--
Tekkie

On Wed, 21 Apr 2021 17:37:52 -0400, Tekkie© <Tekkie@comcast.net> wrote:

>The second time I read your post I noticed I should change the Gravity SMTP
>server setting to localhost. I did that but again it failed but I got this
>error message out of Gravity:
>The attempt to connect failed. The target server is not running the required
>service
>
>Any hints?

Could be the wrong port on Comcast??
> connect = smtp.comcast.net:587

In stunnel.conf - try
connect = smtp.comcast.net:465

On Wed, 21st Apr 2021 17:37:52 -0400, Tekkie© wrote:

>> Try this with sTunnel.conf:
>>
>> [Comcast_SMTP]
[...]
> The first attempt did not work, giving me the same old error messages.
>
> The second time I read your post I noticed I should change the Gravity SMTP
> server setting to localhost. I did that but again it failed but I got this
> error message out of Gravity:
> The attempt to connect failed. The target server is not running the required
> service

As far as I can tell from comcast configuration info on the net, it supports
SMTP with STARTTLS on port 587 and SMTPS on port 465 (like Larry already
suggested as a possible alternative). That's pretty standard and shouldn't
prevent you from logging in from Gravity by way of sTunnel.

From your OP I deduced, that you already tried the more obvious setups. From
your current message, I don't believe this, anymore.

Therefore, I suggest you first keep port 587 and all other settings as I
suggested in my previous posting. Just delete the following line from
sTunnel.conf (or comment it out with a semicolon on first position of the
line):
ProtocolAuthentication = login

Don't forget to reload this configuration in sTunnel. Test this setting from
Gravity and take note of every error message.

If above didn't work, retry with port 465 instead of port 587. (As Larry
suggested.) -> Reload in sTunnel and retry in Gravity; note errors, if any.

If this does not work, either, retry with keeping the port set to 465, but
re-inserting (or uncommenting) above mentioned line:
ProtocolAuthentication = login

Again, don't forget: Reload + Retry + Note_Errors.

For the last two tests (if all up to now have failed), you set Gravity to
/not/ log-in with Name and Password:
Server Setup -> Mail Server (SMTP) -> Mail server password: No password required

Afterwards, you insert the following 2 additional lines in sTunnel.conf:
protocolUsername = USERNAME
protocolPassword = PASSWORD

USERNAME and PASSWORD are your login credentials to comcast. (The ones you
just disabled in Gravity.)

Now you first try with port set to 465. And if this doesn't work, either,
you last try port 587.

If none of these configurations are successful, we need to see any error
messages or log lists for these unsuccessful attempts.

IMPORTANT: Be sure to remove all Login details (name, password,...) from
your log file excerpts when posting them.

HTH.
Bernd

On Wed, 21 Apr 2021 21:53:58 +0000, Larry posted for all of us to digest...

>
> On Wed, 21 Apr 2021 17:37:52 -0400, Tekkie© <Tekkie@comcast.net> wrote:
>
> >The second time I read your post I noticed I should change the Gravity SMTP
> >server setting to localhost. I did that but again it failed but I got this
> >error message out of Gravity:
> >The attempt to connect failed. The target server is not running the required
> >service
> >
> >Any hints?
>
> Could be the wrong port on Comcast??
> > connect = smtp.comcast.net:587
>
> In stunnel.conf - try
> connect = smtp.comcast.net:465

Okay did that and reloaded the stunnel conf
No joy got these error in Gravity, in order:

Socket receive error 10054

The circuit was reset by the remote side
**************************************************
The circuit was reset by the remote side
**************************************************
Could not connect to mail server.
**************************************************

This is stunnel log window before and after being reset

2021.04.22 17:00:30 LOG5[main]: stunnel 5.59 on x64-pc-mingw32-gnu platform
2021.04.22 17:00:30 LOG5[main]: Compiled/running with OpenSSL 1.1.1k 25 Mar
2021
2021.04.22 17:00:30 LOG5[main]: Threading:WIN32 Sockets:SELECT,IPv6
TLS:ENGINE,OCSP,PSK,SNI
2021.04.22 17:00:30 LOG5[main]: Reading configuration from file stunnel.conf
2021.04.22 17:00:30 LOG5[main]: UTF-8 byte order mark detected
2021.04.22 17:00:30 LOG5[main]: FIPS mode disabled
2021.04.22 17:00:30 LOG5[main]: Configuration successful
2021.04.22 17:01:20 LOG5[main]: Reading configuration from file stunnel.conf
2021.04.22 17:01:20 LOG5[main]: UTF-8 byte order mark detected
2021.04.22 17:01:20 LOG5[main]: FIPS mode disabled
2021.04.22 17:01:20 LOG5[main]: Configuration successful
2021.04.22 17:01:46 LOG5[0]: Service [Comcast_SMTP] accepted connection from
127.0.0.1:56356
2021.04.22 17:01:46 LOG5[0]: s_connect: connected 2001:558:fe21:2a::5:465
2021.04.22 17:01:46 LOG5[0]: Service [Comcast_SMTP] connected remote server
from 2601:43:4100:44b0:944e:ad:58c3:b758:56357
2021.04.22 17:02:58 LOG3[0]: Unexpected socket close (s_read)
2021.04.22 17:02:58 LOG5[0]: Connection reset: 0 byte(s) sent to TLS, 0 byte(s)
sent to socket

I hope all this is helpful because I am way out of my league.
--
Tekkie

On Thu, 22nd Apr 2021 17:14:32 -0400, Tekkie© wrote:

> On Wed, 21 Apr 2021 21:53:58 +0000, Larry posted for all of us to digest...
[...]
>> In stunnel.conf - try
>> connect = smtp.comcast.net:465
>
> Okay did that and reloaded the stunnel conf
> No joy got these error in Gravity, in order:
>
> Socket receive error 10054

So you can cross out case 3 of the 5 variants I suggested yesterday.
My best bet would be on case 1. ;-)

Bernd

On Fri, 23 Apr 2021 19:30:02 +0200, Bernd Rose posted for all of us to
digest...

>
> On Thu, 22nd Apr 2021 17:14:32 -0400, Tekkie© wrote:
>
> > On Wed, 21 Apr 2021 21:53:58 +0000, Larry posted for all of us to digest...
> [...]
> >> In stunnel.conf - try
> >> connect = smtp.comcast.net:465
> >
> > Okay did that and reloaded the stunnel conf
> > No joy got these error in Gravity, in order:
> >
> > Socket receive error 10054
>
> So you can cross out case 3 of the 5 variants I suggested yesterday.
> My best bet would be on case 1. ;-)
>
> Bernd

It works!!!! Exuberance is too mild of word to describe my happiness.

I admit the last go around of failure is the fact that Comcast requires me to
change my password every two weeks on this account. When I tested the last
config Gravity gave an error message & to view the event log. The event log was
blank. I now had to put on my aluminum foil hat and think for myself. I forgot
to change my password in Gravity... You now have proof that I am a burnt out
bulb in the chandelier.

I want to thank you for sticking with me and providing a solution I have been
struggling with for years. I am posting the working config in the hope that
someone else can benefit.

[Comcast_SMTP]
client = yes
accept = localhost:25
connect = smtp.comcast.net:587
protocol = smtp
ProtocolAuthentication = login
verifyChain = yes
CAfile = ca-certs.pem
checkHost = smtp.comcast.net
OCSPaia = yes

--
Tekkie

On Sat, 24th Apr 2021 16:01:14 -0400, Tekkie© wrote:

[Gravity-sTunnel-Comcast setup]
> It works!!!! Exuberance is too mild of word to describe my happiness.

Thanks for the feedback! :-)

Btw., the working setup would have been my first suggestion, if you hadn't
fooled me with your initial statement, that you already got many suggestions
and none worked. Therefore, my first variant was a more exotic approach. ;-)

> I admit the last go around of failure is the fact that Comcast requires me to
> change my password every two weeks on this account.

Not a good idea. They should know better. If people need to change their
passwords frequently, they tend to use too simple ones. (Just to be able
to remember them.) The passwords then are easily guessed with dictionary
attacks (maybe combined with counters) and the like. Or users write the
passwords down in places accessible to others.

Moreover, email inboxes are usually accessed from many different places
(PC, Smartphone,...). The programs used for access usually are configured
to save passwords. Although saved passwords usually aren't encrypted too
well on local systems (especially with older programs), frequent changes
of password will provide no advantage in security. If a device is already
compromised, the password change will not alter this. If not, then the
situation is okay, in the first place.

But with many devices, people tend to forget changing passwords. Result
are frequent cases of multiple failing logins. If the provider will not
go out of service in no time, he has to configure his service to react
lenient on invalid logins. This is an invitation for hackers.

Better would be the opposite approach: Require a long complex password,
do not permit unencrypted (with secure, current methods) login and react
harsh on failed login attempts. (Sufficient timeout, but not so long,
that after a hacking attempt, the legitimate user can not login, either.)
Provide (unerasable, nonalterable) login history on a status page for
a feasible amount of time (maybe a month). And require any password
change (and any other basic setup alteration, like means of contact) to
be verified and confirmed across a different - secure - channel.

> I forgot to change my password in Gravity... You now have proof that I am
> a burnt out bulb in the chandelier.

IMHO, the requirement to change mail password every two weeks is just
ridiculous.

Bernd

On Sat, 24 Apr 2021 16:01:14 -0400, Tekkie© <Tekkie@comcast.net> wrote:

>I admit the last go around of failure is the fact that Comcast requires me to
>change my password every two weeks on this account.

When and where did Comcast start this silliness? Any explanation as to
why your email accounts have this limitation?

On Sun, 25 Apr 2021 07:54:17 +0200, Bernd Rose posted for all of us to
digest...

>
> On Sat, 24th Apr 2021 16:01:14 -0400, Tekkie© wrote:
>
> [Gravity-sTunnel-Comcast setup]
> > It works!!!! Exuberance is too mild of word to describe my happiness.
>
> Thanks for the feedback! :-)
>
> Btw., the working setup would have been my first suggestion, if you hadn't
> fooled me with your initial statement, that you already got many suggestions
> and none worked. Therefore, my first variant was a more exotic approach. ;-)
>
> > I admit the last go around of failure is the fact that Comcast requires me to
> > change my password every two weeks on this account.
>
> Not a good idea. They should know better. If people need to change their
> passwords frequently, they tend to use too simple ones. (Just to be able
> to remember them.) The passwords then are easily guessed with dictionary
> attacks (maybe combined with counters) and the like. Or users write the
> passwords down in places accessible to others.
>
> Moreover, email inboxes are usually accessed from many different places
> (PC, Smartphone,...). The programs used for access usually are configured
> to save passwords. Although saved passwords usually aren't encrypted too
> well on local systems (especially with older programs), frequent changes
> of password will provide no advantage in security. If a device is already
> compromised, the password change will not alter this. If not, then the
> situation is okay, in the first place.
>
> But with many devices, people tend to forget changing passwords. Result
> are frequent cases of multiple failing logins. If the provider will not
> go out of service in no time, he has to configure his service to react
> lenient on invalid logins. This is an invitation for hackers.
>
> Better would be the opposite approach: Require a long complex password,
> do not permit unencrypted (with secure, current methods) login and react
> harsh on failed login attempts. (Sufficient timeout, but not so long,
> that after a hacking attempt, the legitimate user can not login, either.)
> Provide (unerasable, nonalterable) login history on a status page for
> a feasible amount of time (maybe a month). And require any password
> change (and any other basic setup alteration, like means of contact) to
> be verified and confirmed across a different - secure - channel.
>
> > I forgot to change my password in Gravity... You now have proof that I am
> > a burnt out bulb in the chandelier.
>
> IMHO, the requirement to change mail password every two weeks is just
> ridiculous.
>
> Bernd

Bernd, be glad you don't have to deal with Comcast. Their customer (non)service
gets consistent subterranean ratings. Comcast agrees that it should not need to
be changed every two weeks, I've complained and I will see next week what
happens. I use Roboform so it helps me generate & remember passwords.

Again, thanks for your help. I would share your solution on the Gravity site
but so far I have been unsuccessful in being able to post.

I am also using your solution on another newsreader that I used for d/l's and
you can credit yourself with a double pat on the back.

Guten abend,

--
Tekkie

On Sun, 25 Apr 2021 15:41:35 +0000, Larry posted for all of us to digest...

>
> On Sat, 24 Apr 2021 16:01:14 -0400, Tekkie© <Tekkie@comcast.net> wrote:
>
> >I admit the last go around of failure is the fact that Comcast requires me to
> >change my password every two weeks on this account.
>
> When and where did Comcast start this silliness? Any explanation as to
> why your email accounts have this limitation?

It's been about six months. It only applies to this account, the rest are fine.

There is no explanation why or how Comcast does things...

My wife's account also gets email from another persons account. We got all the
details where she moved because of this. It seems to have subsided for a month
so maybe it's fixed now. I mean the account names weren't even remotely alike.

Thank you for your help,

--
Tekkie

On Mon, 26th Apr 2021 15:27:43 -0400, Tekkie© wrote:

[sTunnel setup]
> Again, thanks for your help. I would share your solution on the Gravity site
> but so far I have been unsuccessful in being able to post.
>
> I am also using your solution on another newsreader that I used for d/l's and
> you can credit yourself with a double pat on the back.

Your feedback is kind, but the (working) suggestion is really standard and
corresponds even to the basic examples found in sTunnel documentation. So,
there's no need to refer to me when you share the solution. Just post these
settings as working.

Important when sharing the setup is, to point out the client side settings,
as well. (I.e., the settings in the newsreader or mail program.) That's
probably the place, where applying the suggestions you got earlier failed.
With this I mean:

| In Gravity you set
| "Mail server (SMTP)": localhost
| "Server ports SMTP": 25
| and provide your login credentials (Name/Password).
|
| If you use local port 25 with another program, already, change *both*
| occurrences of 25 to an unused port number (e.g. 250).

The other place, referred to in "both", is this sTunnel.conf setting:

| accept = localhost:25

Bernd