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

[MM3-users] Re: Mailman sends Welcome emails, but does not send [List] postings emails

by Mark Sapiro

On 6/7/23 21:30, Nelson Strother wrote: > > Interestingly if I use `systemctl start mailman` thus far the results are: > - the wall clock duration is shorter than when `mailman start` is issued > from the command line, and > -- either that all of the runners remain present once they are started, > -- or I can see in syslog a traceback from each missing runner process > starting from .../mailman/.local/bin/runner and ending with > "flufl.lock._lockfile.NotLockedError: Already unlocked". > > I do not yet understand how to make use of these clues, but at least one > can see an epitaph from each deceased process. The NotLockedError is most likely because a lock has been set with a lifetime and its lifetime has passed and some other process has broken the lock before the original process tries to unlock it. This probably has something to do with the long times to do start/restart. However, the only lock that should be involved is the master lock set by the master watcher, so I don't really understand what might be happening. What is the full traceback from these errors? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

[MM3-users] Re: How to Personalise Email Content with Usernames in Mailman 3

by Mark Sapiro

On 11/17/23 07:03, Zaheer Abbas wrote: > Hello, > > I am currently working with Mailman 3 and looking to enhance the > personalization of the emails sent through our mailing list. Specifically, > I wish to include the recipient's username in the email content, similar to > a personalized greeting (e.g., "Dear [username]"). > > My questions are: > > 1. Does Mailman 3 support the inclusion of personalized data (like > usernames)? You can enable full personalization which will put the recipient's address in the To: header. In addition both Individual and Full personalization allow personalized information in message headers and footers, see https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…. This could be used to add a personalized header, but depending on the MIME structure of the message after content filtering, these may be added as separate MIME parts rather than prepended/appended to the message body. See https://wiki.list.org/x/4030707 for more on this. Mailman has no facility other than the above for modifying message bodies. > 2. If yes, how can I do that? Is there any placeholder for that? See the above links. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: HSTS Missing from HTTPS Server

by Mark Sapiro

On 11/4/24 12:06, jkoral(a)luc.edu wrote: > > My question is, how can enable the Virtual Host for 443 on the server? Or can that configuration be located somewhere else? Or can I just create a new Virtual Host with the added configuration for mailman? For example, this is /etc/apache2/sites-enabled/020-mailman.conf on lists.mailman3.org ``` <VirtualHost *:80> RewriteEngine on RewriteCond %{HTTPS} off [NC] RewriteRule ^/(.*) https://%{HTTP_HOST}/$1 [L,R=permanent] RewriteCond %{SERVER_NAME} =lists.mailman3.org RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent] </VirtualHost> <VirtualHost *:443> SSLEngine on ServerName lists.mailman3.org Alias /static/ /opt/mailman/mm/static/ <Directory "/opt/mailman/mm/static/"> Require all granted </Directory> <IfModule mod_headers.c> RequestHeader unset X-Forwarded-Proto <If "%{HTTPS} =~ /on/"> RequestHeader set X-Forwarded-Proto "https" </If> </IfModule> <IfModule mod_proxy.c> ProxyPreserveHost On ProxyPass "/postorius" "http://127.0.0.1:8000/postorius" ProxyPass "/hyperkitty" "http://127.0.0.1:8000/hyperkitty" ProxyPass "/accounts" "http://127.0.0.1:8000/accounts" ProxyPass "/admin" "http://127.0.0.1:8000/admin" ProxyPass "/user-profile" "http://127.0.0.1:8000/user-profile" ProxyPass "/mailman3" "http://127.0.0.1:8000/mailman3" ProxyPass "/archives" "http://127.0.0.1:8000/archives" ProxyPassMatch "^/$" "http://127.0.0.1:8000/mailman3" </IfModule> Include /etc/letsencrypt/options-ssl-apache.conf SSLCertificateFile /etc/letsencrypt/live/www.list.org/fullchain.pem SSLCertificateKeyFile /etc/letsencrypt/live/www.list.org/privkey.pem </VirtualHost> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: Cron of Mailman notify is not working

by Mark Sapiro

On 1/29/20 12:01 AM, Shashikanth Komandoor wrote: > > I observed that the "notify" subcommand can be run only while I am in the /var/lib/mailman/mailman directory where my mailman core is installed (through GITHUB). I think you mean GitLab, but in any case, the reason for this is you have to be in that directory for the mailman command to find your mailman.cfg file. I deal with this by creating a separate bin/ directory for these commends, in my case /opt/mailman/mm/bin because Mailman is installed in /opt/mailman/mm/, and my /opt/mailman/mm/bin/mailman file contains #!/bin/bash exec /opt/mailman/mm/venv/bin/mailman \ -C "/opt/mailman/mm/mailman.cfg" \ $@ > And moreover I installed all the components of the mailman using the root user only and so there is no mailman user on my machine. > > And hence I wrote the below entry in the crontab directly and found it is working fine. > > 00 08 * * * cd /var/lib/mailman/mailman; /var/lib/mailman/venv3/bin/python /var/lib/mailman/venv3/bin/mailman notify The /var/lib/mailman/venv3/bin/python is probably not needed as /var/lib/mailman/venv3/bin/mailman should contain the shebang line #!/var/lib/mailman/venv3/bin/python -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

[MM3-users] Re: 12/24 hour clock ?

by Mark Sapiro

On 11/28/20 7:18 AM, Per Jessen wrote: > Hi all > > at openSUSE we have recently migrated to mailman3, and we seem to be > having a couple of teething issues: > > a) hyperkitty and postorius both seem to insist on using a 12 hour clock > format, no matter what the user has set. Is there a way of changing it > system-wide ? This is a Django setting. Try TIME_FORMAT = 'H' in settings_local.py. See https://docs.djangoproject.com/en/3.1/ref/settings/#time-format and https://docs.djangoproject.com/en/3.1/ref/templates/builtins/#std:templatef… > b) overriding the default set of footers - despite having set the > template "list:member:regular:footer" to empty for a specific list, I > am still getting the default footers attached. How did you set the template to empty? it works for me in Postorius from the HEAD of the gitlab branch and should work with any Postorius >= 1.3.0 Note that when you set a template in Postorius, it sets the URI in Mailman core for that template to https://<HOST>/<PATH>/api/templates/list/<LIST-ID>/<TEMPLATE-NAME> where the https://<HOST>/<PATH> part is the Django setting for POSTORIUS_TEMPLATE_BASE_URL. Is that URI accessible from the Mailman core host machine? -- 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: Mailman3 doesn't send Mails to users (Debian12 with Plesk)

by Mark Sapiro

On 6/6/24 11:22 AM, Marcus Bautze wrote: > Hi, > > Sorry, that was a wrong information in my mail . I already changed the base url to your suggestion as I wrote the mail (and forgot to change it in the mail) but i‘m getting the same error :-( I have some questions. At https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… you say "Thank you, archiver is now starting. Now there's another problem:". Does this mean messages are being archived in HyperKitty or are they accumulating in (I think the Debian path is) /var/lib/mailman/archives/hyperkitty/spool/? At https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… you say "The Keys are in mailman-hyperkitty.cfg and mailman-web.py and this are the same Keys." To be clear, in mailman-web.py the key is quoted and in mailman-hyperkitty.cfg it is not. E.g., in mailman-hyperkitty.cfg api_key: Some_key and in mailman-web.py MAILMAN_ARCHIVER_KEY = 'Some_key' What are your versions for mailman-hyperkitty and HyperKitty? HyperKitty >= 1.3.5 is incompatible with mailman-hyperkitty < 1.2.0 and if I recall corectly, at least one Debian package was shipped with this incompatibility -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: how to mass change users options ?

by Mark Sapiro

On 4/30/22 02:13, Yvan ♞ wrote: > Hello, I transfered a mailing list from mailman to mailman 3, how can I > change all users options in mass ? > delivery status and receive own posting are blank by default (250 > members is too long one by one..) The `blank` value for for a setting only means that the user has no list based setting for that property. This means either the user's address based value if any applies, otherwise the Mailman global value applies. That said, if you imported the list with `mailman import21`, the Mailman 2.1 settings should have been imported. Finally, you could change a setting for all list members using `mailman shell`. For example ``` $ bin/mailman shell -l list(a)example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list(a)example.com mailing list >>> for member in m.members.members: ... member.preferences.delivery_status = DeliveryStatus.enabled ... member.preferences.receive_own_postings = True ... >>> commit() ``` But this is probably unnecessary as the global settings probably apply and are probably set appropriately. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

[MM3-users] Re: New messages are not archived - may be a path issue

by Mark Sapiro

On 10/20/23 05:31, Wikinaut wrote: > > The built-in template (mailman-hyperkitty.cfg) perhaps needs to be fixed as well (hyperkitty wrong, archive correct)? > # However, if your Mailman installation is accessed via HTTPS, the URL needs > # to match your SSL certificate (e.g. https://lists.example.com/hyperkitty) > # base_url: http://localhost/mailman3/hyperkitty/ > > this line perhaps needs to be changed to > # base_url: http://localhost/mailman3/archives/ I agree that this is confusing because some of our docs recommend that urls.py contain ``` path('postorius/', include('postorius.urls')), path('hyperkitty/', include('hyperkitty.urls')), ``` and docs recommend ``` path('mailman3/', include('postorius.urls')), path('archives/', include('hyperkitty.urls')), ``` I.e. following the first suggestion, you would access Postorius and HyperKitty via `https://www.example.com/postorius/` and `https://www.example.com/hyperkitty/` respectively, but with the second, the urls would be `https://www.example.com/mailman3/` and `https://www.example.com/archives/` respectively. I'm going to address this by adding ``` path('postorius/', include('postorius.urls')), path('hyperkitty/', include('hyperkitty.urls')), ``` to mailman_web's urls.py so the either urls will work. See https://gitlab.com/mailman/mailman-web/-/issues/24 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Re: Welcome message template errors

by Mark Sapiro

On 4/23/24 23:20, Mark wrote: > > The issue is: > > A. With POSTORIUS_TEMPLATE_BASE_URL = > 'http://<REDACTED-PUBLIC-IPv4-ADDRESS>', it sends an empty Welcome > message when a new member is added. > > B. With POSTORIUS_TEMPLATE_BASE_URL = 'https://MYDOMAIN.COM', no Welcome > message gets sent and a timeout error appears on the webpage, although > the new member gets added. I think the difference is http vs https, not the IP vs domain name. Also, with either of these, you are addressing the web server and not the wsgi server. The wsgi server is presumable listening on port 8000 and in the beginning when you had the default POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000' you also got the timeout error and you also got an email to the site owner with 'Site matching query does not exist.' for 'Request URL: http://<REDACTED-PUBLIC-IPv4-ADDRESS>/mailman3/lists/' This leads me to think 'localhost' resolves to <REDACTED-PUBLIC-IPv4-ADDRESS> instead of 127.0.0.1. Also, <REDACTED-PUBLIC-IPv4-ADDRESS> is not in ALLOWED_HOSTS. Have you set ALLOWED_HOSTS in your settings.py? It should be something like ``` ALLOWED_HOSTS = [ "localhost", # Archiving API from Mailman, keep it. "127.0.0.1", "<REDACTED-PUBLIC-IPv4-ADDRESS>", "MYDOMAIN.COM", ] ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

[MM3-users] Re: [Bug] Someone not a member of list is treated as member - strange

by Mark Sapiro

On 8/23/25 11:40, Wikinaut wrote: > > Honestly, I don't think, that addresses (in my current case on top level, but as I understand, this could happen for every "user") should be treated as, sorry for uppercase, MEMBERS, when they are not expressly member of a list with a →distinct← address. > > please let us discuss. Mailman 3 is different from prior Mailman versions in that Mailman 3 has a concept of a person. The person is a user and a user has one or more email addresses one of which is preferred. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/8-mil…>. This corresponds more closely to real life than prior Mailman. If a user is a member of a list with delivery enabled, mail from that list is sent to that user's preferred address. Your own subject recognizes this. You say "Someone not a member of list is treated as member", but the 'Someone', i.e. the person, is a member of the list and should be treated as a member regardless of which of their email addresses they post from. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 4 weeks

Search results for query "sapiro"