On Mon, Jan 31, 2022 at 9:06 PM John Levine via mailop
wrote:
> It appears that Geoff Mulligan via mailop said:
> >1. If a recipient on an email message is both in the To: or Cc: and on
> >the mailing list, should the listserver send the message to the recipient:
> > a) By default
> >
It appears that Geoff Mulligan via mailop said:
>1. If a recipient on an email message is both in the To: or Cc: and on
>the mailing list, should the listserver send the message to the recipient:
> a) By default
> b) Not by default (but configurable)
> c) Never
This is a theologic
On 1/31/22 11:07 AM, Sebastian Nielsen via mailop wrote:
1: never, as the original email has already been sent to the recipient
by the original server.
I disagree.
I /expressly/ want the copy of messages from the mailing list, /NOT/ the
copy directly addressed to me.
Mailman (2.x) has an op
On 1/31/22 12:44 PM, Jaroslaw Rafa via mailop wrote:
Ah, I did not assume that the mailing list server is different from
the originating server. For me, the question *only* has sense when
it is the same server. If they are different servers, then there is
no problem at all.
Remember, SMTP ser
On 1/31/22 11:31 AM, Jaroslaw Rafa via mailop wrote:
The message should be delivered to list,
There is a big difference in the message being delivered to the
(mailing) list (manager) and the MLM re-distributing it to subscribers.
The former should happen.
The latter is dependent on MLM / li
On Sun, Jan 30, 2022 at 4:21 AM Edgaras | SENDER via mailop <
mailop@mailop.org> wrote:
> Hello,
>
> We noticed in Google Postmaster Tools a lot of bad reputation IPs which do
> not belong to us, and are actually forbidden from sending emails on our
> behalf via SPF -all, yet Gmail thinks the mes
Geoff Mulligan via mailop wrote:
> 1. If a recipient on an email message is both in the To: or Cc: and on the
> mailing list, should the listserver send the message to the recipient:
> a) By default
> b) Not by default (but configurable)
> c) Never
If a message was sent to me direct
I replied off list directly to you, Omid.
Udeme - LinkedIn
On Mon, Jan 31, 2022 at 4:41 PM Omid Majdi via mailop
wrote:
> Apologies for the additional noise, but also looking for anyone on list
> (or a contact) for Zoho. We're experiencing some deliverability issues,
> potentially related to a
On 1/31/2022 7:43 AM, Al Iverson via mailop wrote:
In this scenario, my mailing list manager strips the original DKIM
signature and applies its own, as I am now the party responsible for the
message. (I also rewrite the from address.) This has worked fine for me,
but not everyone is a fan of t
There is an interesting botnet generating a very specific threat
traffic, but 99% of it appears to be from compromised servers.
Just got a strange case leaking from RoadRunner MTA's, that would like
to discuss, it might help them find some compromised accounts.
--
"Catch the Magic of Linux...
I was trying to send an email to one of their subscribers, but we're
blocked (funnily enough, their page about mail blocking links to
Spamhaus which shows we have no issues). They don't have a postmaster@.
Any help would be greatly appreciated.
Best,
Douglas
_
Omid,
Feel free to contact me off list, we'll see what's going on.
--
Alex Brotman
Sr. Engineer, Anti-Abuse & Messaging Policy
Comcast
From: mailop On Behalf Of Omid Majdi via mailop
Sent: Monday, January 31, 2022 2:17 PM
To: mailop_at_mailop.org_o...@duck.com
Subject: [EXTERNAL] [mailop] Anyo
Apologies for the additional noise, but also looking for anyone on list (or a
contact) for Zoho. We're experiencing some deliverability issues, potentially
related to a block list that we believe we are now removed from.
Thanks!
Omid Majdi
Product Lead
DuckDuckGo
__
On Mon, Jan 31, 2022 at 10:04 AM Geoff Mulligan via mailop <
mailop@mailop.org> wrote:
> 1. If a recipient on an email message is both in the To: or Cc: and on
> the mailing list, should the listserver send the message to the recipient:
> a) By default
> b) Not by default (but configur
Dnia 31.01.2022 o godz. 20:16:11 Sebastian Nielsen via mailop pisze:
> >>I would say a).
>
> Why? Then you end up with 3 copies of the email.
>
> Remember this:
> You have sender's server, which we can call ServerA.
>
> If recipient is yourn...@example.org and list is mailingl...@examplelist.or
On 1/31/2022 9:43 AM, Geoff Mulligan via mailop wrote:
1. If a recipient on an email message is both in the To: or Cc: and on
the mailing list, should the listserver send the message to the recipient:
a) By default
b) Not by default (but configurable)
c) Never
by default.
Looking for anyone on list (or a contact) for Comcast. We're experiencing some
deliverability issues, potentially related to a block list that we believe we
are now removed from.
Thanks!
Omid Majdi
Product Lead
DuckDuckGo
___
mailop mailing list
mail
>>I would say a).
Why? Then you end up with 3 copies of the email.
Remember this:
You have sender's server, which we can call ServerA.
If recipient is yourn...@example.org and list is mailingl...@examplelist.org
ServerA (sender's server) will now send the email to yourn...@example.org AND
mai
Dnia 31.01.2022 o godz. 10:43:52 Geoff Mulligan via mailop pisze:
> 1. If a recipient on an email message is both in the To: or Cc: and
> on the mailing list, should the listserver send the message to the
> recipient:
> a) By default
> b) Not by default (but configurable)
> c) Never
On Mon 31/Jan/2022 16:43:05 +0100 Al Iverson wrote:
What will that do to legitimate messages that pass through
a mailing list that changes the subject line but does not
use DKIM ?
In this scenario, my mailing list manager strips the original DKIM
signature and applies its own, as I am now the p
On Mon 31/Jan/2022 18:43:52 +0100 Geoff Mulligan via mailop wrote:
1. If a recipient on an email message is both in the To: or Cc: and on the
mailing list, should the listserver send the message to the recipient:
a) By default
Send it by default, but let it be configurable. The standar
I feel this is the best option. Rewrite both MAIL FROM and MIME From:, and
resign the message.
This avoids any authentication errors, including SPF.
Another method is to take the whole message (including its headers, which is a
message/rfc822 object), and encapsulate it in a new message/rfc8
1: never, as the original email has already been sent to the recipient by the
original server.
EXCEPTION: If the message was submitted to the listserver by another means -
for example webform/unix call, or via an authenticated session (where sender is
either authenticated by username/password or
1. If a recipient on an email message is both in the To: or Cc: and on
the mailing list, should the listserver send the message to the recipient:
a) By default
b) Not by default (but configurable)
c) Never
2. If a mailing list is in the BCC: should a message be delivered to the
l
It appears that Andrew C Aitchison via mailop said:
>Yes, but I cannot control what lists do with mails I send to them,
>so it would be useful to know what happens to messages that use
>Evan's recommendation then go through a list that doesn't follow
>your suggestion, but alters the Subject: line
Evan Burke:
I recommend including the Date and Subject fields twice in your DKIM
signature h= string, and possibly other key fields; that will break
the original signature if a second such header is later added.
Andrew C Aitchison:
What will that do to legitimate messages that pass through
a
> What will that do to legitimate messages that pass through
> a mailing list that changes the subject line but does not
> use DKIM ?
>
In this scenario, my mailing list manager strips the original DKIM
signature and applies its own, as I am now the party responsible for the
message. (I also rewri
Yes, I used that tool and they said they fixed the problem this morning. I
have to test it to make sure it got fixed. They said to wait a few hours.
Ken
On Mon, Jan 31, 2022 at 8:16 AM Mathieu Bourdin
wrote:
> Hi,
>
>
>
> Have you tried using their new sender tool ?
>
> https://sendertool.vades
Hi Ángel,
it's Edgar, -as is a suffix in Lithuanian language :)
> I have been looking at your email, but I am confused at how it
was produced, and so which are the weird bits.
You are right, it was produced like this:
- first an attacker sent a test email from our platform (
bounces-test770...@s
Hi,
Have you tried using their new sender tool ?
https://sendertool.vadesecure.com/en/
Mathieu Bourdin.
Dolist.
De : mailop [mailto:mailop-boun...@mailop.org] De la part de Al Iverson via
mailop
Envoyé : dimanche 30 janvier 2022 18:40
À : Ken Robinson
Cc : mailop
Objet : Re: [mailop]
On Sun, 30 Jan 2022, Evan Burke via mailop wrote:
This is indeed a replay attack. It's quite widespread and appears to be
focused on taking advantage of domain reputation on the DKIM d= domain for
various email platforms. The end recipients appear to be exclusively Gmail,
as far as I've seen, an
31 matches
Mail list logo
