21 Jun
2022
21 Jun
'22
9:59 a.m.
On Wed, Jun 15, 2022 at 09:37:46AM -0600, Grant Taylor via COFF wrote:
On 6/14/22 11:14 PM, Tomasz Rola wrote:
As you might know, when the target does not receive email, sender will
try to send it to backup receiver(s), here:
$ dig classiccmp.org MX
; <<>> DiG 9.16.27-Debian <<>> classiccmp.org MX
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27228
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;classiccmp.org. IN MX
;; ANSWER SECTION:
classiccmp.org. 1799 IN MX 10 mx2.ezwind.net.
classiccmp.org. 1799 IN MX 10 mx1.ezwind.net.
[...]
and from this:
[
https://en.wikipedia.org/wiki/MX_record
]
I infer that the actual date when email will get dumped to /dev/null
depends on settings of relevant mail servers (MTAs) - either sending one
or backup receiver. If there is a way to get those value remotely by
talking to the server, I have not yet dug it up, nor looked.
I assume it might be about two weeks in case of classiccmp and each
email author should be notified when his email fails to reach a
recipient. So, we will see (experiment by doing nothing...),
--
Regards,
Tomasz Rola
--
** A C programmer asked whether computer had Buddha's nature. **
** As the answer, master did "rm -rif" on the programmer's home **
** directory. And then the C programmer became enlightened... **
** **
** Tomasz Rola mailto:tomasz_rola@bigfoot.com **
Ah. I too am missing a "noise" coming
from that direction. A
noise, well, a buzz, of bees always repairing their hardware,
nothing negative.
I think that it will be interesting to see how much email makes it
through once services are brought back on line.
I've always retained mail for two weeks before giving up. Not as
may people do so for as long any more.