Re: [mailop] DKIM signed with parent domain

[Byung-Hee HWANG via mailop]

Hellow Oliver,

On Fri, 2024-01-26 at 22:06 +, Gellner, Oliver via mailop wrote:
> 
> > On 25.01.2024 at 16:29 Marco Moock via mailop wrote:
> > 
> > At work we are currently deploying DKIM.
> > 
> > Do people here have experience with messages from sub.example.org
> > signed with d=example.org?
> > That way is much easier to handle for us because we have a lot of
> > domains (machines sending with r...@hostname.example.org etc.).
> > 
> > Will Google accept such messages in the future?
> > I am aware that DMARC can control that, but how will Google handle
> > it?
> 
> Unfortunately I can’t say what Google or other third parties are
> planning to do in the future. At the moment DKIM signatures from a
> parent domain will pass DMARC checks as long as DKIM alignment is in
> relaxed mode.
> 

Google Gmail accept such email: (source from soyeo...@gmail.com)
https://gitlab.com/soyeomul/Gnus/-/raw/d73303d3f304a275bb6f129c0d4934ce30680629/DKIM/gmail-forwarding-header-20240126.txt


Sincerely, Byung-Hee

-- 
^고맙습니다 _布德天下_ 감사합니다_^))//
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] Contact Google Postmaster

[Mark Milhollan via mailop]

On Fri, 26 Jan 2024, Scott Mutter wrote:


The 173.225.104.91 server has sent 68 emails to gmail.com email addresses
thus far in January 2024.


GPT will not present data for that volume.  From their FAQ: "Most of the 
Postmaster Tools dashboards will only display data when there’s a 
sizable daily volume of email traffic (up to the order of hundreds) 
coming from your Authentication Domains and/or certain other conditions, 
in place to prevent abuse."



How am I supposed to remedy a low reputation?


Supposedly the only way is for the receivers to signal Google's system 
that your messages are wanted.  So far as I know that means they must 
remove the spam label (click not spam), actually open the message not 
merely look at the subject/preview before deleting it, and do so pretty 
consistently.  But it might not be reputation that is your issue, or at 
least not only reputation, it might be the content itself so you might 
have to remove or change URLs (don't use any shorteners), graphics, 
and/or words in the messages, especially in boilerplate.



/mark
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] DKIM signed with parent domain

[Grant Taylor via mailop]

On 1/26/24 16:06, Gellner, Oliver via mailop wrote:
Independent of this I wouldn’t use r...@hostname.example.org 
as a sender address to external recipients. This doesn’t look 
professional,


I'll agree that sending from root@ is not best practice.  But 
I don't know if it's unprofessional per se.



makes replying to those emails impossible


I question the veracity of that.

Including a Reply-To: and / or an MX for  to a reachable mail 
server that is a smart host that knows how to deliver email to a host 
that's not directly reachable seems viable to me.


and in case hostname.example.org doesn’t have a public IP address 
it might also increase the risk that those messages are treated as 
spam or rejected, because they are coming from an unresolvable domain.


I question the veracity of anything that balks at a valid MX via smart 
host for a  that is in and of itself unreachble.


After all, what is the effective difference in a host that's in a 
private network using a smart host for outbound and inbound mail and a 
host usually fully reachable / on the Internet that happens to be 
offline do to an extended power outage caused by a winter storm?


I think that there /should/ be /a/ system that is willing to handle mail 
for the system, but I don't agree that it needs to be /the/ /system/ 
/itself/.



Many MTAs provide ways to rewrite sender addresses, 


Agreed.

What I don't agree with is the actual need -> requirement to do so.

Sure, masquerading sending addresses is a useful tool in the toolbox. 
But it's not the only tool in the toolbox.


This will resolve all questions about subdomains once and for all and 
doesn’t even require any changes to the applications which create 
the messages.


I question the veracity of that for multiple reasons.  Doing this on 
each source system will likely be a lossy operation and could have 
serious negative impact on systems inside the organization that would 
otherwise utilize the masqueraded source address.  --  Obviously I think 
that there are ways to make this email work even if the internal system 
isn't reachable from the Internet.  I have other similar / more obtuse 
qualms with the idea that masquerading will resolve all questions about 
subdomains period, much less once and for all.




--
Grant. . . .


smime.p7s
Description: S/MIME Cryptographic Signature
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] Contact Google Postmaster

[Scott Mutter via mailop]

