To whom it concerns,

I'm seeing lots of spooled mail for Dizum.

It looks like it started yesterday morning.

--
Grant. . . .

On 11/30/23 22:50, Grant Taylor wrote:
> I'm seeing lots of spooled mail for Dizum.

I have more than 1000 messages queued waiting on a connection to Dizum.

Grant. . . .

On 12/2/23 03:25, Grant Taylor wrote:
> On 11/30/23 22:50, Grant Taylor wrote:
>> I'm seeing lots of spooled mail for Dizum.
>
> I have more than 1000 messages queued waiting on a connection to Dizum.
>
>
>
> Grant. . . .
>

I am not experiencing this at my shalo mixmaster remailer nor at my SEC3
Pinger.

During your absence from apa-s there was a change at Dizum. A new
hostname and IP address.

zewer.dizum.com [45.66.35.219]

HTH

--
SEC3

YAMN Help Tutorial - https://www.sec3.net/yamnhelp/

On 12/2/23 10:38, SEC3 wrote:
> I am not experiencing this at my shalo mixmaster remailer nor at my SEC3
> Pinger.

Hum.

> During your absence from apa-s there was a change at Dizum. A new
> hostname and IP address.

I don't think that's the problem.

Rather it seems like the problem is somewhere else further away from me.

# dig mx dizum.com
dizum.com. 705 IN MX 10 smtp.dizum.com.

# ping -c 4 smtp.dizum.com
PING smtp.dizum.com (45.66.35.219) 56(84) bytes of data.

--- smtp.dizum.com ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3045ms

# nc -zv smtp.dizum.com 25
nc: connect to smtp.dizum.com port 25 (tcp) failed: Connection timed out

# traceroute -n -T smtp.dizum.com
traceroute to smtp.dizum.com (45.66.35.219), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 45.79.12.101 0.612 ms 0.591 ms 0.578 ms
6 23.203.147.40 1.288 ms 1.314 ms 1.248 ms
7 140.174.28.101 2.572 ms 1.999 ms 1.325 ms
8 129.250.4.19 1.569 ms * 15.654 ms
9 * * 129.250.2.69 1.401 ms
10 129.250.5.13 34.865 ms 30.576 ms *
11 * 62.115.138.70 33.038 ms 33.119 ms
12 * 129.250.2.182 104.728 ms *
13 129.250.5.2 109.922 ms 62.115.137.4 120.742 ms 120.657 ms
14 62.115.120.229 120.771 ms 120.063 ms 129.250.7.65 113.660 ms
15 62.115.169.177 118.507 ms 118.487 ms 128.241.6.27 113.323 ms
16 45.138.38.34 113.296 ms 113.470 ms 185.56.28.107 129.789 ms
17 * * 185.56.28.132 117.607 ms
18 45.138.38.41 122.247 ms 122.930 ms 122.727 ms
19 45.138.38.42 120.768 ms * 121.263 ms
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

--
Grant. . . .

On 12/2/23 13:26, Grant Taylor wrote:
> On 12/2/23 10:38, SEC3 wrote:
>> I am not experiencing this at my shalo mixmaster remailer nor at my
>> SEC3 Pinger.
>
> Hum.
>
>> During your absence from apa-s there was a change at Dizum. A new
>> hostname and IP address.
>
> I don't think that's the problem.
>
> Rather it seems like the problem is somewhere else further away from me.
>
>
>
> # dig mx dizum.com
> dizum.com.              705     IN      MX      10 smtp.dizum.com.
>
>
> # ping -c 4 smtp.dizum.com
> PING smtp.dizum.com (45.66.35.219) 56(84) bytes of data.
>
> --- smtp.dizum.com ping statistics ---
> 4 packets transmitted, 0 received, 100% packet loss, time 3045ms
>
>
> # nc -zv smtp.dizum.com 25
> nc: connect to smtp.dizum.com port 25 (tcp) failed: Connection timed out
>
>
> # traceroute -n -T smtp.dizum.com
> traceroute to smtp.dizum.com (45.66.35.219), 30 hops max, 60 byte packets
>  1  * * *
>  2  * * *
>  3  * * *
>  4  * * *
>  5  45.79.12.101  0.612 ms  0.591 ms  0.578 ms
>  6  23.203.147.40  1.288 ms  1.314 ms  1.248 ms
>  7  140.174.28.101  2.572 ms  1.999 ms  1.325 ms
>  8  129.250.4.19  1.569 ms *  15.654 ms
>  9  * * 129.250.2.69  1.401 ms
> 10  129.250.5.13  34.865 ms  30.576 ms *
> 11  * 62.115.138.70  33.038 ms  33.119 ms
> 12  * 129.250.2.182  104.728 ms *
> 13  129.250.5.2  109.922 ms 62.115.137.4  120.742 ms  120.657 ms
> 14  62.115.120.229  120.771 ms  120.063 ms 129.250.7.65  113.660 ms
> 15  62.115.169.177  118.507 ms  118.487 ms 128.241.6.27  113.323 ms
> 16  45.138.38.34  113.296 ms  113.470 ms 185.56.28.107  129.789 ms
> 17  * * 185.56.28.132  117.607 ms
> 18  45.138.38.41  122.247 ms  122.930 ms  122.727 ms
> 19  45.138.38.42  120.768 ms *  121.263 ms
> 20  * * *
> 21  * * *
> 22  * * *
> 23  * * *
> 24  * * *
> 25  * * *
> 26  * * *
> 27  * * *
> 28  * * *
> 29  * * *
> 30  * * *
>

Yes, something amiss for sure. But not affecting everyone equally.
Tincture pinger is showing 3 straight days of no ping replies from
Dizum. But Frell, Mixmin and SEC3 pingers *are* talking to Dizum.

--
SEC3

YAMN Help Tutorial - https://www.sec3.net/yamnhelp/

On 12/2/23 13:30, SEC3 wrote:
> Yes, something amiss for sure. But not affecting everyone equally.
> Tincture pinger is showing 3 straight days of no ping replies from
> Dizum. But Frell, Mixmin and SEC3 pingers *are* talking to Dizum.

Weird.

--
Grant. . . .

Grant Taylor <gtaylor@tnetconsulting.net> wrote:
: On 12/2/23 13:30, SEC3 wrote:
:> Yes, something amiss for sure. But not affecting everyone equally.
:> Tincture pinger is showing 3 straight days of no ping replies from
:> Dizum. But Frell, Mixmin and SEC3 pingers *are* talking to Dizum.
:
: Weird.x

Currently dizum (45.66.35.0/24) is routed via AS47482, we will move this to AS61125.
We did some preliminary work to make the change go seamless, however that is already not the case, so we will byte the bullet Sun/Mon/Tue.
It seems that connections via AS1299 are f*kked, so this will be the case untill the BGP announcements have been done and picked up. As we also>

Alex de Joode

On 12/3/23 08:32, Alex de Joode wrote:
> Currently dizum (45.66.35.0/24) is routed via AS47482, we will move this
> to AS61125.
> We did some preliminary work to make the change go seamless, however
> that is already not the case, so we will byte the bullet Sun/Mon/Tue.
> It seems that connections via AS1299 are f*kked, so this will be the
> case untill the BGP announcements have been done and picked up. As we
> also>

Thank you for the information.

I'll ignore the issue for a few more days in the hopes that connections
will establish and that store-and-forward network of email will work
like it is capable and ultimately deliver the waiting messages.

--
Grant. . . .

Grant Taylor <gtaylor@tnetconsulting.net> wrote:
: On 12/3/23 08:32, Alex de Joode wrote:
:> Currently dizum (45.66.35.0/24) is routed via AS47482, we will move this
:> to AS61125.
:> We did some preliminary work to make the change go seamless, however
:> that is already not the case, so we will byte the bullet Sun/Mon/Tue.
:> It seems that connections via AS1299 are f*kked, so this will be the
:> case untill the BGP announcements have been done and picked up. As we
:> also>
:
: Thank you for the information.
:
: I'll ignore the issue for a few more days in the hopes that connections
: will establish and that store-and-forward network of email will work
: like it is capable and ultimately deliver the waiting messages.

I've added an alternate IP (45.66.33.250) for smtp.dizum.com, so thinsg should work again. I'll change it back once the migration of the 35.0/24 range to as61125 have been finalised.
--
Alex de Joode

Alex de Joode <usura@local.smersh.su> wrote:
>
> I've added an alternate IP (45.66.33.250) for smtp.dizum.com, so thinsg should work again. I'll change it back once the migration of the 35.0/24 range to as61125 have been finalised.
> --
> Alex de Joode

Great! Thank you.

On 12/3/23 11:50, Alex de Joode wrote:
> I've added an alternate IP (45.66.33.250) for smtp.dizum.com, so thinsg should work again. I'll change it back once the migration of the 35.0/24 range to as61125 have been finalised.

Thank you for that.

The messages cleared as soon as my MTA detected the change.

--
Grant. . . .

Alex de Joode wrote:

> Grant Taylor <gtaylor@tnetconsulting.net> wrote:
> : On 12/3/23 08:32, Alex de Joode wrote:
> :> Currently dizum (45.66.35.0/24) is routed via AS47482, we will
> move this :> to AS61125.
> :> We did some preliminary work to make the change go seamless,
> however :> that is already not the case, so we will byte the bullet
> Sun/Mon/Tue. :> It seems that connections via AS1299 are f*kked, so
> this will be the :> case untill the BGP announcements have been done
> and picked up. As we :> also>
> :
> : Thank you for the information.
> :
> : I'll ignore the issue for a few more days in the hopes that
> connections : will establish and that store-and-forward network of
> email will work : like it is capable and ultimately deliver the
> waiting messages.
>
> I've added an alternate IP (45.66.33.250) for smtp.dizum.com, so
> thinsg should work again. I'll change it back once the migration of
> the 35.0/24 range to as61125 have been finalised.

Hi Alex,

I get errors, with smtp.dizum.com.

Error Mail: 452 4.3.1 Insufficient system storage

Regards
Stefan
--
----Ed25519 Signature----
4d21cb51f3941b77287d151dcba63078cfd77b4c6c8b11f093d3c82f1569e111
726b48f947a575bd8e2e689aab285b4cbe84d6c8a960a3a210a6e4e2d2e2c605

On 12/6/23 12:23, Stefan Claas wrote:
> I get errors, with smtp.dizum.com.

I too am seeing errors with dizum again.

> Error Mail: 452 4.3.1 Insufficient system storage

+49 queued messages.

--
Grant. . . .

On 12/3/23 11:50, Alex de Joode wrote:
> I've added an alternate IP (45.66.33.250) for smtp.dizum.com, so thinsg
> should work again. I'll change it back once the migration of the 35.0/24
> range to as61125 have been finalised.

Did you forget to update DNS?

dig +trace still shows 45.66.33.250 as the IP address for smtp.dizum.com
which no longer responds ICMP nor TCP port 25.

It looks lik3 45.66.35.219 does respond to both ICMP and TCP port 25.

--
Grant. . . .

Grant Taylor <gtaylor@tnetconsulting.net> wrote:
: On 12/3/23 11:50, Alex de Joode wrote:
:> I've added an alternate IP (45.66.33.250) for smtp.dizum.com, so thinsg
:> should work again. I'll change it back once the migration of the 35.0/24
:> range to as61125 have been finalised.
:
: Did you forget to update DNS?
:
: dig +trace still shows 45.66.33.250 as the IP address for smtp.dizum.com
: which no longer responds ICMP nor TCP port 25.
:
: It looks lik3 45.66.35.219 does respond to both ICMP and TCP port 25.

Good catch. Fixed.

--
Alex de Joode

Alex de Joode <usura@local.smersh.su> wrote in
news:ukif4j$fqf$1@toxic.dizum.net:

> Grant Taylor <gtaylor@tnetconsulting.net> wrote:
>: On 12/3/23 08:32, Alex de Joode wrote:
>:> Currently dizum (45.66.35.0/24) is routed via AS47482, we will move
>:> this
>:> to AS61125.
>:> We did some preliminary work to make the change go seamless, however
>:> that is already not the case, so we will byte the bullet
>:> Sun/Mon/Tue. It seems that connections via AS1299 are f*kked, so
>:> this will be the case untill the BGP announcements have been done
>:> and picked up. As we also>
>:
>: Thank you for the information.
>:
>: I'll ignore the issue for a few more days in the hopes that
>: connections will establish and that store-and-forward network of
>: email will work like it is capable and ultimately deliver the waiting
>: messages.
>
> I've added an alternate IP (45.66.33.250) for smtp.dizum.com, so
> thinsg should work again. I'll change it back once the migration of
> the 35.0/24 range to as61125 have been finalised.

Thanks!

Grant Taylor <gtaylor@tnetconsulting.net> wrote in
news:ul2gnn$ro7$1@tncsrv09.home.tnetconsulting.net:

> On 12/3/23 11:50, Alex de Joode wrote:
>> I've added an alternate IP (45.66.33.250) for smtp.dizum.com, so
>> thinsg should work again. I'll change it back once the migration of
>> the 35.0/24
>> range to as61125 have been finalised.
>
> Did you forget to update DNS?
>
> dig +trace still shows 45.66.33.250 as the IP address for
> smtp.dizum.com which no longer responds ICMP nor TCP port 25.
>
> It looks lik3 45.66.35.219 does respond to both ICMP and TCP port 25.

Let's have a look.

[Historical] Injection-Info: sewer.dizum.com - 2001::1/128

[Random Internet DNS server]

nslookup sewer.dizum.com
sewer.dizum.com
45.66.35.221
25 Error: TimedOut

nslookup 45.66.35.221
Name: sewer.dizum.com
Address: 45.66.35.221
25 Error: TimedOut

nslookup smtp.dizum.com
Name: smtp.dizum.com
Address: 45.66.33.250
25 Error: TimedOut

nslookup 45.66.33.250
Name: no-reverse-yet.spectreops.net
Address: 45.66.33.250
25 Error: TimedOut

nslookup zewer.dizum.com
Name: zewer.dizum.com
Address: 45.66.35.219
25 220 zewer.dizum.com ESMTP Postfix (Debian/GNU)

nslookup 45.66.35.219
Name: zewer.dizum.com
Address: 45.66.35.219
25 220 zewer.dizum.com ESMTP Postfix (Debian/GNU)

MX
preference: 10
exchange: smtp.dizum.com

[I run my own DNS servers]

dnscmd /ClearCache
.. completed successfully.
Command completed successfully.

nslookup smtp.dizum.com
Server: localhost
Address: ::1

Non-authoritative answer:
Name: smtp.dizum.com
Address: 45.66.35.219

[Back to client]

ipconfig /flushdns
Successfully flushed the DNS Resolver Cache.

nslookup smtp.dizum.com
Name: smtp.dizum.com
Address: 45.66.35.219

nslookup sewer.dizum.com
Name: sewer.dizum.com
Address: 45.66.35.221

nslookup zewer.dizum.com
Name: zewer.dizum.com
Address: 45.66.35.219

>>>>>>>>>>>>>>>
We will have to look at the below again later
>>>>>>>>>>>>>>>

nslookup -d2 45.66.35.219

{SKIP extraneous}

QUESTIONS:
219.35.66.45.in-addr.arpa, type = PTR, class = IN
ANSWERS:
-> 219.35.66.45.in-addr.arpa
type = PTR, class = IN, dlen = 17
name = zewer.dizum.com
ttl = 3600 (1 hour)

------------
Name: zewer.dizum.com
Address: 45.66.35.219

<<<<<<<<<<<<<<<<<<<<<<
> set type=MX
> dizum.com

dizum.com MX preference = 10, mail exchanger = smtp.dizum.com

smtp.dizum.com internet address = 45.66.35.219
<<<<<<<<<<<<<<<<<<<<<<

<<<<<<<<<<<<<<<<<<<<<<
ping smtp.dizum.com

Pinging smtp.dizum.com [45.66.35.219] with 32 bytes of data:
Reply from 45.66.35.219: bytes=32 time=165ms TTL=51
Reply from 45.66.35.219: bytes=32 time=160ms TTL=51
Reply from 45.66.35.219: bytes=32 time=164ms TTL=51
Reply from 45.66.35.219: bytes=32 time=161ms TTL=51

Ping statistics for 45.66.35.219:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 160ms, Maximum = 165ms, Average = 162ms

ping zewer.dizum.com

Pinging zewer.dizum.com [45.66.35.219] with 32 bytes of data:
Reply from 45.66.35.219: bytes=32 time=160ms TTL=51
Reply from 45.66.35.219: bytes=32 time=178ms TTL=51
Reply from 45.66.35.219: bytes=32 time=163ms TTL=51
Reply from 45.66.35.219: bytes=32 time=163ms TTL=51

Ping statistics for 45.66.35.219:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 160ms, Maximum = 178ms, Average = 166ms

ping sewer.dizum.com

Pinging sewer.dizum.com [45.66.35.221] with 32 bytes of data:
Request timed out.
<<<<<<<<<<<<<<<<<<<<<<

The rest of the Interent must also catch up as Alex noted.

Thank for your support and services Alex.

On 12/9/23 15:27, Alex de Joode wrote:
> Good catch. Fixed.

;-)

I found it because email hadn't drained from the spool when I last
looked in response to your other "fixed" message.

I just looked and it looks like everything spooled for Dizum has now
drained / been delivered.

Thank you for taking care of things.

Have a good day.

--
Grant. . . .

Grant Taylor <gtaylor@tnetconsulting.net> wrote:
: On 12/9/23 15:27, Alex de Joode wrote:
:> Good catch. Fixed.
:
: ;-)
:
: I found it because email hadn't drained from the spool when I last
: looked in response to your other "fixed" message.
:
: I just looked and it looks like everything spooled for Dizum has now
: drained / been delivered.
:
: Thank you for taking care of things.
:
: Have a good day.
:

tnx && yw

--
Alex de Joode