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

[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

6 years, 1 month

[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, 8 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, 4 months

[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

5 years, 1 month

[MM3-users] Re: Virtual alias + shell

by Mark Sapiro

On 5/26/23 4:36 AM, alopez(a)ac.upc.edu wrote: > Hello, > I want to have a mailman configured together with virtual alias. To do that I need to use alias_domain. > I have tried to do it with mailman shell. The domain seams to be created but when I leave the shell and enter again, the domain is not longer there. Because you are leaving mailman shell with exit() which doesn't commit changes. You deed to either explicitly commit with `commit()` or exit with control-D. Recent mailman shell will report in its banner 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. > On the other hand, If I create a domain in administrator interface, it is not listed in the shell. If I create in the web interface, which field correspond to the alias_domain : Domain Name, Display Name , Mail domain? Your Postorius is too old to support alias_domain, and your Mailman core may be too - requires core >= 3.2.0. -- 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: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by Mark Sapiro

On 6/16/20 5:03 PM, kelly.close(a)lrewater.com wrote: > I resolved this myself with a search that turned up a 2018 post from Mark that suggested typing "mailman aliases" to create the hash/alias/lookup table/file things in /var/lib/mailman3/data (that's where they are on Ubuntu 18.04). I looked in that folder and sure enough it was empty so I typed "sudo mailman aliases" which did indeed create the 4 things that needed to be there: > postfix_domans > postfix_domains.db > postfix_lmtp > postfix_lmtp.db > > But, they were owned by root:root and everything else under that /ver/lib/mailman3 folder is owned by "list" so I took a guess changed the ownership on the 4 files to list:list. Because that's how you ran it. Run sudo -u list mailman aliases. > Seems to have worked! I was perplexed about why I had to do this though because these were created automatically last time I did this, but I figured that out too. Current `mailman start` should create the aliases. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: Monthly job failure

by Mark Sapiro

On 6/25/19 4:08 PM, andrew.bernard(a)gmail.com wrote: > Yes I did. So something is out of sync, the job are referring to lists no longer existing. What is this? I'm confused. The subject of this thread is 'Monthly job failure', but your original post said 'I see this error on startup:' Perhaps you are confused in that the error occurs in 'rebuild_mailinglist_cache_for_month'. That is not a monthly job. That is a queued task to rebuild the cached data for a particular 'by month' view. That task is queued whenever a post is added to update the monthly cache for the year and month of the date of the post, and whenever a thread is deleted to update the monthly cache for the year and month of the date the thread was active. I'm guessing here, but I think you have a task queued for a list that no longer exists in HyperKitty. Go to the Django web admin and look at the DJANGO Q section, particularly Queued tasks, but maybe the others too. Maybe there's a task you can delete. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Re: migration

by Mark Sapiro

On 7/30/21 12:06 PM, Dave McGuire wrote: > > Is there a way that I can "dump" the configuration from an existing > mailman3 server, and "import" it into a new instance? I'd really like > to avoid re-doing all of the configuration, etc, as there are quite a > few lists and everything is set up pretty much the way I want it. If you use the same database manager it should be no problem to get a dump of the existing Mailman database to load into the new instance, or if these are on the same server, just point the new instance to the existing database. In either case, the database should be loaded and the Django commands `migrate`, collectstatic`, `compress` and `compilemessages` run[1] before starting Mailman services. Mailman core will run any necessary updates to its database upon startup. You may also need to rebuild the HyperKitty search index with the `update_index` Django command, but you may be able to use the existing one if the search engine is the same. [1] See https://docs.mailman3.org/en/latest/install/virtualenv.html?highlight=colle… et seq. -- 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: mail loops back to myself

by Mark Sapiro

On 6/12/25 05:28, Florian Sukup wrote: > > When I look into the log, first the smtpd receives the message from my > mail client. Then the email is queued. > And then the smtp initiates a TLS layer to send it to the smtpd on the > same machine. For my understanding this cannot be correct. The smtpd at > first should hand it to mailman and not relay it to itself. Is that > correct? That is not correct. Postfix should receive the initial connect and smtp for the list and then transport_maps should tell it to relay the message via lmtp to the configured lmtp_host and lmtp_port (127.0.0.1:8024 per your previously posted mailman.cfg). You have also posted that Postfix main.cf contains transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp What is the content of that file? In particular does it contain mylists(a)lists.yyy.com lmtp:[127.0.0.1]:8024 and is the timestamp of /var/lib/mailman3/data/postfix_lmtp.db >= that of /var/lib/mailman3/data/postfix_lmtp, and have you restarted/reloaded Postfix since updating main.cf? And, is Mailman core running and listening on port 8024? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months

[MM3-users] Re: Implicit destination

by Mark Sapiro

On 08/26/2018 12:54 PM, David Krantz wrote: > > I have a spam-problem like anyone else. Most of the spam my listserver > receives has some kind of impilict destination so the implicit rule > catches most of the spam that way. This is fine. What is not so fine, > however, is that this results in a moderation message to the sender. > I'd like to stop that so that the spammer has no confirmation that the > mail was received. That is not the issue. Sending the held message notice to a spammer, if it reaches the spammer, is probably inconsequential. The issue is that virtually always in spam the sender address is either undeliverable or is the address of an innocent 3rd party. Sending these notices to innocent 3rd parties is called backscatter and is a bad thing. To avoid this backscatter, you can set the list's respond_to_post_requests attribute to False. There are two problems here. One is this setting is not currently exposed in Postorius, and the other is this will also stop desired held message notices such as those from list members. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

Search results for query "sapiro"