I've had domains listed in Google Postmaster Tools since 2016.  Never
gotten one lick of any information from any of those except for "No data to
display at this time. Please come back later. Postmaster Tools requires
that your domain satisfies certain conditions before data is visible for
this chart."

I eventually stopped adding domains because it didn't do me any good.

The 173.225.104.91 server has sent 68 emails to gmail.com email addresses
thus far in January 2024.  As far as I know, this block just happened
today.  Today was the first time it was brought to my attention that
messages from this server are going into the spam folder.

Again, how am I supposed to know that Google is treating this IP's
reputation poorly?

How am I supposed to remedy a low reputation?


I set up another domain on the same 173.225.104.91 server, SPF, DKIM, and
DMARC all set up (and verified with https://www.learndmarc.com).  Sent a
message to an @gmail.com address through this account, and it went to the
spam folder.

Set up the same domain on another server - 205.209.102.251 - which,
coincidentally is also an Interserver IP.  Again, verified that SPF, DKIM,
and DMARC were all set up with https://www.learndmarc.com.  I sent the same
test message to the same @gmail.com address.  Message came through in the
INBOX without incident.

What conclusions would everybody else draw?


It's frustrating because none of the too big to fail email service
providers have any way to test a sending IP or sending domain's reputation
with their service.  They block them or weigh them heavily without any
method of remediation.

It would be nice if I could check the reputation of my outbound IPs daily
and be proactive in remedying any issues with these major email service
providers, rather than have to be told by my clients that something is
amiss.  And then battle through a 2 week waiting period for the provider to
reply back or hope that someone from the provider is on MailOps and can
provide any insight.
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] DKIM signed with parent domain

[Al Iverson via mailop]

> Independent of this I wouldn’t use r...@hostname.example.org as a sender 
> address to external recipients. This doesn’t look professional, makes 
> replying to those emails impossible and in case hostname.example.org doesn’t 
> have a public IP address it might also increase the risk that those messages 
> are treated as spam or rejected, because they are coming from an unresolvable 
> domain.
> Many MTAs provide ways to rewrite sender addresses, so you could rewrite both 
> MAIL FROM and header From to someth...@example.org before delivering the 
> messages. This will resolve all questions about subdomains once and for all 
> and doesn’t even require any changes to the applications which create the 
> messages.

Agreed. Example: Depending on your unix config, you can do like I did
and create /etc/mailutils.conf with this in it:

address {
  email-domain xnnd.com;
};

So that any `echo "notification" | mail aiver...@wombatmail.com` will
come from u...@xnnd.com, not u...@server32.xnnd.com.

Cheers,
Al Iverson

-- 

Al Iverson / Deliverability blogging at https://www.spamresource.com
Subscribe to the weekly newsletter at https://ml.spamresource.com
DNS Tools: https://xnnd.com / (312) 725-0130 / Chicago (Central Time)
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] DKIM signed with parent domain

[Gellner, Oliver via mailop]

> On 25.01.2024 at 16:29 Marco Moock via mailop wrote:
>
> At work we are currently deploying DKIM.
>
> Do people here have experience with messages from sub.example.org
> signed with d=example.org?
> That way is much easier to handle for us because we have a lot of
> domains (machines sending with r...@hostname.example.org etc.).
>
> Will Google accept such messages in the future?
> I am aware that DMARC can control that, but how will Google handle it?

Unfortunately I can’t say what Google or other third parties are planning to do 
in the future. At the moment DKIM signatures from a parent domain will pass 
DMARC checks as long as DKIM alignment is in relaxed mode.

Independent of this I wouldn’t use r...@hostname.example.org as a sender 
address to external recipients. This doesn’t look professional, makes replying 
to those emails impossible and in case hostname.example.org doesn’t have a 
public IP address it might also increase the risk that those messages are 
treated as spam or rejected, because they are coming from an unresolvable 
domain.
Many MTAs provide ways to rewrite sender addresses, so you could rewrite both 
MAIL FROM and header From to someth...@example.org before delivering the 
messages. This will resolve all questions about subdomains once and for all and 
doesn’t even require any changes to the applications which create the messages.

—
BR Oliver



dmTECH GmbH
Am dm-Platz 1, 76227 Karlsruhe * Postfach 10 02 34, 76232 Karlsruhe
Telefon 0721 5592-2500 Telefax 0721 5592-2777
dmt...@dm.de * www.dmTECH.de
GmbH: Sitz Karlsruhe, Registergericht Mannheim, HRB 104927
Geschäftsführer: Christoph Werner, Martin Dallmeier, Roman Melcher

Datenschutzrechtliche Informationen
Wenn Sie mit uns in Kontakt treten, beispielsweise wenn Sie an unser 
ServiceCenter Fragen haben, bei uns einkaufen oder unser dialogicum in 
Karlsruhe besuchen, mit uns in einer geschäftlichen Verbindung stehen oder sich 
bei uns bewerben, verarbeiten wir personenbezogene Daten. Informationen unter 
anderem zu den konkreten Datenverarbeitungen, Löschfristen, Ihren Rechten sowie 
die Kontaktdaten unserer Datenschutzbeauftragten finden Sie 
hier.
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] Contact Google Postmaster

[Gellner, Oliver via mailop]

> On 26.01.2024 at 19:36 Scott Mutter via mailop wrote:
>
> It seems messages being sent from 173.225.104.91 are being delivered into 
> Gmail user's spam boxes.

Is each and every message from different organizational domains sent by this 
server placed into the spam folder? Or does it affect only certain sender 
domains or messages generated by a certain MUA? You can create an account at 
Gmail and test this.

It is rumored that Gmail takes message characteristics and sender domain 
reputation more into account than IP address reputation, so maybe the issue is 
not related to the IP address at all.

—
BR Oliver


dmTECH GmbH
Am dm-Platz 1, 76227 Karlsruhe * Postfach 10 02 34, 76232 Karlsruhe
Telefon 0721 5592-2500 Telefax 0721 5592-2777
dmt...@dm.de * www.dmTECH.de
GmbH: Sitz Karlsruhe, Registergericht Mannheim, HRB 104927
Geschäftsführer: Christoph Werner, Martin Dallmeier, Roman Melcher

Datenschutzrechtliche Informationen
Wenn Sie mit uns in Kontakt treten, beispielsweise wenn Sie an unser 
ServiceCenter Fragen haben, bei uns einkaufen oder unser dialogicum in 
Karlsruhe besuchen, mit uns in einer geschäftlichen Verbindung stehen oder sich 
bei uns bewerben, verarbeiten wir personenbezogene Daten. Informationen unter 
anderem zu den konkreten Datenverarbeitungen, Löschfristen, Ihren Rechten sowie 
die Kontaktdaten unserer Datenschutzbeauftragten finden Sie 
hier.
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] [E] Contact Google Postmaster

[Opti Pub via mailop]

> The Google Postmaster tool is a joke for me.  Apparently you have to have
10's of millions of messages coming from the server for Google Postmaster
to report anything.

You don’t have to have that much volume for data… this behavior is typical
of GMT if your domain rep is very low (IE bad/dark red) — they will stop
giving you any data at all, bc spammers with data are better spammers :)

If GMT isn’t giving you data that’s a pretty bad sign tbh. And if I had to
guess you prob have list hygiene issues or acquisition issues.

I’d follow Als advice AFTER you are sure you have everything in line. But
be nice ;)

GL



On Fri, Jan 26, 2024 at 3:51 PM John Levine via mailop 
wrote:

> It appears that Scott Mutter via mailop  said:
> >But as it stands now, it's only when our users notify us that their
> >messages are being sent to their Gmail spambox do I realize there's an
> >issue.  There's no rejection or anything from Google's acceptance of the
> >message to indicate that there is any problem.
>
> That's not a bug, you know.
>
> >You have to try to see this from my perspective.  How am I suppose to know
> >that Google is treating messages from this IP poorly?
>
> Why do think it has anything to do with your IP?  Do you send mail from
> other IPs with the same DKIM and SPF domain?
>
> AS people have been hinting, the reason your mail is going into the
> spam folder is most likely that the recipients have been marking it as
> spam or otherwise treating it as mail they don't want. Google's mail
> sorting depends mostly on their own internal data.
>
> R's,
> John
> ___
> mailop mailing list
> mailop@mailop.org
> https://list.mailop.org/listinfo/mailop
>
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] [E] Contact Google Postmaster

[John Levine via mailop]

It appears that Scott Mutter via mailop  said:
>But as it stands now, it's only when our users notify us that their
>messages are being sent to their Gmail spambox do I realize there's an
>issue.  There's no rejection or anything from Google's acceptance of the
>message to indicate that there is any problem.

That's not a bug, you know.

>You have to try to see this from my perspective.  How am I suppose to know
>that Google is treating messages from this IP poorly?

Why do think it has anything to do with your IP?  Do you send mail from
other IPs with the same DKIM and SPF domain?

AS people have been hinting, the reason your mail is going into the
spam folder is most likely that the recipients have been marking it as
spam or otherwise treating it as mail they don't want. Google's mail
sorting depends mostly on their own internal data.

R's,
John
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] [E] Contact Google Postmaster

[Scott Mutter via mailop]

>> I'm not seeing where 173.225.104.91 is on any public blacklist.
> That is also not relevant. Your reputation and what receivers think about
your email is relevant.

Maybe not, but please pray tell how else I'm suppose to know the reputation
of my server's IP address?  Does Google have a public blacklist checker
that I can check?  Does Yahoo?  Does Microsoft?  I get that there's a
reason they keep these private.  But if I'm not seeing anything on a public
blacklist then what am I suppose to think?

If the IP was covered up with listing on public blacklists, then yea I'd
agree there's likely an issue on the server and a reason for the listing,
and probably a reason why Google is sending the messages into the spam box.

But as it stands now, it's only when our users notify us that their
messages are being sent to their Gmail spambox do I realize there's an
issue.  There's no rejection or anything from Google's acceptance of the
message to indicate that there is any problem.

You have to try to see this from my perspective.  How am I suppose to know
that Google is treating messages from this IP poorly?

The Google Postmaster tool is a joke for me.  Apparently you have to have
10's of millions of messages coming from the server for Google Postmaster
to report anything.  I've never had one ounce of anything helpful from
Google's Postmaster tools, the only thing I ever get is "No data to display
at this time. Please come back later. Postmaster Tools requires that your
domain satisfies certain conditions before data is visible for this chart"
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

[mailop] ebay postmaster contact

[Marco Moock via mailop]

Hello!

Does anybody of ebay reads here?

At work we receive mails from ebay (SPF valid) to an address that isn't
assigned to an account and can't be registered by the ebay user because
he can't access the inbox, it is root@our.domain.

I already called their customer service and they said the email address
isn't assigned to any ebay account.

We receive invoices and private messages for the ebay user here.

rcpt to is root@ on our MX, so it is not a forward/alias in our system

Is there any way to contact them so they can figure out the source of
those mails?

-- 
kind regards
Marco

Spam und Werbung bitte an ichschickerekl...@cartoonies.org
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] Contact Google Postmaster

[Al Iverson via mailop]

How to contact Google to beg for Gmail spam folder forgiveness:
https://www.spamresource.com/2022/01/gmails-sender-contact-form-what-and-why.html

Cheers,
Al Iverson

On Fri, Jan 26, 2024 at 12:34 PM Scott Mutter via mailop
 wrote:
>
> It seems messages being sent from 173.225.104.91 are being delivered into 
> Gmail user's spam boxes.
>
> These messages are DKIM signed, pass SPF and DMARC.
>
> I'm not seeing where 173.225.104.91 is on any public blacklist.
>
> Anyone from Google able to shed any light on this?
>
> Thanks
> ___
> mailop mailing list
> mailop@mailop.org
> https://list.mailop.org/listinfo/mailop



-- 

Al Iverson / Deliverability blogging at https://www.spamresource.com
Subscribe to the weekly newsletter at https://ml.spamresource.com
DNS Tools: https://xnnd.com / (312) 725-0130 / Chicago (Central Time)
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] Extortion spam from OVH-hosted *.sbs domains

[Randolf Richardson, Postmaster via mailop]

> According to Randolf Richardson, Postmaster via mailop 
> :
> > I'm just chiming in here with some support for you because I know a 
> >few people who use OVH as well.
> >
> > Blocking on a case-by-case basis is the better approach so that 
> >legitimate (non-spamming) hosts aren't penalized.
> 
> When I look at my logs and see the amount of spam from OVH networks,
> it's just not worth the effort to try and pick out the trickle of
> non-spam.

Everyone has different experiences.  When a network is a spam sewer 
that's dumping onto your systems, then blocking the entire network is 
certainly the more sensible option.

...and then making exceptions for the few who are "lost at sea on 
the wrong boat" in said network's polluted waters and who your users 
want/need to receive communications from.  (It's terrible that the 
internet has come to this, and I remember a few people in NANAE, 
decades ago, predicting these types of problems.)

> If you want people to accept your mail, act like you do and send it
> from a network that doesn't gush spam.

I agree.

