be fixed
>
>
> Thomas
>
>
>
>
>
> Von:"K Post"
> An:"ASSP development mailing list" <
> assp-test@lists.sourceforge.net>
> Datum: 29.06.2020 17:04
> Betreff:Re: [Assp-test] 20161 - relay auth failures after upda
9.06.2020 17:04
Betreff: Re: [Assp-test] 20161 - relay auth failures after update -
no auth used
Thanks Doug. I must have something suddenly misconfigured, or I've had
something not quite right all along but the auth changes in 20161 cause
the problem.
On Sat, Jun 27, 2020 at 9:03 AM Doug L
Thanks Doug. I must have something suddenly misconfigured, or I've had
something not quite right all along but the auth changes in 20161 cause the
problem.
On Sat, Jun 27, 2020 at 9:03 AM Doug Lytle wrote:
> On 6/27/20 8:17 AM, K Post wrote:
> > Is anyone else seeing this?
>
> I'm not, all 535
On 6/27/20 8:17 AM, K Post wrote:
Is anyone else seeing this?
I'm not, all 535 messages are from outside my home network.
Searching for unauthenticated results in no hits.
This, though is only a small setup for my home mail server.
Doug
___
Is anyone else seeing this? I tried again to no avail. I get emails of
errors, so I'm alerted immediately. I'm wondering if this might be
widespread but people aren't seeing it in their logs
On Thu, Jun 25, 2020 at 9:16 AM K Post wrote:
> I reverted to 20085 to test, no config changes,
I reverted to 20085 to test, no config changes, and the error stops. Was I
supposed to do something with AUTHrelayTable if I'm using 20161??
On Thu, Jun 25, 2020 at 9:02 AM K Post wrote:
> I've noticed that after updating to 20161, all relays through ASSP from
> allowed IP's are issuing the
I've noticed that after updating to 20161, all relays through ASSP from
allowed IP's are issuing the warning:
*error: authentication failed (535 Authentication failed. Restarting
authentication process.) - try to continue unauthenticated*
The IP's are allowed to relay and they're not trying to
