[Mailman-Users] Re: Change in email routing
Thank you, Stephen, for the reply and valuable tips. I will upgrade Mailman to the latest version asap. I have an urgent solution for the following issue. Postfix is configured to use the O365 as a relay host in our Mailman use case in our Mailman use case. One of our lists has close to 6k members. There were two messages for approval. I approved one and received it for both my list subscriptions. After about an hour or so, I approved the second message. The second message was not delivered to any of the subscribers. The reason is that the O365 email id used for relay host authentication was blocked with the following statement in the O365 Admin console: "Potentially compromised account. Anomalous sending patterns were detected, resulting in the user being restricted sending mails" I'm told that there are per minute and per hour restrictions of 30 and 1800 emails respectively (inbound and outbound) on o365. How can the said restrictions be complied with in Mailman? Thanks in advance, Francis From: Stephen J. Turnbull Sent: 01 August 2022 19:42 To: Francis Jayakanth Cc: mailman-users@python.org Subject: [Mailman-Users] Change in email routing External Email Francis Jayakanth via Mailman-Users writes: > Hi, I'm administering and moderating a list with Mailman version > 2.1.20. This is extremely old. If it works, that's fine, but you're missing 19 releases worth of security fixes, including some quite nasty and easily exploitable ones (like cross-site scripting). > I need to make the following changes with immediate effect: > > 1. Switch to the Postfix email router from Sendmail, > 2. Use Office 365 with authentication as the relay host > > I have stopped the Sendmail service and configured Postfix for > email transactions. What does "configure for email transactions" mean? We really can't help unless you're quite precise about these things. Where does the O365 relay host sit? Between Mailman and Postfix, or between Postfix and the Internet? > Things are not working as they used to while using Sendmail. I have > specifically noticed that the following Mailman functions are not > working after the change over: > > 1. Online membership registrations are not receiving email > communication about the membership being held for approval. > 2. The moderator does not receive communication about new online > registrations. So, new online registrations are not > happening. > 3. Adding new subscriptions through the command line works, but > neither the subscriber nor the moderator receives any > communication. Ex. ./add_members -r new -w y -a y listname Is O365 involved in transmitting these notifications? If so, is the sending agent (Mailman or Postfix) configured to use the authentication credentials? What do the logs say? Both Mailman and the MTAs should be keeping logs of all outgoing messages. > 4. No confirmation email is received after posting a message by > a subscribed member. Does the post go out to the subscribers? Are you sure this notification is enabled? (In my experience members hate it with a passion). Again, this should be logged by Mailman and both MTAs. > 5. The email address of the approved messages is changing > to the authentication email id, but the name remains that of > the member making the post. Is it possible that this issue is affecting receipt of notifications because recipients have not whitelisted the authenticated address, and they're being discarded or quarantined as spam? Is the authenticated address in the same domain as Mailman, and if not, do you have a DMARC policy of p=reject or p=quarantine? That sounds like something that O365 is doing. Mailman should not touch the From email address unless you have configured one of the following: - from is list (normally used to work around DMARC issues) - anonymous list - full personalization Stock Mailman will not use connection creditials to modify the message; it only becomes aware of them at the point it actually connects to the MTA. Steve -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Re: Change in email routing
Francis Jayakanth via Mailman-Users writes: > I'm told that there are per minute and per hour restrictions of 30 > and 1800 emails respectively (inbound and outbound) on o365. I'm not sure what "limit of 30 emails/minute" means. In the below, I am going to assume it means "addresses to be delivered." The other meaning I could imagine would be "connections", which would make it much easier to comply (as long as you have a few "giant" destinations like Gmail and Yahoo). > How can the said restrictions be complied with in Mailman? There is no facility for this in Mailman itself. Mailman does maintain queues, but their purpose is only to ensure that messages are processed by each function in order and do not get lost while waiting for processing. It contains no logic for "fair queuing" or "throttling" for individual outgoing messages. It just sends them all to the MTA (Postfix), with popular domains getting multiple addressees and only one message body. The only restriction implemented in Mailman is the maximum number of addressees per message. That is maybe you have 1500 Gmail addresses, then you could limit to 25 addressees per SMTP transaction, to allow 5 other emails to get through every minute. Normally I would recommend using Postfix to do the throttling you need (see the various "recipient_limit" and "rate_delay" parameters in postconf(5)), but given this requirement: > One of our lists has close to 6k members. you are in a bad place no matter how you look at it unless you can throttle the *incoming* posts to 4-6 per day, spaced at least 3 and probably 4 hours apart. Once one post is in the queue, I don't think there is any way to guarantee it will be sent to all addressees before the next post starts to be sent. So unless you can guarantee posts spaced out in time, you could end up in a situation where 1/4 of the list gets the post, then you wait until the hour, but before that another post sneaks in and it gets delivered to the same 1/4 of the list. That is as far as I know an MTA goes through the recipient domains in a deterministic order, and will start over on the domains that have already had post #1 delivered, by delivering post #2 to them. And of course processing just one post for this list is going to make it difficult for anything else to get delivered until it's done. Of course the whole time this is going on, you have to keep all of the queued posts on disk, one copy plus the address list per domain. For that reason it would be nice if Mailman handled the queuing for you, but it doesn't. -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Re: Change in email routing
This is a hard limit (30 emails per minute, 1800 per hour per mailbox) built into O365. Microsoft reccomends using 3rd party bulk mail oroviders like MailChimp. O365 mailboxes are not really suitable for mass emailing, and you can only relay through a desgnated mailbox, iirc. This isn’t fixable with O365 as the relay host afaik. If the list server can be made public facing so that Postfix manages outgoing email outright (a lot more work because its’ another public-facing server, along with any security implications) We use O365, but our SMTP is handled by Barracuda which provides anti-spam, anti impersonation and other services, and we can exempt specific hosts/addresses from these limits with that. On Aug 2, 2022, at 7:49 AM, Stephen J. Turnbull mailto:stephenjturnb...@gmail.com>> wrote: Francis Jayakanth via Mailman-Users writes: I'm told that there are per minute and per hour restrictions of 30 and 1800 emails respectively (inbound and outbound) on o365. I'm not sure what "limit of 30 emails/minute" means. In the below, I am going to assume it means "addresses to be delivered." The other meaning I could imagine would be "connections", which would make it much easier to comply (as long as you have a few "giant" destinations like Gmail and Yahoo). -- Bruce Johnson University of Arizona College of Pharmacy Information Technology Group Institutions do not have opinions, merely customs -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Re: Flooded with signup requests
On 29.07.22 13:25, Stephen J. Turnbull wrote: In 'General Options' set admin_immed_notify to No, and only one mail will be sent per day. That helps a lot. Now I just got the summary for the day: I have for each mailinglist 2023 open signup requests. that means If I want to delete and ban every one of them 4046 mouse clicks in the admin back-end. But as you see there are lots of duplicates. These lists were not set to 'advertised'. ttze...@gmail.com Thu Jul 28 10:43:51 2022 sking2...@gmail.com Sat Jul 30 13:54:16 2022 timcharp...@gmail.com Sat Jul 30 13:54:46 2022 typetosa...@gmail.com Sat Jul 30 13:56:25 2022 sking2...@gmail.com Sat Jul 30 13:56:48 2022 myr...@gmail.com Sat Jul 30 13:57:24 2022 timcharp...@gmail.com Sat Jul 30 13:57:42 2022 jordanlehm...@gmail.com Sat Jul 30 13:58:09 2022 ojambr...@me.com Sat Jul 30 13:58:10 2022 jordanlehm...@gmail.com Sat Jul 30 13:59:14 2022 ojambr...@me.com Sat Jul 30 13:59:46 2022 myr...@gmail.com Sat Jul 30 14:04:06 2022 myr...@gmail.com Sat Jul 30 14:04:24 2022 typetosa...@gmail.com Sat Jul 30 14:05:02 2022 ojambr...@me.com Sat Jul 30 14:06:00 2022 typetosa...@gmail.com Sat Jul 30 14:06:33 2022 timcharp...@gmail.com Sat Jul 30 14:08:52 2022 myr...@gmail.com Sat Jul 30 14:10:42 2022 timcharp...@gmail.com Sat Jul 30 14:11:04 2022 ojambr...@me.com Sat Jul 30 14:11:23 2022 timcharp...@gmail.com Sat Jul 30 14:13:36 2022 typetosa...@gmail.com Sat Jul 30 14:17:52 2022 typetosa...@gmail.com Sat Jul 30 14:23:27 2022 myr...@gmail.com Sat Jul 30 14:24:59 2022 myr...@gmail.com Sat Jul 30 14:27:57 2022 ojambr...@me.com Sat Jul 30 14:27:58 2022 typetosa...@gmail.com Sat Jul 30 14:29:09 2022 ojambr...@me.com Sat Jul 30 14:32:14 2022 pearce.lo...@gmail.com Sat Jul 30 14:39:45 2022 myr...@gmail.com Sat Jul 30 14:42:01 2022 timcharp...@gmail.com Sat Jul 30 14:48:04 2022 myr...@gmail.com Sat Jul 30 14:49:42 2022 myr...@gmail.com Sat Jul 30 14:50:16 2022 timcharp...@gmail.com Sat Jul 30 14:51:42 2022 ojambr...@me.com Sat Jul 30 14:56:22 2022 ojambr...@me.com Sat Jul 30 15:05:19 2022 timcharp...@gmail.com Sat Jul 30 15:05:31 2022 myr...@gmail.com Sat Jul 30 15:06:47 2022 ojambr...@me.com Sat Jul 30 15:12:31 2022 timcharp...@gmail.com Sat Jul 30 15:12:50 2022 myr...@gmail.com Sat Jul 30 15:13:12 2022 timcharp...@gmail.com Sat Jul 30 15:14:31 2022 ojambr...@me.com Sat Jul 30 15:20:26 2022 myr...@gmail.com Sat Jul 30 15:20:41 2022 ojambr...@me.com Sat Jul 30 15:21:29 2022 myr...@gmail.com Sat Jul 30 15:23:25 2022 caitlin.ro...@yahoo.com Sat Jul 30 15:28:51 2022 pebhedr...@yahoo.com Sat Jul 30 15:30:44 2022 bakerig...@yahoo.com Sat Jul 30 15:32:04 2022 ilenekrea...@gmail.com Sat Jul 30 15:32:55 2022 timcharp...@gmail.com Sat Jul 30 15:33:45 2022 myr...@gmail.com Sat Jul 30 15:34:06 2022 timcharp...@gmail.com Sat Jul 30 15:35:03 2022 ojambr...@me.com Sat Jul 30 15:37:20 2022 bakerig...@yahoo.com Sat Jul 30 15:37:21 2022 myr...@gmail.com Sat Jul 30 15:37:35 2022 bakerig...@yahoo.com Sat Jul 30 15:39:10 2022 bakerig...@yahoo.com Sat Jul 30 15:39:20 2022 ilenekrea...@gmail.com Sat Jul 30 15:39:30 2022 timcharp...@gmail.com Sat Jul 30 15:40:39 2022 ilenekrea...@gmail.com Sat Jul 30 15:41:47 2022 timcharp...@gmail.com Sat Jul 30 15:42:57 2022 ilenekrea...@gmail.com Sat Jul 30 15:43:28 2022 ilenekrea...@gmail.com Sat Jul 30 15:46:17 2022 hmarp...@yahoo.com Sat Jul 30 15:47:50 2022 ojambr...@me.com Sat Jul 30 15:49:06 2022 timcharp...@gmail.com Sat Jul 30 15:51:50 2022 timcharp...@gmail.com Sat Jul 30 15:53:35 2022 spconnoll...@yahoo.com Sat Jul 30 15:56:53 2022 timcharp...@gmail.com Sat Jul 30 15:58:01 2022 dkpbp...@gmail.com Sat Jul 30 16:01:16 2022 mtorre...@yahoo.com Sat Jul 30 16:03:32 2022 ojambr...@me.com Sat Jul 30 16:05:24 2022 timcharp...@gmail.com Sat Jul 30 16:07:31 2022 dkpbp...@gmail.com Sat Jul 30 16:09:32 2022 ojambr...@me.com Sat Jul 30 16:13:21 2022 dg7...@yahoo.com Sat Jul 30 16:13:35 2022 myr...@gmail.com Sat Jul 30 16:13:49 2022 madsj...@yahoo.com Sat Jul 30 16:14:25 2022 angelmadiso...@yahoo.com Sat Jul 30 16:14:44 2022 dkpbp...@gmail.com Sat Jul 30 16:16:25 2022 dg7...@yahoo.com Sat Jul 30 16:17:47 2022 madsj...@yahoo.com Sat Jul 30 16:18:07 2022 dkpbp...@gmail.com Sat Jul 30 16:20:09 2022 myr...@gmail.com Sat Jul 30 16:21:17 2022 timcharp...@gmail.com Sat Jul 30 16:21:22 2022 myr...@gmail.com Sat Jul 30 16:23:56 2022 dkpbp...@gmail.com Sat Jul 30 16:25:44 2022 myr...@gmail.com Sat Jul 30 16:26:10 2022 timcharp...@gmail.com Sat Jul 30 16:26:59 2022 dkpbp...@gmail.com Sat Jul 30 16:28:04 2022 ojambr...@me.com Sat Jul 30 16:29:44 2022 ojambr...@me.com Sat Jul 30 16:29:50 2022 ojambr...@me.com Sat
[Mailman-Users] Re: Flooded with signup requests
On 8/1/22 06:31, Max wrote: I have for each mailinglist 2023 open signup requests. that means If I want to delete and ban every one of them 4046 mouse clicks in the admin back-end. But as you see there are lots of duplicates. If your Mailman is >= 2.1.30, there is a REFUSE_SECOND_PENDING mm_cfg.py setting that will cause a second request to subscribe to a list when there is already a pending confirmation for that user. You can also delete all these pending subs with a withlist script. Here's an interactive example: ``` $ ./withlist -i No list name supplied. Python 2.7.18 (default, Jul 1 2022, 12:27:04) [GCC 9.4.0] on linux2 Type "help", "copyright", "credits" or "license" for more information. (InteractiveConsole) >>> for list in Utils.list_names(): ... mlist = MailList(list, lock=True) ... for id in mlist.GetSubscriptionIds(): ... try: ... mlist.HandleRequest(id, mm_cfg.DISCARD) ... except: ... pass ... mlist.Unlock() ... >>> ``` -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Re: Flooded with signup requests
On 7/29/22 09:54, Mark Sapiro wrote: Mailman 3 does this. The message is not so gracious, just "Subscription request already pending", but this is not the case with Mailman 2.1. While it would be possible in MM 2.1 to check the `pending` and `requests` data for an existing request before accepting a new one, MM 2.1 is EOL and won't be changed to do this. I misspoke. MM 2.1 >= 2.1.30 has a REFUSE_SECOND_PENDING mm_cfg.py setting that will cause a second request to subscribe to a list when there is already a pending confirmation for that user to be rejected. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] B.S. With Google Yellow Boxes and GNU Mailman
This may well be a Dream Host administrative issue rather than a GNU Mailman issue.?? That said I'm wondering if: a) There is anything I can do from the administrative interface, or b) Anything I can ask Dream Host to do as they have admin rights on the server CONCERN: Gmail has started sticking a yellow warning box on every GNU Mailman email to Gmail users this week stating to "Be careful with this message" and that they can't verify that it actually came from clinicians-excha...@lists.clinicians-exchange.org. They then provide buttons to report it as spam or phishing. Gmail is also indicating: SPF:?? NEUTRAL with IP 64.90.62.202 DKIM:?? 'FAIL' with domain gmail.com This is freaking out a few of my users. I'm attaching a screenshot of the message and source code for the same message.?? Hopefully this list allows attachments... I already tried using filters in Gmail (as an end user) to try and mark the messages safe, but this does not work. I have a support message in with Dream Host as well. Thanks Michael *Michael Reeder, LCPC * *Hygeia Counseling Services : Baltimore / Mt. Washington Village location* *410-871-TALK / michael(at)hygeiacounseling.com* *http://www.hygeiacounseling.com - main website. * Delivered-To: reederfullsl...@gmail.com Received: by 2002:ac4:9195:0:b0:535:ca28:6c09 with SMTP id m21csp2767303pic; Mon, 1 Aug 2022 19:06:43 -0700 (PDT) X-Google-Smtp-Source: AA6agR7TXywrqhmADbZsCtXoT4kqeag0EzhJYZnuTsGrT/XSrKIJUK0gYPC0MOfhbCltn2768vYa X-Received: by 2002:a63:8249:0:b0:41b:d328:20fd with SMTP id w70-20020a63824900b0041bd32820fdmr9923565pgd.38.1659406003685; Mon, 01 Aug 2022 19:06:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1659406003; cv=none; d=google.com; s=arc-20160816; b=Ocea1qHkq5N549blu8KlrcDtjWxI5EEq7nayKcjwZ7T3VJs4mORFVA5teXBpn0Q5U/ AgrQqbs/BrijHcIZ+0LWCGEZRLCUAKo3Y9KZ+YHGmS8S/V/ronUrZJODn/8JCLWtV8SV Biw982zCdA/F1i0rzR+Grqv3bjN7H/JLa2Pqd8eG3g9j4myjAwfBTaByfLlVDIYWex3/ HMdq/ALSJldd9fG1WMORXghnCv+k2vZBEojMG+bo0SPn1MoAT9afqLOUQWHXSBvouaZo dsrCjP957ZuLUSdPZofGNbklURveO1u82Qfs8QPpDKHH7mJSkoS+P8N3i+c0yk4nPVeW ymPw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=sender:errors-to:content-transfer-encoding:cc:reply-to:from :list-subscribe:list-help:list-post:list-archive:list-unsubscribe :list-id:precedence:subject:to:content-language:user-agent :mime-version:date:message-id:dkim-signature:delivered-to; bh=kx4Auo4pZg7gqLor2KAw7AUVYYsK0WHZVldxAiqLcJw=; b=L8amcDITQmLhNG0NOziwhI/ovkp7m583eNTH/X8XYu1LWY5kdOscRG7dEBXed1sREv 7JQ3qP9t9shs+v1VREtNWzZs72SGv2J+iCASY6XEApbJ3JeHyoyfxRJqz7k6EmywVvkk Vvg9yrdcBuL3xYSA14bhXkV0htyPa+ycS8laIiLS4hRam7q0WealZDQJG32FwjJ1yZQa ce/JXjI0VanVDLrolkC00hMIA36LZJn68PIx54m3jZgoxi4q5tSukbzdmvfmDZStyBhD 3oU3A4Pc/uEzvVvoHLIRBHBur0v0bYCROHu+21vbfbNMhQK+rHY8i2YGCWXQse8Yrgiy iDwQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=neutral (body hash did not verify) header.i=@gmail.com header.s=20210112 header.b=CNSOtBcq; spf=neutral (google.com: 64.90.62.202 is neither permitted nor denied by best guess record for domain of clinicians-exchange-boun...@lists.clinicians-exchange.org) smtp.mailfrom=clinicians-exchange-boun...@lists.clinicians-exchange.org Return-Path: Received: from pdx1-mailman01.dreamhost.com (pdx1-mailman01.dreamhost.com. [64.90.62.202]) by mx.google.com with ESMTPS id bx13-20020a056a00428d00b0051840478994si759670pfb.375.2022.08.01.19.06.43 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 01 Aug 2022 19:06:43 -0700 (PDT) Received-SPF: neutral (google.com: 64.90.62.202 is neither permitted nor denied by best guess record for domain of clinicians-exchange-boun...@lists.clinicians-exchange.org) client-ip=64.90.62.202; Authentication-Results: mx.google.com; dkim=neutral (body hash did not verify) header.i=@gmail.com header.s=20210112 header.b=CNSOtBcq; spf=neutral (google.com: 64.90.62.202 is neither permitted nor denied by best guess record for domain of clinicians-exchange-boun...@lists.clinicians-exchange.org) smtp.mailfrom=clinicians-exchange-boun...@lists.clinicians-exchange.org Received: from pdx1-mailman01.dreamhost.com (pdx1-mailman01.dreamhost.com [IPv6:::1]) by pdx1-mailman01.dreamhost.com (Postfix) with ESMTP id 2E33B20AD6; Mon, 1 Aug 2022 19:06:43 -0700 (PDT) X-Original-To: clinicians-excha...@lists.clinicians-exchange.org Delivered-To: clinicians-exchange-clinicians-exchange@pdx1-mailman01.dreamhost.com Received: from mail-io1-f42.google.com (mail-io1-f42.google.com [209.85.166.42]) by pdx1-mailman01.dreamhost.com (Postfix) with ESMTP id F09D9204A4 for ; Mon, 1 Aug 2022 19:06:36 -0700 (PDT) Received: by mail-io1-f42.google.com with SMTP id q14so9749920iod.3 for ; Mon, 01 Aug 2022 19:06:36 -
[Mailman-Users] Re: B.S. With Google Yellow Boxes and GNU Mailman
See https://support.google.com/a/answer/174124?hl=en This is probably not specific to Mailman. There is lots of advice (such as the link I just found, but not just that) about how to set up DKIM and SPF, and it sounds like these might solve your problem. DMARC is also mentioned, but that is not necessary. I don't know what Dream Host allows you to do. On 08/02/22 14:43, Michael Reeder LCPC -- Hygeia Regular wrote: > This may well be a Dream Host administrative issue rather than a GNU > Mailman issue.?? That said I'm wondering if: > > a) There is anything I can do from the administrative interface, or > b) Anything I can ask Dream Host to do as they have admin rights on > the server > > > CONCERN: Gmail has started sticking a yellow warning box on every GNU > Mailman email to Gmail users this week stating to "Be careful with > this message" and that they can't verify that it actually came from > clinicians-excha...@lists.clinicians-exchange.org. They then provide > buttons to report it as spam or phishing. > > Gmail is also indicating: > SPF:?? NEUTRAL with IP 64.90.62.202 > DKIM:?? 'FAIL' with domain gmail.com > > This is freaking out a few of my users. I'm attaching a screenshot of > the message and source code for the same message.?? Hopefully this > list allows attachments... -- Jonathan Baron, Professor of Psychology, University of Pennsylvania Home page: https://www.sas.upenn.edu/~baron Founding Editor: Judgment and Decision Making (http://journal.sjdm.org) -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Re: B.S. With Google Yellow Boxes and GNU Mailman
On 2022-08-02 1:43 PM, Michael Reeder LCPC -- Hygeia Regular wrote: ... DKIM:?? 'FAIL' with domain gmail.com ... > b) Anything I can ask Dream Host to do as they have admin rights on > the server Tell them you need a DKIM DNS record for clinicians-exchange.org. Hopefully that gets to someone who knows what it means and is able to work with you. Dima -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Re: B.S. With Google Yellow Boxes and GNU Mailman
On 8/2/22 11:43, Michael Reeder LCPC -- Hygeia Regular wrote: Gmail is also indicating: SPF:?? NEUTRAL with IP 64.90.62.202 DKIM:?? 'FAIL' with domain gmail.com Dreamhost should be DKIM signing the outgoing list mail with the list's domain. If they aren't you can ask them to do it, and they can come here for help if they need it. It may not be an issue, but you should also enable DMARC mitigations. For Mailman >= 2.1.18, in Privacy options... -> Sender filters, set dmarc_moderation_action to Munge From and dmarc_quarantine_moderation_action) to Yes. Older versions 2.1.16 and 2.1.17 you can set General Options from_is list to Munge From, but this requires setting ALLOW_FROM_IS_LIST to Yes in mm_cfg.py. This is also available in 2.1.18+, and will apply mitigations to all messages, not just ones publishing DMARC polocy reject or quarantine, This is freaking out a few of my users. I'm attaching a screenshot of the message and source code for the same message.?? Hopefully this list allows attachments... Not images, only attached messages, text and pgp ang pkcs7 signatures. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Re: B.S. With Google Yellow Boxes and GNU Mailman
Thank you all! Dream Host added an SPF DNS record: /"They're [Google] looking for a DNS record called SPF that defines what mail servers are allowed for lists.clinicians-exchange.org. I have added one as a courtesy."// / *For now -- problem solved!** * I will take a look at Mark's DMARC mitigations below also. Thanks, Michael *Michael Reeder, LCPC * *Hygeia Counseling Services : Baltimore / Mt. Washington Village location* *410-871-TALK / michael(at)hygeiacounseling.com* *http://www.hygeiacounseling.com - main website. * On 8/2/2022 4:50 PM, Mark Sapiro wrote: On 8/2/22 11:43, Michael Reeder LCPC -- Hygeia Regular wrote: Gmail is also indicating: SPF:?? NEUTRAL with IP 64.90.62.202 DKIM:?? 'FAIL' with domain gmail.com Dreamhost should be DKIM signing the outgoing list mail with the list's domain. If they aren't you can ask them to do it, and they can come here for help if they need it. It may not be an issue, but you should also enable DMARC mitigations. For Mailman >= 2.1.18, in Privacy options... -> Sender filters, set dmarc_moderation_action to Munge From and dmarc_quarantine_moderation_action) to Yes. Older versions 2.1.16 and 2.1.17 you can set General Options from_is list to Munge From, but this requires setting ALLOW_FROM_IS_LIST to Yes in mm_cfg.py. This is also available in 2.1.18+, and will apply mitigations to all messages, not just ones publishing DMARC polocy reject or quarantine, This is freaking out a few of my users. I'm attaching a screenshot of the message and source code for the same message.?? Hopefully this list allows attachments... Not images, only attached messages, text and pgp ang pkcs7 signatures. -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
