It appears that Julian Bradfield via mailop said:
>An idle question: people who do SRS or similar things usually use
>'=' as the replacement for '@' in the rewritten address
>localpart=origdomain@mydomain
>
>Is there any reason not to use the old routing character '%' instead?
You will still run
On 3/8/2024 9:21 AM, Bill Cole via mailop wrote:
Yes: it is an old routing character
As such, some sites may misinterpret it in ways that are NOT
appropriate for SRS.
oh?
SRS is not a standard. If there are sites trying to do automated
interpretation -- other than the site that put the
On 3/8/2024 9:21 AM, Bill Cole via mailop wrote:
Yes: it is an old routing character
As such, some sites may misinterpret it in ways that are NOT
appropriate for SRS.
oh?
SRS is not a standard. If there are sites trying to do automated
interpretation -- other than the site that put the
On 3/8/2024 9:07 AM, Julian Bradfield via mailop wrote:
Is there any reason not to use the old routing character '%' instead?
Well, that's certainly a bit of ancient history. Fwiw, here's some
background on it:
I chose % for use in CSNet mostly because of its established postal use
IRL to
On 8 March 2024 17:04:36 Stefano Bagnara via mailop wrote:
I just got an answer from them that the issue is fixed.
Thanks to everyone!
Thank you to you for doing the right thing.
I know everyone wants to smack down on OVH but ascribing actions such as
those mentioned in this thread to an
On 2024-03-08, Bill Cole via mailop wrote:
> On 2024-03-08 at 12:07:23 UTC-0500 (Fri, 08 Mar 2024 17:07:23 +)
> Julian Bradfield via mailop
> is rumored to have said:
>> Is there any reason not to use the old routing character '%' instead?
> Yes: it is an old routing character
>
> As such,
On 2024-03-08 at 12:07:23 UTC-0500 (Fri, 08 Mar 2024 17:07:23 +)
Julian Bradfield via mailop
is rumored to have said:
Is there any reason not to use the old routing character '%' instead?
Yes: it is an old routing character
As such, some sites may misinterpret it in ways that are NOT
An idle question: people who do SRS or similar things usually use
'=' as the replacement for '@' in the rewritten address
localpart=origdomain@mydomain
Is there any reason not to use the old routing character '%' instead?
I did this some years ago when I hacked in SRS to keep gmail happy
with
On Fri, 8 Mar 2024 at 17:47, Stefano Bagnara wrote:
> > Poking a few people, this looks like a return path issue on Freenet's
> > side; So they likely fnorded something on their side.
> > Guess the only way to get this fixed is for them to realize the issue.
> > ;-)
>
> I wrote an email to
On Fri, 8 Mar 2024 at 17:18, Tobias Fiebig via mailop wrote:
> Moin,
> to get a bit back to the networking part of things...
:-)
> Poking a few people, this looks like a return path issue on Freenet's
> side; So they likely fnorded something on their side.
> Guess the only way to get this fixed
Moin,
to get a bit back to the networking part of things...
Poking a few people, this looks like a return path issue on Freenet's
side; So they likely fnorded something on their side.
Guess the only way to get this fixed is for them to realize the issue.
;-)
So if somebody can poke netops of
+1
- Mark Alley
On 3/8/2024 10:01 AM, Bill Cole via mailop wrote:
On 2024-03-08 at 09:13:32 UTC-0500 (Fri, 8 Mar 2024 15:13:32 +0100)
Stefano Bagnara via mailop
is rumored to have said:
Well,
I undestand you all hate OVH, but this really doesn't look like an
intended block.
Sure it does.
On 2024-03-08 at 09:13:32 UTC-0500 (Fri, 8 Mar 2024 15:13:32 +0100)
Stefano Bagnara via mailop
is rumored to have said:
Well,
I undestand you all hate OVH, but this really doesn't look like an
intended block.
Sure it does.
I tested that when I log to my @freenet.de email I am not able to
On 2024-03-08 09:13, Stefano Bagnara via mailop wrote:
I undestand you all hate OVH, but this really doesn't look like an
intended block.
your understanding is wrong; your tarring "all" with the same brush is
unacceptable; and hate has nothing to do with this.
my personal position: if
Well,
I undestand you all hate OVH, but this really doesn't look like an
intended block.
I tested that when I log to my @freenet.de email I am not able to
write emails to any domain whose DNS are hosted by OVH. I know plenty
of italian companies whose domain zone is at OVH: even if their email
Dnia 8.03.2024 o godz. 12:45:18 Paul Gregg via mailop pisze:
> I can confirm your observations. I can't see their NS from my OVH box,
> nor can I connect to port 25 of the 3 IPs behind their MX.
> From home (UK broadband), I can see and query DNS servers, but I can't
> talk to port 25.
> From
On 2024-03-08 07:48, Stefano Bagnara via mailop wrote:
On Fri, 8 Mar 2024 at 13:04, Mark Alley wrote:
Have you considered they may be blocking OVH ASNs on their firewall?
Well, blocking the whole ASNs even to their NS sounds something very
unexpected.
Extreme, yes. Unexpected? I disagree.
On Fri, Mar 08, 2024 at 02:15:21PM +0100, Marco Moock via mailop wrote:
> Can you test 53/udp and 53/tcp on their authoritative NS from home?
pgregg@pgsurfacepro8:~$ dig +short +tcp soa freenet.de @ns1.fdkcloud.de.
ns1.fdkcloud.de. hostmaster.freenet-business.de. 2024030701 28800 7200
604800 3600
Am 08.03.2024 schrieb Paul Gregg via mailop :
> They do claim to use RBLs, but my OVH IP isn't on any RBLs (not even
> uceprotect-L3 amazingly right now) - and based on my home 'DUL' IP not
> being able to connect, they're certainly using RBLs on port 25.
Can you test 53/udp and 53/tcp on their
Having seen this behavior before from overzealous network admins,
especially given the fact that freenet owns their netblock and their NS are
self-hosted on said netblock rather than cloud DNS SaaS, it's very likely a
firewall rule.
I wouldn't be surprised if it was the case, OVH isn't exactly
On Fri, 8 Mar 2024 at 13:04, Mark Alley wrote:
> Have you considered they may be blocking OVH ASNs on their firewall?
Well, blocking the whole ASNs even to their NS sounds something very
unexpected. This mean any service (not only email) that is hosted in
OVH (in europe is the biggest provider)
On Fri, Mar 08, 2024 at 01:26:48PM +0100, Stefano Bagnara via mailop wrote:
> On Fri, 8 Mar 2024 at 13:17, Marco Moock wrote:
> > Can you access their website on freenet.de from OVH?
>
> No. I can't even reach their NS from OVH network.
> So I can't resolve www.freenet.de: but if I try with the
On Fri, 8 Mar 2024 at 13:17, Marco Moock wrote:
> Can you access their website on freenet.de from OVH?
No. I can't even reach their NS from OVH network.
So I can't resolve www.freenet.de: but if I try with the IP, then I
can't ping it.
> > From my servers @OVH they are not reachable at all.
>
>
Am 08.03.2024 schrieb Stefano Bagnara via mailop :
> I can't even lookup the domain as I cannot reach their NS, but the
> same happens even if I try to ping their email server IP address:
I can reach them properly from AS8820.
Do you get any ICMP messages back?
tcptraceroute 194.97.8.138 53
Have you considered they may be blocking OVH ASNs on their firewall?
Their NS and zone seems resolvable and reachable from pretty much
everything else on the internet according to DNSchecker.org.
- Mark Alley
On Fri, Mar 8, 2024, 5:54 AM Stefano Bagnara via mailop
wrote:
> Hi,
>
> I'm
Hi,
I'm experiencing routing issues to freenet.de MX since almost 3 days.
I can't even lookup the domain as I cannot reach their NS, but the
same happens even if I try to ping their email server IP address:
194.97.8.138
195.4.92.217
From my servers @OVH they are not reachable at all.
I
26 matches
Mail list logo
