Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: Bad Signature with Gmail

by Mark Sapiro

On 9/19/20 12:33 PM, Massimo Zappalà wrote: > Hi Mark, thanks for the reply. > > my /etc/opendkim.conf > AutoRestart Yes > AutoRestartRate 10/1h > UMask 002 > Syslog yes > SyslogSuccess Yes > LogWhy Yes > Canonicalization relaxed/simple > ExternalIgnoreList refile:/etc/opendkim/TrustedHosts > InternalHosts refile:/etc/opendkim/TrustedHosts > KeyTable refile:/etc/opendkim/KeyTable > SigningTable refile:/etc/opendkim/SigningTable > Mode sv > PidFile /var/run/opendkim/opendkim.pid > SignatureAlgorithm rsa-sha256 > UserID opendkim:opendkim > Socket inet:12301@localhost > > > my /etc/opendkim/SigningTable > *(a)catania.linux.it mailselector._domainkey.catania.linux.it Assuminng your list's domain is catania.linux.it, what you need to do to enable DKIM signing of this message is add SenderHeaders List-Post,Sender,From to /etc/opendkim.conf > full email django error > Internal Server Error: /hyperkitty/api/mailman/archive > > OperationalError at /hyperkitty/api/mailman/archive > (1366, "Incorrect string value: '\\xF0\\x9F\\x98\\xB1\\xF0\\x9F...' for column `mailman3web`.`hyperkitty_email`.`content` at row 1") Unfortunately, the rest of the detail doesn't help. What we need to see is the raw message. You should be able to find it in Mailman's var/archives/prototype/<list_address/new/ directory, perhaps by timestamp or something in the headers. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: Re-enable member after bouce processed disable

by Mark Sapiro

On 12/9/21 6:07 AM, Henrik Rasmussen wrote: > Recently I upgraded Mailman to GNU Mailman 3.3.4 (Tom Sawyer) (Postorius: 1.3.5 and HyperKitty: 1.3.4) which is now processing bounces. > > When a member have been disabled due to bounces, how is the member re-enabled? I would guess it would be under the "Users -> Members -> Member options -> Delivery status", but theses are both (Enabled and disabled) unchecked, not indicating whether or not the member is either or. You are looking at the user's list based preferences. If one of these is unset, it falls back to address based preferences and from there to the user's global preferences. You can see all of these for yourself at the Mailman settings choice in the dropdown at your user name, but for another list member you only see the list based preferences. > How do I or the list admins re-enable a bounce-disabled member? Just set the member's delivery status on the page you see to Enabled. Even though it was not previously shown as Disabled by Bounces, it will be enabled. Likewise the member can set her Delivery status to Enabled. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

[MM3-users] Re: mailing list aliases

by Mark Sapiro

On 01/19/2018 03:09 PM, Dmitry Makovey wrote: > Not sure whether to mark this "SOLVED" yet - but when I manually updated > postgres DB with the aliases I wanted - everything started to work as > expected. > > so it does sound like a bug in mailman-core 3.3.0 . Shall I file it or > was it already fixed in 3.3.1 (anouncement page didn't list that fix) As far as I know, this is not a bug in core. It is <https://gitlab.com/mailman/postorius/issues/58> however, this may in fact be a bug in the REST API in which case I don't think it's fixed in API 3.3.1 >> 2. Related to #1 - we've migrated our mailing lists from foo(a)my.com to >> foo(a)lists.my.com however we've preserved old addresses. But in new setup >> mail sent in gets stopped for moderation with: "X-Mailman-Rule-Hits: >> implicit-dest" . What's the best course of action here to get mailing >> list respond to multiple email addresses? acceptable_aliases is the way to address this, but as you note, it can't be properly set via Postorius and possibly via REST. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 1 month

[MM3-users] Re: list footer questions

by Mark Sapiro

On 6/7/20 3:22 PM, kelly.close(a)lrewater.com wrote: > Well, Glory Be! My .cfg settings were fine but the public.template table was empty (I'm using PostgreSQL and accessing it with pgAdmin). I had not considered that there needed to be database content representing the template but it makes sense. Everything else is in there, which is the whole reason why we went with Mailman3 in the first place. > > After manually creating this record in the public.template table it WORKED!!! > name = list:member:regular:footer > context = f2p2-test.udfcd-lists.org > uri = file:////var/lib/mailman3/templates/lists/f2p2-test.udfcd-lists.org/en/list… > (username and password were left blank) username and password are only required for basic auth to the URI if needed so blank is correct. However, you shouldn't have needed to do that. I only mentioned it in case there was an entry for the name and context with a URI pointing elsewhere. The default if there is no entry is to use Mailman's normal search rules which include templates/lists/<list-id>/en/list:member:regular:footer.txt. So I have to think that without that entry, it was searching a different templates/ directory. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

[MM3-users] Re: Hyperkitty 403 Forbidden Error

by Mark Sapiro

On 6/24/20 8:30 AM, Kelly Close wrote: > I suspect then that my MAILMAN_ARCHIVER_FROM setting is deficient or... > that ACCOUNT_DEFAULT_HTTP_PROTOCOL variable is a new one to me - I don't > think I have that set anyplace. Perhaps that would have helped? I don't think so. ACCOUNT_DEFAULT_HTTP_PROTOCOL is a Django allauth setting and I think only affects things like logging in to Django. MAILMAN_ARCHIVER_FROM is definitely relevant. > I'm going > to leave it be for now since the listener did the trick, but I will also > copy these remarks into my Ubuntu 18.04 Mailman3 setup guide which just > keeps getting better over time! Thanks. The bottom line here is if the only thing that changed that allowed things to work was creating a virtual host in Apache for 127.0.0.1:80 to not redirect to https, then Mailman core must have been (must be) going to port 80 (http). You've probably already done this more than once, but I suggest giving the following command mailman conf -s archiver.hyperkitty -k configuration This will print the path to the mailman-hyperkitty configuration file. Look in that file for the base_url: setting and verify that it has an https scheme. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

[MM3-users] Re: Filter who can send on mailman3 list?

by Mark Sapiro

On 4/7/21 11:27 PM, Marcus Granath wrote: > It seems like the version used is: Postorius Version 1.1.2 Current Postorius is 1.3.4. If you can't upgrade, someone with shell access to the server can do this with `mailman shell` > What I basically want to achieve is that my "sendmail" script (executed from linux) will send announce-mails to this mailing list - and will set an "pseudo-address" (not my own name and address) as sender of this e-mail, i.e "ABC Announcement <no-reply(a)abc.com>" - and to get this "pseudo-mail" to be one of the accepted users (together with me and some team mates with real addresses) to send on the list - one option I understood was to use the "non-member" user for this "ABC Announcement <no-reply(a)abc.com>". > > But in my web-interface (as described above), I cannot find where to add and manage such user (non-member). > Or can I use some other API (then the web-page) to do that kind of operation? ;-) Just add the no-reply(a)abc.com address as a member and set its delivery status to disabled. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Mark Sapiro

On 10/22/22 09:35, Onyeibo Oku wrote: > > Strangely, all files in /opt/mailman/venv belong to the mailman group > > ls -lh /opt/mailman/venv/lib/python3.10/site-packages/zope* > -rw-r--r--. 1 mailman mailman 529 Oct 19 18:31 /opt/mailman/venv/lib/python3.10/site-packages/zope.component-5.0.1-py3.8-nspkg.pth > -rw-r--r--. 1 mailman mailman 529 Oct 19 18:31 /opt/mailman/venv/lib/python3.10/site-packages/zope.configuration-4.4.1-py3.9-nspkg.pth > -rw-r--r--. 1 mailman mailman 529 Oct 19 18:31 /opt/mailman/venv/lib/python3.10/site-packages/zope.event-4.5.0-py3.6-nspkg.pth > -rw-r--r--. 1 mailman mailman 529 Oct 19 18:31 /opt/mailman/venv/lib/python3.10/site-packages/zope.hookable-5.2-py3.10-nspkg.pth > -rw-r--r--. 1 mailman mailman 529 Oct 19 18:31 /opt/mailman/venv/lib/python3.10/site-packages/zope.i18nmessageid-5.0.1-py3.10-nspkg.pth > -rw-r--r--. 1 mailman mailman 529 Oct 19 18:31 /opt/mailman/venv/lib/python3.10/site-packages/zope.interface-5.5.0-py3.10-nspkg.pth > -rw-r--r--. 1 mailman mailman 529 Oct 19 18:31 /opt/mailman/venv/lib/python3.10/site-packages/zope.schema-6.2.1-py3.8-nspkg.pth > > and so it goes in the subdirectories. The specific error you reported refers tp /opt/mailman/venv/lib/python3.10/site-packages/zope.i18nmessageid-5.0.1-py3.10.egg-info/PKG-INFO what does ``` ls -l /opt/mailman/venv/lib/python3.10/site-packages/zope.i18nmessageid-5.0.1-py3.10.egg-info/PKG-INFO ``` show? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: Mailman3 not able to deliver emails sent through list, but moderation notifications

by Mark Sapiro

On 11/26/22 05:09, Daniel Böhmer wrote: > > During startup /var/log/mailman3/mailman.log receives: > >> Cannot connect to SMTP server localhost on port 25 ... > I found this article stating the the SMTP error message > might be misleading: > https://blog.tfiu.de/mailman3-cannot-connect-to-smtp-server-localhost-on-po… > > How to further debug this? > What could be wrong with my Mailman3 instance and how to fix it? The article is relevant and mentions the most likely issue which is lack of permission on one or more message templates. Everything in Mailman's var/ directory should be owned by Mailman's user:group - normally `list:list` in Debian packages. I'm only guessing here, but I suspect you ran `mailman import21` at some point as `root`. Never run `mailman` commands as `root`. Only run them as the Mailman user - `list` in Debian packages. Note that Mailman core in Debian Buster is 3.2.1. Since 3.3.5, "The mailman command will refuse to run as root unless the new --run-as-root option is specified." in order to help avoid this issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: Inaccessible User Profile

by Mark Sapiro

On 2/14/26 08:02, awingnut wrote: > I have a long time user that cannot access their profile. When I click > on users/members then that user as superuser, I get this error. > > Page not found > > This page either doesn't exist, or it moved somewhere else. It appears you may have an older version of the Users->members page cached in your browser or somewhere. > When I click that uers manage button, the page comes up but it says > there are no subscriptions. This user was subscribed as of couple of > days ago. Can this be fixed via admin functions? It appears the user was somehow unsubscribed. Unfortunately, Mailman's subscribe.log (by default part of mailman.log) is incomplete. See https://gitlab.com/mailman/mailman/-/issues/1143 This is fixed for the next release (3.3.11) but unless you've installed Mailman core from the head of the GitLab branch you don't have the fix. Even so, grepping Mailman's logs for the user's address may give a clue as to how the user was unsubscribed. To re-subscribe the user, you can use Postorius Mass operations->Mass subscribe or the command line `mailman addmembers`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 week, 5 days

[MM3-users] Re: [Mailman-Users] Re: Member posting to a list but address not in membership list.

by Mark Sapiro

On 1/12/22 7:42 PM, Adam Morris wrote: > Hi Mark, > I've looked in all these places and the address isn't anywhere. (please keep the thread on the list) Then the address that's posting isn't what you think it is or something in your installation is broken. As I said, it could be that Reply-To: or Sender: is the list member, but depending on list settings, these things get overwritten in mail from the list, so you can't really know. If something is broken, you need to discuss this with your hosting provider who, unfortunately, may be no help. Many, not all, cPanel hosts offer mailman because it comes with cPanel, but actually know nothing about Mailman. See https://wiki.list.org/DOC/Mailman%20and%20CPanel > On 13-January-2022 11:31, Mark Sapiro wrote: >> On 1/11/22 7:51 PM, Adam Morris wrote: >>> I have someone who is posting to a list I run. >>> I subscribed them originally but their address doesn't show up in the >>> list of members so I can't change moderation status etc. >>> Where else could I look to find their address? >> >> >> The first check on a post is if any of the address in From:, Reply-To: >> or Sender: headers or the envelope sender is a list member, i.e. in >> the web admin Membership List. If so, that member's moderation is >> applied. If not, the next check is if the From:the *_these_nonmembers >> lists under Privacy options... -> Sender filters and finally Privacy >> options... -> Sender filters -> generic_nonmember_action. >> >> If a post to the list is being accepted without being held for >> moderation, either some address in From:, Reply-To: or Sender: headers >> or the envelope sender is in the Membership List with `mod` unchecked, >> or the From: or possibly Sender: address is in accept_these_nonmembers >> or generic_nonmember_action is Accept. >> > > -- > > Adam Morris > Mobile: 0414 431105 > Email, iMessage & FaceTime > adam(a)damorris.com > -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

Search results for query "sapiro"