[Mailman-Users] Re: Need help diagnosing an intermittent DMARC mung failure

On 4/20/24 08:21, Jim P. via Mailman-Users wrote: Does the sender have an internationalized domain name (IDN)? Nope. My domain is one of them. Yahoo is another. The 3rd, which I don't remember at the moment, is a .net or .com. Are you able to reliably dig the sender's DMARC record over an

[Mailman-Users] Need help diagnosing an intermittent DMARC mung failure

Hi, I'd like some help diagnosing an intermittent DMARC mung failure on Mailman 2.1.29. Some of the time DMARC munging works perfectly fine, and then seemingly with no configuration changes, DMARC munging stops working. Then after restarting Mailman it may start working again. -- We don't

[Mailman-Users] Re: Question regarding message-ids

On 9/13/23 7:42 AM, Ralf Hildebrandt via Mailman-Users wrote: * A mail goes to both lists. A singular email is sent to both lists as a recipient. * The mail is delivered twice (to an exchange server), in two SMTP sessions, to the same user adress. I get two positive delivery confirmations.

[Mailman-Users] Re: Python 2.7.15, etc, vs Python3...

On 7/17/23 7:24 PM, rich...@karmannghia.org wrote: OTOH, can Python3 (what's there now) be THAT backwards incompatible?! How incompatible are AM & FM radio? How incompatible are IPv4 and IPv6? How incompatible are gasoline and Diesel motors? SURELY I can make it happy somehow, right? As C

[Mailman-Users] Re: Line breaks in monthly reminder emails

On 12/2/22 5:33 PM, Mark Sapiro wrote: There is a -l/--listname option to limit to a list or, if repeated, lists, but no option to limit to a single user. Sounds like a reason to (temporarily) create a new list with yourself as the only subscriber and test things. -- Grant. . . . unix || d

[Mailman-Users] Re: Line breaks in monthly reminder emails

On 12/1/22 11:45 PM, Stephen J. Turnbull wrote: Possibly more flexible (but harder to implement and dependent on user MUAs) would be to use format=flowed in Content-Type. +10 for format=flowed IMHO format=flowed is not hard to implement and it produces responsive emails which wrap to whatever

[Mailman-Users] Re: Duplicate emails being received

On 10/17/22 9:20 PM, Mark Dale via Mailman-Users wrote: Thanks for that pointer. You're welcome. At the moment the Postfix smtpd_timeout = 60s. I think the original default is 300s. I don't see any problem with having the higher value. Most connections will complete well within that amoun

[Mailman-Users] Re: Duplicate emails being received

On 10/17/22 5:25 PM, Mark Dale via Mailman-Users wrote: Does anyone have any tips or pointers? I've seen this type of duplication when there were communications problems that were causing your outbound MTA to send messages multiple times. This usually happens when there are communications pr

[Mailman-Users] Re: Plus addressing

On 3/21/22 8:01 AM, robertowenbere...@gmail.com wrote: Does the list support plus addressing? Yes and no. I believe the more proper name for this is user+detail. I see "plus(ed) addressing" used more commonly more recently. Yes, Mailman will happily accept user+detail addresses from subscr

[Mailman-Users] Re: Email different content in an unique list

+2 for topics On 12/9/21 11:18 AM, Mark Sapiro wrote: For individual messages, Mailman 2.1 has a Topics feature. This is not yet in Mailman 3 in any form, but works for Mailman 2.1. In the Topics section of the admin UI you define topics via regexps to match against the Subject: or Keywords: (

[Mailman-Users] Re: Viewing bounces from Mailman-generated messages?

On 10/12/21 9:30 AM, Jayson Smith wrote: However, since Sendmail logs don't actually show the full rejection message, that's all I know, and it's not enough to go on. I have seen tell of a patch in the comp.mail.sendmail newsgroup to have Sendmail log the full error message (SMTP response).

[Mailman-Users] Re: Gmail and DKIM problems

On 6/30/21 4:37 PM, Thomas Gramstad wrote: I understand that he can't do anything about the DKIM setup at gmail. Nor should he, or anyone else, need to. Can I as list admin do something in the list setup (Mailman 2.29)? As others have said, remove incoming DKIM headers from incoming messag

[Mailman-Users] Re: Okay, you can call me an idiot now

On 5/17/21 11:41 AM, Jayson Smith wrote: Hi again, Hi, Last night I posted a message about Mailman and/or Sendmail failing to deliver Emails to a particular address with an upper case first letter. Two of you pointed out that the mail was probably stuck in Sendmail's outgoing queue, and i

[Mailman-Users] Re: MM2/Sendmail failing to send messages to upper case Email addresses?

On 5/16/21 8:34 PM, Mark Sapiro wrote: Why is a sendmail question. Possibly someone on this list knows the answer, but a sendmail list might be a better resource. I give it about a 98% chance that Sendmail still has the message in it's queue or that it has bounced it. (Possibly sending it to

[Mailman-Users] Re: Does mailman work well for large lists?

On 2/26/21 3:29 PM, david.bar...@mail.com wrote: Good day, Hi, Looking for a solution to have about 50-200 lists for subscribers. Any good examples of mailman being used for 50+ lists you can share for me to see? Trying to see the feasibility of implementing a solution in next 90 days. I

[Mailman-Users] Re: OpenPGP and S/MIME aware Mailman

On 2/14/21 3:02 PM, Dennis Putnam wrote: I was considering taking that plug-in and modifying it to at least work with GPG and mailman 2.1.36. You might look to see if you can move the problem to the MTA level. E.g. have the MTA, or something like a milter on it's behalf, encrypt outgoing mess

[Mailman-Users] Re: OpenPGP and S/MIME aware Mailman

On 2/12/21 3:01 AM, Mailman-admin wrote: And you need to distribute their public keys to your users. Fortunately, S/MIME makes this simple. All you need to do is sign the message. Recipients can extract the public key from the signature. -- Grant. . . . unix || die smime.p7s Descripti

[Mailman-Users] Re: Addressing of list messages by the server

On 2/10/21 10:26 AM, Christian Buser via Mailman-Users wrote: Hi all Hi, My questions - just to understand it, since the list seems to work perfectly: 1) What does cause this different addressing I'm guessing this is related to DMARC. 2) How does the receiving mail server know where to d

[Mailman-Users] Re: Topic hack to streamline use of topics.

On 10/15/20 4:08 PM, Mark Sapiro wrote: Actually, as I note in another post, the header is Keywords:, not Topics:. That was my error. *nod*nod* I was following your lead. Simple mistakes happen. It's how we correct them that matters. ;-) -- Grant. . . . unix || die smime.p7s Descripti

[Mailman-Users] Topic hack to streamline use of topics.

While on the topic of topics ... ;-) I implemented a hack in my LDA to search the body of messages for specific keywords. When one (or more) of the keywords is found, it adds a specific value to the Topics: header. This way, posters don't have to worry about defining the topics before they

