Moin,
> I am intentionally double-posting this email (once from my personal
> domain, once from reads-this-mailinglist.com) to see how well
> preserving messages as sent works/impacts deliverability.
Some results on this: For the mail from @reads-this-mailinglist.com all
DMARC reports indicated
> ... however I'm getting different errors now for the Slack-group
> specific URLs:
>
> ...
>
> validation failure : signatures from unknown keys
> from 2620:fe::fe
Was able to fix this by running `unbound-anchor` after fixing my system
clock. I think everything is working normally now.
Thanks!
> You can use rdate to jump the clock instead.
That updated my system clock to the correct time. dig queries against
Slack now work as expected, however I'm getting different errors now for
the Slack-group specific URLs:
```
# dig @::1 kubernetes.slack.com
; <<>> DiG 9.10.6 <<>>
On 2024-03-18, Evan Sherwood wrote:
>> Wild guess, your time is off.
>
> Huh, I think you're right. `date` shows me 7 hours ahead of my timezone.
>
> I restarted ntpd and I see no errors in /var/log/daemon, but the time is
> still off. I should be 1200 PDT but it's showing me as 1900 PDT (not
>
> Wild guess, your time is off.
Huh, I think you're right. `date` shows me 7 hours ahead of my timezone.
I restarted ntpd and I see no errors in /var/log/daemon, but the time is
still off. I should be 1200 PDT but it's showing me as 1900 PDT (not
UTC).
What do I do to fix this? Pretty sure I
They seem to be using extremely short-lived signatures, probably created
by an online-signer.
$ dig +short ns slack.com
ns-1493.awsdns-58.org.
ns-166.awsdns-20.com.
ns-1901.awsdns-45.co.uk.
ns-606.awsdns-11.net.
$ TZ=UTC dig @ns-1493.awsdns-58.org. +norec +dnssec +multiline +nocrypto
slack.com
I have an unbound server using Quad9 as an upstream DNS provider. I have
been unable to resolve records from slack.com recently using my local
unbound.
On the server:
```
# dig @::1 slack.com
; <<>> dig 9.10.8-P1 <<>> @::1 slack.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;;
Claudio Miranda :
> MATE in OpenBSD does have a display utility. Via the command line,
> it's called mate-display-properties. Launching from the MATE menu,
> it's in System --> Preferences --> Hardware --> Displays.
>
> You might have been missing some of the MATE packages.
Strange, I started
MATE in OpenBSD does have a display utility. Via the command line,
it's called mate-display-properties. Launching from the MATE menu,
it's in System --> Preferences --> Hardware --> Displays.
You might have been missing some of the MATE packages.
On Mon, Mar 18, 2024 at 11:48 AM Dan wrote:
>
>
Hello,
In these days searching to fix security details on my station, eg. reducing
the exposure to GUI programs,
etc. I tried to port my dev environment from Xfce to Mate and here some of my
thoughts:
1) Mate is much lighter, eg tcl/tk software go up like a twist;
2) by multi screens the
10 matches
Mail list logo
