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

[MM3-users] Re: installation

by Mark Sapiro

On 11/22/20 3:54 PM, Henry S wrote: > > Now I am trying to figure out how to configure mailman+postfix to pass > the unnecessarily convoluted world of spam-free certification and ip > blockings by those 'security lawmakers'. > > Any suggestions on how to not be blocked by gmail, hotmail, etc? I have > used DKIM (no signing yet), SPF, DMARC to no avail. Maybe not an > appropriate question to this mailman list. You need a fixed IP address and "full circle" aka "forward confirmed reverse DNS" <https://en.wikipedia.org/wiki/Forward-confirmed_reverse_DNS>. You also need to DKIM sign your outgoing mail from your domain and publish an SPF record allowing your IP as a sender for your domain. I'm not sure, but publishing a DMARC policy, even if it's p=none is possibly helpful with some recipient domains. Beyond that check your IP for blacklisting with a tool like <http://mxtoolbox.com/blacklists.aspx> and monitor your mail logs for blocked email and follow up with the blockers to get unblocked. Things get better over time as your server develops a reputation. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: is there a mailman command/setting to periodically clean archives?

by Mark Sapiro

On 12/29/21 3:58 PM, William Oliver wrote: > > I'd like to delete all my archives that are more than a certain age, > e.g. more than a week old. I can easily do that with a cron job, > deleting old files in > > > /opt/mailman/mm/var/archives/prototype/testlist(a)example.com/* > > which is, as far as I can see the only place archive emails live. Those are emails archived in the prototype archiver. That's all the prototype archiver does - store the mail there. The HyperKitty archived emails are stored in the mailmanweb database in the hyperkitty_email table. Attachments are in the hyperkitty_attachment table and other tables are also involved. > However... I was wondering if there was some mailman command or config > variable that would accomplish this without using cron. The cron will work for the prototype archives, but it's probably easier to just disable the prototype archiver. For HyperKitty, see the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: URL-lines in templates get folded

by Mark Sapiro

On 10/18/22 06:52, Frank Steinberg wrote: > Hi, > > I’ve added links to some templates to give owners and moderators > shortcuts to the postorius UI for moderation tasks, e.g., I’ve added > > https://lists.xxx.de/postorius/lists/$list_id/held_messages <https://lists.xxx.de/postorius/lists/$list_id/held_messages> > > Unfortunately those lines seem to exceed a certain limit and get > folded, so that they appear as, e.g. > > https://lists.xxx.de/postorius/lists/$list_id/held_ <https://lists.xxx.de/postorius/lists/$list_id/held_> > messages > > (or similar) and are not directly useful. How are you editing the templates? I.e., are you editing them via Postorius or by putting them in Mailman's var/templates/ directory or ?? Also are those lines of the form https://... <https://...> what you are entering or is that duplication and artifact of your mail client? You should be entering just a URL either with or without angle brackets, but not both. Is the folding actually in the raw message or is it an artifact of the mail client viewing the message? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[MM3-users] Re: Different Mail Domain Cause Key Error

by Mark Sapiro

On 4/21/20 10:12 PM, Torge Riedel wrote: > Am 21.04.20 um 23:08 schrieb Brian Carpenter: >> Maybe I can get the client to agree to use the web domain as part of >> their list address. > > Hi, > > maybe it is a solution for you what I did on my side (since it was > already the setup for mailman2 my customer is happy with it): > > Set everything up in mailman3 with lists.domain.com and define in > postfix (if you use postfix, others should support it also) aliases from > - let's say - list1(a)domain.com -> list1(a)lists.domain.com for each mail > list. > > In the list setup in mailman3 (available via postorius) define > list1(a)domain.com as an allowed alias for list1(a)lists.domain.com This is a good workaround, however to be complete, you may also want MTA aliases for the list1-*(a)domain.com addresses. Note, I'm currently working on a fix for <https://gitlab.com/mailman/postorius/-/issues/394>. Hopefully that will be in the next Postorius release. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: Mailman 3 - docker container - sync_members

by Mark Sapiro

On 10/20/20 9:45 AM, holman(a)uw.edu wrote: > I would like to populate list members via the Mailman 3 sync_members script. > > However, I am using Mailman 3 in docker containers and it doesn't appear to have this command. How are others completing this synchronization? I'm not sure what version of Mailman core is in the Docker containers. According to https://asynchronous.in/docker-mailman/NEWS.html, Mailman core is docker version 1.1.1 released Aug 9 2017 which is about the time of MM Core 3.1.0 which is quite old and has neither a `mailman syncmembers` (introduced in core 3.3.2) command nor the older `mailman members --sync` option (introduced in core 3.3.1). There are `rolling releases` <https://asynchronous.in/docker-mailman/#rolling-releases> which should have these. > Searching this list I found a reasonable approach: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > Is there a different/preferred solution? The script at <https://gitlab.med.stanford.edu/irt-public/mailman-tools/-/blob/master/sync…> seems fine. The alternative is to update your Docker container to one including the appropriate `mailman` sub-command. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: hyperkitty url not found

