From Newsgroup: alt.privacy.anon-server

It's always kicking!

https // mail2dizum virebent art :4443,

On est d'accord !

Victor HCC 666

--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.privacy.anon-server

Big improvements:

Message-ID now assigned by dizum.com rCo removed the Message-ID header from the outgoing message so the final MTA generates one under its own domain.

Removed deprecated X-XSS-Protection header rCo CSP already covers this.

Removed CORS rCo the three Access-Control-* wildcard headers were unnecessary and exposed the app to cross-origin calls.

TLS 1.3 only rCo SSLProtocol -all +TLSv1.3 on both SSL vhosts.

127.0.0.1 instead of localhost in ProxyPass to avoid IPv4/IPv6 resolution ambiguity.

we live in hell
but we live well

Victor HCC 666

--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.privacy.anon-server

Am 02.06.26 um 22:16 schrieb Victor:

127.0.0.1 instead of localhost in ProxyPass to avoid IPv4/IPv6 resolution ambiguity.

Can you explain that further?
--
Gru|f
Marco

Spam bitte an abfalleimer2001@stinkedores.dorfdsl.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.privacy.anon-server

Marco Moock wrote:

Am 02.06.26 um 22:16 schrieb Victor:

127.0.0.1 instead of localhost in ProxyPass to avoid IPv4/IPv6
resolution ambiguity.

Can you explain that further?

First, address selection.
When localhost resolves to more than one address, etc/hosts, the connecting side decides which to try first.
That choice is governed by /etc/gai.conf and the RFC 6724 destination-address selection algorithm, which by default prefers IPv6.

So localhost tends to be attempted as ::1 before 127.0.0.1.

Second, what the backend listens on.

The Go server binds explicitly to 127.0.0.1:SomePort,
IPv4 only, nothing on ::1.

So when the resolver hands back the IPv6 loopback first, the proxy reaches for [::1]:SomePort, finds no socket, and you get a connection refused surfacing as an intermittent 502.

AFAIK
burrrp

--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.privacy.anon-server

Much more important is the fact that the smtp onion imposes its onion address on the message-id of the post.

And I don't like that.

much better the more generic dizum.

--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.privacy.anon-server

Victor wrote:

Much more important is the fact that the smtp onion imposes its onion > address on the message-id of the post.

And I don't like that.

much better the more generic dizum.

does it?

--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.privacy.anon-server

Much more important is the fact that the smtp onion imposes its onion > address on the message-id of the post.

And I don't like that.

much better the more generic dizum.

does it?

I <3 it.

<20260602211405.269a0cabbaf9889e3c387850@dizum.com>

--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.privacy.anon-server

On 02 Jun 2026, Victor <mail2dizum@proxy.interface> posted some news:20260602194310.7EEA5400A5@qee4i7sags6phsvb2yodwecfj7noimfhhalsjktsvikrwotxzis3raad.onion:

It's always kicking!

https // mail2dizum virebent art :4443,

On est d'accord !

Victor HCC 666

Woot!

--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.privacy.anon-server

Am 02.06.26 um 22:38 schrieb Victor:

The Go server binds explicitly to 127.0.0.1:SomePort,
IPv4 only, nothing on ::1.

Then fix this.
--
Gru|f
Marco

Spam bitte an abfalleimer2001@stinkedores.dorfdsl.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.privacy.anon-server

Marco Moock wrote:

Am 02.06.26 um 22:38 schrieb Victor:

The Go server binds explicitly to 127.0.0.1:SomePort,
IPv4 only, nothing on ::1.

Then fix this.

lol
i fix you

--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.privacy.anon-server

On 02 Jun 2026, Victor <mail2dizum@proxy.interface> posted some news:20260602203811.9AB04401F6@qee4i7sags6phsvb2yodwecfj7noimfhhalsjktsvi krwotxzis3raad.onion:

Marco Moock wrote:

Am 02.06.26 um 22:16 schrieb Victor:

127.0.0.1 instead of localhost in ProxyPass to avoid IPv4/IPv6
resolution ambiguity.

Can you explain that further?

First, address selection.
When localhost resolves to more than one address, etc/hosts, the
connecting side decides which to try first. That choice is governed by /etc/gai.conf and the RFC 6724 destination-address selection
algorithm, which by default prefers IPv6.

So localhost tends to be attempted as ::1 before 127.0.0.1.

Second, what the backend listens on.

The Go server binds explicitly to 127.0.0.1:SomePort,
IPv4 only, nothing on ::1.

So when the resolver hands back the IPv6 loopback first, the proxy
reaches for [::1]:SomePort, finds no socket, and you get a connection
refused surfacing as an intermittent 502.

AFAIK
burrrp

Very good.

--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: alt.privacy.anon-server

On 02 Jun 2026, Victor <mail2dizum@proxy.interface> posted some news:20260602204643.F32074012B@qee4i7sags6phsvb2yodwecfj7noimfhhalsjktsvi krwotxzis3raad.onion:

Much more important is the fact that the smtp onion imposes its onion
address on the message-id of the post.

And I don't like that.

much better the more generic dizum.

+1

--- Synchronet 3.22a-Linux NewsLink 1.2