[Mailman-Users] Re: Help with Topics

On 10/13/20 3:51 PM, Mark Sapiro wrote: For example, if topic1 has regexp \WMailman\W and topic2 has regexp \Wlist\W, any message containing a Subject: or Topics: header or pseudo header containing the word Mailman ... What is a "pseudo header" in this context? Are you referring to the first

[Mailman-Users] Re: Alternate URL hostname in web UI

On 7/27/20 12:22 PM, Kevin Bowen wrote: Hello, Hi, I'm trying to set up the mailman (2.1.9) web UI behind a load balancer in order to offload the TLS to it (because this is an ancient machine which doesn't support modern TLS versions, and newer browsers are complaining about it). I need all

Re: [Mailman-Users] Best way to slow down all the spam to my lists?

On 12/13/19 9:02 PM, Mark Sapiro wrote: As postgrey learns, it will remember triplets (sender, sending IP, recipient) and not delay them and in addition will whitelist domains that retry successfully more than a few times. The bigger senders are doing things now (more than ever) that they wer

Re: [Mailman-Users] LDAP routing

On 11/14/19 11:31 AM, Zinski, Steve wrote: We are migrating from sendmail (virtuser) mail routing to LDAP routing. Setting up routing for users is pretty straightforward using the inetLocalMailRecipient class and the mail/mailLocalAddress/mailRoutingAddress attributes. But I was wondering what

