Alan,
On 2020-07-29 23:58, Alan Corey wrote:
Could it be because you changed the subject line? It wouldn't
surprise me if something does a hash of the subject. I don't know a
lot about secure email with SSL and all that.
I don't think so - posting this note also caused me to receive similar
error messages - even though in both cases the email made it onto the
list . . must be some sort of DKIM problem I think . .
Thanks,
Phil.
On 7/29/20, Philip Rhoades <phil@xxxxxxxxxxxxx> wrote:
People,
I tried to reply to my previous thread with a slightly modified
Subject:
SOLVED: Re: Anybody got Google Meet going on Linux (Fedora) with
just
ALSA (ie not with PulseAudio)?
and received a response:
This is an authentication failure report for an email message received
from pricom.com.au on Wed Jul 29 10:43:32 UTC 2020
Received-SPF: pass (domain of lists.sourceforge.net designates
216.105.38.7 as permitted sender)
Authentication-Results: atlas201.free.mail.ir2.yahoo.com;
dkim=perm_fail header.i=@sourceforge.net header.s=x;
dkim=perm_fail header.i=@sf.net header.s=x;
dkim=perm_fail header.i=@pricom.com.au header.s=phr1;
spf=pass smtp.mailfrom=lists.sourceforge.net;
dmarc=success(p=NONE,sp=NONE) header.from=pricom.com.au;
.
.
How can I fix this?
Thanks,
Phil.
--
Philip Rhoades
PO Box 896
Cowra NSW 2794
Australia
E-mail: phil@xxxxxxxxxxxxx
_______________________________________________
Alsa-user mailing list
Alsa-user@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/alsa-user
--
Philip Rhoades
PO Box 896
Cowra NSW 2794
Australia
E-mail: phil@xxxxxxxxxxxxx
_______________________________________________
Alsa-user mailing list
Alsa-user@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/alsa-user
