menuentry "NetBSD" {
insmod part_gpt
insmod chain
chainloader (hd0,gpt2)/EFI/boot/bootx64.efi
}
I am not sure I followed everything, but if you've already gone that far
and use GRUB instead, why not load the kernel directly from there?
menuentry "netbsd -v" {
I have a NetBSD 9.2, postfix and opendkim based setup.
If I send emails using command line 'mail' client I can see that dkim
header is getting attached.
However if I use mutt or neomutt the headers don't contain dkim.
Can someone advise about the mutt/neomutt setting to look for, for this
"Aaron B." writes:
> On Sun, 30 Oct 2022 16:54:34 -0700
> Andy Ruhl wrote:
>
>> On Sun, Oct 30, 2022 at 2:18 PM Aaron B. wrote:
>
>> There used to be a way to build a kernel with a hardcoded NFS root
>> option. I dug around in evbarm and aarch64 and didn't see something
>> familiar to me
On Mon, 31 Oct 2022 at 07:07, Pierre-Philipp Braun wrote:
>
> > menuentry "NetBSD" {
> > insmod part_gpt
> > insmod chain
> > chainloader (hd0,gpt2)/EFI/boot/bootx64.efi
> > }
>
> I am not sure I followed everything, but if you've already gone that far
> and use GRUB
On Mon, Oct 31, 2022 at 05:53:10PM +0530, Mayuresh wrote:
> If I send emails using command line 'mail' client I can see that dkim
> header is getting attached.
>
> However if I use mutt or neomutt the headers don't contain dkim.
mutt's sendmail variable defaults to the following, I checked it in
On Mon, Oct 31, 2022 at 05:53:10PM +0530, Mayuresh wrote:
> I have a NetBSD 9.2, postfix and opendkim based setup.
>
> If I send emails using command line 'mail' client I can see that dkim
> header is getting attached.
>
> However if I use mutt or neomutt the headers don't contain dkim.
>
> Can
On Mon, Oct 31, 2022 at 05:53:10PM +0530, Mayuresh wrote:
> However if I use mutt or neomutt the headers don't contain dkim.
It seems that "set from" to my email alias which is from a different
domain is the problem. If I use local domain then dkim gets inserted.
Is there any way I can attach
On Mon, Oct 31, 2022 at 11:53:51AM -0400, Jan Schaumann wrote:
> That'd be an OpenDKIM configuration thing.
Oh yes, thanks. I didn't realize I could set up those keys for alias
domain as well. Now added and dkim is getting attached.
--
Mayuresh
On Mon, Oct 31, 2022 at 08:21:01PM +0530, Mayuresh wrote:
> sendmail="/usr/sbin/sendmail -oem -oi"
And if I try the same command on command line directly (with -t
added) then dkim does get inserted.
Really confusing why it doesn't happen when using mutt.
--
Mayuresh
On Mon, Oct 31, 2022 at 10:10:10AM -0500, Jonathan A. Kollasch wrote:
> Is mutt sending through the same path as your sendmail(1)?
In /etc/mailer.conf I see the following (but I do not know whether this is
what mail command uses, 'man mail' doesn't point to this file):
sendmail
Mayuresh wrote:
> So, in short, if I don't own the alias domain, I can't sign dkim?
Correct - that is the point of DKIM.
-Jan
Mayuresh wrote:
> On Mon, Oct 31, 2022 at 05:53:10PM +0530, Mayuresh wrote:
> > However if I use mutt or neomutt the headers don't contain dkim.
>
> It seems that "set from" to my email alias which is from a different
> domain is the problem. If I use local domain then dkim gets inserted.
>
>
On Mon, Oct 31, 2022 at 09:50:40PM +0530, Mayuresh wrote:
> I didn't realize I could set up those keys for alias domain as well. Now
> added and dkim is getting attached.
But, now just the key gets attached. It can't be validated because the
alias domain is not owned by me, so can't create DNS
On Mon, Oct 31, 2022 at 12:54:52PM -0400, Jan Schaumann wrote:
> Mayuresh wrote:
> > So, in short, if I don't own the alias domain, I can't sign dkim?
>
> Correct - that is the point of DKIM.
I have noticed some mail servers (of a bank in a recent incidence , seems
Microsoft based from the log
14 matches
Mail list logo
