Re: N2Usenet nym gateway issue

Ch1ffr3punk wrote:
> Gabx wrote:
> > 
> > Our Nym requester on Victor recently stopped forwarding traffic because
> > the public Nym gateway it was registered with became unreachable and
> > refused connections on both its main WebSocket endpoint and fallback IP
> > address.
> > 
> > The gateway was not operated by us or directly by the Nym team. It was a
> > public Nym gateway run by an independent network operator.
> > 
> > The exact reason for the outage remains unknown. Possible causes include
> > a stopped service, reverse proxy failure, firewall changes, a software
> > incompatibility, or an issue with the operator’s server.
> > 
> > We restored service by registering a working gateway, updating the
> > corresponding requester address on Pietro, and verifying the complete
> > SMTP and TLS path.
> > 
> > Operating our own Nym gateway is also being considered to  reduce
> > dependence on randomly selected third-party infrastructure.
> 
> Hi Gabx,
> 
> you should consider using old gateways, which are in service for
> already many years, like the ones from wunderbaer, which are
> reliable and I use them as well. Or run your own gateway, which
> gives you the identity-key for your very own Nym SDK software
> components, so that you are the only person responsible for any
> outages.

P.S. I am currently working on nym-validator CLI, which can
list all exit gateways etc. and can be later included for a
postfix MTA whitelist for a new YAMN remailer network, to
allow only YAMN traffic from Nym exit gateways to remailers
and additionally a remop can set-up a whitelist for outgoing
email addresses too. That way OmniCrap users are excluded,
which spread false informations, insulting people, or sending
death threats etc.

-- 
https://oc2mx.net