Re: [Mailman-Users] Finding list user in redacted FBL reports

On 8/5/19 10:14 PM, Scott Neader wrote: Hi all! I have a list member with a comcast.net email address that is marking most every list message as spam. I have Personalization enabled, and have the subscriber's email address in the footer, but Comcast redacts the email address. Unfortunately, th

Re: [Mailman-Users] Maximum attachment size

On 6/5/19 3:59 PM, Robert Heller wrote: I wonder if this is *mailman* or your MTA that is complaining... It might also be a webserver thing trying to react to the pending moderators request / hold screen (page). -- Grant. . . . unix || die smime.p7s Description: S/MIME Cryptographic Sig

Re: [Mailman-Users] Maximum attachment size

On 6/5/19 3:18 PM, Bryan Blackwell wrote: Hi folks, Hi, I've run into an apparent limit in size - we send newsletters through one of our lists, and they can get large. One in particular runs over 20MB, and I get an error on the held messages page trying to process it. I'm guessing that yo

Re: [Mailman-Users] question about email automation

On 5/30/19 8:04 AM, Fabian A. Santiago wrote: Hello, Hi, i run a mailing list on mm 2.x. periodically i send out an event opening email to the list. this is typically followed by a conclusion email at the end of a specific period. How specific is the period? Is the end known at the start,

Re: [Mailman-Users] Training Mailman to find email address from NDR

On 5/15/19 10:55 AM, Mark Sapiro wrote: This message is a disaster. Is this an actual bounce as received? It almost looks like an RFC 3464 compliant DSN except see comment below. ~chuckle~ Agreed. The message body is that of a MIME multipart message, but the main content type is text/plain i

Re: [Mailman-Users] Training Mailman to find email address from NDR

On 5/15/19 7:45 AM, Andrew Hodgson wrote: Hi, Hi, Here is the bounce message, I know I can enable VERP and this problem should go away, but I wanted to see if I could get this working without VERP as we have a large mail traffic on the list. Did you redact anything significant from the bo

Re: [Mailman-Users] Prevent users from changing email address

On 4/23/19 5:02 AM, Kiffin Gish wrote: Is it possible to configure mailman so that it is not possible for users to change their email address, e.g. disabling the option and including the service desk contact information instead? What will prevent users from unsubscribing with the old address a

Re: [Mailman-Users] Spam / Email Spoofing Problem (SPF check possible?)

On 4/5/19 11:59 AM, Valentin Schwarze via Mailman-Users wrote: Are there any settings that we as administrators of the list could change to end that behavior? For example, is it possible in any way, that Mailman only accepts emails that passed a SPF check? Or any other option to prevent email w

Re: [Mailman-Users] FetchMail feed into Mailman

On 3/26/19 12:36 AM, Jim Ziobro wrote: You won't know how important until you start getting duplicate messages like RFC 1047 . How would having a local MTA change the behavior in the face of a duplicate message? I've seen symptoms of duplicate messages wh

Re: [Mailman-Users] FetchMail feed into Mailman

On 3/26/19 12:36 AM, Jim Ziobro wrote: why not setup standard Mailman under your favorite mail system and let FetchMail do what it does best? The unneeded complexity of a local mail system. FetchMail & SMTP Auth would work against an ISP's email server over dynamic / dial up connections. Su

Re: [Mailman-Users] mailman on google comput engine

On 3/24/19 11:50 PM, Stephen J. Turnbull wrote: This should work in Mailman 2, but won't in Mailman 3 (which expects incoming posts via LMTP). Noted. I think it would be possible to interject a shim between fetchmail that would extract what's necessary to speak LMTP to Mailman. Is the LMTP

Re: [Mailman-Users] mailman on google comput engine

On 3/21/19 4:04 PM, Dimitri Maziuk via Mailman-Users wrote: I honestly don't remember the details but if I was passing mail to local MTA configured as my home MX, I don't see why mailman wouldn't work behind that. I think that it should. I'm talking about bypassing the local MTA all together.

Re: [Mailman-Users] mailman on google comput engine

On 3/21/19 2:05 PM, Dimitri Maziuk via Mailman-Users wrote: IST vaguely R firing up fetchmail from a dip script to inject messages from my school mailbox into my local qmail... Plenty typical at the time. Fetchmail itself is plenty common. I had no idea that it was as common with Mailman. 20

Re: [Mailman-Users] mailman on google comput engine

On 3/21/19 11:58 AM, Adam Goldberg wrote: There are ways around this. I see no technical reason why Mailman couldn't function via something like fetchmail from a POP3 mailbox and SMTP Authentication to send. Fetchmail would pull the messages from an external 3rd party email server, do a lit

Re: [Mailman-Users] mailman on google comput engine

On 3/21/19 12:40 AM, 황병희 wrote: in this case i can run mailman with other port (example 625)? again question, Mailman can act with 625 or 1625 or 2625, ...? No. Not directly. Mailman is not a mail server. You must have a mail server (daemon) sit in front of Mailman. You can make that mail

Re: [Mailman-Users] email to sms?

On 02/27/2019 02:22 PM, Dave Stevens wrote: Hi, Hi Dave, I've been using mailman to send routine announcements for a long time and more and more what people want is a text message. I've been able to discover gateways for individual carriers so that I can send to @..com and the subscriber ge

Re: [Mailman-Users] Automatic subscription based on e-mail subject

On 2/1/19 6:49 PM, Richard Damon wrote: Yes, Mailman has a feature call topics, but that is very different then what the OP is asking for. Agreed. (I thought I covered that in my last email. Maybe I wasn't clear.) The Mailman 'Topic' operation basically provides the ability of the list owne

Re: [Mailman-Users] Automatic subscription based on e-mail subject

On 02/01/2019 01:14 AM, R. Diez via Mailman-Users wrote: Of course there is the concept of 'Topic' in a mailing list. Mailman, the web interface, or whatever, does know how to group topics together. That is an obvious feature, because people tend to work/participate in threads. I believe that

Re: [Mailman-Users] Allow posting from addresses with modifiers?

On 01/14/2019 11:13 AM, Mark Sapiro wrote: To place the burden on john, he can subscribe both addresses and set j...@example.com to nomail. This is what I have done for many mailing lists. — I subscribe with one private address for email filtering and reply from another public email address

Re: [Mailman-Users] mm-handler same as postfix-to-mailman.py

On 01/07/2019 09:59 AM, Dmitri Maziuk via Mailman-Users wrote: We used to run irix whose sendmail sent every message from host.domain and every A record had to have an adjacent MX record for e-mail to even work. That way lies madness. Hum. I think Sendmail (and other MTAs that I've tested) de

Re: [Mailman-Users] mm-handler same as postfix-to-mailman.py

Hi Jim, On 1/4/19 3:40 AM, Jim Ziobro wrote: Setting up mailing lists in a separate domain has a nice administrative appeal. Agreed. That's how I've always done it. If I ever cared enough, I could set up a forward (et al) from l...@example.net to l...@lists.example.net. Maybe not automatic

Re: [Mailman-Users] UTF-8 and digests...

On 11/30/2018 10:33 AM, Mark Sapiro wrote: Plain text digests are encoded in Mailman's character set for the list's preferred_language. For English, this is us-ascii unless you've changed it. Thus, non-ascii unicodes will be rendered as '?' in the plain digest. You can change Mailman's character

[Mailman-Users] UTF-8 and digests...

Is it expected that Mailman will preserve UTF-8 (punctuation symbols) in non-MIME digests? I'm having errors reported to me from (non-MIME) digest subscribers to lists mailing lists. Is this a known limitation of non-MIME digests? Or is it possibly a symptom of a problem? -- Grant. . .

Re: [Mailman-Users] mm-handler or aliases to integrate with sendmail

On 11/29/2018 02:00 AM, Jim Ziobro wrote: Mm-handler is definitely a cool idea. But it seems that once Mailman can update Sendmail's aliases immediately there is no need for mm-handler. I view things a little bit differently. Why should I need to reconfigure the MTA when I'm making a change to

Re: [Mailman-Users] mm-handler v3

On 11/28/2018 02:39 PM, Jim Ziobro wrote: I now realize that mm-handler would not be necessary if Mailman fully connected to Sendmail.  The Postfix connection looks very close. Please elaborate on what you mean by "if Mailman fully connected to Sendmail". Rather, how is Mailman not already co

Re: [Mailman-Users] OT - Smart .forward replacement?

On 11/25/18 1:03 PM, Lindsay Haisley (linode) wrote: mail redirected through a .forward will always fail SPF validation. That is not always accurate. It is relatively easy to configure an MTA to support Sender Rewriting Scheme, either for everything that is sent out or just things that don'

Re: [Mailman-Users] OT - Smart .forward replacement?

On 11/24/18 10:17 PM, Jayson Smith wrote: Hi, Hi, I've been using .forward to forward Email from some user mailboxes to other addresses. Normally this works just fine, but a few weeks ago a situation happened which demonstrates how it can be an epic fail. I had a Mailman/DNS problem after u

Re: [Mailman-Users] GPG Sig parse error

On 11/01/2018 01:49 PM, Jim Popovitch via Mailman-Users wrote: Apologies Grant it this is too much discussion of you :-) I'm only trying to get to the root of the issue. No problem. I'm using S/MIME, not PGP (GPG). Let's see if this makes it through happier. -- Grant. . . . unix || die

Re: [Mailman-Users] mm-handler support

On 10/31/2018 08:14 PM, Mark Sapiro wrote: I think that would be good. ACK See my reply to Jim if you have opinions on how / when it's done. See Intriguing. My python is quite bad, but that looks like it reads from STDIN a

Re: [Mailman-Users] mm-handler starting version

On 10/31/2018 08:41 AM, Jim Ziobro wrote: I am starting from the contrib directory file named:     mm-handler-2.1.10 inside is line:     $VERSION = '$Id: mm-handler 2.1.10 2008-04-14 00:00:00 $'; My goals:  * patch upper/lowercase issue solved a decade ago  * allow mail to postmas...@list.e

Re: [Mailman-Users] mm-handler support

On 10/29/2018 09:22 PM, Mark Sapiro wrote: The most up to date version is . For some info on the differences between this and the original

Re: [Mailman-Users] mm-handler support

On 10/25/2018 09:22 AM, Mark Sapiro wrote: Please make whatever changes you feel are needed and post them here, and I will include them in the next release. What is the authoritative version / source of mm-handler? I've got three different versions: - 2.1.10 - 5100 - modified form of an un

Re: [Mailman-Users] non-subscribers getting through--email address in "Real Name"

m: header has the original sender's email address. [1] If the From: header reflects the mailing list, there is no DMARC conflict with the original sender's domain. [1] I think it may be possible to move the email address into the human friendly portion of the address and replace the ac

Re: [Mailman-Users] ARC

On 07/25/2018 03:53 AM, Stephen J. Turnbull wrote: That's not how "on behalf of" worked in practice. What happened in April 2014, was that a home business owner (HBO) would send a pile of completed order notices to intuit.com, and intuit.com would send an invoice to each customer on behalf of

Re: [Mailman-Users] non-subscribers getting through--email address in "Real Name"

rtion of the From: header comes into play. I.e. From: Grant Taylor Becomes: From: Grant Taylor via Mailman-Users This can show up in the index of a mailbox. Or the two lines that I'm suggesting prefixing the body with. Grant Taylor wrote the following: Granted, that do

Re: [Mailman-Users] non-subscribers getting through--email address in "Real Name"

shed DMARC records. I.e. From: Grant Taylor Becomes: From: Grant Taylor via Mailman-Users Thus removing any conflict with any DMARC records published by tnetconsulting.net Since the message is now from the Mailman-Users mailing list, it's perfectly possible to insert a line at t

Re: [Mailman-Users] non-subscribers getting through--email address in "Real Name"

On 07/24/2018 06:59 PM, Richard Damon wrote: You CAN’T strip DMARC. I can most certainly strip any DKIM related headers from messages that are coming into my server on their way to my mailing list. I'm not talking about altering other people's view of DNS. (That's a completely different to

Re: [Mailman-Users] non-subscribers getting through--email address in "Real Name"

On 07/24/2018 06:51 PM, Mark Sapiro wrote: The stolen address books were used to send phishing emails purportedly from the owner of the address book the the addresses in the book. I.e., a message From: a_known_fri...@yahoo.com saying things look at this great thing I found and a URL to evilsit

Re: [Mailman-Users] non-subscribers getting through--email address in "Real Name"

On 07/24/2018 03:16 PM, John Levine wrote: Turning it on for aol.com, yahoo.com, and other domains with user mailboxes, So, are you stating that DMARC should NOT be used on domains that (predominantly) contain end user mailboxes? to outsource the pain of the spam they were getting I'm not

Re: [Mailman-Users] non-subscribers getting through--email address in "Real Name"

On 07/22/2018 04:25 PM, Richard Damon wrote: What actions do you think mailing lists are doing improperly? I personally believe that mailing lists are their own end entity, just like our individual mailboxes. (Particularly discussion mailing lists.) I also believe that SPF, DKIM, and DMARC

Re: [Mailman-Users] ARC, was non-subscribers getting through--email address in "Real Name"

On 07/22/2018 11:02 PM, Stephen J. Turnbull wrote: You're misunderstanding. The ARC community doesn't discourage whitelisting other sites. The work to do whitelisting does. Thank you for clarifying Stephen. I was afraid that you were somehow implying that there was some sort of guideline on

Re: [Mailman-Users] non-subscribers getting through--email address in "Real Name"

On 07/22/2018 02:03 PM, John Levine wrote: No, it was specified in full knowledge that it would break pretty much every mailing list on the planet if used on domains with human users, instead of its intended target of notices from robot domains like paypal.com. I choose to believe the mailing

Re: [Mailman-Users] ARC, was non-subscribers getting through--email address in "Real Name"

On 07/22/2018 02:05 PM, John Levine wrote: Every domain added to a whitelist like this involves manual work. Yes. Why would you waste time on domains that aren't likely to send mail with ARC headers? I'm not suggesting wasting time on domains that wouldn't send ARC headers. I'm questioning

Re: [Mailman-Users] non-subscribers getting through--email address in "Real Name"

On 07/19/2018 04:59 PM, Phil Stracchino wrote: Actually, mailing lists and other redistribution are among the places DMARC notably breaks. Does DMARC actually break or otherwise behave in a manner contrary to it's specification? I personally believe that DMARC (and SPF and DKIM) are doing ex

Re: [Mailman-Users] ARC, was non-subscribers getting through--email address in "Real Name"

On 07/21/2018 02:24 PM, John Levine wrote: I know people working on whiteish lists to use with ARC, to say that these domain are known to host real mailing lists so you should believe their ARC assertions. Is there some place that I can find out more about these people and / or their projects

Re: [Mailman-Users] non-subscribers getting through--email address in "Real Name"

On 07/20/2018 12:40 AM, Jayson Smith wrote: Could either of these milter solutions linked previously be adapted for use as a Sendmail milter? I'd love to find something which would query Mailman about the status of a particular sender address at the RCPT stage of the SMTP transaction so spoofed

Re: [Mailman-Users] non-subscribers getting through--email address in "Real Name"

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

Re: [Mailman-Users] non-subscribers getting through--email address in "Real Name"

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 -

Re: [Mailman-Users] non-subscribers getting through--email address in "Real Name"

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

Re: [Mailman-Users] non-subscribers getting through--email address in "Real Name"

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

Re: [Mailman-Users] non-subscribers getting through--email address in "Real Name"

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

Re: [Mailman-Users] non-subscribers getting through--email address in "Real Name"

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

Re: [Mailman-Users] Spam Subscriptions

On 06/03/2018 04:11 PM, Mark Sapiro wrote: Ban list regexps are case insensitive. Thank you for the clarification Mark. The fact that the ones I saw never had periods following the plus sign. ACK -- Grant. . . . unix || die -- Mailman-U

Re: [Mailman-Users] Spam Subscriptions

On 06/02/2018 09:29 PM, Mark Sapiro wrote: I use this regexp in the GLOBAL_BAN_LIST ^[0-9a-z.]{8,}\+[0-9a-z]{4,}@gmail\.com$ Are you not looking for capital letters? I can see how the period in the first class would work, but I don't see that in the second class. What am I missing? -- G

Re: [Mailman-Users] How do I run 2.x mailman more securely?

On 05/31/2018 09:33 PM, incoming-pythonli...@rjl.com wrote: I wrote scripts that read the list and generated a rule per network. It can be slow, but has worked reliably for many years. Since it is a mailserver, performance has not been a big issue. I am in the process of designing a replaceme

Re: [Mailman-Users] How do I run 2.x mailman more securely?

On 05/31/2018 06:37 PM, incoming-pythonli...@rjl.com wrote: Both are valid alternatives. There may be performance advantages, to stopping attacks at the firewall level instead of higher up in the application stack. Agreed, on both accounts. Firewalls also have a tendency to protect multiple

Re: [Mailman-Users] How do I run 2.x mailman more securely?

On 05/31/2018 03:05 PM, Dimitri Maziuk wrote: What exactly is it about mailman usernames and passwords that you are trying to protect with HTTPS? I wasn't talking about Mailman usernames (email addresses) and passwords. I was talking about the usernames and passwords for Basic HTTP(S) authen

Re: [Mailman-Users] How do I run 2.x mailman more securely?

On 05/31/2018 01:18 PM, Dimitri Maziuk wrote: Yeah, I too once thought that was a good idea. I'm not quite following you. Are you saying that you now dislike HTTP(S) usernames & passwords specifically? Or are you saying that you dislike hosting something yourself? And then heartbleed came

Re: [Mailman-Users] How do I run 2.x mailman more securely?

I feel like I'm missing something and as such have some questions. On 05/31/2018 11:42 AM, incoming-pythonli...@rjl.com wrote: Depending on where your users are coming from, it might be easier to limit access to the GUI using a firewall. Why are you using a firewall instead of leveraging the w

Re: [Mailman-Users] How do I run 2.x mailman more securely?

On 05/31/2018 12:25 PM, Grant Taylor wrote: IMHO the web server has a LOT more experience at user access control than most web applications. As such, I feel like the web server probably has a better handle on how to do it. Apache (and I suspect Nginx) has the ability to use client side TLS

Re: [Mailman-Users] How do I run 2.x mailman more securely?

On 05/30/2018 03:36 PM, Parker, Michael D. wrote: I've been assigned the task of attempting to secure our current implementation of GNU MailMan. One thing that I've not seen (or missed) in this thread is the idea of leveraging HTTPS usernames and passwords to protect the web interface. IMHO

Re: [Mailman-Users] GDPR

On 05/22/2018 07:46 PM, Stephen J. Turnbull wrote: Many posts will include their names in CCs, especially on lists that munge Reply-To. Don't forget the munged reply. }:-) Some of these may be hidden (eg, Reply-To is normally not displayed; I don't know offhand if it's in the mbox files).

Re: [Mailman-Users] [Mailman-cabal] GDPR

hat the infinite wisdom of politicians will say that the entire paper needs to be shredded. I think it also significantly depends on what needs to be redacted. Removing "supercalifragilisticexpialidocious" is a LOT different than removing "Grant Taylor" from the Mailman-Users arch

Re: [Mailman-Users] [Mailman-cabal] GDPR

On 05/17/2018 02:56 AM, Bernd Petrovitsch wrote: FWIW and IMHO, I think we are in violent agreement here. :-) In the old-school life: the sender (because s/he said it on her/his free will) - I hope;-). But the person who overheard it may tell the story to a third person. And it's just/only

Re: [Mailman-Users] GDPR

Duly noted. On 05/15/2018 07:04 PM, Mark Sapiro wrote: Actually, the easiest way is to just redact the cumulative LIST.mbox/LIST.mbox file and rebuild the archive with 'bin/arch --wipe' but that can have undesired side effects. Doesn't that run the risk of renumbering messages, thus breaking

Re: [Mailman-Users] [Mailman-cabal] GDPR

On 05/15/2018 03:08 AM, Andrew Hodgson wrote: What do I redact or remove in this instance? - Personal details about the original poster and the event who had not consented to having their email posted to the mailing list; I would likely have (presuming sufficient motivation): 1) Get mailman

Re: [Mailman-Users] [Mailman-cabal] GDPR

On 05/15/2018 03:18 AM, Andrew Hodgson wrote: At the moment the list administrator and moderator account is accessed via no username and a single password. If that password is shared, I have no audit trail of who logged into the system. ACK I like to run Mailman (et al) administration pages

Re: [Mailman-Users] [Mailman-cabal] GDPR

On 05/14/2018 04:11 PM, Bernd Petrovitsch wrote: Seriously, these folks don't know what they imply. Nope. Politicians (almost) never fully understand what's going on. And to be honest: If person X fullquotes and the email ends in an archive, who's fault is it? Obviously the archive's (or m

Re: [Mailman-Users] [Mailman-cabal] GDPR

On 05/14/2018 04:02 PM, Ángel wrote: IMHO they would mostly fail under §18 and GDPR wouldn't apply: Okay. What happens if a subsequent data breach (malware / infection) causes said individual archives to become public information? }:-) Of course, if a company was using the mailing list to

Re: [Mailman-Users] [Mailman-cabal] GDPR

On 05/14/2018 06:33 AM, Andrew Hodgson wrote: - Archive purge requests. We have discussed the same items as on the list to date. I am looking at doing a simple grep for the relevant person's details and changing that. The main reason for doing this is that if we just remove the author's messa

Re: [Mailman-Users] [Mailman-cabal] GDPR

On 05/12/2018 03:35 PM, Bernd Petrovitsch wrote: Well, it's the very nature of an archive that everything stays there (similar to a backup). Yes. But I believe that GDPR has implications on expunging things from archives / backups too. Not doing so is not within the spirit of forgetting som

Re: [Mailman-Users] [Mailman-cabal] GDPR

On 05/12/2018 02:39 PM, Stephen J. Turnbull wrote: It would be a much more annoying matter if they claimed the right to be deleted from third party posts that quoted and identified them, though. If there is a "right to be forgotten" that impinges on mailing list archives, that seems plausible t

Re: [Mailman-Users] 'from' header at delivered email from inside / outside organization

On 04/19/2018 04:17 AM, kan...@yamachu-tokachi.co.jp wrote: Hello Mailman experts, I'm not an expert, but I've got questions. I created a mailing list (i.e. a...@ml.abc.co.jp) with mailman in our organization. I don't think it matters, but I want to make sure I'm not assuming anything inco

Re: [Mailman-Users] (relatively) new DMARC issues - and Gmail

Have you considered sending your message to the Mailop mailing list? I know that there are a couple of Gmail admins / coworkers that are subscribed to Mailop and will respond to issues like this. Plus, it might also be a better forum and get more engagement / suggestions / gratitude by others

Re: [Mailman-Users] Yahoo rejects

On 03/16/2018 07:54 PM, Grant Taylor via Mailman-Users wrote: Has there been any noise about Yahoo on mailop about this new behavior? I just read a handful of messages on mailop where multiple people are reporting this issue. One of the last messages indicated that the problem might be

Re: [Mailman-Users] Yahoo rejects

On 03/16/2018 01:57 PM, Jim Dory wrote: -- Forwarded message -- From: MAILER-DAEMON@domain2.example To: nome-announce-bounces@domain1.example Cc: Bcc: Date: Subject: Delivery failure Message from domain2.example. Unable to deliver message to the following address(es). >: This use

  1   2   3   4   >