by Mark Sapiro

On 3/14/22 12:24, Eggert Ehmke wrote: > So I have to use the external url via https? > > I can access the address > https://lists.[1]<tld>_/mailman3/archives/api/_ > > so I set: (<tld> is my existing domain) > > base_url: https://lists.<tld>/mailman3/archives > Now I get this in the mailman.log: > > Mar 14 19:40:21 2022 (166928) ACCEPT: <12973151.uLZWGnKmhe@wookie> > Mar 14 19:40:21 2022 (166932) HyperKitty failure on https://lists.<tld>/mailman3/archives/ > api/mailman/urls: <html><title>Forbidden</title><body> > <h1>Access is forbidden</h1><p>Please check the IP addresses > assigned to MAILMAN_ARCHIVER_FROM in the settings file. > </p></body></html> (403) > In my settings I have my local IP and 127.0.0.1 and ::1. What should I set there? Is whatever is proxying to Django forwarding the IP and are you sure it matches the "my local IP" you set? You might instead try setting base_url to http://localhost:8000/mailman3/archives/ or more likely http://localhost:8000/archives/ (I.e. whatever your webserver proxies the https://lists.<tld>/mailman3/archives/ url to. -- 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: [MM3-users]Exim, Mailman3 and missing Message-ID:

by Mark Sapiro

Rob's reply in this thread was garbled due to <https://gitlab.com/mailman/mailman/issues/616>. The text of the reply is quoted below. On 7/27/19 12:54 AM, Rob Lister wrote: > > One thing that does occur to me is that my exim header fudge will > probably cause the Message-ID header to move around from its original > position, and if someone is doing hashing or actually validating (gpg > signing?) the headers haven't been tampered with, then it might > complain, since although the message-id hasn't changed, it might be in a > different place in the headers. > > Then again, mailman can make plenty of other modifications and additions > to the headers anyway, so I'm not sure it matters. > > Probably the more correct way to do it is only add a new header if it's > missing, and if it's there, leave it alone. > > This is probably possible in exim with some more variables and a lot of > nested curly braces... -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

[MM3-users] Re: Delete Django profiles not signed up to a list

by Mark Sapiro

On 1/1/21 4:41 PM, Andrew Hodgson wrote: > > I don't want to add captchas to the form right now but is there any way to clean out these users from the database perhaps periodically based on whether the accounts are subscribed to any list? I have attached a script that will delete users from Django's user database (the auth_user table) if there is no Mailman user with the Django user's email address or if there is a Mailman user but it's not a member, nonmember, owner or moderator of any lists. The setting DELETE_MAILMAN_USER controls whether it will also delete the corresponding Mailman user that's not a member, nonmember, owner or moderator of any lists. If set to True, it will. The script has a few installation specific paths that may need adjustment. Also, if Mailman is installed in a virtualenv, the script needs to be run by the python in that virtualenv so that the imports all work (as with the shebang in the script). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: 400 Bad Request when administrator tries to selectively override member options

by Mark Sapiro

On 5/8/21 1:17 PM, ieso(a)johnwillson.com wrote: > This is probably Design Intent, but I'd just like to confirm. > > When an administrator submits partial 'member options', it comes back with the details of a 400 - Bad Request, indicating essentially that all of the member options must be set. > > Screenshot: https://ibb.co/pzM5Z4m > > It would be a bit smoother to check that all values are selected before sending the request, and inform the administrator that they cannot selectively override member settings for their list. > > But most importantly, I would like to confirm that nothing is corrupt/broken in our implementation. What Postorius version is this? I just tried it on Postorius 1.3.5b1 (The HEAD of the gitlab branch), and for a user with no options at all set at the list level, I was able to set `Receive own postings` only with no problem. I think this is https://gitlab.com/mailman/postorius/-/issues/178 fixed in Postorius 1.2.0 by https://gitlab.com/mailman/postorius/-/merge_requests/321 -- 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

[MM3-users] Re: # comment allowed in a template file?

by Mark Sapiro

On 7/24/20 3:19 AM, skenny(a)scss.tcd.ie wrote: > > I'm running Mailman 3 in maxking's Docker container. I'm also using Puppet to do as much configuration as possible, so I'd like to add a comment to the file that reads something like: > # This file is managed by Puppet. > > Is it ok to do this? I may not have searched the docs enough, but I couldn't find anything relating to comments. If you mean can you add a '#' line that won't be part of the actual rendered template, the answer is No. > One other observation in case it's any use: Initially, I created the template files with owner set to "root". This resulted in postings to lists getting stuck in mailman-core. It's vital that these files are owned by user "mailman". Once I changed the owner of the file to the latter, everything worked. I don't think they need to be owned by 'mailman' as long as they are readable by 'mailman' -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

Search results for query "sapiro"