[mailop] Microsoft 365 IP addresses listed on Spamcop

[Christopher Hawker via mailop]

Hello all,

I am attempting to send mail from a M365 tenancy, however, we are seeing issues 
with it being filtered due to the address appearing on bl.spamcop.net.
"Decision Engine classified the mail item was rejected because of IP Block 
(from outbound normal IP pools) -> 550 mail from 40.107.107.97 refused, see 
http://www.spamcop.net - Your mail provider is blocked because is sending SPAM."
If there is anyone on-list from Microsoft, could you please take a look? It's 
causing issues 

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

Re: [mailop] Opinions on what qualifies as a "false positive" RBL listing that should be fixed?

[Jay Hennigan via mailop]

On 2/14/24 15:20, Robert L Mathews via mailop wrote:
I find myself having a difference of opinion with Spamhaus about a 
certain type of RBL listing, and I'm wondering what others think.


The situation is that the Reply-To email address of a public library's 
"your book is due in five days" reminder system is listed in the 
Spamhaus HBL 
, which Spamhaus says is because messages involving that address are hitting spamtraps.


(That sounds plausible: Maybe some library users don't update their 
email addresses, then the library unwisely doesn't remove bouncing 
messages to discontinued domain names, and the addresses eventually get 
repurposed as spamtraps.


If the message is "your book is due in five days", it doesn't seem 
reasonable that legitimate addresses are going to belong to discontinued 
domains repurposed as spamtraps within that time period. Certainly not a 
lot of them.


Perhaps the library's mail system has been compromised and either is or 
was actually sending spam.


Does the library use confirmed opt-in or otherwise verify the email 
addresses of its patrons? Maybe the patrons are putting in bogus 
addresses. When asked for an email address by someone that I never want 
to hear from, I've been known to enter "nob...@example.com". This 
shouldn't wind up as a spamtrap, however.


How do they process bounces?

--
Jay Hennigan - j...@west.net
Network Engineering - CCIE #7880
503 897-8550 - WB6RDV

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

Re: [mailop] Is forwarding to Gmail basically dead?

[Philip Paeps via mailop]

On 2024-02-15 02:51:17 (+0800), Gellner, Oliver via mailop wrote:

On 13.02.2024 at 17:05 John Levine via mailop wrote:

It appears that Taavi Eomäe via mailop  said:


On 13/02/2024 05:16, John Levine via mailop wrote:
Right now if you get a message from Gmail or Yahoo with a valid 
DKIM signature, you
can be quite confident that it came from whichever Gmail or Yahoo 
user

is in the From header.


That's absolutely not the guarantee provided by DKIM though.


More to the point, whether it's DKIM nor S/MIME or PGP, bad guys can
and do sign their mail, too.


True, however I never came across a S/MIME- or PGP-signed spam or 
phishing message - and we receive a lot of S/MIME emails. I wonder if 
others on this list have made different experiences.


I see a fair amount of S/MIME phishing.  As John points out: S/MIME is a 
very regional thing.  As far as I can tell, it's something people in 
Europe do a lot and people elsewhere do very rarely.


Having said that: I have seen S/MIME and even PGP signed spear fishing.

The spammers do use DKIM though, but that’s probably only because 
they have to or because the service they are using performs this task 
automatically anyway.


If the large mailbox providers made S/MIME and/or PGP mandatory, it 
wouldn't take very long for automated systems to start doing exactly 
that.  And I wouldn't be at all surprised if the spammers got their 
automation in place before legitimate senders.


Honestly, we're not going to "fix" this problem.

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

Re: [mailop] [E] Re: Is forwarding to Gmail basically dead?

[Marcel Becker via mailop]

On Wed, Feb 14, 2024 at 10:56 AM Gellner, Oliver via mailop <
mailop@mailop.org> wrote:

> True, however I never came across a S/MIME- or PGP-signed spam or phishing
> message - and we receive a lot of S/MIME emails. I wonder if others on this
> list have made different experiences.
> The spammers do use DKIM though, but that’s probably only because they
> have to or because the service they are using performs this task
> automatically anyway.
>

You answered it yourself. Spammers do what is necessary and reasonably cost
effective to achieve their goals. Just like legit senders as well (well,
sometimes better).
Why should they sign their emails if it's not required to deliver to an
inbox?
On the flipside though: Authenticating emails is required.

But I am certain they would sign the emails if we made that mandatory

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

Re: [mailop] Opinions on what qualifies as a "false positive" RBL listing that should be fixed?

[John Levine via mailop]

It appears that Robert L Mathews via mailop  said:
>Spamhaus says they don't remove such listings, though, because by their 
>definition, it's not a false positive if some of the messages
>are reaching spamtraps -- in other words, that addresses sending to spamtraps 
>are correctly listed as "This email address is used for
>malicious activities" in the HBL description solely because of the spamtraps.

It sounds reasonable to me. For people who live near your library, the
mail is likely to be real. For the other 99.999% of the world, it's
almost certainly spam. It is not surprising that you sometimes need to
tune your spam filters for local conditions.

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

Re: [mailop] Opinions on what qualifies as a "false positive" RBL listing that should be fixed?

[Jarland Donnell via mailop]

I think it's very situational. But Spamhaus seems to imply that it's 
currently relevant, not just a one time mistake. It could be more than 
just poor list hygiene. Well intentioned people creating systems that 
are abused by spammers is something I come across daily. I'll give an 
example:


Just today I had a conversation with a customer about how their 
Wordpress registration form was being used to send spam. They are not 
spammers, their website is not spammy. But when you register, you input 
a name and email. Wordpress then sends an email to the address you 
entered on their website, and the first sentence in the body of the 
email is "Hi {name}" where "{name}" is the name entered into the form. 
So, as you probably already guessed, "Hi you can purchase cheap viagra 
from bit.ly/spammyurl" (paraphrased example) was the first sentence in 
the body of the emails they were sending out.


Just like that Wordpress user had no idea that their systems were 
perfectly set up for abuse, the library may have a problem of their own.


On 2024-02-14 17:20, Robert L Mathews via mailop wrote:

I find myself having a difference of opinion with Spamhaus about a
certain type of RBL listing, and I'm wondering what others think.

The situation is that the Reply-To email address of a public library's
"your book is due in five days" reminder system is listed in the
Spamhaus HBL [1], which Spamhaus says is because messages involving
that address are hitting spamtraps.

(That sounds plausible: Maybe some library users don't update their
email addresses, then the library unwisely doesn't remove bouncing
messages to discontinued domain names, and the addresses eventually
get repurposed as spamtraps. Or maybe the library isn't properly
verifying the user-supplied addresses to start with. If people want to
check their own logs, the listed Reply-To email address is
mcpldpubserv at gmail dot com, with an envelope sender of sierranot at
marmot dot org.)

Anyway: One of my customers complained that this listing is causing
SpamAssassin to block their library reminder messages. I "whitelisted"
the address on our end, but in an attempt to be helpful, I also
reported it to Spamhaus as a false positive, because it's affecting
messages that are requested by recipients and transactional.

Spamhaus says they don't remove such listings, though, because by
their definition, it's not a false positive if some of the messages
are reaching spamtraps -- in other words, that addresses sending to
spamtraps are correctly listed as "This email address is used for
malicious activities" in the HBL description solely because of the
spamtraps.

I'm a little surprised by that. The sender is of course engaging in
poor list hygiene, and it's reasonable for an automated RBL process to
initially list an address that is sending to spamtraps. But I've
always thought that trusted RBLs should have a policy of "if it turns
out that a listing is also affecting user-requested, non-malicious,
transactional messages, that's not okay".

Am I off base with that expectation?

(I've also contacted the library, who I have no connection to, but
this has been happening for months, so... )

--
Robert L Mathews



Links:
--
[1] 
https://docs.spamhaus.com/datasets/docs/source/10-data-type-documentation/datasets/030-datasets.html#hbl

___
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] Is forwarding to Gmail basically dead?

