Re: [qmailtoaster] SMTPS Port - Who is Failing ?

2020-04-20 Thread David Bray
Hi Andy - you have grasped the problem accurately As I understand it, the transaction does not leave a great deal of scope - negotiate the encryption, send a password successfully or unsuccessfully - (at that point it's logged) So it has to be the negotiation phase ... but: - I've only just

Re: [qmailtoaster] SMTPS Port - Who is Failing ?

2020-04-20 Thread Andrew Swartz
Port 465 should be SMTP over SSL/TLS. Therefore the sequence of events is: 1. Establish TCP connection 2. Negotiate SSL/TLS session 3. Begin SMTP session Of these, the SSL/TLS negotiation is by far the most CPU-intensive. Consider trying to see what is happening with the SSL/TLS

Re: [qmailtoaster] Re: Login activity report

2020-04-20 Thread ChandranManikandan
Hi Team, Thanks for your advise. On Sat, Apr 18, 2020 at 12:18 AM Craig McLaughlin < craig.p.mclaugh...@gmail.com> wrote: > > Seems this would not be something typically out of box (and I'd advise > your management that this won't necessarily give them an accurate read of > people's 'work

Re: [qmailtoaster] SMTPS Port - Who is Failing ?

2020-04-20 Thread remo
I will give more suggestions in the morning time for bed. > Il giorno 19 apr 2020, alle ore 23:13, David Bray ha > scritto: > >  > Hey thanks Remo > smtps is an inbound port, they are contacting me - this IP is in Russia > somewhere - so do I want to engage (perhaps, probably not but ..) >

[qmailtoaster] SMTP outgoing error on thunderbird

2020-04-20 Thread ChandranManikandan
Hi Folks, I am facing outgoing smtp error issue in thunderbird. Sending of the message failed. Peer’s Certificate has been revoked. The configuration related to smtp.example.com must be corrected But outlook and webmail is working fine both incoming and outgoing. Could anyone face the same

Re: [qmailtoaster] SMTPS Port - Who is Failing ?

2020-04-20 Thread David Bray
Hey thanks Remo smtps is an inbound port, they are contacting me - this IP is in Russia somewhere - so do I want to engage (perhaps, probably not but ..) I could of course block that IP - but that doesn't help, I'd have to block endless IPs I'd like to know what's taking the CPU load, in theory