Hi,
Both of these approaches seem to be specific to Postfix if I'm not
mistaken. There's a similar milter for Sendmail called Mailman-Milter
which I was using for a while. However, it worked based on Mailman's
action E.G. it would use a Python script to determine what Mailman would
do with a
On 07/19/2018 05:27 PM, Mark Sapiro wrote:
The problem is downstream has to trust me. If I'm gmail.com, I'll probably
be trusted. If I'm msapiro.net, probably not. Python.org, who knows.
Yep.
I've not yet seen any indication that there will be any good way to
establish this trust relationship
On 07/19/2018 06:22 PM, Mark Sapiro wrote:
If Mailman is asked to remove or replace DKIM headers, the
headers affected are DomainKey-Signature, DKIM-Signature and
Authentication-Results.
Good to know.
Thank you for clarifying Mark.
--
Grant. . . .
unix || die
-
On 07/19/2018 03:55 PM, Matt Morgan wrote:
> BTW I'm kind of flummoxed that in Mark's mail he sees the
> j...@johngreenwaltlee.com address, because that's exactly what I deleted and
> replaced with the obfuscated "xxxjohnxxx.com." In what I wrote, that real
> email address *did not appear*. !@#$% g
On 07/19/2018 03:31 PM, Grant Taylor via Mailman-Users wrote:
>
> I'm lumping various in as well, which I'm not aware of Mailman being
> able to remove.
>
> Authentication-Results:
>
> I think there are others that fall into the same category, but I don't
> recall them at the moment.
If Mailma
On 07/19/18 19:27, Mark Sapiro wrote:
> On 07/19/2018 03:59 PM, Phil Stracchino wrote:
>>
>> Actually, mailing lists and other redistribution are among the places
>> DMARC notably breaks. The real answer, which was created for this
>> purpose, is ARC (Authenticated Received Chain). That is design
On 07/19/2018 03:59 PM, Phil Stracchino wrote:
>
> Actually, mailing lists and other redistribution are among the places
> DMARC notably breaks. The real answer, which was created for this
> purpose, is ARC (Authenticated Received Chain). That is designed from
> the start to pass through mailing
On 07/19/18 17:11, John Levine wrote:
> In article
> you write:
>> Yes. Just about everything can be spoofed to some degree. It really
>> depends on what information the owner of the purported sending domain
>> publishes and what filtering / consumption of said information the
>> receiving s
BTW I'm kind of flummoxed that in Mark's mail he sees the
j...@johngreenwaltlee.com address, because that's exactly what I deleted and
replaced with the obfuscated "xxxjohnxxx.com." In what I wrote, that real
email address *did not appear*. !@#$% gmail.
On Thu, Jul 19, 2018 at 6:51 PM, Matt Morgan
Thanks, everyone, for the thoughtful comments on my tiny little spam
problem! I've returned from my day job and will look at Mark's diagnosis
suggestions.
Best,
Matt
On Thu, Jul 19, 2018 at 6:43 PM, John Levine wrote:
> In article <1ca714d0-da89-aa23-d247-4faa2133b...@msapiro.net> you write:
>
In article <1ca714d0-da89-aa23-d247-4faa2133b...@msapiro.net> you write:
>DMARC checks won't help prevent posts that spoof a member address unless
>every list member's domain publishes a DMARC policy of quarantine or
>reject, and even then it only checks the From: domain and not the domain
>of othe
On 07/19/2018 04:16 PM, Mark Sapiro wrote:
Mailman can be configured to remove DKIM related headers from
incoming mail before sending.
ACK
I'm lumping various in as well, which I'm not aware of Mailman being
able to remove.
Authentication-Results:
I think there are others that fall into th
On 07/19/2018 02:37 PM, Grant Taylor via Mailman-Users wrote:
>
> I'd argue that it's best to:
>
> 1) Do all the typical DMARC, DKIM, SPF, etc. filtering on email inbound
> to the mail server.
> 2) Strip DKIM (related) headers from messages going into Mailman.
Mailman can be configured to rem
At Thu, 19 Jul 2018 14:17:55 -0600 Grant Taylor
wrote:
>
>
> Content-Language: en-US
>
> On 07/19/2018 11:44 AM, Robert Heller wrote:
> > All of which can be spoofed.
>
> Yes. Just about everything can be spoofed to some degree. It really
> depends on what information the owner of the pur
On 07/19/2018 02:11 PM, John Levine wrote:
> In article
> you write:
>> Yes. Just about everything can be spoofed to some degree. It really
>> depends on what information the owner of the purported sending domain
>> publishes and what filtering / consumption of said information the
>> receiv
On 07/19/2018 03:11 PM, John Levine wrote:
Well, you know, this is what DMARC is intended to address. While DMARC
checks on mail that has passed through mailing lists has all sorts of
well known problems, doing DMARC checks on mail that arrives at a list
server would be pretty benign. It's pr
In article
you write:
>Yes. Just about everything can be spoofed to some degree. It really
>depends on what information the owner of the purported sending domain
>publishes and what filtering / consumption of said information the
>receiving server exercises.
Well, you know, this is what DMA
On 07/19/2018 11:44 AM, Robert Heller wrote:
All of which can be spoofed.
Yes. Just about everything can be spoofed to some degree. It really
depends on what information the owner of the purported sending domain
publishes and what filtering / consumption of said information the
receiving s
On July 19, 2018 6:53:52 PM UTC, Jim Popovitch wrote:
>On July 19, 2018 5:28:24 PM UTC, Mark Sapiro wrote:
>>On 07/19/2018 08:02 AM, Grant Taylor via Mailman-Users wrote:
>>>
>>> I have often wondered about enhancing Mailman, or augmenting it with
>>a
>>> milter, to be able to test the SMTP enve
On July 19, 2018 5:28:24 PM UTC, Mark Sapiro wrote:
>On 07/19/2018 08:02 AM, Grant Taylor via Mailman-Users wrote:
>>
>> I have often wondered about enhancing Mailman, or augmenting it with
>a
>> milter, to be able to test the SMTP envelope from, to, and body
>content
>> against list parameters a
At Thu, 19 Jul 2018 10:25:01 -0700 Mark Sapiro wrote:
>
> On 07/19/2018 05:16 AM, Robert Heller wrote:
> > At Wed, 18 Jul 2018 19:33:20 -0700 Mark Sapiro wrote:
> >
> >>
> >> On 07/18/2018 07:10 PM, Robert Heller wrote:
> >>>
> >>> Mailman only checks the From: header...
> >>
> >>
> >> Not tru
On 07/19/2018 08:02 AM, Grant Taylor via Mailman-Users wrote:
>
> I have often wondered about enhancing Mailman, or augmenting it with a
> milter, to be able to test the SMTP envelope from, to, and body content
> against list parameters and be able to reject messages during the SMTP
> delivery tra
On 07/19/2018 05:16 AM, Robert Heller wrote:
> At Wed, 18 Jul 2018 19:33:20 -0700 Mark Sapiro wrote:
>
>>
>> On 07/18/2018 07:10 PM, Robert Heller wrote:
>>>
>>> Mailman only checks the From: header...
>>
>>
>> Not true. See my other reply in this thread.
>
> I mean it does not check things like
On 07/19/2018 07:25 AM, Scott Neader wrote:
> Hi all. Running Mailman v2.1.26 on CentOS 6. When the list
> has digest_send_periodic set to Yes, and a size of 100kb, users are seeing
> digests with upwards of a week's worth of mail, if the list has been
> quiet. i.e. it seems to be respecting the
On 07/19/2018 06:16 AM, Robert Heller wrote:
I mean it does not check things like the Received: headers*by default*. If
the email part of the From: header is a list member address, Mailman
will consider that the mail is from that member and pass the message on
to the list,*even if the From: hea
Hi all. Running Mailman v2.1.26 on CentOS 6. When the list
has digest_send_periodic set to Yes, and a size of 100kb, users are seeing
digests with upwards of a week's worth of mail, if the list has been
quiet. i.e. it seems to be respecting the 100kb limit, but not
the digest_send_periodic setti
At Wed, 18 Jul 2018 19:33:20 -0700 Mark Sapiro wrote:
>
> On 07/18/2018 07:10 PM, Robert Heller wrote:
> >
> > Mailman only checks the From: header...
>
>
> Not true. See my other reply in this thread.
I mean it does not check things like the Received: headers *by default*. If
the email part
27 matches
Mail list logo