I remember setting up a Virtual Machine for a client on OVH many 
years ago.  There were major limitations on OS installation, which 
was confirmed by their technical support, so we closed the account 
and chose a different provider.  So, given that OVH runs a limited 
service (or maybe they don't do that anymore?), I'm surprised that 
they don't seem to be so stringent about their clients sending spam.

-- 
Postmaster - postmas...@inter-corporate.com
Randolf Richardson, CNA - rand...@inter-corporate.com
Inter-Corporate Computer & Network Services, Inc.
Vancouver, British Columbia, Canada
https://www.inter-corporate.com/


___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] Contact Google Postmaster

[John Levine via mailop]

It appears that Scott Mutter via mailop  said:
>-=-=-=-=-=-
>-=-=-=-=-=-
>
>It seems messages being sent from 173.225.104.91 are being delivered into
>Gmail user's spam boxes.
>
>These messages are DKIM signed, pass SPF and DMARC.
>
>I'm not seeing where 173.225.104.91 is on any public blacklist.
>
>Anyone from Google able to shed any light on this?

I'm not Google, but I can report that you're not in a great neighborhood.

On my network, 100% of the mail I've gotten from Interserver's network
in the past five years has been spam, the most recent last week. I've
had part of that network blocked for ten years and as far as I know
never got a false positive.

___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] [E] Contact Google Postmaster

[Marcel Becker via mailop]

On Fri, Jan 26, 2024 at 10:35 AM Scott Mutter via mailop 
wrote:

> It seems messages being sent from 173.225.104.91 are being delivered into
> Gmail user's spam boxes.
> These messages are DKIM signed, pass SPF and DMARC.
>

Properly meeting basic email authentication standards does not mean
receivers are required to deliver your emails to the Inbox.


> I'm not seeing where 173.225.104.91 is on any public blacklist.
>

That is also not relevant. Your reputation and what receivers think about
your email is relevant.

 -- Marcel
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

[mailop] Contact Google Postmaster

[Scott Mutter via mailop]

It seems messages being sent from 173.225.104.91 are being delivered into
Gmail user's spam boxes.

These messages are DKIM signed, pass SPF and DMARC.

I'm not seeing where 173.225.104.91 is on any public blacklist.

Anyone from Google able to shed any light on this?

Thanks
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

[mailop] [ADMIN] Re: Extortion spam from OVH-hosted *.sbs domains

[Graeme Fowler via mailop]

On 26 Jan 2024, at 10:28, Jaroslaw Rafa via mailop  wrote:
> But even people who have extensive theoretical knowledge often fail to
> actually apply it when it comes to practice.

This has absolutely nothing at all to do with email or interoperating email 
systems. Please desist.

More generally, and I’m disappointed to have to type this *again*: if your post 
is not actually adding value to a discussion, don’t post it. If your post is 
aimed at a list member, rather than what they wrote, don’t post it. If you do, 
you can expect at the very least to be put on moderation.

Thanks!

Graeme
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] DKIM signed with parent domain

[Byung-Hee HWANG via mailop]

Hellow Jörg,

On Fri, 2024-01-26 at 10:49 +0100, Jörg Backschues via mailop wrote:
> Am 25.01.24 um 23:58 schrieb Anne Mitchell via mailop:
> 
> > > On Jan 25, 2024, at 3:24 PM, Byron Lunz via mailop
> > >  wrote:
> > > 
> > > Or, you can use https://aboutmy.email/ - not affiliated, just a
> > > pleased user.
> > 
> > Yes, absolutely, aboutmy.email rocks!  And, is offered by a very
> > trusted source!
> 
> Sorry, but there are issues with AboutMy.email when using multiple
> DKIM 
> signatures e.g. RSA & Ed25519.
> 

As far as I know, both sites perform ed25519 verification.

*DNSWL* and *Protonmail*


And several debian developers also are using Ed25519 key.

 
Sincerley, Byung-Hee

-- 
^고맙습니다 _布德天下_ 감사합니다_^))//
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] [EXTERNAL] Re: MTA-STS: No TLS reports from Google since January 9th

[Byung-Hee HWANG via mailop]

Hellow Alex,

On Thu, 2024-01-25 at 19:55 +, Brotman, Alex via mailop wrote:
> I did start getting reports again, I haven't looked to see if they're
> consistently appearing
> 

Me too. Also i received again that reports from Google, today!


Sincerely, Byung-Hee

-- 
^고맙습니다 _布德天下_ 감사합니다_^))//
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] DKIM signed with parent domain

[Slavko via mailop]

Dňa 26. 1. o 10:49 Jörg Backschues via mailop napísal(a):

Sorry, but there are issues with AboutMy.email when using multiple DKIM 
signatures e.g. RSA & Ed25519.


I was curious, and no, there are not issues with dual signed DKIM, both 
my signatures are in pass state, the only missing thing is, that detail 
page about signature(s) lacks the key algorithm, but that is cosmetic.


regards

--
Slavko

___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] Extortion spam from OVH-hosted *.sbs domains

[Jaroslaw Rafa via mailop]

Dnia 25.01.2024 o godz. 22:00:08 John Levine via mailop pisze:
> 
> As I may have said once or twice before, when you pick the cheapest,
> crummiest option, often you get what you pay for.

s/the cheapest, crummiest option/the option you CAN actually afford/

Certainly you, John, are not the person who needs to be taught about the
fact that Internet is not only an American thing, and even more - it's not
only a "Western" thing, and that there are HUGE economic discrepancies
between countries in the world, as well as different financial regulations,
different currencies etc.

But even people who have extensive theoretical knowledge often fail to
actually apply it when it comes to practice.
-- 
Regards,
   Jaroslaw Rafa
   r...@rafa.eu.org
--
"In a million years, when kids go to school, they're gonna know: once there
was a Hushpuppy, and she lived with her daddy in the Bathtub."
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] DKIM signed with parent domain

[Jörg Backschues via mailop]

Am 25.01.24 um 23:58 schrieb Anne Mitchell via mailop:


On Jan 25, 2024, at 3:24 PM, Byron Lunz via mailop  wrote:

Or, you can use https://aboutmy.email/ - not affiliated, just a pleased user.


Yes, absolutely, aboutmy.email rocks!  And, is offered by a very trusted source!


Sorry, but there are issues with AboutMy.email when using multiple DKIM 
signatures e.g. RSA & Ed25519.


--
Regards
Jörg Backschues

___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] Extortion spam from OVH-hosted *.sbs domains

[Hans-Martin Mosner via mailop]

Am 26.01.24 um 09:42 schrieb Simon Bressier via mailop:

Hi all,

FYI Hans-Martin, I reached out to ovh team yesterday night to push 
your message, seems your abuse report has been processed by the proper 
team. No idea if they answered you, but at least, they have handled 
the report, and probably done the appropriate actions.


Thanks Simon!

Good to know the abuse address is not a black hole, although it would be 
a bit nicer if there were at least some feedback indicating that the 
something was done (not a bot feedback confirming receipt, although that 
would still be more than silence). Since the *.sbs spam stopped, I 
already assumed that the situation had been dealt with.


Cheers,
Hans-Martin

___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] Extortion spam from OVH-hosted *.sbs domains

[Simon Bressier via mailop]

Hi all,

FYI Hans-Martin, I reached out to ovh team yesterday night to push your
message, seems your abuse report has been processed by the proper team. No
idea if they answered you, but at least, they have handled the report, and
probably done the appropriate actions.

On Thu, Jan 25, 2024 at 7:13 AM Hans-Martin Mosner via mailop <
mailop@mailop.org> wrote:

> Tonight we received a huge wave of extortion spams from OVH hosted domains
> trying to get bitcoin payments. The senders claim that recipients watched
> child porn.
>
> This is the final straw for me to add a rule to reject all mail traffic
> from OVH until the sender is whitelisted. OVH is completely unresponsive to
> abuse complaints, they won't even react when clearly criminal activity
> happens from their IP space.
>
> The domains used were:
>
> aoyn.sbs
> bnop.sbs
> burx.sbs
> enux.sbs
> fojr.sbs
> hnls.sbs
> nbot.sbs
> ouhb.sbs
> pxur.sbs
> rnuh.sbs
>
> with the IP addresses
>
> 51.89.5.129
> 51.89.5.145
> 51.89.175.30
> 51.89.175.173
> 51.89.175.196
> 54.38.1.200
> 57.128.16.249
> 57.128.60.137
> 57.128.83.193
> 57.128.123.32
> 57.128.165.75
> 57.128.166.120
> 91.134.96.213
> 91.134.97.224
> 91.134.97.232
> 135.125.66.34
> 135.125.66.86
> 135.125.66.217
> 135.125.217.78
> 141.94.64.94
> 141.95.108.175
> 148.113.137.42
> 148.113.139.81
> 148.113.140.91
> 148.113.141.117
> 148.113.143.4
> 162.19.68.117
>
> It's probably pointless to call for a general OVH boycott, as much as I
> would like to do that :-)
>
> Cheers,
> Hans-Martin
> ___
> mailop mailing list
> mailop@mailop.org
> https://list.mailop.org/listinfo/mailop
>
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop