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

[MM3-users] Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by Mark Sapiro

On 7/9/22 8:48 AM, kisner(a)live.com wrote: > Thanks! > > OK, ran through again on a vanilla Debian 11.3 install, got this error (I'll try to create the directory and see if I can get past it): > > (venv) mailman@lists:~$ mailman-web migrate > Traceback (most recent call last): > File "/usr/lib/python3.9/logging/config.py", line 564, in configure > handler = self.configure_handler(handlers[name]) > File "/usr/lib/python3.9/logging/config.py", line 745, in configure_handler > result = factory(**kwargs) > File "/usr/lib/python3.9/logging/handlers.py", line 445, in __init__ > logging.FileHandler.__init__(self, filename, mode=mode, > File "/usr/lib/python3.9/logging/__init__.py", line 1142, in __init__ > StreamHandler.__init__(self, self._open()) > File "/usr/lib/python3.9/logging/__init__.py", line 1171, in _open > return open(self.baseFilename, self.mode, encoding=self.encoding, > FileNotFoundError: [Errno 2] No such file or directory: '/opt/mailman/web/logs/mailmanweb.log' Creation of the directory is documented. From https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu… ``` # Make sure that this directory is created or Django will fail on start. LOGGING['handlers']['file']['filename'] = '/opt/mailman/web/logs/mailmanweb.log' ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: "to" Headers for Non-Anonymous lists

by Mark Sapiro

On 6/10/25 09:40, Dan Caballero wrote: > > I've done some testing and this is close to what we need. However, I seem to be having an issue with the option for "Explicit Reply-to set; no Cc added". The messages are still including a Cc field with the sender's email. Is there another setting that affects the Cc field? The difference between "Explicit Reply-to header set" and "Explicit Reply-to set; no Cc added" only affects lists with Personalize = Full. For those cases, the To: in delivered posts is replaced with the recipient's address which means in some cases, the list's posting address is not exposed so we put it in Cc: unless Reply goes to list is "Explicit Reply-to set; no Cc added". This setting is intended for announce type lists where members normally do not post to the list. If DMARC mitigations are applied and Reply goes to list is anything other than No Munging, the original From: will always be added to Cc:. There is no setting to avoid this. This is so reply-all will include the original sender. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 2 weeks

[MM3-users] Re: Renaming a server after building

by Mark Sapiro

On 11/26/21 1:46 AM, Philip Colmer wrote: > > However, although the above works, if I then go back to the *Mailman* > interface and go to /mailman3/domains/, the web interface recreates a > domain for the original domain name that was in place when the server was > created, i.e. we end up with "lists" and "new-lists". > > We've tried deleting that "new-lists" domain, rebooting and trying again > but "new-lists" keeps on being created again. > > What am I overlooking here? Is there a better/approved way to achieve what > we want to achieve? Each list has a mail_host attribute. this is not displayed in Postorius other than as the domain part of the list posting address which is displayed near the top of each page. Is this the new-lists.example.com domain? If so, you probably would need to change it. I think by having mailman domains like new-lists.example.com is asking for trouble. Why don't you set up Mailman on the new server(s) with domains like lists.example.com and just rely on DNS to get to the correct server. -- 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: Migrating from old V2 server to new V3 server. Questions.

by Mark Sapiro

On 11/13/24 18:44, jkoral(a)luc.edu wrote: > > Now I am getting this error in mail.log. I have changed quite a few settings to try and not bother you anymore, but nothing seems to be working. Hopefully this will be an easy one for you. The unknown IP address is our F5 where the mail is coming through. > > 2024-11-13T20:31:15.988423-06:00 lstprdls01 postfix/smtpd[2261655]: connect from unknown[10.18.3.105] > 2024-11-13T20:31:16.486460-06:00 lstprdls01 postfix/smtpd[2261655]: disconnect from unknown[10.18.3.105] ehlo=1 quit=1 commands=2 > 2024-11-13T20:31:18.246010-06:00 lstprdls01 postfix/smtpd[2261655]: connect from unknown[10.18.3.105] > 2024-11-13T20:31:18.708146-06:00 lstprdls01 postfix/smtpd[2261655]: NOQUEUE: reject: RCPT from unknown[10.18.3.105]: 550 5.1.1 <joetest(a)listservnew.luc.edu>: Recipient address rejected: User unknown in local recipient table; from=<jkoral(a)luc.edu> to=<joetest(a)listservnew.luc.edu> proto=ESMTP helo=<CO1PR03CU002.outbound.protection.outlook.com> > 2024-11-13T20:31:18.852290-06:00 lstprdls01 postfix/smtpd[2261655]: disconnect from unknown[10.18.3.105] ehlo=2 mail=1 rcpt=0/1 rset=1 quit=1 commands=5/6 What is joetest(a)listservnew.luc.edu? Is that a list? If so, is it mentioned in Mailman's var/data/postfix_lmtp and is that included in transport_maps and in local_recipient_maps in Postfix main.cf? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

[MM3-users] Re: task runjobs minutely uses 100% cpu

by Mark Sapiro

On 2/10/20 1:37 PM, Bjoern Franke wrote: > > I tried to switch to Xapian, but hyperkitty's update of the index fails > now: > ERROR 2020-02-10 22:35:24,787 25592 hyperkitty.lib.utils Failed to > update the fulltext index: update() got an unexpected keyword argument > 'commit' > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/hyperkitty/lib/utils.py", line > 179, in run_with_lock > fn(*args, **kwargs) > File "/usr/lib/python3/dist-packages/hyperkitty/search_indexes.py", > line 115, in update_index > update_cmd.update_backend("hyperkitty", "default") > File > "/usr/lib/python3/dist-packages/haystack/management/commands/update_index.py", > line 276, in update_backend > last_max_pk=max_pk) > File > "/usr/lib/python3/dist-packages/haystack/management/commands/update_index.py", > line 97, in do_update > backend.update(index, current_qs, commit=commit) > TypeError: update() got an unexpected keyword argument 'commit' > > I didn't find any further relevant configuration options in > https://github.com/notanumber/xapian-haystack/tree/master How did you install Xapian? Did you follow all the Installation and Configuration instructions at <https://github.com/notanumber/xapian-haystack/blob/master/README.rst>? Did you run the Django Admin rebuild_index command after installing and setting up Xapian? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Re: Mailman3 not working following distribution upgrade from Debian 10 to 11.

by Mark Sapiro

On 2/18/22 08:43, gordon(a)dickens.com wrote: > > My only remaining problem is that I cannot access the individual mailing lists. That is, when I navigate a list and click on the list name then my browser displays: > > "Server error > An error occurred while processing your request." > > Concurrent with the above browser display, mailman3 sends an email to the system admin with the subject: > > "[Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/lists/list_local_name.domain.tld" > > This email and my logs now complain about: > > "Internal Server Error: /mailman3/lists/list_local_name.domain.tld/ > MultipleObjectsReturned at /mailman3/lists/list_local_name.domain.tld/ > get() returned more than one EmailAddress -- it returned 3!" > > Also, I get the same errors after I create a new mailing list as well. > > I hope that Mark and/or somebody here can offer up suggestions on what I need to do to fix this. Any suggestions would be very much appreciated! It seems like a database issue. I would like to help. What is the Traceback from that error? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

[MM3-users] Re: Change 'from' server for outgoing messages

by Mark Sapiro

On 3/11/23 08:18, Benjamin Goldberg wrote: > > Signup confirmation and welcome emails are working. They appear to be coming from the intended host, which is 757pug.org Welcome messages are sent from Mailman core the same way as posts. > But emails from the mailing lists are being blocked by the smtp relay. I think it's because they are not coming from 757pug.org; They are coming from smart.bnmng.com Assuming the Mailman core list name is xxx(a)757pug.org, Mailman will send both posts and welcome messages with envelope from xxx-bounces(a)757pug.org if not VERPed or if VERPed, xxx-bounces+user=example.com(a)757pug.org. The only difference is the From: header. for a welcome message the From: address is xxx-request(a)757pug.org. For a post if the list is anonymous or if DMARC mitigations are applied the From: address is xxx(a)757pug.org. Otherwise it is the From: address of the incoming post. For failures from the smtp relay, there should be messages in Mailman's smtp.log of the form: $msgid delivery to $recip failed with code $smtpcode, $smtpmsg with the appropriate substitutions. What are the error messages in these entries. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: Welcome message template errors

by Mark Sapiro

On 4/23/24 14:59, Mark wrote: > > The welcome message is returned. > > root@hel:~# sudo -u mailman curl > https://LISTS.MYDOMAIN.COM/mailman3/api/templates/list/MYTESTLIST.LISTS.MYD… > Test Welcome message for new subscribers.root@hel:~# I don't know what the issue is. curl, running as user mailman, is able to get the url, but Mailman core, presumably running as user mailman, times out trying to get the url. I can't explain why. Try the following in `mailman shell` running as user mailman ``` (venv) $ mailman shell 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. >>> import requests >>> r = requests.get( ... 'https://LISTS.MYDOMAIN.COM/mailman3/api/templates/list/MYTESTLIST.LISTS.MYD…', ... timeout=5) >>> t.text ``` Note the URL above is all on one line. This is exactly what Mailman core is doing to get the template assuming the `uri` in the template` table entry is the argument of the requests.get(). If this times out, try increasing the timeout= value. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: Setting archive_policy "private" using REST changes web UI setting Archive policy, but does not hide archive until UI Save

by Mark Sapiro

On 8/14/24 01:15, Henrik Rasmussen wrote: > I am working on disabling a list removing all members using REST and then setting archive_policy to "private" also using REST. This changes the UI Archive policy setting to Private archives as I would expect, but I just discovered that the (now previous) member, still logged in, and alså public (not logged in), still have access to the archive. It is not browser cache. > > At the moment I click Save in the UI settings/archiving, both logged in user and not logged in user (other browser) changed to "This mailing list is private. You must be subscribed to view the archives." on page reload. > > It seems that i need to click Save on every list having been changed, before the archive is hidden. Is that a bug? The daily Django hyperkitty sync_mailman job will probably do it. Or, you can figure out what REST calls saving the settings in Postorius does and do that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

[MM3-users] Re: Chinese characters in list name shows question mark (?)

by Mark Sapiro

On 10/24/19 4:53 AM, Franklin Weng wrote: > > Thanks for your help. I did what you said above, but then I still got the > same result even after restarting mailman3 services. > > ~# mailman shell -l zh-l10n.lists.linux.org.tw > Welcome to the GNU Mailman shell > The variable 'm' is the zh-l10n.lists.linux.org.tw mailing list >>>> m.preferred_language > <Language [zh_TW] Chinese (Taiwan)> >>>> quit() The issue is the list welcome message is sent in the character set of the new member's preferred language and if that is not set in the subscription request, and it's not possible to do that in Postorius, it defaults to the installation's preferred language. It should probably default to the list's preferred language. See <https://gitlab.com/mailman/mailman/issues/608> You have two choices: You can set the installation's default language by putting [mailman] default_language: zh_TW in your mailman.cfg, or you can leave the default language English and set the character set for English to utf-8 by putting [language.en] charset: utf-8 in your mailman.cfg. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

Search results for query "sapiro"