From james at dorydesign.com Sat Jan 4 00:48:32 2020 From: james at dorydesign.com (Jim Dory) Date: Fri, 3 Jan 2020 20:48:32 -0900 Subject: [Mailman-Users] msg marked as spam 554 5.7.1 [P4] Message-ID: So I'm just a volunteer who doesn't understand much about email systems.. just rudimentary - and I am managing an email list for community announcements and trade, by subscription only. We have about 1500 subscribers. I have one problem that when a particular user (the city) sends an announcement, it tends to bounce hundreds of mainly one ISP's users.. that ISP being Alaska's GCI.com . Other users, say on hotmail, yahoo, etc.. don't get bounced. I manage the emails via gmail and lately I've been "locked out of gmail due to suspicious email activity" which is a pain in the rear. Also causes my host (Hawkhost) grief.. the overhead they dislike though they haven't complained lately. So I'm motivated to look into this a bit. Sometimes I do get this: host mx1.arandomserver.com [198.252.100.64] SMTP error from remote mail server after end of data: 550 Headers contain illegal BOM on my personal email from the same sender (city), but not sure that is same issue. The city usually includes a link to the city codes on a public webpage - perhaps that triggers GCI. I could post one of the headers in total but it is probably about 3 pages worth. Everything sort of looks ok to me except I notice this: BODY: Bayes spam probability is 0 to 1% [score: 0.0000] 0.0 RCVD_IN_DNSWL_BLOCKED RBL: ADMINISTRATOR NOTICE: The query to DNSWL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [34.212.96.103 listed in list.dnswl.org] -0.0 SPF_PASS SPF: sender matches SPF record 0.0 HTML_MESSAGE BODY: HTML included in message The link in the messages is https://www.codepublishing.com/AK/Nome/ . I can post more of the header if need be. Could it be that GCI needs to whitelist or something? thx, Jim From hansen at rc.org Sat Jan 4 20:47:45 2020 From: hansen at rc.org (Allan Hansen) Date: Sat, 4 Jan 2020 17:47:45 -0800 Subject: [Mailman-Users] MM3 startup issues Message-ID: <51806F2E-E5FC-4F1B-9193-7044E8E59E05@rc.org> After having MM3 installed, I?m trying to get it setup up correctly for my lists. I have a couple of issues at this point: a. The server was set up with the wrong domain name (our fault), so I had to add the ?correct? one. I had seen the command ?Add Domain? in the UI and thought that would do it, but Brian kindly sent me a list of additional instructions, which we then implemented. That made it possible to create a list in the new domain, subscribe people and post messages. However, messages are not archived. What extra step is needed to enable archiving? The instructions we received were these: How to setup an additional domain to the Mailman 3 server: ? Add the additional domain name to Django Sites and Mail domains via the Django admin panel. This will require superuser access. ? Make sure the list admin(s) of any list is registered with Django. ? Setup the new list domain in nginx (/etc/nginx/conf.d). You can copy and paste the existing record there to the new record. Just make sure you modify the server_name directive in the record to the new domain name. The record file name should be newdomainname.com.conf. This will need to be done via shell with sudo privileges. ? Test nginx configuratin (nginx -t) ? Reload nginx (nginx -s reload) ? Generate LetsEncrypt Cert (certbot --nginx -d newdomainname.com) Before doing this make sure the appropriate DNS records are setup pointing the new list domain to your Mailman 3 server otherwise this part will fail. ? Add the new list domain to /opt/mailman/mm/settings_local.py in the ALLOWED_HOSTS section. ? Add list domain to Postorius. ? Create the list in Postorius using the new list domain. b. When go to the server using the new domain (both before and after logging in), I see not just the lists I created in the new domain, but the lists created in the old domain. These lists of lists are domain specific and should not be listed together. That?s just IMHO, but not serious, as I will soon get rid of anything in the old domain. So feel free to ignore this one if this is intended, which I could see might be the case. c. I then moved on to the templates and added a template for the message text to send to new subscribers. That resulted in the following error message when I went in as moderator to approve of a new subscription: Something went wrong Mailman REST API not available. Please start Mailman core. Oh, and Happy New Year to all, Allan Hansen From mark at msapiro.net Sat Jan 4 22:16:33 2020 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 4 Jan 2020 19:16:33 -0800 Subject: [Mailman-Users] MM3 startup issues In-Reply-To: <51806F2E-E5FC-4F1B-9193-7044E8E59E05@rc.org> References: <51806F2E-E5FC-4F1B-9193-7044E8E59E05@rc.org> Message-ID: <7ddb62a8-5800-9ab2-c61a-cf9b65b3a861@msapiro.net> On 1/4/20 5:47 PM, Allan Hansen wrote: > > a. The server was set up with the wrong domain name (our fault), so I had to add the ?correct? one. I had seen the command ?Add Domain? in > the UI and thought that would do it, but Brian kindly sent me a list of additional instructions, which we then implemented. That made it possible to create a list in the new domain, subscribe people and post messages. However, messages are not archived. What extra step is needed to enable archiving? What are the setytings in Postorius -> Settings -> Archiving? > b. When go to the server using the new domain (both before and after logging in), I see not just the lists I created in the new domain, but the lists created in the old domain. These lists of lists are domain specific and should not be listed together. That?s just IMHO, but not serious, as I will soon get rid of anything in the old domain. So feel free to ignore this one if this is intended, which I could see might be the case. Set FILTER_VHOST = True in settings_local.py > c. I then moved on to the templates and added a template for the message text to send to new subscribers. That resulted in the following error message when I went in as moderator to approve of a new subscription: > > Something went wrong > Mailman REST API not available. Please start Mailman core. Postorius is unable to access core's REST API. Is Mailman running? If so, what's in /opt/mailman/mm/var/logs/mailmansuite.log or whatever it's called - defined as `filename` in the `file` handler in the LOGGING definition in settings(_local).py. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From turnbull.stephen.fw at u.tsukuba.ac.jp Sun Jan 5 04:56:01 2020 From: turnbull.stephen.fw at u.tsukuba.ac.jp (Stephen J. Turnbull) Date: Sun, 5 Jan 2020 18:56:01 +0900 Subject: [Mailman-Users] msg marked as spam 554 5.7.1 [P4] In-Reply-To: References: Message-ID: <24081.45745.493936.167226@turnbull.sk.tsukuba.ac.jp> Jim Dory writes: > I have one problem that when a particular user (the city) sends an > announcement, it tends to bounce hundreds of mainly one ISP's users.. that > ISP being Alaska's GCI.com . I assume you mean that the attempt to deliver to users at GCI bounce back to you? What we would like to see is the delivery service message from GCI which explains why the message is being refused. > Sometimes I do get this: host mx1.arandomserver.com [198.252.100.64] > SMTP error from remote mail server after end of data: > 550 Headers contain illegal BOM > on my personal email from the same sender (city), but not sure that is same > issue. I don't understand. You say it's personal mail *from the city*, but you're getting the bounce message? That should not happen; the bounce message should go to the city. > The city usually includes a link to the city codes on a public webpage - > perhaps that triggers GCI. Are you saying there's a link in the header? Those are common (eg, Mailman can be configured to put certain links in the header), and should not cause problems if correctly formed. Nothing in the content should cause any kind of bounce except a 552 "We don't like your mail for some reason" Administrative Denial (or perhaps another 55x response. > I could post one of the headers in total but it is probably about 3 pages > worth. That's nothing. Don't hesitate. It's much more annoying to have to go back and forth if you send incomplete headers. > Everything sort of looks ok to me except I notice this: > BODY: Bayes spam probability is 0 to 1% [score: 0.0000] 0.0 > RCVD_IN_DNSWL_BLOCKED RBL: ADMINISTRATOR NOTICE: The query to DNSWL was > blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block > for more information. [34.212.96.103 listed in list.dnswl.org] -0.0 > SPF_PASS SPF: sender matches SPF record 0.0 HTML_MESSAGE BODY: HTML > included in message The sentence about querying DNSWL is a bit weird, but I don't think it's a problem. That check was just skipped. The rest is perfectly normal and is not symptomatic of a problem. > The link in the messages is https://www.codepublishing.com/AK/Nome/ . That link is never going to cause a problem. > > I can post more of the header if need be. > > Could it be that GCI needs to whitelist or something? Not enough information. It sounds like either or both the city and GCI have difficulty with email since it's that particular combination, but which one is whack I can't tell without a look at the delivery status notice (bounce message) for the mass bounces. This is often in your mail server's log as well. Steve From james at dorydesign.com Sun Jan 5 13:48:09 2020 From: james at dorydesign.com (Jim Dory) Date: Sun, 5 Jan 2020 09:48:09 -0900 Subject: [Mailman-Users] msg marked as spam 554 5.7.1 [P4] In-Reply-To: <24081.45745.493936.167226@turnbull.sk.tsukuba.ac.jp> References: <24081.45745.493936.167226@turnbull.sk.tsukuba.ac.jp> Message-ID: On Sun, Jan 5, 2020 at 12:56 AM Stephen J. Turnbull < turnbull.stephen.fw at u.tsukuba.ac.jp> wrote: > Jim Dory writes: > > > > Sometimes I do get this: host mx1.arandomserver.com [198.252.100.64] > > SMTP error from remote mail server after end of data: > > 550 Headers contain illegal BOM > > on my personal email from the same sender (city), but not sure that is > same > > issue. > > I don't understand. You say it's personal mail *from the city*, but > you're getting the bounce message? That should not happen; the bounce > message should go to the city. > > > I don't think the city would see a bounce because the list accepted their message and a lot of subscribers would see it.. but it was rejected only by one or two other subscriber email providers. That is my understanding anyway, perhaps I'm wrong. I see the bounces as admin for the list. Isn't this proper behavior of the mailman software? It seems that people would complain (or ask about it) if they saw all the bounces caused by one of their messages and they never have. > > That's nothing. Don't hesitate. It's much more annoying to have to > go back and forth if you send incomplete headers. > > > > > > Could it be that GCI needs to whitelist or something? > > Not enough information. It sounds like either or both the city and > GCI have difficulty with email since it's that particular combination, > but which one is whack I can't tell without a look at the delivery > status notice (bounce message) for the mass bounces. This is often in > your mail server's log as well. > > > Steve, thanks very much for replying and looking at this. I realize now I didn't provide sufficient info and will in the future amend my ways. I'm going to contact GCI and see if I can get them to either whitelist or clean up a possible mis-configure in their system. Another kind gentlemen from this mailman list contacted me off-list with an offer to help - I sent him the complete header and reject message.. and he felt that there was nothing apparent to warrant an email provider to reject it. thanks, Jim From johnson at Pharmacy.Arizona.EDU Sun Jan 5 17:23:19 2020 From: johnson at Pharmacy.Arizona.EDU (Bruce Johnson) Date: Sun, 5 Jan 2020 22:23:19 +0000 Subject: [Mailman-Users] msg marked as spam 554 5.7.1 [P4] In-Reply-To: References: <24081.45745.493936.167226@turnbull.sk.tsukuba.ac.jp> Message-ID: <0DB24D4D-16D4-4302-A781-719C4362FE63@pharmacy.arizona.edu> I was the off-list person... This was the actual bounce error from one of the offending messages: A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: [redacted]@alaskan.com host inbound.gci.net [69.168.106.130] SMTP error from remote mail server after end of data: 554 5.7.1 [P4] Message blocked due to spam content in the message. It?s being bounced by some spam rule on CGI.net; it?s a global one so it?s something in their configuration, since none of the other providers are bouncing it, it?s not really recognizable as spam. (or one user reported it as spam and they took the lazy way out and blocked all the emails from that list address?we have one user who routinely marks email from one list on our domain as ?spam??then complains that he?s not getting emails from the list?sigh ) > On Jan 5, 2020, at 11:48 AM, Jim Dory wrote: > > On Sun, Jan 5, 2020 at 12:56 AM Stephen J. Turnbull < > turnbull.stephen.fw at u.tsukuba.ac.jp> wrote: > >> Jim Dory writes: >> >> >>> Sometimes I do get this: host mx1.arandomserver.com [198.252.100.64] >>> SMTP error from remote mail server after end of data: >>> 550 Headers contain illegal BOM >>> on my personal email from the same sender (city), but not sure that is >> same >>> issue. >> >> I don't understand. You say it's personal mail *from the city*, but >> you're getting the bounce message? That should not happen; the bounce >> message should go to the city. >> >> >> > > I don't think the city would see a bounce because the list accepted their > message and a lot of subscribers would see it.. but it was rejected only by > one or two other subscriber email providers. That is my understanding > anyway, perhaps I'm wrong. I see the bounces as admin for the list. Isn't > this proper behavior of the mailman software? It seems that people would > complain (or ask about it) if they saw all the bounces caused by one of > their messages and they never have. > > > >> >> That's nothing. Don't hesitate. It's much more annoying to have to >> go back and forth if you send incomplete headers. >> >> >>> >>> Could it be that GCI needs to whitelist or something? >> >> Not enough information. It sounds like either or both the city and >> GCI have difficulty with email since it's that particular combination, >> but which one is whack I can't tell without a look at the delivery >> status notice (bounce message) for the mass bounces. This is often in >> your mail server's log as well. >> >> >> > Steve, thanks very much for replying and looking at this. I realize now I > didn't provide sufficient info and will in the future amend my ways. > > I'm going to contact GCI and see if I can get them to either whitelist or > clean up a possible mis-configure in their system. Another kind gentlemen > from this mailman list contacted me off-list with an offer to help - I sent > him the complete header and reject message.. and he felt that there was > nothing apparent to warrant an email provider to reject it. > > thanks, Jim > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at python.org > https://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > Unsubscribe: https://mail.python.org/mailman/options/mailman-users/johnson%40pharmacy.arizona.edu -- Bruce Johnson University of Arizona College of Pharmacy Information Technology Group Institutions do not have opinions, merely customs From jaybird at bluegrasspals.com Sun Jan 5 18:43:34 2020 From: jaybird at bluegrasspals.com (Jayson Smith) Date: Sun, 5 Jan 2020 18:43:34 -0500 Subject: [Mailman-Users] msg marked as spam 554 5.7.1 [P4] In-Reply-To: <0DB24D4D-16D4-4302-A781-719C4362FE63@pharmacy.arizona.edu> References: <24081.45745.493936.167226@turnbull.sk.tsukuba.ac.jp> <0DB24D4D-16D4-4302-A781-719C4362FE63@pharmacy.arizona.edu> Message-ID: Hi, I've seen this exact error before with various ISPs. I believe one of them is Centurytel. I assume what's happened is that several ISPs use a certain spam filtering service or app, and that filter is rejecting the messages for some unknown reason. If that's the case, the particular ISP in question probably won't have a clue what's going on. Hopefully they'll care enough to consult with the third-party filtering service. Jayson On 1/5/2020 5:23 PM, Bruce Johnson wrote: > I was the off-list person... > > This was the actual bounce error from one of the offending messages: > > A message that you sent could not be delivered to one or more of its > recipients. This is a permanent error. The following address(es) failed: > > > [redacted]@alaskan.com > > host > inbound.gci.net > [69.168.106.130] > SMTP error from remote mail server after end of data: > 554 5.7.1 [P4] Message blocked due to spam content in the message. > > It?s being bounced by some spam rule on CGI.net; it?s a global one so it?s something in their configuration, since none of the other providers are bouncing it, it?s not really recognizable as spam. > > (or one user reported it as spam and they took the lazy way out and blocked all the emails from that list address?we have one user who routinely marks email from one list on our domain as ?spam??then complains that he?s not getting emails from the list?sigh ) > > > >> On Jan 5, 2020, at 11:48 AM, Jim Dory wrote: >> >> On Sun, Jan 5, 2020 at 12:56 AM Stephen J. Turnbull < >> turnbull.stephen.fw at u.tsukuba.ac.jp> wrote: >> >>> Jim Dory writes: >>> >>> >>>> Sometimes I do get this: host mx1.arandomserver.com [198.252.100.64] >>>> SMTP error from remote mail server after end of data: >>>> 550 Headers contain illegal BOM >>>> on my personal email from the same sender (city), but not sure that is >>> same >>>> issue. >>> I don't understand. You say it's personal mail *from the city*, but >>> you're getting the bounce message? That should not happen; the bounce >>> message should go to the city. >>> >>> >>> >> I don't think the city would see a bounce because the list accepted their >> message and a lot of subscribers would see it.. but it was rejected only by >> one or two other subscriber email providers. That is my understanding >> anyway, perhaps I'm wrong. I see the bounces as admin for the list. Isn't >> this proper behavior of the mailman software? It seems that people would >> complain (or ask about it) if they saw all the bounces caused by one of >> their messages and they never have. >> >> >> >>> That's nothing. Don't hesitate. It's much more annoying to have to >>> go back and forth if you send incomplete headers. >>> >>> >>>> Could it be that GCI needs to whitelist or something? >>> Not enough information. It sounds like either or both the city and >>> GCI have difficulty with email since it's that particular combination, >>> but which one is whack I can't tell without a look at the delivery >>> status notice (bounce message) for the mass bounces. This is often in >>> your mail server's log as well. >>> >>> >>> >> Steve, thanks very much for replying and looking at this. I realize now I >> didn't provide sufficient info and will in the future amend my ways. >> >> I'm going to contact GCI and see if I can get them to either whitelist or >> clean up a possible mis-configure in their system. Another kind gentlemen >> from this mailman list contacted me off-list with an offer to help - I sent >> him the complete header and reject message.. and he felt that there was >> nothing apparent to warrant an email provider to reject it. >> >> thanks, Jim >> ------------------------------------------------------ >> Mailman-Users mailing list Mailman-Users at python.org >> https://mail.python.org/mailman/listinfo/mailman-users >> Mailman FAQ: http://wiki.list.org/x/AgA3 >> Security Policy: http://wiki.list.org/x/QIA9 >> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ >> Unsubscribe: https://mail.python.org/mailman/options/mailman-users/johnson%40pharmacy.arizona.edu From turnbull.stephen.fw at u.tsukuba.ac.jp Sun Jan 5 23:21:51 2020 From: turnbull.stephen.fw at u.tsukuba.ac.jp (Stephen J. Turnbull) Date: Mon, 6 Jan 2020 13:21:51 +0900 Subject: [Mailman-Users] msg marked as spam 554 5.7.1 [P4] In-Reply-To: <0DB24D4D-16D4-4302-A781-719C4362FE63@pharmacy.arizona.edu> References: <24081.45745.493936.167226@turnbull.sk.tsukuba.ac.jp> <0DB24D4D-16D4-4302-A781-719C4362FE63@pharmacy.arizona.edu> Message-ID: <24082.46559.647775.43736@turnbull.sk.tsukuba.ac.jp> Thanks for the update, Bruce! Bruce Johnson writes: > This was the actual bounce error from one of the offending messages: > > A message that you sent could not be delivered to one or more of its > recipients. This is a permanent error. The following address(es) failed: > > > [redacted]@alaskan.com > > host > inbound.gci.net > [69.168.106.130] > SMTP error from remote mail server after end of data: > 554 5.7.1 [P4] Message blocked due to spam content in the message. Note to OP: This is different from the message mentioned by you ("550 illegal Unicode BOM in header" or similar). I'd need to see that message's full header to debug that fully, but it sounds like GCI is generally not doing a great job here. > It?s being bounced by some spam rule on CGI.net; it?s a global one > so it?s something in their configuration, since none of the other > providers are bouncing it, it?s not really recognizable as spam. Bruce, Looking at your "from" address, I wonder did your message mention pharmaceuticals, conditions, or treatments by name? I know that for a long time my personal filter had an enormous variety of spellings of erectile dysfunction treatments. :-/ Nevertheless, I would say very probably GCI is responsible. Recipient ISPs are very hard problems, as such ISPs generally don't give anywhere near as many damns about lost mail (which they invariably blame on senders and/or mailing lists) as they do about any uptick in spam. The list should start by opening an issue with GCI, if necessary by mail to postmaster. If they give you "you're not a customer" BS, report that to their users, too (see below). At the same time, I would inform the sender of the mail that's systematically misclassified and ask *them* to open an issue with GCI, and to inform you of any response. Since they're a governmental body according to the OP, they may have more pull than a mailing list with a "mere" X,000 members. If they don't get a timely, responsive answer, or get "not a customer", send a post to the list saying "GCI-based subscribers *are provably* losing certain kinds of list mail on a regular basis, and since it's an automated filter, *may* be losing non-list mail as well. GCI is not cooperating in resolving the problem." Cc: the help desk, or if necessary, postmaster at gci. If that gets no action, the next step would be to suggest well-behaved competitors to GCI. }:^} (If postmaster@ bounces, this is the first step. ;-) I agree with Jayson Smith that it's quite possible that GCI is not running its own spam filters, but that's too bad for them. postmaster at GCI is responsible for the health of its mail system by definition, and that includes getting timely action from outsourced service vendors. I don't think there's much the list can do about this (short of unsubscribing GCI addresses, which is not recommended unless required by law or applicable regulation ;-), as both the sender and the recipients' providers are effectively sovereign in this area, and the message content is apparently innocuous. Steve From hansen at rc.org Mon Jan 6 02:51:01 2020 From: hansen at rc.org (Allan Hansen) Date: Sun, 5 Jan 2020 23:51:01 -0800 Subject: [Mailman-Users] Mailman-Users Digest, Vol 191, Issue 3 In-Reply-To: References: Message-ID: Thanks again, Mark! My responses below. > On 1/4/20 5:47 PM, Allan Hansen wrote: >> >> a. The server was set up with the wrong domain name (our fault), so I had to add the ?correct? one. I had seen the command ?Add Domain? in >> the UI and thought that would do it, but Brian kindly sent me a list of additional instructions, which we then implemented. That made it possible to create a list in the new domain, subscribe people and post messages. However, messages are not archived. What extra step is needed to enable archiving? > > > What are the setytings in Postorius -> Settings -> Archiving? Archive policy: Private archives Archive archivers: hyperkitty, prototype > > >> b. When go to the server using the new domain (both before and after logging in), I see not just the lists I created in the new domain, but the lists created in the old domain. These lists of lists are domain specific and should not be listed together. That?s just IMHO, but not serious, as I will soon get rid of anything in the old domain. So feel free to ignore this one if this is intended, which I could see might be the case. > > > Set > > FILTER_VHOST = True > > in settings_local.py > Yes, Brian told me to do the same. This is the what I wrote back: hansen at rccrmail:/opt/mailman/mm$ sudo vi settings.py Edited the setting to: # Only display mailing-lists from the same virtual host as the webserver FILTER_VHOST = True Then Brian told me to restart qcluster: hansen at rccrmail:/opt/mailman/mm$ sudo systemctl restart qcluster I then logged in, but the same lists are showing. It either takes the system a long time to reset or it has ignored the setting. Just tried it again, and the lists are all showing. Do I need to manually recompile the file? > >> c. I then moved on to the templates and added a template for the message text to send to new subscribers. That resulted in the following error message when I went in as moderator to approve of a new subscription: >> >> Something went wrong >> Mailman REST API not available. Please start Mailman core. > > > Postorius is unable to access core's REST API. Is Mailman running? Well, I was able to post to the lists, so I assume it is. Listing at processes, I see a bunch of postgres, python3, nginx, django-adminp but nothing explicitly with a ?mailman? string. > If so, what's in /opt/mailman/mm/var/logs/mailmansuite.log or whatever it's > called - defined as `filename` in the `file` handler in the LOGGING > definition in settings(_local).py. hansen at rccrmail:/opt/mailman/mm/logs$ tail -f mailmansuite.log return Site.objects.get_current(request) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sites/models.py", line 60, in get_current return self._get_site_by_request(request) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sites/models.py", line 45, in _get_site_by_request SITE_CACHE[domain] = self.get(domain__iexact=domain) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/db/models/manager.py", line 82, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/db/models/query.py", line 408, in get self.model._meta.object_name django.contrib.sites.models.Site.DoesNotExist: Site matching query does not exist. [ABH] At this point I click to accept a subsription request: ERROR 2020-01-06 07:32:41,439 699 postorius.middleware Mailman REST API not available Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py", line 672, in urlopen chunked=chunked, File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py", line 421, in _make_request six.raise_from(e, None) File "", line 3, in raise_from File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py", line 416, in _make_request httplib_response = conn.getresponse() File "/usr/lib/python3.7/http/client.py", line 1321, in getresponse response.begin() File "/usr/lib/python3.7/http/client.py", line 296, in begin version, status, reason = self._read_status() File "/usr/lib/python3.7/http/client.py", line 265, in _read_status raise RemoteDisconnected("Remote end closed connection without" http.client.RemoteDisconnected: Remote end closed connection without response So yes, the REST API is not there. How can I get it going? Before we added the new domain, I was able to accept subscription requests to the previous domain?s lists. No more. Yours, Allan > > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan From james at dorydesign.com Mon Jan 6 00:20:54 2020 From: james at dorydesign.com (Jim Dory) Date: Sun, 5 Jan 2020 20:20:54 -0900 Subject: [Mailman-Users] msg marked as spam 554 5.7.1 [P4] In-Reply-To: <24082.46559.647775.43736@turnbull.sk.tsukuba.ac.jp> References: <24081.45745.493936.167226@turnbull.sk.tsukuba.ac.jp> <0DB24D4D-16D4-4302-A781-719C4362FE63@pharmacy.arizona.edu> <24082.46559.647775.43736@turnbull.sk.tsukuba.ac.jp> Message-ID: On Sun, Jan 5, 2020 at 7:21 PM Stephen J. Turnbull < turnbull.stephen.fw at u.tsukuba.ac.jp> wrote: > > I'd need to see that > message's full header to debug that fully, but it sounds like GCI is > generally not doing a great job here. > > > Ok - just for curiosity sake, here is full header. I've 'ed out names. But Bruce and Stephen are probably correct in that I need to contact GCI. I will also put out a request to subscribers of our list to ask that people don't mark these messages as spam. I have done this in the past probably to no avail.. what helps there is getting on email providers' feedback loops where I've been able to solve yahoo.com user problems. But I haven't found one with GCI. For clarity, I have my email address set as admin that is my own domain hosted on Hawkhost. It is POP3'd to gmail, so that's the first part of the header where gmail gets involved. The list is nome-announce at nomekennelclub.com (the kennelclub just lets us use their domain), also on Hawkhost, who uses arandomserver.com as their DNS server, I believe. Alaskan.com is a GCI.net domain, as well as a few others. GCI is the one blocking these messages from the city to its subscribers. The city domain is nomealaska.org . Delivered-To: @gmail.com Received: by 2002:ac8:4912:0:0:0:0:0 with SMTP id e18csp19003587qtq; Fri, 3 Jan 2020 11:56:18 -0800 (PST) X-Google-Smtp-Source: APXvYqwk2NggdPGoR1J3DEcdLZMVhDU2UAjEn8UBHjRZFns/bzyDwsAyaLWiml3ZpNgU9VgmRWhOKdATxXI= X-Received: by 2002:ac8:d86:: with SMTP id s6mr59784558qti.237.1578081378216; Fri, 03 Jan 2020 11:56:18 -0800 (PST) Authentication-Results: mx.google.com; spf=neutral (google.com: 198.252.100.64 is neither permitted nor denied by best guess record for domain of mailman-bounces at cloud.nomekennelclub.com.cloud.nomekennelclub.com) smtp.mailfrom= mailman-bounces at cloud.nomekennelclub.com.cloud.nomekennelclub.com Received-SPF: neutral (google.com: 198.252.100.64 is neither permitted nor denied by best guess record for domain of mailman-bounces at cloud.nomekennelclub.com.cloud.nomekennelclub.com) client-ip=198.252.100.64; Received: by 2002:ac8:7104:: with POP3 id z4mf28611506qto.6; Fri, 03 Jan 2020 11:56:18 -0800 (PST) X-Gmail-Fetch-Info: james@.com 1 mail..com 110 james@.com Return-Path: < mailman-bounces at cloud.nomekennelclub.com.cloud.nomekennelclub.com> Delivered-To: james@.com Received: from lax003.hawkhost.com by lax003.hawkhost.com with LMTP id eJ7WCJSYD15vFQAAva6gig (envelope-from < mailman-bounces at cloud.nomekennelclub.com.cloud.nomekennelclub.com>) for .com>; Fri, 03 Jan 2020 11:40:04 -0800 Return-path: < mailman-bounces at cloud.nomekennelclub.com.cloud.nomekennelclub.com> Envelope-to: james@.com Delivery-date: Fri, 03 Jan 2020 11:40:04 -0800 Received: from se001.arandomserver.com ([198.252.100.64]:48764) by lax003.hawkhost.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from < mailman-bounces at cloud.nomekennelclub.com.cloud.nomekennelclub.com>) id 1inSnj-0001sJ-TR for james@.com; Fri, 03 Jan 2020 11:40:04 -0800 Received: from cloud.nomekennelclub.com ([198.252.100.6]) by se001.arandomserver.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from < mailman-bounces at cloud.nomekennelclub.com.cloud.nomekennelclub.com>) id 1inSni-000Hqn-Aw for james@.com; Fri, 03 Jan 2020 14:40:03 -0500 Received: from [127.0.0.1] (port=35254 helo= cloud.nomekennelclub.com.cloud.nomekennelclub.com) by cloud.nomekennelclub.com with esmtp (Exim 4.92) (envelope-from < mailman-bounces at cloud.nomekennelclub.com.cloud.nomekennelclub.com>) id 1inSnh-000IHZ-Gi; Fri, 03 Jan 2020 19:40:01 +0000 Received: from [127.0.0.1] (port=35252 helo= cloud.nomekennelclub.com.cloud.nomekennelclub.com) by cloud.nomekennelclub.com with esmtp (Exim 4.92) (envelope-from < nome-announce-bounces at nomekennelclub.com>) id 1inSng-000IHH-Fe for nome-announce-owner at nomekennelclub.com; Fri, 03 Jan 2020 19:40:00 +0000 Subject: Bounce action notification From: mailman at nomekennelclub.com To: nome-announce-owner at nomekennelclub.com MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7118919187349444018==" Message-ID: < mailman.423.1578080399.54331.nome-announce_nomekennelclub.com at nomekennelclub.com > Date: Fri, 03 Jan 2020 19:39:59 +0000 Precedence: list X-BeenThere: nome-announce at nomekennelclub.com X-Mailman-Version: 2.1.29 List-Id: Trade and Community Announcements X-List-Administrivia: yes Errors-To: mailman-bounces at cloud.nomekennelclub.com.cloud.nomekennelclub.com Sender: Nome-announce < mailman-bounces at cloud.nomekennelclub.com.cloud.nomekennelclub.com> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cloud.nomekennelclub.com X-AntiAbuse: Original Domain - .com X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - cloud.nomekennelclub.com.cloud.nomekennelclub.com X-Get-Message-Sender-Via: cloud.nomekennelclub.com: acl_c_authenticated_local_user: mailman/mailman X-Authenticated-Sender: cloud.nomekennelclub.com: mailman at cloud.nomekennelclub.com.cloud.nomekennelclub.com X-Source: X-Source-Args: X-Source-Dir: Authentication-Results: se001.arandomserver.com; dmarc=pass header.from= nomekennelclub.com X-Filter-Label: newsletter X-SpamExperts-Class: whitelisted X-SpamExperts-Evidence: sender X-Recommended-Action: accept X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0c2Pj46HODYmpAMVAv0J1pOpSDasLI4SayDByyq9LIhV6obGWHmXteYh AHmP4j2Eq5/d0eQJp4TxpTJf6svkibVP3NiT+4ZMbYPeVBF9/B6zInhaVKtf4ZQXxYmGiNzppW2n S6ZASPhDAtQT2fAqIj34CvjpTc5F8owxokd2bs1RcciY2z4hq7SqXAJrAGow5IPAgTtUp75uqlx0 KezvZHUDd+1wd2dHPCUV5YnPqAejHOkshxy4q0pAdH6oJuD11nYrj/NBMmAdcWAnSnLdmEBMC2ZI 2FFWYgXHqY5UJ4/W0yG3jX4dycteGfaWmIWC7DXiCAZcOgRiwuziOrY9Exilk6iLOvzJGCYfseu8 gWUSPCy6JTT+N7cWHQUbdijqdlH7cSh97d6E5oWj68zsWkQu1sXqDo9GKNBkthSl+IlOfogYpg/X B9ovSXzPpGJShj5HONSWRnLaBIvLEQNgbZQZrjjiNtMpY3Y+i/EM3bbRnjZwqkIZ9u6PTog2DRVg vwishGoxFT89bFD2VBjZPnfNBz6C+Mu+hGpwr7PBqmKn7FPKyyngvSmVQaKBrHzPLqesaGON71i/ lzkSA6vCrkgbsiz5qmSISl6qm4DF/bhUC7Ebc2qmp7YiQCEcumyY6kDDzPtXhTYfsGfK+urci+aW O/SZjV84b961KrpPFiB1Mk6EwUJFn55dCacfSJsXodsHRkKKm0/eI/cJVtBzgMInPBGJEqj0P7co Lz3x16q25OwVDz9YWiSIE6UlBHmyBOTxrBhSQ8FaF+kEO3mnzYL2b+yLsLqYHF/fxqeBk+sDLfQm PWfG5h1/k88svc3a1myDoWoANh/p7ZbqfN9Ql3sccBIk1Sag4dKiqCrF8eZZaqiqynGMtha2fjb3 Ot4nDQQag0f4dbi1L9Bosy7v/PlO/LqcegxMSqa2PvYPtY7VZm8w9ixZkv58RakcfXWBTwBZnlU+ Jl6ES1IphMuosSg13G5DPdkqJzeEjrfpxwv2Oi+G2wty43cRSQ8qLbbzwJ6AzCu3B2h2CCsdky5f 0co= X-Report-Abuse-To: spam at se001.arandomserver.com --===============7118919187349444018== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit This is a Mailman mailing list bounce action notice: List: Nome-announce Member: @alaskan.com Action: Subscription bounce score incremented. Reason: Excessive or fatal bounces. The triggering bounce notice is attached below. Questions? Contact the Mailman site administrator at mailman at nomekennelclub.com. --===============7118919187349444018== Content-Type: message/rfc822 MIME-Version: 1.0 Received: from mailnull by cloud.nomekennelclub.com with local (Exim 4.92) id 1inSnf-000IH9-Cx for nome-announce-bounces at nomekennelclub.com; Fri, 03 Jan 2020 19:39:59 +0000 X-Failed-Recipients: @alaskan.com Auto-Submitted: auto-replied From: Mail Delivery System To: nome-announce-bounces at nomekennelclub.com Content-Type: multipart/report; report-type=delivery-status; boundary=1578080399-eximdsn-114499101 MIME-Version: 1.0 Subject: Mail delivery failed: returning message to sender Message-Id: Date: Fri, 03 Jan 2020 19:39:59 +0000 --1578080399-eximdsn-114499101 Content-type: text/plain; charset=us-ascii This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: @alaskan.com host inbound.gci.net [69.168.106.130] SMTP error from remote mail server after end of data: 554 5.7.1 [P4] Message blocked due to spam content in the message. --1578080399-eximdsn-114499101 Content-type: message/delivery-status --1578080399-eximdsn-114499101 Content-type: message/rfc822 Return-path: Received: from [127.0.0.1] (port=35150 helo= cloud.nomekennelclub.com.cloud.nomekennelclub.com) by cloud.nomekennelclub.com with esmtp (Exim 4.92) (envelope-from < nome-announce-bounces at nomekennelclub.com>) id 1inSnT-000IG1-8h; Fri, 03 Jan 2020 19:39:47 +0000 Received: from se001.arandomserver.com ([198.252.100.64]:49018) by cloud.nomekennelclub.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <@nomealaska.org>) id 1inSnR-000IFu-Md for nome-announce at nomekennelclub.com; Fri, 03 Jan 2020 19:39:46 +0000 Received: from mail.delivery-4-us-west-2.prod.hydra.sophos.com ([34.212.96.103]) by se001.arandomserver.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from <@nomealaska.org>) id 1inSnQ-000HiL-BI for nome-announce at nomekennelclub.com; Fri, 03 Jan 2020 14:39:45 -0500 Received: from ip-172-17-2-162.us-west-2.compute.internal (ip-172-17-2-162.us-west-2.compute.internal [127.0.0.1]) by mail.delivery-4-us-west-2.prod.hydra.sophos.com (Postfix) with ESMTP id 47qFbg17WjzWf14 for ; Fri, 3 Jan 2020 19:39:43 +0000 (UTC) X-Sophos-Email-ID: 093ea574cb7a4339800d1e39f9c94899 Received: from mail.nomealaska.org (unknown [67.59.108.41]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by relay-us-west-2.prod.hydra.sophos.com (Postfix) with ESMTPS id 47qFbc4ngrznTWV for ; Fri, 3 Jan 2020 19:39:40 +0000 (UTC) Received: from OSBORN1.cn.lan ([::1]) by Osborn1.cn.lan ([::1]) with mapi id 14.03.0468.000; Fri, 3 Jan 2020 10:39:39 -0900 To: Nome Announce Thread-Topic: Community Benefits Share Proposals Due January 9th Thread-Index: AdXCbYZdlZq+N0FNTSa6EYBLNqw8LQ== Date: Fri, 3 Jan 2020 19:39:38 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.199.1.123] MIME-Version: 1.0 X-LASED-Pver: 0000002 X-Sophos-Email: [us-west-2] Antispam-Engine: 3.4.1, AntispamData: 2020.1.3.191517 X-LASED-SpamProbabilty: 0.081286 X-LASED-Hits: BODYTEXTH_SIZE_10000_LESS 0.000000, BODYTEXTH_SIZE_3000_MORE 0.000000, BODYTEXTP_SIZE_3000_LESS 0.000000, BODY_SIZE_5000_5999 0.000000, BODY_SIZE_7000_LESS 0.000000, HREF_LABEL_TEXT_ONLY 0.000000, HTML_70_90 0.100000, KNOWN_MSGID 0.000000, OUTBOUND 0.000000, OUTBOUND_SOPHOS 0.000000, RDNS_GENERIC_POOLED 0.000000, RDNS_SUSP_GENERIC 0.000000, SUPERLONG_LINE 0.050000, WEBMAIL_SOURCE 0.000000, WEBMAIL_XOIP 0.000000, WEBMAIL_X_IP_HDR 0.000000, __ANY_URI 0.000000, __BODY_NO_MAILTO 0.000000, __BODY_TEXT_X4 0.000000, __CP_URI_IN_BODY 0.000000, __CT 0.000000, __CTYPE_HAS_BOUNDARY 0.000000, __CTYPE_MULTIPART 0.000000, __CTYPE_MULTIPART_ALT 0.000000, __HAS_FROM 0.000000, __HAS_HTML 0.000000, __HAS_MSGID 0.000000, __HAS_XOIP 0.000000, __HREF_LABEL_TEXT 0.000000, __HREF_LABEL_URI 0.000000, __HTML_AHREF_TAG 0.000000, __HTML_TAG_DIV 0.000000, __HTTPS_URI 0.000000, __IMS_MSGID 0.000000, __MIME_HTML 0.000000, __MIME_TEXT_H 0.000000, __MIME_TEXT_H1 0.000000, __MIME_TEXT_H2 0.000000, __MIME_TEXT_P 0.000000, __MIME_TEXT_P1 0.000000, __MIME_TEXT_P2 0.000000, __MIME_VERSION 0.000000, __MULTIPLE_URI_HTML 0.000000, __MULTIPLE_URI_TEXT 0.000000, __SANE_MSGID 0.000000, __STYLE_RATWARE_NEG 0.000000, __STYLE_TAG 0.000000, __SUBJ_ALPHA_END 0.000000, __TAG_EXISTS_HTML 0.000000, __TO_MALFORMED_2 0.000000, __TO_NAME 0.000000, __TO_NAME_DIFF_FROM_ACC 0.000000, __TO_REAL_NAMES 0.000000, __URI_IN_BODY 0.000000, __URI_NOT_IMG 0.000000, __URI_NO_MAILTO 0.000000, __URI_NS 0.000000, __URI_WITHOUT_PATH 0.000000, __URI_WITH_PATH 0.000000 X-LASED-Authed: 1 X-LASED-Spam: NonSpam Received-SPF: pass (se001.arandomserver.com: domain of nomealaska.org designates 34.212.96.103 as permitted sender) client-ip=34.212.96.103; envelope-from=@nomealaska.org; helo= mail.delivery-4-us-west-2.prod.hydra.sophos.com; X-SPF-Result: se001.arandomserver.com: domain of nomealaska.org designates 34.212.96.103 as permitted sender Authentication-Results: se001.arandomserver.com; dmarc=pass header.from= nomealaska.org Authentication-Results: arandomserver.com; spf=pass smtp.mailfrom=@ nomealaska.org X-SpamExperts-Class: whitelisted X-SpamExperts-Evidence: recipient X-Recommended-Action: accept X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0c2Pj46HODYmpAMVAv0J1pOpSDasLI4SayDByyq9LIhVz4430uhYEAks X1w7WrWJIbAzHTGDSgSjQibbuaLsHgQfIHNbbhu5Jo+JL+C3bIUp0qRiSaRjfl4miP6LoQ4WjdKu nWXPO9t8lla9EjtrBMQdshjed0ulRpFkgAewkZiS5qKmVilAhlIqutZW2YLmn2a5oeSOtBki+F5I niDEug7X8GBK2+FCvMRX/exKBeIM9UHslcVUQPXc7RxsFltix+/Xn0pY/wWW7xfEbTwPHIgb8HFM 0h0hSAzrBBvn4GAtQfM9+qCEAyQExvyKY4W3iNgF9feD4yS5QvbyIp8rc3wgtdfpUoTshHiwMYu5 p1EI2VFtzUnBgJnEoLqjHcvWPWr9MqwvBg3kVh6skm3bYMFutRPMd4ie25IhJYnEjdNZ/8tAUFWW CkYm3LxAu7IzZJS8NstuqK+uxo87Hos9CiJIj47XQhA/8/ezXvaI7PEoPd0rEuGjFyZoidhtHm+W oT3uFOguAjnmORAgpq0OUrCzCjBSaSJjQlB2l/TAO94yybxQmwA+8NxVIq0MJiSKg9jlDHh8k6TT dHl8m1/8O/8sbUFIE3GR+VmWiSaV6wW6uss4LY88kOm6pUVzg5JaInDNwnqcC4drj2M7j5mMJvsB IkUL/j1Y48GvmeURQjjE1tBzCVvl8dH0j7GWn/qD6plCwXRq+WA468hSYTf7abBoGGIOJNjaglHb 6GMpHiXt/wc1v/QUNTHjXTcKDVfEEkStKzRfejKhNzyP+juq6XEgRrbXfWxmRS1HBwy3RcsTHxV+ fpNOPuJs4tyjllYviRRA5tACfY8moSOqVevk8OCcTD53rSwSTIedTYkUaByAjS280r/O32VBX9Mk 2gw+m5oiu8eNlY3cwoWTHujvw4kpjSRxYDnqEE9xgrMnp9w/n5DgwlbrHOL055PTfStjkEJ4KU+6 OgHFhvdX/qVI+vy5cphnkf+EuIHDfh+Krh33bW4kjbOXAqIuk+RgRq1OB/7ZrX6ecBRcEwpbz0rS MrTeNHk15VolAGHS5rCXQKDybV9zdb1vHXfXDHeWzX7dVt/I6s7aah4jjyh8hwRvEUc= X-Report-Abuse-To: spam at se001.arandomserver.com X-Spam-Status: No, score=-1.9 X-Spam-Score: -18 X-Spam-Bar: - X-Ham-Report: Spam detection software, running on the system " cloud.nomekennelclub.com", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see root\@localhost for details. Content preview: The Nome City Council is soliciting funding proposals for the 2019 NSEDC community benefits share. Proposals received will be presented to the City Council at a work session at 5:00 PM on Monday Janua [...] Content analysis details: (-1.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] 0.0 RCVD_IN_DNSWL_BLOCKED RBL: ADMINISTRATOR NOTICE: The query to DNSWL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [34.212.96.103 listed in list.dnswl.org] -0.0 SPF_PASS SPF: sender matches SPF record 0.0 HTML_MESSAGE BODY: HTML included in message X-Spam-Flag: NO Subject: [NA] Community Benefits Share Proposals Due January 9th X-BeenThere: nome-announce at nomekennelclub.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Trade and Community Announcements List-Unsubscribe: < http://nomekennelclub.com/mailman/options/nome-announce_nomekennelclub.com>, List-Archive: < http://nomekennelclub.com/mailman/private/nome-announce_nomekennelclub.com/> List-Post: List-Help: List-Subscribe: < http://nomekennelclub.com/mailman/listinfo/nome-announce_nomekennelclub.com>, From: Bryant via Nome-announce Reply-To: Bryant <@nomealaska.org> Content-Type: multipart/mixed; boundary="===============3120893443203709838==" Errors-To: nome-announce-bounces at nomekennelclub.com Sender: Nome-announce --===============3120893443203709838== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_D28717464A42A944B7857AC27E292E35BD4A5826Osborn1cnlan_" --_000_D28717464A42A944B7857AC27E292E35BD4A5826Osborn1cnlan_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable The Nome City Council is soliciting funding proposals for the 2019 NSEDC co= mmunity benefits share. Proposals received will be presented to the City Co= uncil at a work session at 5:00 PM on Monday January 13th. Applicants will = have a chance to present their proposals and answer questions during the wo= rk session. Please include a detailed narrative describing the proposed use of the fund= s requested and a budget detailing how the funds will be spent. Proposals are due at the City Clerk's Office by the close of business on Th= ursday January 9, 2020. Please contact the Clerk's Office at 443-6663 with any questions. Bryant City Clerk (907) 443-6663 www.nomealaska.org Nome Code of Ordinances available at: https://www.codepublishing.com/AK/Nome/ --_000_D28717464A42A944B7857AC27E292E35BD4A5826Osborn1cnlan_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Th= e Nome City Council is soliciting funding proposals for the 2019 NSEDC community benefits share. Proposals received will be pres= ented to the City Council at a work session at 5:00 PM on Monday January 13= th. Applicants will have a chance to present their proposals and= answer questions during the work session.

Pl= ease include a detailed narrative describing the proposed use of the funds = requested and a budget detailing how the funds will be spent.

Proposals are due at the City Clerk’s Office by the close of business on Thursday January 9, 2020.

Please contact the = Clerk’s Office at 443-6663 with any questions.

 

 

 

Bryant

City Clerk

(907) 443-6663

 

www.nomealask= a.org

Nome Code of Ordinances available at:

= https://www.codepublishing.com/AK/Nome/

 

--_000_D28717464A42A944B7857AC27E292E35BD4A5826Osborn1cnlan_-- --===============3120893443203709838== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Nome-announce mailing list Nome-announce at nomekennelclub.com UNSUBSCRIBE, user settings, archives, and UNSUBSCRIBE here: http://nomekennelclub.com/mailman/listinfo/nome-announce_nomekennelclub.com --===============3120893443203709838==-- --1578080399-eximdsn-114499101-- --===============7118919187349444018==-- From mark at msapiro.net Mon Jan 6 13:02:03 2020 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 6 Jan 2020 10:02:03 -0800 Subject: [Mailman-Users] MM3 startup issues In-Reply-To: References: Message-ID: <178e6ba3-186e-19e4-344e-0b4be85864ad@msapiro.net> Restoring original Subject:, and doesn't this thread belong on mailman-users at msailman3.org - CCing there. On 1/5/20 11:51 PM, Allan Hansen wrote: > > Thanks again, Mark! > My responses below. > >> On 1/4/20 5:47 PM, Allan Hansen wrote: >>> >>> a. The server was set up with the wrong domain name (our fault), so I had to add the ?correct? one. I had seen the command ?Add Domain? in >>> the UI and thought that would do it, but Brian kindly sent me a list of additional instructions, which we then implemented. That made it possible to create a list in the new domain, subscribe people and post messages. However, messages are not archived. What extra step is needed to enable archiving? >> >> >> What are the setytings in Postorius -> Settings -> Archiving? > > Archive policy: Private archives > Archive archivers: hyperkitty, prototype Are the messages in Mailman's var/archives/prototype/LIST at DOMAIN/new directory? Are there messages in Mailman's var/archives/hyperkitty/spool/ directory? What's the setting for base_url in mailman-hyperkitty.cfg? Are there any errors in var/logs/mailman.log? >>> b. When go to the server using the new domain (both before and after logging in), I see not just the lists I created in the new domain, but the lists created in the old domain. These lists of lists are domain specific and should not be listed together. That?s just IMHO, but not serious, as I will soon get rid of anything in the old domain. So feel free to ignore this one if this is intended, which I could see might be the case. >> >> >> Set >> >> FILTER_VHOST = True >> >> in settings_local.py >> > > Yes, Brian told me to do the same. This is the what I wrote back: > > hansen at rccrmail:/opt/mailman/mm$ sudo vi settings.py > > Edited the setting to: > # Only display mailing-lists from the same virtual host as the webserver > FILTER_VHOST = True You shouldn't edit settings.py. You should override the setting by putting it in settings_local.py. > Then Brian told me to restart qcluster: > hansen at rccrmail:/opt/mailman/mm$ sudo systemctl restart qcluster qcluster is not what you need to restart. You need to restart whatever is supporting the wsgi interface to Django. This may be uwsgi or gunicorn or ??. Whatever it is, that's what needs to be restarted. > I then logged in, but the same lists are showing. It either takes the system a long time to reset or it has ignored the > setting. > Just tried it again, and the lists are all showing. Do I need to manually recompile the file? > >> >>> c. I then moved on to the templates and added a template for the message text to send to new subscribers. That resulted in the following error message when I went in as moderator to approve of a new subscription: >>> >>> Something went wrong >>> Mailman REST API not available. Please start Mailman core. >> >> >> Postorius is unable to access core's REST API. Is Mailman running? > > Well, I was able to post to the lists, so I assume it is. Listing at processes, I see a bunch of postgres, python3, nginx, django-adminp but > nothing explicitly with a ?mailman? string. If you do `ps ax|grep runner=`, what do you see? If you don't see at least three processes with `--runner=rest:0:1`, stop Mailman and start Mailman. >> If so, what's in /opt/mailman/mm/var/logs/mailmansuite.log or whatever it's >> called - defined as `filename` in the `file` handler in the LOGGING >> definition in settings(_local).py. > > hansen at rccrmail:/opt/mailman/mm/logs$ tail -f mailmansuite.log > return Site.objects.get_current(request) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sites/models.py", line 60, in get_current > return self._get_site_by_request(request) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sites/models.py", line 45, in _get_site_by_request > SITE_CACHE[domain] = self.get(domain__iexact=domain) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/db/models/manager.py", line 82, in manager_method > return getattr(self.get_queryset(), name)(*args, **kwargs) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/db/models/query.py", line 408, in get > self.model._meta.object_name > django.contrib.sites.models.Site.DoesNotExist: Site matching query does not exist. This is because of the domain change. In settings(_local).py you have a setting for SITE_ID. Possibly, setting that in settings_local.py to a value one greater that the current setting will do. To be certain of the correct value, you need to look at the django_site table in mailman's database. That table has 3 columns, id, domain and name. The id for the row of your domain is what needs to be set as SITE_ID. > [ABH] At this point I click to accept a subsription request: > > ERROR 2020-01-06 07:32:41,439 699 postorius.middleware Mailman REST API not available > Traceback (most recent call last): > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py", line 672, in urlopen > chunked=chunked, > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py", line 421, in _make_request > six.raise_from(e, None) > File "", line 3, in raise_from > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py", line 416, in _make_request > httplib_response = conn.getresponse() > File "/usr/lib/python3.7/http/client.py", line 1321, in getresponse > response.begin() > File "/usr/lib/python3.7/http/client.py", line 296, in begin > version, status, reason = self._read_status() > File "/usr/lib/python3.7/http/client.py", line 265, in _read_status > raise RemoteDisconnected("Remote end closed connection without" > http.client.RemoteDisconnected: Remote end closed connection without response > > So yes, the REST API is not there. How can I get it going? Stop Mailman and then start it. > Before we added the new domain, I was able to accept subscription requests to the previous domain?s lists. No more. > > Yours, > > Allan -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From e.e.schmitz at ziggo.nl Mon Jan 6 13:13:04 2020 From: e.e.schmitz at ziggo.nl (Erwin Schmitz) Date: Mon, 6 Jan 2020 19:13:04 +0100 Subject: [Mailman-Users] Bug in Mailman version 2.1.23 Message-ID: <23558df4-f902-2177-f34f-112aaf4d06cc@ziggo.nl> LS, I'm using mailman mailinglists, only private lists are configured. Mailman Administrator Authentication page (.../cgi-bin/mailman/admin/mailman) After entering password and clicking on "Let me in" this message appears : ------------------------------------ Bug in Mailman version 2.1.23 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. ---------------------------- The log (error) contains : admin(9779): [----- Mailman Version: 2.1.23 -----] admin(9779): [----- Traceback ------] admin(9779): Traceback (most recent call last): admin(9779): File "/var/lib/mailman/scripts/driver", line 117, in run_main admin(9779): main() admin(9779): File "/var/lib/mailman/Mailman/Cgi/admin.py", line 239, in main admin(9779): show_results(mlist, doc, category, subcat, cgidata) admin(9779): File "/var/lib/mailman/Mailman/Cgi/admin.py", line 465, in show_results admin(9779): otherlinks.AddItem(Link(mlist.GetBaseArchiveURL(), admin(9779): File "/var/lib/mailman/Mailman/Archiver/Archiver.py", line 143, in GetBaseArchiveURL admin(9779): hostname = re.match('[^:]*://([^/]*)/.*', url).group(1)\ admin(9779): AttributeError: 'NoneType' object has no attribute 'group' Via listinfo (left below screen shows : List Description Mailman [no description available] (Why should this be a list?) click on Mailman (lnks to .../cgi-bin/mailman/admin/mailman) admin(9744): [----- Mailman Version: 2.1.23 -----] admin(9744): [----- Traceback ------] admin(9744): Traceback (most recent call last): admin(9744): File "/var/lib/mailman/scripts/driver", line 117, in run_main admin(9744): main() admin(9744): File "/var/lib/mailman/Mailman/Cgi/listinfo.py", line 77, in main admin(9744): list_listinfo(mlist, language) admin(9744): File "/var/lib/mailman/Mailman/Cgi/listinfo.py", line 181, in list_listinfo admin(9744): replacements = mlist.GetStandardReplacements(lang) admin(9744): File "/var/lib/mailman/Mailman/HTMLFormatter.py", line 400, in GetStandardReplacements admin(9744): '' : self.FormatArchiveAnchor(), admin(9744): File "/var/lib/mailman/Mailman/HTMLFormatter.py", line 336, in FormatArchiveAnchor admin(9744): return '' % self.GetBaseArchiveURL() admin(9744): File "/var/lib/mailman/Mailman/Archiver/Archiver.py", line 143, in GetBaseArchiveURL admin(9744): hostname = re.match('[^:]*://([^/]*)/.*', url).group(1)\ admin(9744): AttributeError: 'NoneType' object has no attribute 'group' admin(9744): [----- Python Information -----] Questions: Why is the link "Mailman" shown on the screen, only public lists should be shown Why is this shown as "Mailman", which is not a 'normal' mailinglist. How to solve this. From mark at msapiro.net Tue Jan 7 12:28:34 2020 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 7 Jan 2020 09:28:34 -0800 Subject: [Mailman-Users] Bug in Mailman version 2.1.23 In-Reply-To: <23558df4-f902-2177-f34f-112aaf4d06cc@ziggo.nl> References: <23558df4-f902-2177-f34f-112aaf4d06cc@ziggo.nl> Message-ID: On 1/6/20 10:13 AM, Erwin Schmitz wrote: > > Mailman Administrator Authentication page > (.../cgi-bin/mailman/admin/mailman) > > After entering password and clicking on "Let me in" this message appears : > ------------------------------------ > Bug in Mailman version 2.1.23 > > We're sorry, we hit a bug! > > Please inform the webmaster for this site of this problem. Printing of > traceback and other system information has been explicitly inhibited, > but the webmaster can find this information in the Mailman error logs. > ---------------------------- > > The log (error) contains : > admin(9779): [----- Mailman Version: 2.1.23 -----] > admin(9779): [----- Traceback ------] > admin(9779): Traceback (most recent call last): > admin(9779):?? File "/var/lib/mailman/scripts/driver", line 117, in > run_main > admin(9779):???? main() > admin(9779):?? File "/var/lib/mailman/Mailman/Cgi/admin.py", line 239, > in main > admin(9779):???? show_results(mlist, doc, category, subcat, cgidata) > admin(9779):?? File "/var/lib/mailman/Mailman/Cgi/admin.py", line 465, > in show_results > admin(9779):???? otherlinks.AddItem(Link(mlist.GetBaseArchiveURL(), > admin(9779):?? File "/var/lib/mailman/Mailman/Archiver/Archiver.py", > line 143, in GetBaseArchiveURL > admin(9779):???? hostname = re.match('[^:]*://([^/]*)/.*', url).group(1)\ > admin(9779): AttributeError: 'NoneType' object has no attribute 'group' The web_page_url attribute of the `mailman` list does not look like `http(s)://host.name/...` > Via listinfo (left below screen shows : > List???? Description > Mailman???? [no description available]??? (Why should this be a list?) Every Mailman 2.1 installation must have a site list, usually named `mailman`. > click on Mailman (lnks to .../cgi-bin/mailman/admin/mailman) > > admin(9744): [----- Mailman Version: 2.1.23 -----] > admin(9744): [----- Traceback ------] > admin(9744): Traceback (most recent call last): > admin(9744):?? File "/var/lib/mailman/scripts/driver", line 117, in > run_main > admin(9744):???? main() > admin(9744):?? File "/var/lib/mailman/Mailman/Cgi/listinfo.py", line 77, > in main > admin(9744):???? list_listinfo(mlist, language) > admin(9744):?? File "/var/lib/mailman/Mailman/Cgi/listinfo.py", line > 181, in list_listinfo > admin(9744):???? replacements = mlist.GetStandardReplacements(lang) > admin(9744):?? File "/var/lib/mailman/Mailman/HTMLFormatter.py", line > 400, in GetStandardReplacements > admin(9744):???? ''?? : self.FormatArchiveAnchor(), > admin(9744):?? File "/var/lib/mailman/Mailman/HTMLFormatter.py", line > 336, in FormatArchiveAnchor > admin(9744):???? return '' % self.GetBaseArchiveURL() > admin(9744):?? File "/var/lib/mailman/Mailman/Archiver/Archiver.py", > line 143, in GetBaseArchiveURL > admin(9744):???? hostname = re.match('[^:]*://([^/]*)/.*', url).group(1)\ > admin(9744): AttributeError: 'NoneType' object has no attribute 'group' > admin(9744): [----- Python Information -----] > > Questions: > Why is the link "Mailman" shown on the screen, only public lists should > be shown The `mailman` list is probably public. > Why is this shown as "Mailman", which is not a 'normal' mailinglist. Yes it is. It is the site list which is a list like any other. See > How to solve this. Possibly running fix_url will fix this. /path/to/mailman/bin/withlist -l -r fix_url mailman That should allow you to access the listinfo and admin pages for this list and you can then set its Privacy options... -> Subscription rules -> advertised to No. You will probably need to use the site password to log in to the admin page. If you don't have one, you can set it via /path/to/mailman/bin/mmsitepass PASSWORD or you can set a list password via /path/to/mailman/bin/change_pw -l mailman -q -p PASSWORD -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From jimpop at domainmail.org Fri Jan 10 10:52:45 2020 From: jimpop at domainmail.org (Jim Popovitch) Date: Fri, 10 Jan 2020 10:52:45 -0500 Subject: [Mailman-Users] Apache subscription Referer rules Message-ID: (I think I asked this a few months back, but I couldn't locate any emails on it) What is the Apache rule syntax for rejecting subscription linking that doesn't come from the same domain/site? tia, -Jim P. From mark at msapiro.net Sat Jan 11 22:09:52 2020 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 11 Jan 2020 19:09:52 -0800 Subject: [Mailman-Users] Mailman 2.1.30rc1 released Message-ID: <5a026b89-f93a-e544-a4a2-9e3a5bcc50e6@msapiro.net> I am pleased to announce the release of Mailman 2.1.30rc1. Python 2.6 is the minimum supported, but Python 2.7 is strongly recommended. This is a routine bug fix release with a few new features. See the attached README.txt for details. Mailman 2.1.30 will be the last release of the Mailman 2.1 branch from the GNU Mailman project. It contains some new strings which are untranslated in most of the i18n translations. If you can help update any of the translations, please contribute your changes. Changes can be submitted via a bzr merge proposal on Launchpad or by sending an updated mailman.po file and or templates directly to me. This will be the last chance to get i18n updates into a release. Mailman is free software for managing email mailing lists and e-newsletters. Mailman is used for all the python.org and SourceForge.net mailing lists, as well as at hundreds of other sites. For more information, please see our web site at one of: http://www.list.org https://www.gnu.org/software/mailman http://mailman.sourceforge.net/ Mailman 2.1.30rc1 can be downloaded from https://launchpad.net/mailman/2.1/ https://ftp.gnu.org/gnu/mailman/ https://sourceforge.net/projects/mailman/ -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -------------- next part -------------- 2.1.30rc1 (11-Jan-2020) New Features - Thanks to Jim Popovitch, there is now a dmarc_moderation_addresses list setting that can be used to apply dmarc_moderation_action to mail From: addresses listed or matching listed regexps. This can be used to modify mail to addresses that don't accept external mail From: themselves. - There is a new MAX_LISTNAME_LENGTH setting. The fix for LP: #1780874 obtains a list of the names of all the all the lists in the installation in order to determine the maximum length of a legitimate list name. It does this on every web access and on sites with a very large number of lists, this can have performance implications. See the description in Defaults.py for more information. - Thanks to Ralf Jung there is now the ability to add text based captchas (aka textchas) to the listinfo subscribe form. See the documentation for the new CAPTCHA setting in Defaults.py for how to enable this. Also note that if you have custom listinfo.html templates, you will have to add a tag to those templates to make this work. This feature can be used in combination with or instead of the Google reCAPTCHA feature added in 2.1.26. - Thanks to Ralf Hildebrandt the web admin Membership Management section now has a feature to sync the list's membership with a list of email addresses as with the bin/sync_members command. - There is a new drop_cc list attribute set from DEFAULT_DROP_CC. This controls the dropping of addresses from the Cc: header in delivered messages by the duplicate avoidance process. (LP: #1845751) - There is a new 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. This can be set to Yes to prevent mailbombing of a third party by repeatedly posting the subscribe form. (LP: #1859104) i18n - The Japanese translation has been updated by Yasuhito FUTATSUKI. Bug Fixes and other patches - Fixed the confirm CGI to catch a rare TypeError on simultaneous confirmations of the same token. (LP: #1785854) - Scrubbed application/octet-stream MIME parts will now be given a .bin extension instead of .obj. - Added bounce recognition for a non-compliant opensmtpd DSN with Action: error. (LP: #1805137) - Corrected and augmented some security log messages. (LP: #1810098) - Implemented use of QRUNNER_SLEEP_TIME for bin/qrunner --runner=All. (LP: #1818205) - Leading/trailing spaces in provided email addresses for login to private archives and the user options page are now ignored. (LP: #1818872) - Fixed the spelling of the --no-restart option for mailmanctl. - Fixed an issue where certain combinations of charset and invalid characters in a list's description could produce a List-ID header without angle brackets. (LP: #1831321) - With the Postfix MTA and virtual domains, mappings for the site list -bounces and -request addresses in each virtual domain are now added to data/virtual-mailman (-owner was done in 2.1.24). (LP: #1831777) - The paths.py module now extends sys.path with the result of site.getsitepackages() if available. (LP: #1838866) - A bug causing a UnicodeDecodeError in preparing to send the confirmation request message to a new subscriber has been fixed. (LP: #1851442) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From turnbull.stephen.fw at u.tsukuba.ac.jp Mon Jan 13 22:34:54 2020 From: turnbull.stephen.fw at u.tsukuba.ac.jp (Stephen J. Turnbull) Date: Tue, 14 Jan 2020 12:34:54 +0900 Subject: [Mailman-Users] Apache subscription Referer rules In-Reply-To: References: Message-ID: <24093.14046.273109.100361@turnbull.sk.tsukuba.ac.jp> Jim Popovitch via Mailman-Users writes: > (I think I asked this a few months back, but I couldn't locate any > emails on it) > > What is the Apache rule syntax for rejecting subscription linking that > doesn't come from the same domain/site? Don't know what you need exactly, but mod_rewrite can be used for similar purposes: https://httpd.apache.org/docs/2.4/rewrite/access.html There's also a pointer in that page to "SetEnvIf refer" which may be usable. HTH Steve From mailmanu-20190215 at billmail.scconsult.com Tue Jan 14 00:19:26 2020 From: mailmanu-20190215 at billmail.scconsult.com (Bill Cole) Date: Tue, 14 Jan 2020 00:19:26 -0500 Subject: [Mailman-Users] Apache subscription Referer rules In-Reply-To: References: Message-ID: <5486EEF8-8D9E-43A9-AA76-5DF659CF52B7@billmail.scconsult.com> On 10 Jan 2020, at 10:52, Jim Popovitch via Mailman-Users wrote: > (I think I asked this a few months back, but I couldn't locate any > emails on it) > > What is the Apache rule syntax for rejecting subscription linking that > doesn't come from the same domain/site? First step: Header always set Referrer-Policy "same-origin" This assures (to the degree that browsers comply with directives provided in headers) that legitimate internal links and sub-resource loads have a Referer header (see https://en.wikipedia.org/wiki/HTTP_referer) which you can use. The next step is to read https://httpd.apache.org/docs/2.4/rewrite/access.html#blocked-inline-images and adapt the example to your site. -- Bill Cole bill at scconsult.com or billcole at apache.org (AKA @grumpybozo and many *@billmail.scconsult.com addresses) Not For Hire (currently) From jimpop at domainmail.org Tue Jan 14 10:14:51 2020 From: jimpop at domainmail.org (Jim Popovitch) Date: Tue, 14 Jan 2020 10:14:51 -0500 Subject: [Mailman-Users] Apache subscription Referer rules In-Reply-To: <5486EEF8-8D9E-43A9-AA76-5DF659CF52B7@billmail.scconsult.com> References: <5486EEF8-8D9E-43A9-AA76-5DF659CF52B7@billmail.scconsult.com> Message-ID: <2cdc7ea8f4a1d2a7686cddf8def6c4bfd5597c61.camel@domainmail.org> On Tue, 2020-01-14 at 00:19 -0500, Bill Cole wrote: > On 10 Jan 2020, at 10:52, Jim Popovitch via Mailman-Users wrote: > > > (I think I asked this a few months back, but I couldn't locate any > > emails on it) > > > > What is the Apache rule syntax for rejecting subscription linking that > > doesn't come from the same domain/site? > > First step: > > Header always set Referrer-Policy "same-origin" > > This assures (to the degree that browsers comply with directives > provided in headers) that legitimate internal links and sub-resource > loads have a Referer header (see > https://en.wikipedia.org/wiki/HTTP_referer) which you can use. > > The next step is to read > https://httpd.apache.org/docs/2.4/rewrite/access.html#blocked-inline-images > and adapt the example to your site. > Mod_Rewrite is "too heavy" for something this simple. I couldn't recall the specifics, but your mod_rewrite link actually mentioned the way to do something similar without mod_rewrite. From that, I extrapolated this (which I haven't been able to test yet): SetEnvIfNoCase Referer "https://.*/mailman/listinfo/" ListInfoReferer SetEnvIfNoCase Request_Protocol "POST" HttpPostProto Require env ListInfoReferer Require env HttpPostProto thoughts? -Jim P. From turnbull.stephen.fw at u.tsukuba.ac.jp Thu Jan 16 04:09:35 2020 From: turnbull.stephen.fw at u.tsukuba.ac.jp (Stephen J. Turnbull) Date: Thu, 16 Jan 2020 18:09:35 +0900 Subject: [Mailman-Users] Apache subscription Referer rules In-Reply-To: <2cdc7ea8f4a1d2a7686cddf8def6c4bfd5597c61.camel@domainmail.org> References: <5486EEF8-8D9E-43A9-AA76-5DF659CF52B7@billmail.scconsult.com> <2cdc7ea8f4a1d2a7686cddf8def6c4bfd5597c61.camel@domainmail.org> Message-ID: <24096.10319.314262.344439@turnbull.sk.tsukuba.ac.jp> Jim Popovitch via Mailman-Users writes: > Mod_Rewrite is "too heavy" for something this simple. It's only too heavy if it actually has an unacceptable impact on system load. That said, I like the SetEnvIf* approach better. > SetEnvIfNoCase Referer "https://.*/mailman/listinfo/" ListInfoReferer I see three possible issues with the regexp. First, evidently you're handling multiple domains. You might want to include that the referral comes from the same domain (I don't know how to do it offhand, though -- that might justify the "heavier" mod_rewrite approach?) Second, I think I've seen referrals that are relative to the base URL in the logs. You might want to check that the referer (sp? I would write "referrer" but I don't know if that's correct) in this context is always a full URL. Third, if as I suspect the ".*" is intended to match just the authority component (domain) of the URL, you may wish to change that to "[^/]*" or perhaps "[^/]+". (I don't think I've ever seen a "https:///..." URL with no domain -- that can't be validated by SSL without a domain!) > thoughts? I haven't checked the command syntax. It seems to me SetEnvIf expresses the intent better than mod_rewrite does, and I did a little thinking about when you would want the extra flexibility that mod_rewrite allows, and didn't come up with anything, for what that's worth. Steve From tom.corcoran at moonbade.com Fri Jan 17 04:34:28 2020 From: tom.corcoran at moonbade.com (tom.corcoran at moonbade.com) Date: Fri, 17 Jan 2020 09:34:28 +0000 Subject: [Mailman-Users] auto approving Message has implicit destination Message-ID: Previously you helped me with auto discarding on my mailing list for myself and my wife: https://www.mail-archive.com/mailman-users at python.org/msg72213.html In the same mailing list I am regularly having to constantly approve emails from the same address with message: Reason: Message has implicit destination. Is there a setting I can make on the mailing list admin that means the email comes straight through without the need to do this approval? Cheers, Tom. From mark at msapiro.net Fri Jan 17 12:36:38 2020 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 17 Jan 2020 09:36:38 -0800 Subject: [Mailman-Users] auto approving Message has implicit destination In-Reply-To: References: Message-ID: <4cefa42c-9ea8-be8e-eb6e-08a5e237de0f@msapiro.net> On 1/17/20 1:34 AM, tom.corcoran at moonbade.com wrote: > > In the same mailing list I am regularly having to constantly approve > emails from the same address with message: Reason:? Message has implicit > destination. Is there a setting I can make on the mailing list admin > that means the email comes straight through without the need to do this > approval? Set Privacy options... -> Recipient filters -> require_explicit_destination to No -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From johnson at Pharmacy.Arizona.EDU Fri Jan 17 13:01:20 2020 From: johnson at Pharmacy.Arizona.EDU (Bruce Johnson) Date: Fri, 17 Jan 2020 18:01:20 +0000 Subject: [Mailman-Users] auto approving Message has implicit destination In-Reply-To: References: Message-ID: <906A4E67-56AE-45C5-8DF1-265AAD5809B3@pharmacy.arizona.edu> On Jan 17, 2020, at 2:34 AM, tom.corcoran at moonbade.com wrote: In the same mailing list I am regularly having to constantly approve emails from the same address with message: Reason: Message has implicit destination. Is there a setting I can make on the mailing list admin that means the email comes straight through without the need to do this approval? We run into this ALL the time with our lists; it means that the list address in the email is in the BCC rather than the TO or CC field. From the FAQ: https://wiki.list.org/DOC/What%20does%20%22message%20has%20implicit%20destination%22%20mean%3F "Alternatively, if you want to accept all BCCs to the list and get rid of this message entirely, go to Privacy Options / Recipient Filters and set the require_explicit_destination option to be "No". This should be the first option on the page, and by default, Mailman will set this option to be "Yes?.? -- Bruce Johnson University of Arizona College of Pharmacy Information Technology Group Institutions do not have opinions, merely customs From tom.corcoran at moonbade.com Mon Jan 20 16:59:11 2020 From: tom.corcoran at moonbade.com (Tom Corcoran) Date: Mon, 20 Jan 2020 21:59:11 +0000 Subject: [Mailman-Users] auto approving Message has implicit destination In-Reply-To: <4cefa42c-9ea8-be8e-eb6e-08a5e237de0f@msapiro.net> References: <4cefa42c-9ea8-be8e-eb6e-08a5e237de0f@msapiro.net> Message-ID: <406fb5f1-5d5d-d140-3a6a-b27163230994@moonbade.com> On 17/01/2020 17:36, Mark Sapiro wrote: > On 1/17/20 1:34 AM, tom.corcoran at moonbade.com wrote: >> In the same mailing list I am regularly having to constantly approve >> emails from the same address with message: Reason:? Message has implicit >> destination. Is there a setting I can make on the mailing list admin >> that means the email comes straight through without the need to do this >> approval? > > Set Privacy options... -> Recipient filters -> > require_explicit_destination to No Worked great, thank you :-) From gkasica at netwrx1.com Wed Jan 22 11:44:22 2020 From: gkasica at netwrx1.com (George R. Kasica) Date: Wed, 22 Jan 2020 16:44:22 +0000 Subject: [Mailman-Users] =?utf-8?q?User_can=E2=80=99t_perform_functions?= References: <371e937f-5d39-470e-943e-387d1fd54b2e@Spark> Message-ID: I have a user listed in both list administrators and moderators - same valid email for both and they?re not able to post to the list. It?s closed only admins and moderators can post. I have no Idea what could be different the setup is pretty straightforward just list the addresses in the respective boxes. Can someone provide some guidance here as right now I?m the only moderator that can do anything and I have other things to get done besides admin other folks lists. Thank you very much. I can add any additional info you may require. --- George R. Kasica From mark at msapiro.net Wed Jan 22 11:59:55 2020 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 22 Jan 2020 08:59:55 -0800 Subject: [Mailman-Users] =?utf-8?q?User_can=E2=80=99t_perform_functions?= In-Reply-To: References: <371e937f-5d39-470e-943e-387d1fd54b2e@Spark> Message-ID: <37055422-3ba2-e1b7-66ad-c15a6fd00af8@msapiro.net> On 1/22/20 8:44 AM, George R. Kasica wrote: > I have a user listed in both list administrators and moderators - same valid email for both and they?re not able to post to the list. It?s closed only admins and moderators can post. I have no Idea what could be different the setup is pretty straightforward just list the addresses in the respective boxes. Can someone provide some guidance here as right now I?m the only moderator that can do anything and I have other things to get done besides admin other folks lists. I'm assuming this is Mailman 2.1 since this is a Mailman 2.1 list. If it is Mailman 3, please join the mailman-users at mailman3.org list at and post there. First, it is redundant to put the same address in both the owner and moderator lists, since all these do is provide addresses for the sending of notices and owners get them all. Being in that list conveys no posting rights. See the FAQ articles at and . If you want this address to be able to post without the post being held, they can post with an Approved: header as noted in the second of the above FAQ articles or you can add their address to Privacy options... -> Sender filters -> accept_these_nonmembers. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From gkasica at netwrx1.com Sat Jan 25 09:55:25 2020 From: gkasica at netwrx1.com (George R. Kasica) Date: Sat, 25 Jan 2020 14:55:25 +0000 Subject: [Mailman-Users] =?utf-8?q?User_can=E2=80=99t_perform_functions?= In-Reply-To: <37055422-3ba2-e1b7-66ad-c15a6fd00af8@msapiro.net> References: <371e937f-5d39-470e-943e-387d1fd54b2e@Spark> <37055422-3ba2-e1b7-66ad-c15a6fd00af8@msapiro.net> Message-ID: Yes its 2.1. They are a list member as well. Added to the Privacy options... -> Sender filters -> accept_these_nonmembers and we'll see what that gets him. Thanks! George R. Kasica Jackson, WI USA gkasica at netwrx1.com http://www.netwrx1.com -----Original Message----- From: Mailman-Users On Behalf Of Mark Sapiro Sent: Wednesday, 22 January, 2020 11:00 To: mailman-users at python.org Subject: Re: [Mailman-Users] User can?t perform functions On 1/22/20 8:44 AM, George R. Kasica wrote: > I have a user listed in both list administrators and moderators - same valid email for both and they?re not able to post to the list. It?s closed only admins and moderators can post. I have no Idea what could be different the setup is pretty straightforward just list the addresses in the respective boxes. Can someone provide some guidance here as right now I?m the only moderator that can do anything and I have other things to get done besides admin other folks lists. I'm assuming this is Mailman 2.1 since this is a Mailman 2.1 list. If it is Mailman 3, please join the mailman-users at mailman3.org list at and post there. First, it is redundant to put the same address in both the owner and moderator lists, since all these do is provide addresses for the sending of notices and owners get them all. Being in that list conveys no posting rights. See the FAQ articles at and . If you want this address to be able to post without the post being held, they can post with an Approved: header as noted in the second of the above FAQ articles or you can add their address to Privacy options... -> Sender filters -> accept_these_nonmembers. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users at python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/gkasica%40netwrx1.com -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5571 bytes Desc: not available URL: From mark at msapiro.net Sat Jan 25 12:00:12 2020 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 25 Jan 2020 09:00:12 -0800 Subject: [Mailman-Users] =?utf-8?q?User_can=E2=80=99t_perform_functions?= In-Reply-To: References: <371e937f-5d39-470e-943e-387d1fd54b2e@Spark> <37055422-3ba2-e1b7-66ad-c15a6fd00af8@msapiro.net> Message-ID: On 1/25/20 6:55 AM, George R. Kasica wrote: > Yes its 2.1. > > They are a list member as well. Added to the Privacy options... -> Sender filters -> accept_these_nonmembers and we'll see what that gets him. If his address is a list member, adding it to *_these_nonmembers will have no effect. What happens when he tries to post. Is the post held? Does it disappear? is there any notice? Anything in Mailman's logs? If the message just disappears, the FAQ article at may help. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From jelledejong at powercraft.nl Sun Jan 26 12:03:44 2020 From: jelledejong at powercraft.nl (Jelle de Jong) Date: Sun, 26 Jan 2020 18:03:44 +0100 Subject: [Mailman-Users] how to disable main mailman-request and mailman list without stopping mailman functionality Message-ID: Hello everybody, I am seeing our mailman at lists.company.nl being used to try to spam people and receiving mail delivery failures from mailman-request at lists.company.nl attempts. I removed the mailman mailinglist but that ended up disabling mailman and all of the mailinglsit from working. I created the mailman mailinglist again and the spam started again. I looked at the the options but can not find the right ones that might help? PS. I had mailman not advertised by default but some Debian update a while back seem to have made it advertised. I disabled the advertising of the list but the spam keeps coming. Maybe disable advertising by default for the mailman default list? What are the recommended steps? Kind regards, Jelle de Jong From mark at msapiro.net Mon Jan 27 09:52:27 2020 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 27 Jan 2020 06:52:27 -0800 Subject: [Mailman-Users] how to disable main mailman-request and mailman list without stopping mailman functionality In-Reply-To: References: Message-ID: On 1/26/20 9:03 AM, Jelle de Jong wrote: > > PS. I had mailman not advertised by default but some Debian update a > while back seem to have made it advertised. I disabled the advertising > of the list but the spam keeps coming. Maybe disable advertising by > default for the mailman default list? First, advertised or not, it is well known that every Mailman 2.1 installation has a site list, usually called mailman. Also the mailman at example.com address is exposed on both the listinfo and admin overview pages in the web UI. > What are the recommended steps? It depends on how your MTA deliveres to Mailman. If it uses aliases, you can change the mailman-request alias in mailman's aliases, but if Mailman automatically generates these, that may get undone. A better approach is to put an alias for the mailman-request and maybe other mailman- addresses in an alias file that is processed before Mailman's aliases or delivery. You can use these to send the mail to /dev/null or to some user or mailbox if you want to see the mail. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From jelledejong at powercraft.nl Tue Jan 28 06:13:58 2020 From: jelledejong at powercraft.nl (Jelle de Jong) Date: Tue, 28 Jan 2020 12:13:58 +0100 Subject: [Mailman-Users] how to disable main mailman-request and mailman list without stopping mailman functionality In-Reply-To: References: Message-ID: Thank you Mark for taking the time to reply, much appreciated. On 2020-01-27 15:52, Mark Sapiro wrote: > On 1/26/20 9:03 AM, Jelle de Jong wrote: >> >> PS. I had mailman not advertised by default but some Debian update a >> while back seem to have made it advertised. I disabled the advertising >> of the list but the spam keeps coming. Maybe disable advertising by >> default for the mailman default list? > > First, advertised or not, it is well known that every Mailman 2.1 > installation has a site list, usually called mailman. Also the > mailman at example.com address is exposed on both the listinfo and admin > overview pages in the web UI. > >> What are the recommended steps? > > It depends on how your MTA deliveres to Mailman. If it uses aliases, you > can change the mailman-request alias in mailman's aliases, but if > Mailman automatically generates these, that may get undone. A better > approach is to put an alias for the mailman-request and maybe other > mailman- addresses in an alias file that is processed before Mailman's > aliases or delivery. You can use these to send the mail to /dev/null or > to some user or mailbox if you want to see the mail. So how can I make a alias for all mailman- addresses that go to /dev/null? mailman version 1:2.1.23-1+deb9u4 # /usr/lib/mailman/bin/genaliases --help Regenerate Mailman specific aliases from scratch. Does not give me much useful informaiton. Kind regards, Jelle de Jong From mark at msapiro.net Tue Jan 28 11:51:41 2020 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 28 Jan 2020 08:51:41 -0800 Subject: [Mailman-Users] how to disable main mailman-request and mailman list without stopping mailman functionality In-Reply-To: References: Message-ID: On 1/28/20 3:13 AM, Jelle de Jong wrote: > On 2020-01-27 15:52, Mark Sapiro wrote: >> >> It depends on how your MTA deliveres to Mailman. If it uses aliases, >> you can change the mailman-request alias in mailman's aliases, but if >> Mailman automatically generates these, that may get undone. A better >> approach is to put an alias for the mailman-request and maybe other >> mailman- addresses in an alias file that is processed before Mailman's >> aliases or delivery. You can use these to send the mail to /dev/null >> or to some user or mailbox if you want to see the mail. > > So how can I make a alias for all mailman- addresses that go to /dev/null? Assuming your MTA is configured to use /etc/aliases and puts it before Mailman's data/aliases. Add the following lines to /etc/aliases mailman-admin: /dev/null mailman-bounces: /dev/null mailman-confirm: /dev/null mailman-join: /dev/null mailman-leave: /dev/null mailman-owner: /dev/null mailman-request: /dev/null mailman-subscribe: /dev/null mailman-unsubscribe: /dev/null And then run `newaliases` -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From dmaziuk at bmrb.wisc.edu Wed Jan 29 10:43:38 2020 From: dmaziuk at bmrb.wisc.edu (dmaziuk) Date: Wed, 29 Jan 2020 09:43:38 -0600 Subject: [Mailman-Users] send_reminders frequency Message-ID: Hi all, apologies if this is a faq and my google-fu's failing to find the answer: can I change send_reminders to e.g. yearly? Thanks, Dima From mark at msapiro.net Wed Jan 29 13:23:48 2020 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 29 Jan 2020 10:23:48 -0800 Subject: [Mailman-Users] send_reminders frequency In-Reply-To: References: Message-ID: On 1/29/20 7:43 AM, dmaziuk via Mailman-Users wrote: > > apologies if this is a faq and my google-fu's failing to find the > answer: can I change send_reminders to e.g. yearly? Mailman's cron/mailpasswds is run via cron. You can edit Mailman's crontab to run it on whatever schedule you like. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From dmaziuk at bmrb.wisc.edu Wed Jan 29 13:28:16 2020 From: dmaziuk at bmrb.wisc.edu (Dimitri Maziuk) Date: Wed, 29 Jan 2020 12:28:16 -0600 Subject: [Mailman-Users] send_reminders frequency In-Reply-To: References: Message-ID: <9a7d9db9-034f-405b-58f2-15f200554c40@bmrb.wisc.edu> On 1/29/20 12:23 PM, Mark Sapiro wrote: > On 1/29/20 7:43 AM, dmaziuk via Mailman-Users wrote: >> >> apologies if this is a faq and my google-fu's failing to find the >> answer: can I change send_reminders to e.g. yearly? > > > Mailman's cron/mailpasswds is run via cron. You can edit Mailman's > crontab to run it on whatever schedule you like. > Thank you Mark -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 190 bytes Desc: OpenPGP digital signature URL: From chip at aresti.com Wed Jan 29 19:33:20 2020 From: chip at aresti.com (Chip Davis) Date: Wed, 29 Jan 2020 19:33:20 -0500 Subject: [Mailman-Users] send_reminders frequency In-Reply-To: References: Message-ID: <633f1ff6-05a2-d4ef-3dcf-82262c51f797@aresti.com> I administer around a dozen (mostly v2.1) Mailman lists, but they are all on shared servers running cPanel or some equivalent "we won't let you get your hands dirty" interface.? Not by my choice, and with wildly varying support from the server vendors. I often see questions about how to do something or another that I would dearly love to do, only to find that the simple, straightforward procedure recommended is beyond my server credentials.? It would be very helpful to me if those answers acknowledged that: * this can't be done on a shared server implementation, don't bother trying * this can also be done on a shared server, and here's how (or at least, the magic words to ask your vendor) For example, the recent answer about "cloning" lists (impossible unless you have full access to the server's filesystem, then trivially easy) was disappointing because I have multiple lists that need to stay in-synch.? So I wrote a Rexx program that screen-scrapes the Mailman configuration screens and generates a checklist of each extracted setting, input field, textarea, etc. for use when cloning a new list.? It's a kludge compared to simply copying a couple of files into a new directory, but it works for those of us out here in the cheap seats. Thanks, -Chip- On 1/29/2020 1:23 PM, Mark Sapiro wrote: > On 1/29/20 7:43 AM, dmaziuk via Mailman-Users wrote: >> >> apologies if this is a faq and my google-fu's failing to find the >> answer: can I change send_reminders to e.g. yearly? > > > Mailman's cron/mailpasswds is run via cron. You can edit Mailman's > crontab to run it on whatever schedule you like. > From mark at msapiro.net Wed Jan 29 20:40:11 2020 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 29 Jan 2020 17:40:11 -0800 Subject: [Mailman-Users] Acknowledging 'access required' - was: send_reminders frequency In-Reply-To: <633f1ff6-05a2-d4ef-3dcf-82262c51f797@aresti.com> References: <633f1ff6-05a2-d4ef-3dcf-82262c51f797@aresti.com> Message-ID: <040df1fc-5887-8785-33a1-8a271135878e@msapiro.net> On 1/29/20 4:33 PM, Chip Davis wrote: > > I often see questions about how to do something or another that I would > dearly love to do, only to find that the simple, straightforward > procedure recommended is beyond my server credentials.? It would be very > helpful to me if those answers acknowledged that: > > ?* this can't be done on a shared server implementation, don't bother > ?? trying > ?* this can also be done on a shared server, and here's how (or at > ?? least, the magic words to ask your vendor) I can understand your frustration when presented with a simple solution that you can't implement because of lack of access to the server or adverse impact on other users of a shared server. I'm sure if you look through the archives, you'll find many posts with various caveats. I just did and got 218 hits, so it's not that we're completely oblivious to this issue, but frankly, I and others already spend a great deal of time and energy supporting Mailman as volunteers and taking the additional time on every thread to determine what if any disclaimer is required is something I don't think I can do. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From dmaziuk at bmrb.wisc.edu Thu Jan 30 11:18:18 2020 From: dmaziuk at bmrb.wisc.edu (dmaziuk) Date: Thu, 30 Jan 2020 10:18:18 -0600 Subject: [Mailman-Users] send_reminders frequency In-Reply-To: <633f1ff6-05a2-d4ef-3dcf-82262c51f797@aresti.com> References: <633f1ff6-05a2-d4ef-3dcf-82262c51f797@aresti.com> Message-ID: <3c951505-1a79-6739-b7ad-5c5cd309b594@bmrb.wisc.edu> On 1/29/2020 6:33 PM, Chip Davis wrote: > I often see questions about how to do something or another that I would > dearly love to do, only to find that the simple, straightforward > procedure recommended is beyond my server credentials.? It would be very > helpful to me if those answers acknowledged that: > > ?* this can't be done on a shared server implementation, don't bother > ?? trying > ?* this can also be done on a shared server, and here's how (or at > ?? least, the magic words to ask your vendor) Well, the crontab is mailman-global so changing it affects every list on the server. (Lucky for me, on this particular server that is acceptable.) That's obvious when you look at it. What some provider may or may not let you do via their glitzy cGooey is a question to the provider. How would any of us know? Dima From stinga at wolf-rock.com Thu Jan 30 22:29:03 2020 From: stinga at wolf-rock.com (stinga) Date: Fri, 31 Jan 2020 11:29:03 +0800 Subject: [Mailman-Users] acceptable_aliases does not seem to work (or more likely I don't understand) V2.1.23 Message-ID: <60a04924-5d22-3304-e679-a0f6bd046a25@wolf-rock.com> G'day all, I can't seem to get acceptable_aliases to work... (domain names changed to protect the innocent, but all match up) comm at lists.lf.me = List email address info at lf.me = Google group (google group has one email address which is comm at lists.lf.me info at lf.me is a member of the mailman list and is set for nomail User another at domain.com sends email to info at lf.me List receives email and bounces with: List: comm at lists.lf.me From: another at domain.com Subject: Testing Reason: Post by non-member to a members-only list The above is correct as user another at domain.com is not a member of the mailman list In the email header there is To: I have in acceptable_aliases (tried various things) info at lf.me "info at lf.me" .*info at lf.me.* and require_explicit_destination is yes I believe that should allow email sent to info at lf.me to be accepted by the list, maybe I am reading this all wrong? If I am doing this wrong how do I get a google email to send to mailman and be accepted? info at lf.me was a real email address and I converted to a group so that all on the list could see it rather than person having to deal with the email. (I could have just forwarded the email in google but I didn;t want to have to deal with the email account that would never be looked at.) -- 'ooroo Stinga...(:)-) --------------------------------------------------- Email: stinga at wolf-rock.com o You need only two tools. o ///// A hammer and duct tape. If it /@ `\ /) ~ doesn't move and it should use > (O) X< ~ Fish!! the hammer. If it moves and `\___/' \) ~ shouldn't, use the tape. \\\ --------------------------------------------------- From timhfl at yahoo.com Fri Jan 31 00:03:03 2020 From: timhfl at yahoo.com (Tim H) Date: Fri, 31 Jan 2020 05:03:03 +0000 (UTC) Subject: [Mailman-Users] Mailman on TMDHosting.com In-Reply-To: <3c951505-1a79-6739-b7ad-5c5cd309b594@bmrb.wisc.edu> References: <633f1ff6-05a2-d4ef-3dcf-82262c51f797@aresti.com> <3c951505-1a79-6739-b7ad-5c5cd309b594@bmrb.wisc.edu> Message-ID: <967489867.526341.1580446983036@mail.yahoo.com> I just moved a cluster of domains to TMDHosting.com I had two Mailman mailing lists on the old service.? I made a gziped tarball of the entire account using the usual tool. Staff at TMD brought it over and in minutes all my files were in place.? But. They do not have Mailman in cPanel. They do not have Mailman available in Softalicious.? This is a shared hosting type of account.? I don't have root access to the server.? Their suggestion was to create an email address the same as the mailing list address, then use that to set up BCC to a group of contacts in Roundcube.?? So I tried to create mymailinglist at mydomain.com I could not create the address. Instead I got an error message saying a mailing list with that address already exists.?? But the address does not show up in the list of email addresses in cPanel, so, I cannot delete it. I didn't think about the Mailman mailing lists when I set up to do the transfer.? I took the time to save the member lists and some of the archives, but I should have gone ahead and deleted the lists. I did not suspect that the new service would not have Mailman.? Every web service provider I've been with in years and years has had Mailman.? So - what now?? Anyone on TMDHosting?? Have you been where I just landed? Thanks. Tim? From evanbhansen at gmail.com Fri Jan 31 11:09:39 2020 From: evanbhansen at gmail.com (Evan Hansen) Date: Fri, 31 Jan 2020 10:09:39 -0600 Subject: [Mailman-Users] Changing the send email address from 2.1 Message-ID: So when I went to the FAQ page it told me to select Non-Digest options and go and select full personalization, however that isn't on the Non-digest page nor could I locate it anywhere else within version 2.1.27. All i want to do is modify the address my emails come from https://wiki.list.org/DOC/How%20do%20I%20hide%20the%20fact%20that%20I%27m%20using%20a%20mailing%20list%20management%20system%3F From mark at msapiro.net Fri Jan 31 12:31:14 2020 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 31 Jan 2020 09:31:14 -0800 Subject: [Mailman-Users] Changing the send email address from 2.1 In-Reply-To: References: Message-ID: On 1/31/20 8:09 AM, Evan Hansen wrote: > So when I went to the FAQ page it told me to select Non-Digest options and > go and select full personalization, however that isn't on the Non-digest > page nor could I locate it anywhere else within version 2.1.27. All i want > to do is modify the address my emails come from The Personalization options are only available if the site allows it. If you have access to Mailman's mm_cfg.py, you an add OWNERS_CAN_ENABLE_PERSONALIZATION = Yes to enable this, but if this is not your server, that is probably not possible. In any case, Full Personalization only affects the To: header of the delivered mail, not the From: You can hide the address of the sender of the post by setting anonymous_list to Yes on the ewb admin General Options page. If that is not what you want, please explain in more detail what you do want. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Fri Jan 31 12:43:03 2020 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 31 Jan 2020 09:43:03 -0800 Subject: [Mailman-Users] Mailman on TMDHosting.com In-Reply-To: <967489867.526341.1580446983036@mail.yahoo.com> References: <633f1ff6-05a2-d4ef-3dcf-82262c51f797@aresti.com> <3c951505-1a79-6739-b7ad-5c5cd309b594@bmrb.wisc.edu> <967489867.526341.1580446983036@mail.yahoo.com> Message-ID: On 1/30/20 9:03 PM, Tim H via Mailman-Users wrote: > I just moved a cluster of domains to TMDHosting.com > I had two Mailman mailing lists on the old service.? I made a gziped tarball of the entire account using the usual tool. Staff at TMD brought it over and in minutes all my files were in place. > But. They do not have Mailman in cPanel. As far as I know, every cPanel installation has Mailman 2.1. The issue may be that they just dropped your files into somewhere in /usr/local/cpanel/3rdparty/mailman. You can't just do that. cPanel's Mailman is different enough that the config.pck files aren't directly compatible and the file names and or locations maybe different to. See . Also, there are others on this list who are much more knowledgeable about cPanel Mailman than I am, and they may chime in. > So I tried to create mymailinglist at mydomain.com > I could not create the address. Instead I got an error message saying a mailing list with that address already exists. Which indicates cPanel is aware of it. > But the address does not show up in the list of email addresses in cPanel, so, I cannot delete it. You need advice from someone who knows more about Mailman in cPanel than I do. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Fri Jan 31 13:26:02 2020 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 31 Jan 2020 10:26:02 -0800 Subject: [Mailman-Users] acceptable_aliases does not seem to work (or more likely I don't understand) V2.1.23 In-Reply-To: <60a04924-5d22-3304-e679-a0f6bd046a25@wolf-rock.com> References: <60a04924-5d22-3304-e679-a0f6bd046a25@wolf-rock.com> Message-ID: <1b39a85e-f70f-c298-b5af-4cc0bf63b5e9@msapiro.net> On 1/30/20 7:29 PM, stinga wrote: > G'day all, > > I can't seem to get acceptable_aliases to work... > > > (domain names changed to protect the innocent, but all match up) > > comm at lists.lf.me = List email address > info at lf.me = Google group (google group has one email address which is > comm at lists.lf.me > info at lf.me is a member of the mailman list and is set for nomail > > User another at domain.com sends email to info at lf.me > > List receives email and bounces with: > > ??? List:??? comm at lists.lf.me > ??? From:??? another at domain.com > ??? Subject: Testing > ??? Reason:? Post by non-member to a members-only list > > The above is correct as user another at domain.com is not a member of the > mailman list And that is the entire issue. acceptable_aliases and require_explicit_destination have nothing to do with this. > In the email header there is > To: > > I have in acceptable_aliases (tried various things) > info at lf.me > "info at lf.me" > .*info at lf.me.* > > and require_explicit_destination is yes > > I believe that should allow email sent to info at lf.me to be accepted by > the list, maybe I am reading this all wrong? All that does is avoid the message's being held for "implicit destination" it doesn't bypass other checks. > If I am doing this wrong how do I get a google email to send to mailman > and be accepted? There are a few of choices. You can set Privacy options... -> Sender filters -> generic_nonmember_action to Accept in order to accept posts from any nonmember, but you may not want that. You can ensure that everyone sending mail to info at lf.me is a member of the comm at lists.lf.me list. You can make use of the fact that mailman considers a post to be from a member if any of the From:, Reply-To: Sender: or envelope sender addresses is a list member. Posts from google groups generally have no Sender: header, and the envelope sender is something like 'info+bncbcn2p7unuujrbfxhspsakgqe7gew6fa at googlegroups.com' where the 'bncbcn2p7unuujrbfxhspsakgqe7gew6fa' may not be constant. However, messages from Google Groups have a Reply-To: groupname at googlegroups.com header. If that address is a member of your list, it should be OK. You say info at lf.me is a member of your list. Is that an address you control which forwards to the google group?. If so, you want to make groupname at googlegroups.com a member of your list set to nomail. If in fact by info at lf.me you mean the actual groupname at googlegroups.com address, then I don't know what the problem is. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From evanbhansen at gmail.com Fri Jan 31 13:40:59 2020 From: evanbhansen at gmail.com (Evan Hansen) Date: Fri, 31 Jan 2020 12:40:59 -0600 Subject: [Mailman-Users] Changing the send email address from 2.1 In-Reply-To: References: Message-ID: It will according to the mailman website. all I want is for my mailing list emails to be sent from my email as opposed to a bounce-mail at domain.com On Fri, Jan 31, 2020 at 12:31 PM Mark Sapiro wrote: > On 1/31/20 9:32 AM, Evan Hansen wrote: > > problem is my host has root access disabled and I can't get to that file > > without ssh commands and knowing the file location > > That doesn't matter because if I understand correctly, enabling Full > Personalization won't accomplish what you want anyway. Please follow up > on the list with more detail as to exactly what you want. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > From brian_carpenter at emwd.com Fri Jan 31 13:27:18 2020 From: brian_carpenter at emwd.com (Brian Carpenter) Date: Fri, 31 Jan 2020 13:27:18 -0500 Subject: [Mailman-Users] Mailman on TMDHosting.com In-Reply-To: <967489867.526341.1580446983036@mail.yahoo.com> References: <633f1ff6-05a2-d4ef-3dcf-82262c51f797@aresti.com> <3c951505-1a79-6739-b7ad-5c5cd309b594@bmrb.wisc.edu> <967489867.526341.1580446983036@mail.yahoo.com> Message-ID: <3e09bc10-c8e5-be26-974c-414a0f74c99a@emwd.com> On 1/31/20 12:03 AM, Tim H via Mailman-Users wrote: > I just moved a cluster of domains to TMDHosting.com > I had two Mailman mailing lists on the old service.? I made a gziped tarball of the entire account using the usual tool. Staff at TMD brought it over and in minutes all my files were in place. > But. They do not have Mailman in cPanel. They do not have Mailman available in Softalicious.? This is a shared hosting type of account.? I don't have root access to the server. > Their suggestion was to create an email address the same as the mailing list address, then use that to set up BCC to a group of contacts in Roundcube. > So I tried to create mymailinglist at mydomain.com > I could not create the address. Instead I got an error message saying a mailing list with that address already exists. > But the address does not show up in the list of email addresses in cPanel, so, I cannot delete it. > I didn't think about the Mailman mailing lists when I set up to do the transfer.? I took the time to save the member lists and some of the archives, but I should have gone ahead and deleted the lists. I did not suspect that the new service would not have Mailman.? Every web service provider I've been with in years and years has had Mailman. > So - what now?? Anyone on TMDHosting?? Have you been where I just landed? > Thanks. > Tim > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at python.org > https://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > Unsubscribe: https://mail.python.org/mailman/options/mailman-users/brian_carpenter%40emwd.com Hi Tim, Screenshots of what you are seeing would be helpful. Are you sure Mailman is not accessible via cPanel? They are under Mailing Lists in the Email section of cPanel. Mailing lists and email accounts are treated as separate services on a cPanel server. Also Mailman is not available via Softaculous. -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/ From mark at msapiro.net Fri Jan 31 14:03:34 2020 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 31 Jan 2020 11:03:34 -0800 Subject: [Mailman-Users] Changing the send email address from 2.1 In-Reply-To: References: Message-ID: <2b777bc3-7168-2610-a920-edfa008dc522@msapiro.net> On 1/31/20 10:40 AM, Evan Hansen wrote: > It will according to the mailman website. If that's the case, that FAQ needs updating/correcting. I'll look into it. > all I want is for my mailing list > emails to be sent from my email as opposed to a bounce-mail at domain.com Mail is sent with envelope from listname-bounces at example.com to enable automated bounce processing. It also contains that address in Sender: and Errors-To: headers. Normally issues with the display of this address in mail clients are due to the Sender: header. If your Mailman is 2.1.14+ and the host has not changed the default, there will be an include_sender_header setting near the bottom of the list admin General Options page. Setting that to No may solve this for you. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan