On Sun, 30 Oct 2022 15:10:59 +0100, Merlin Büge wrote:
> Hi,
>
> On Sun, 30 Oct 2022 11:42:24 +, Spencer Collyer wrote:
> > My initial idea was something like the following:
> >
> > 1) Install a basic Arch system on the new computer
> > 2) Get the list of installed packages from the old compu
On Sun, 30 Oct 2022 20:00:39 +0800, 謝晉凡 Hsieh Chin Fan wrote:
> > 2) Get the list of installed packages from the old computer (I think
> > there is a way to do this using Pacman?)
>
> pacman -Qe
>
> > 5) Copy over my /home directory
> > 6) Copy over various data directories/partitions I have
>
On Sun, 30 Oct 2022 12:28:41 -0400, David Rosenstrauch wrote:
> On 10/30/22 7:42 AM, Spencer Collyer wrote:
> > I am looking to replace my current desktop PC, which is getting on
> > for 8 years old now, with a more up-to-date one. Ideally I want the
> > new one to be set up the same as my current
On 10/30/22 19:04, Jaron Kent-Dobias wrote:
On Sunday, 30 October 2022 at 23:57 (+0100), Jaron Kent-Dobias wrote:
Confirmation: when Arch Linux forwards a base8 encoded email to the
list, it mangles the DKIM. It does appear to be an Arch problem!
Excellent debugging - congrats for finding the
On Sunday, 30 October 2022 at 23:57 (+0100), Jaron Kent-Dobias wrote:
Confirmation: when Arch Linux forwards a base8 encoded email to the
list, it mangles the DKIM. It does appear to be an Arch problem!
One last email: what the lists are specifically doing is rewriting 8bit
encoded emails in a
On Sunday, 30 October 2022 at 23:56 (+0100), Jaron Kent-Dobias wrote:
Consider this email as a test for what the Arch Liunx lists do: α, β,
γ, …
Confirmation: when Arch Linux forwards a base8 encoded email to the
list, it mangles the DKIM. It does appear to be an Arch problem!
Now to deal wi
On Sunday, 30 October 2022 at 18:52 (-0400), David Rosenstrauch wrote:
On 10/30/22 6:48 PM, Jaron Kent-Dobias wrote:
On Sunday, 30 October 2022 at 23:45 (+0100), Jaron Kent-Dobias wrote:
Perhaps something about the content transfer encoding is causing
the problem?
After a quick google, this a
On 10/30/22 6:48 PM, Jaron Kent-Dobias wrote:
On Sunday, 30 October 2022 at 23:45 (+0100), Jaron Kent-Dobias wrote:
Perhaps something about the content transfer encoding is causing the
problem?
After a quick google, this appears to be a known and old problem:
https://stbuehler.de/blog/articl
On Sunday, 30 October 2022 at 23:45 (+0100), Jaron Kent-Dobias wrote:
Perhaps something about the content transfer encoding is causing the
problem?
After a quick google, this appears to be a known and old problem:
https://stbuehler.de/blog/article/2011/05/19/dkim_fails_at_content-transfer-encod
On Sunday, 30 October 2022 at 18:30 (-0400), David Rosenstrauch wrote:
I guess it's working now, so all's well that ends well? But still
really weird.
Maybe not - your latest email also failed DKIM for me. Regarding Genes'
email, python-dkim's 'dkimverify' utility also registers a fail.
One
For what it's worth, I get the same from time to time.
I've blamed my setup and/or OpenDKIM up until this point.
And I will try to evaluate the recommendations from Gene as well as
correlate my error messages with the headers given here.
//Anton
On 10/30/22 23:37, David Rosenstrauch wrote:
On 10/30/22 6:27 PM, Genes Lists wrote:
Hi David / Jaron
One thought - typically dmarc gets dkim validation from a separate
milter dmarc.
And many folks still run opendkim which is unmaintained.
Versions prior to 2.11.0.Beta2 (which arch kindly offers) are definitely
broken. I don't even t
On 10/30/22 6:13 PM, Jaron Kent-Dobias wrote:
On Sunday, 30 October 2022 at 17:58 (-0400), David Rosenstrauch wrote:
Anyone know why these fail messages might be happening?
FWIW, my OpenDKIM with default settings flagged your earlier email with
a DKIM fail, but passed this one. The failure
Hi David / Jaron
One thought - typically dmarc gets dkim validation from a separate
milter dmarc.
And many folks still run opendkim which is unmaintained.
Versions prior to 2.11.0.Beta2 (which arch kindly offers) are definitely
broken. I don't even trust that one.
Jaron do you run opendk
On Sunday, 30 October 2022 at 17:58 (-0400), David Rosenstrauch wrote:
After posting a message to this list earlier today, I immediately
received nearly a dozen DKIM fail messages, all being sent by the
"OpenDMARC Filter" at various domains, and all saying that the DKIM
fail reason was "signatu
After posting a message to this list earlier today, I immediately
received nearly a dozen DKIM fail messages, all being sent by the
"OpenDMARC Filter" at various domains, and all saying that the DKIM fail
reason was "signature verification failed".
I raised this issue with support at my hostin
> 2) Get the list of installed packages from the old computer (I think
> there is a way to do this using Pacman?)
pacman -Qe
--
謝晉凡 Hsieh Chin Fan | https://topo.tw/about
On 10/30/22 7:42 AM, Spencer Collyer wrote:
I am looking to replace my current desktop PC, which is getting on for
8 years old now, with a more up-to-date one. Ideally I want the new one
to be set up the same as my current one, which has been running on Arch
since I first got it.
What is the
Hi Spencer,
I haven't tested it but I think a better solution to your issue would be to
create a RAID1 with both hard disks. This way the kernel will keep both in
sync automatically and you don't need to dd every night. If one fails the
raid will be degraded but still bootable so you can just use
On 2022-10-30 at 15:10:59 +0100,
Merlin Büge wrote:
> > 5) Copy over my /home directory
>
> If you have the time and care, instead of copying the entire /home,
> you could manually copy the contents and decide what you want to
> keep. You may want to omit ~/.cache and some configuration dotfiles
Hi,
On Sun, 30 Oct 2022 11:42:24 +, Spencer Collyer wrote:
> My initial idea was something like the following:
>
> 1) Install a basic Arch system on the new computer
> 2) Get the list of installed packages from the old computer (I think
> there is a way to do this using Pacman?) 3) Somehow ge
On Thu, 27 Oct 2022 16:02:17 +0200
Ralf Mardorf wrote:
> 1. Format the the new drive with the wanted file system.
> 2. Restart the computer and boot a live Linux from DVD, USB or what ever
>media you prefer.
> 3. Mount the old partition, mount the new partition.
> 4. Open a terminal.
> 5. Bec
> 2) Get the list of installed packages from the old computer (I think
> there is a way to do this using Pacman?)
pacman -Qe
> 5) Copy over my /home directory
> 6) Copy over various data directories/partitions I have
> I found thread https://bbs.archlinux.org/viewtopic.php?id=171726...
Yes, rsyn
Hi,
This is sort-of a follow-on to my earlier message regarding how to best
set up a new desktop to match the existing one I have running Arch.
I'm intending that my new computer will have an M2 drive as the boot
disk. As well as the OS it will also hold my /home partition.
Because of a bad expe
I am looking to replace my current desktop PC, which is getting on for
8 years old now, with a more up-to-date one. Ideally I want the new one
to be set up the same as my current one, which has been running on Arch
since I first got it. I keep my Arch up-to-date by running a full
update roughly eve
25 matches
Mail list logo
