Den 21.11.2022 18.06, skrev Simon Ser: > On Monday, November 21st, 2022 at 18:02, Simon Ser <contact@xxxxxxxxxxx> wrote: > >> On Monday, November 21st, 2022 at 17:52, Noralf Trønnes noralf@xxxxxxxxxxx wrote: >> >>> Den 21.11.2022 14.33, skrev Simon Ser: >>> >>>> I think you can apply for a linux.dev mailbox 1. >>> >>> Yeah you're right, I didn't know about that possibility. >>> But it depends on whether or not I can just use their smtp server and >>> keep my current email address. This looks like what's the problem with >>> my current ISP, I need to use the email account I have in their email >>> service (that I've never used) for sending through their smtp server, >>> but I want to send From: another email address. >> >> That's not possible. It breaks DKIM, so your emails will end up in Spam >> folders or be rejected. You need to use the SMTP server tied to your >> email address. > > That said, you can send patches from an email address different from > the one in your patches. IOW, you can send patches committed by > <noralf@xxxxxxxxxxx> from any email account. > > The From in the email header won't match the commit, but the very first > line of the patch will hold that information. Thanks that was useful information. I've seen the DKIM abbr. but haven't looked into the meaning of it. I tried: git send-email --from=noralf.tronnes@xxxxxxxxxxxxxx --reply=noralf@xxxxxxxxxxx and now I'm getting 'pass' in the Authentication-Results field, so that's progress. I'm still not getting all the emails through, so I still have that problem, I'll have to wait and see what the ISP can tell me. But this means that a linux.dev mailbox is an option for me should my ISP be a blocker. Noralf.
