Hi — not a code issue, sorry. This is about the domain in this repo's homepage, and I thought you would rather know than not.
What I found
loresoft.com publishes DMARC, but with p=none.
p=none is report-only. It tells you spoofing is happening; it does not stop a single message. Mail that fails your checks ("v=spf1 include:spf.protection.outlook.com -all") is still delivered to the recipient's inbox. Your current record: "v=DMARC1; p=none; rua=mailto:62c75d5449c743ee88c772fe6156bd42@dmarc-reports.cloudflare.net"
Verify it yourself in one line:
dig +short TXT _dmarc.loresoft.com
dig +short TXT loresoft.com | grep spf1
The fix — free, no strings
Add this TXT record and you go from nothing to full visibility immediately, with zero risk of losing real mail (p=none does not affect delivery):
Host: _dmarc.loresoft.com
Type: TXT
Value: v=DMARC1; p=none; rua=mailto:dmarc@loresoft.com; fo=1
That is genuinely the whole first step. Point rua at a mailbox you read, wait a week, and the aggregate reports will show you every system sending as loresoft.com — usually a couple you forgot about (a billing tool, a CRM, an old marketing platform). Once those are all passing, you move to p=quarantine and then p=reject, and spoofing stops working.
If you would rather not run that project
The record above is easy. The part that eats time is the middle bit — reading the XML aggregate reports, hunting down every legitimate sender, getting SPF and DKIM aligned for each one, and stepping the policy up without silently dropping your own invoices or password resets. That is the part people start and abandon at p=none for years.
I do that as a fixed-scope job: $90, about two weeks, and you end at p=reject with a one-page sender inventory. No retainer, no subscription — you pay when it is done and enforcing. If it turns out your setup is trivial I will say so and you can finish it yourself for free.
Either way, please add the record. Reply here if you want the paid version or if anything above does not match what you see.
— Fayaz Bin Salam (@p32929)
Hi — not a code issue, sorry. This is about the domain in this repo's homepage, and I thought you would rather know than not.
What I found
loresoft.compublishes DMARC, but withp=none.p=noneis report-only. It tells you spoofing is happening; it does not stop a single message. Mail that fails your checks ("v=spf1 include:spf.protection.outlook.com -all") is still delivered to the recipient's inbox. Your current record:"v=DMARC1; p=none; rua=mailto:62c75d5449c743ee88c772fe6156bd42@dmarc-reports.cloudflare.net"Verify it yourself in one line:
The fix — free, no strings
Add this TXT record and you go from nothing to full visibility immediately, with zero risk of losing real mail (
p=nonedoes not affect delivery):That is genuinely the whole first step. Point
ruaat a mailbox you read, wait a week, and the aggregate reports will show you every system sending asloresoft.com— usually a couple you forgot about (a billing tool, a CRM, an old marketing platform). Once those are all passing, you move top=quarantineand thenp=reject, and spoofing stops working.If you would rather not run that project
The record above is easy. The part that eats time is the middle bit — reading the XML aggregate reports, hunting down every legitimate sender, getting SPF and DKIM aligned for each one, and stepping the policy up without silently dropping your own invoices or password resets. That is the part people start and abandon at
p=nonefor years.I do that as a fixed-scope job: $90, about two weeks, and you end at
p=rejectwith a one-page sender inventory. No retainer, no subscription — you pay when it is done and enforcing. If it turns out your setup is trivial I will say so and you can finish it yourself for free.Either way, please add the record. Reply here if you want the paid version or if anything above does not match what you see.
— Fayaz Bin Salam (@p32929)