[John Levine via mailop]

It appears that Gellner, Oliver via mailop  said:
>
>> On 13.02.2024 at 17:05 John Levine via mailop wrote:
>> It appears that Taavi Eomäe via mailop  said:
>>>
>>> On 13/02/2024 05:16, John Levine via mailop wrote:
 Right now if you get a message from Gmail or Yahoo with a valid DKIM 
 signature, you
 can be quite confident that it came from whichever Gmail or Yahoo user
 is in the From header.
>>>
>>> That's absolutely not the guarantee provided by DKIM though.
>>
>> More to the point, whether it's DKIM nor S/MIME or PGP, bad guys can
>> and do sign their mail, too.
>
>True, however I never came across a S/MIME- or PGP-signed spam or phishing 
>message - and we receive a lot of S/MIME emails.

I suspect that's because none of the large webmail systems understand
S/MIME so why bother.  Spammers go for volume.

It seems to be a regional thing. There is basically no S/MIME in the
U.S. other than internal mail in organizations with their own key
management.

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

[mailop] Opinions on what qualifies as a "false positive" RBL listing that should be fixed?

[Robert L Mathews via mailop]

I find myself having a difference of opinion with Spamhaus about a certain type 
of RBL listing, and I'm wondering what others think.

The situation is that the Reply-To email address of a public library's "your 
book is due in five days" reminder system is listed in the Spamhaus HBL 
,
 which Spamhaus says is because messages involving that address are hitting 
spamtraps.

(That sounds plausible: Maybe some library users don't update their email 
addresses, then the library unwisely doesn't remove bouncing messages to 
discontinued domain names, and the addresses eventually get repurposed as 
spamtraps. Or maybe the library isn't properly verifying the user-supplied 
addresses to start with. If people want to check their own logs, the listed 
Reply-To email address is mcpldpubserv at gmail dot com, with an envelope 
sender of sierranot at marmot dot org.)

Anyway: One of my customers complained that this listing is causing 
SpamAssassin to block their library reminder messages. I "whitelisted" the 
address on our end, but in an attempt to be helpful, I also reported it to 
Spamhaus as a false positive, because it's affecting messages that are 
requested by recipients and transactional.

Spamhaus says they don't remove such listings, though, because by their 
definition, it's not a false positive if some of the messages are reaching 
spamtraps -- in other words, that addresses sending to spamtraps are correctly 
listed as "This email address is used for malicious activities" in the HBL 
description solely because of the spamtraps.

I'm a little surprised by that. The sender is of course engaging in poor list 
hygiene, and it's reasonable for an automated RBL process to initially list an 
address that is sending to spamtraps. But I've always thought that trusted RBLs 
should have a policy of "if it turns out that a listing is also affecting 
user-requested, non-malicious, transactional messages, that's not okay".

Am I off base with that expectation?

(I've also contacted the library, who I have no connection to, but this has 
been happening for months, so... )

-- 
Robert L Mathews

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

Re: [mailop] Is forwarding to Gmail basically dead?

[Gellner, Oliver via mailop]

> On 13.02.2024 at 17:05 John Levine via mailop wrote:
> It appears that Taavi Eomäe via mailop  said:
>>
>> On 13/02/2024 05:16, John Levine via mailop wrote:
>>> Right now if you get a message from Gmail or Yahoo with a valid DKIM 
>>> signature, you
>>> can be quite confident that it came from whichever Gmail or Yahoo user
>>> is in the From header.
>>
>> That's absolutely not the guarantee provided by DKIM though.
>
> More to the point, whether it's DKIM nor S/MIME or PGP, bad guys can
> and do sign their mail, too.

True, however I never came across a S/MIME- or PGP-signed spam or phishing 
message - and we receive a lot of S/MIME emails. I wonder if others on this 
list have made different experiences.
The spammers do use DKIM though, but that’s probably only because they have to 
or because the service they are using performs this task automatically anyway.

—
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] Is forwarding to Gmail basically dead?

[Gellner, Oliver via mailop]

> On 13.02.2024 at 10:11 Taavi Eomäe via mailop wrote:
>
> I've described one of the reasons why that's the case. The other reason is 
> probably the fact that key management is incredibly difficult. Which is also 
> probably why it has seen adoption in environments that simplify it - large 
> organizations or entire countries. Both of these aspects have seen advances 
> recently, the CA/B Forum S/MIME baseline and implementations for 
> synchronizing cryptographic keys (currently in the form of Passkeys).

Do you have more information about passkeys in regards to S/MIME certificates? 
This sounds interesting. Or do you only mean that passkeys as well as S/MIME 
both use asymmetric keys?

—
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] Is forwarding to Gmail basically dead?

[황병희]

On Wed, 2024-02-14 at 21:31 +0900, Byunghee HWANG (황병희) via mailop
wrote:
> Hellow Cyril,
> 
> On Wed, 2024-02-14 at 11:06 +0100, Cyril - ImprovMX via mailop wrote:
> > That's a good argument. I can do even better:
> > 
> > Email is not designed for spam. Stop spamming. Problem solved.
> 
> Yes, you are right. And I know what you're thinking.
> 
> But please give me a chance to say this.
> 
> Even if you catch spam emails with SPF, I think you should be able to
> distinguish between legitimate emails -- this is forwarding emails.
> 
> Isn't it?
> 
> That's why I like Google. Google accepts forwarding emails even if
> SPF/DMARC fails.

Actually, i don't solve SPAM problem with SPF. So I don't use SPF.

As I continued to say in previous threads, this is because forwarding
is necessary. SPF causes problems in forwarding.

My goal is to receive all emails from the Debian project's debian-bugs-
dist mailing to my Gmail INBOX. Yes, my main goal is to contribute to
the Debian project. Hence I needed forwarding technology. 

After all, I've found the way. That is DKIM/ARC.

Thank you!


Sincerely, Byunghee

-- 
^고맙습니다 _布德天下_ 감사합니다_^))//


signature.asc
Description: This is a digitally signed message part
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] Gmail Affiliate Marketers.. getting stupid excessive... Yahoo/ATT

[Christine Borgia via mailop]

What are you seeing from .shop? That is often used by Shopify customers.

On Wed, Feb 14, 2024 at 10:09 AM Michael Peddemors via mailop <
mailop@mailop.org> wrote:

> All throw away domains, .xyz, .shop, .online, they are using ATT/Yahoo
> addresses, the emails are obvious.. Been reported a couple months back
> to the Yahoo people, no change to volumes..
>
> (Note, it's all going to spam folders of course)
>
> Return-Path: 
> Received: from mail-oo1-f78.google.com (HELO mail-oo1-f78.google.com)
> (209.85.161.78)
> ..
> Received: from sonic310-21.consmr.mail.gq1.yahoo.com
> (sonic310-21.consmr.mail.gq1.yahoo.com. [98.137.69.147])
>  by mx.google.com with ESMTPS id
> f13-20020a63510d00b005dc82971737si3113552pgb.365.2024.02.14.06.24.06
>  for 
>  (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
>  Wed, 14 Feb 2024 06:24:06 -0800 (PST)
> ..
> Date: Wed, 14 Feb 2024 14:24:02 + (UTC)
> From: RTIC backpack cooler 
> To: "k...@gh.furryfrinest.shop" 
> Message-ID: <1421162354.1897075.1707920642...@mail.yahoo.com>
> Subject: Your chance to receive a FREE RTIC backpack cooler
> ...
>
>
> It's just another example, that indicates Gmail doesn't care about
> outgoing spam.. And that security for the world is NOT THAT important to
> them, unless of course it serves their business interests..
>
> (Ooops.. sorry, rants probably don't belong on this list, but enough
> about email forwarding to Gmail ;)  Haven't had my morning coffee yet)
>
> Lil? Marcel? Any luck stopping these actors from your end?
>
>
>
>
>
> --
> "Catch the Magic of Linux..."
> 
> Michael Peddemors, President/CEO LinuxMagic Inc.
> Visit us at http://www.linuxmagic.com @linuxmagic
> A Wizard IT Company - For More Info http://www.wizard.ca
> "LinuxMagic" a Reg. TradeMark of Wizard Tower TechnoServices Ltd.
> 
> 604-682-0300 Beautiful British Columbia, Canada
> ___
> 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] Gmail Affiliate Marketers.. getting stupid excessive... Yahoo/ATT

[Marcel Becker via mailop]

On Wed, Feb 14, 2024 at 7:11 AM Michael Peddemors via mailop <
mailop@mailop.org> wrote:

> All throw away domains, .xyz, .shop, .online, they are using ATT/Yahoo
> addresses



> From: RTIC backpack cooler 
>
> Lil? Marcel? Any luck stopping these actors from your end?
>

Looking. Those are ATT accounts (we don't own that part). But we own the
outbound mail piece.
Thanks.
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

[mailop] Gmail Affiliate Marketers.. getting stupid excessive... Yahoo/ATT

[Michael Peddemors via mailop]

All throw away domains, .xyz, .shop, .online, they are using ATT/Yahoo 
addresses, the emails are obvious.. Been reported a couple months back 
to the Yahoo people, no change to volumes..


(Note, it's all going to spam folders of course)

Return-Path: 
Received: from mail-oo1-f78.google.com (HELO mail-oo1-f78.google.com) 
(209.85.161.78)

..
Received: from sonic310-21.consmr.mail.gq1.yahoo.com 
(sonic310-21.consmr.mail.gq1.yahoo.com. [98.137.69.147])
by mx.google.com with ESMTPS id 
f13-20020a63510d00b005dc82971737si3113552pgb.365.2024.02.14.06.24.06

for 
(version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
Wed, 14 Feb 2024 06:24:06 -0800 (PST)
..
Date: Wed, 14 Feb 2024 14:24:02 + (UTC)
From: RTIC backpack cooler 
To: "k...@gh.furryfrinest.shop" 
Message-ID: <1421162354.1897075.1707920642...@mail.yahoo.com>
Subject: Your chance to receive a FREE RTIC backpack cooler
...


It's just another example, that indicates Gmail doesn't care about 
outgoing spam.. And that security for the world is NOT THAT important to 
them, unless of course it serves their business interests..


(Ooops.. sorry, rants probably don't belong on this list, but enough 
about email forwarding to Gmail ;)  Haven't had my morning coffee yet)


Lil? Marcel? Any luck stopping these actors from your end?





--
"Catch the Magic of Linux..."

Michael Peddemors, President/CEO LinuxMagic Inc.
Visit us at http://www.linuxmagic.com @linuxmagic
A Wizard IT Company - For More Info http://www.wizard.ca
"LinuxMagic" a Reg. TradeMark of Wizard Tower TechnoServices Ltd.

604-682-0300 Beautiful British Columbia, Canada
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] Outgoing Spam from Microsoft IPs

[Michael Peddemors via mailop]

On 2024-02-13 22:57, Hans-Martin Mosner via mailop wrote:
We've been seeing runs of spam mails from Microsoft IP addresses without 
reverse DNS (possibly cloud servers).


One is sending with addresses , starting on February 8.

The other (same or different spammer?) uses  and 
started just yesterday.


Have others seen these? Is there some way to identify the host IPs which 
are used by those cloud servers, so one could block incoming SMTP from 
them if Microsoft can't be bothered to block outgoing SMTP?


Cheers,
Hans-Martin



Hans, you should be blocking ANY connection attempts to port 25 with no 
PTR record, most of us have been safely doing this for many years..


And of course, can you confirm if this is possibly attempt at SMTP AUTH?

We have been seeing a lot of that for the last two years.

Oh, and a sample IP would be helpful, DYK you can download a JSON file 
from Microsoft that covers all their IP Space, and the purposes.  Not 
100% easy or accurate, but gets you where you need to be.


(DO wish these "Too Big to Block" would SWIP their IP space more 
fractionally, or run their own 'rwhois' services with accurate details)



--
"Catch the Magic of Linux..."

Michael Peddemors, President/CEO LinuxMagic Inc.
Visit us at http://www.linuxmagic.com @linuxmagic
A Wizard IT Company - For More Info http://www.wizard.ca
"LinuxMagic" a Reg. TradeMark of Wizard Tower TechnoServices Ltd.

604-682-0300 Beautiful British Columbia, Canada

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

Re: [mailop] Is forwarding to Gmail basically dead?

[Cyril - ImprovMX via mailop]

> Even if you catch spam emails with SPF, I think you should be able to
> distinguish between legitimate emails -- this is forwarding emails.

SPF/DKIM/DMARC and spam are two entirely different things.
Talking about spam and SPF is like talking about fish and fruit salad.

I think John Levine now has an automated snippet to mention this every 15
minutes ;)

Le mer. 14 févr. 2024 à 13:34, Byunghee HWANG (황병희) via mailop <
mailop@mailop.org> a écrit :

> Hellow Cyril,
>
> On Wed, 2024-02-14 at 11:06 +0100, Cyril - ImprovMX via mailop wrote:
> > That's a good argument. I can do even better:
> >
> > Email is not designed for spam. Stop spamming. Problem solved.
>
> Yes, you are right. And I know what you're thinking.
>
> But please give me a chance to say this.
>
> Even if you catch spam emails with SPF, I think you should be able to
> distinguish between legitimate emails -- this is forwarding emails.
>
> Isn't it?
>
> That's why I like Google. Google accepts forwarding emails even if
> SPF/DMARC fails.
>
>
> Sincerely, Byunghee
>
> ps. Your mail was my spam trap -- HTML Email.
>
> --
> ^고맙습니다 _布德天下_ 감사합니다_^))//
> ___
> 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] Is forwarding to Gmail basically dead?

[황병희]

Hellow Cyril,

On Wed, 2024-02-14 at 11:06 +0100, Cyril - ImprovMX via mailop wrote:
> That's a good argument. I can do even better:
> 
> Email is not designed for spam. Stop spamming. Problem solved.

Yes, you are right. And I know what you're thinking.

But please give me a chance to say this.

Even if you catch spam emails with SPF, I think you should be able to
distinguish between legitimate emails -- this is forwarding emails.

Isn't it?

That's why I like Google. Google accepts forwarding emails even if
SPF/DMARC fails.


Sincerely, Byunghee

ps. Your mail was my spam trap -- HTML Email.

-- 
^고맙습니다 _布德天下_ 감사합니다_^))//


signature.asc
Description: This is a digitally signed message part
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] Is forwarding to Gmail basically dead?

[Cyril - ImprovMX via mailop]

That's a good argument. I can do even better:

Email is not designed for spam. Stop spamming. Problem solved.

...

Le mer. 14 févr. 2024 à 01:56, Benny Pedersen via mailop 
a écrit :

> Byunghee HWANG  via mailop skrev den 2024-02-14 01:00:
>
> > I really strongly agree with this opinion. That's why I wish people in
> > the world didn't use SPF. SPF is a serious obstacle when forwarding.
>
> spf is not designed for forwarding, stop forwarding, problem solved
>
> dmarc need spf to find aligned mails
>
> ___
> 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] Is forwarding to Gmail basically dead?

[황병희]

Hellow Benny,

> (...) please be open minded, you already is using opensource

Thanks, usually i don't say 'No' to someone i like. In any case. I'm
going to try your advice someday.

Thanks again Benny!


Sincerely, Byunghee

-- 
^고맙습니다 _布德天下_ 감사합니다_^))//


signature.asc
Description: This is a digitally signed message part
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] Is forwarding to Gmail basically dead?

[Benny Pedersen via mailop]

Byunghee HWANG  via mailop skrev den 2024-02-14 05:45:


spf is not designed for forwarding, stop forwarding, problem solved

Yes, you are right!


good then :=)


And if Google stops email service, i will also stop forwarding.


https://wiki.debian.org/PostfixAndSASL

see section SASL authentication in the Postfix SMTP client

optional try this https://github.com/roundcube/roundcubemail/issues/7610

please be open minded, you already is using opensource
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop