Re: Avoid ending up in Spam

Hi, having relaxed the DMARC rules, please let me know if this message was more successful than those previously sent from jakob@givoni.dk Thanks! On Sat, May 30, 2020 at 1:20 AM Ben Ramsey <ben@benramsey.com> wrote: > > > On May 29, 2020, at 18:01, Reindl Harald <h.reindl@thelounge.net> wrote: > > > > > > > > Am 30.05.20 um 00:58 schrieb Ben Ramsey: > >>> On May 29, 2020, at 17:34, Jakob Givoni <jgivoni.php@gmail.com> wrote: > >>> > >>> On Sat, May 30, 2020 at 12:07 AM Benas IML <benas.molis.iml@gmail.com> > >>> wrote: > >>>> > >>>> Here's a quote from Ben Ramsey that basically sums up the problem: > >>>> > >>>>> This appears to be happening due to DMARC rules on the domains of the > >>>>> senders. > >>>>> I had the same thing happen to my emails, so I had to relax my DMARC > >>>>> rules. If > >>>>> your rules are set too strict, servers see the From address coming from a > >>>>> server not authorized by the domain, so it gets quarantined. > >>>> > >>> > >>> Shouldn't I just be able to add lists.php.net or something to my SPF > >>> record for my domain then? > >> > >> > >> That might work. I haven’t tried it. I’ll try to look into it next week and see > >> what I can figure out. > > > > how do you imagine that a SPF for any random domain could affect > > envelope senders ending with "@lists.php.net"? > > > > DMARC is not just about SPF > > SPF is not about "From address" in the From-Header > > > I thought SPF allowed you to specify domains/IPs that are allowed to send email “from” your > domain. > > Why wouldn’t something like this help? > > v=spf1 include:_spf.google.com include:lists.php.net ~all > > (In this example, assuming one already has an SPF record allowing Google Apps to send email for > their domain.) > > Cheers, > Ben >