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

[MM3-users] Re: False attachments in Outlook 2019?

by Mark Sapiro

On 1/24/21 3:29 AM, Brian Olesen wrote: > Dear Mailman 3 users, > > I seriously think of upgrading from Mailman 2.1.33 to this new RC2 or the > final one, when it comes out. > > > > But there is an annoying issue that I'd like to ask you about. > > It's the false attachments that Outlook creates for the footer. Is this > still an issue when using Mailman 3, or have you made some sort of work > around? See the FAQ at <https://wiki.list.org/x/4030707> for a discussion of why we don't try to insert headers and footers into HTML message parts. This applies to Mailman 3 as well as Mailman 2.1. I don't know if anyone has tried it, but the MIMEDefang solution mentioned in the FAQ would probably work with Mailman 3. -- 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: Unable to get Postfix to bounce messages to non-existent lists

by Mark Sapiro

On 2/19/24 09:14, skenny(a)scss.tcd.ie wrote: > > The only problem with this is that if someone sends a message to a non-existent mailing list, Postfix nevertheless accepts the mail, and it loiters in the queue for several days before eventually being bounced back to the sender. I want to get Postfix to reject mail to non-existent mailing lists immediately. I've come up short with each variation of main.cf settings I've tried, and would greatly appreciate any advice. What is Postfix's reason for deferring the mail - `mailq` will show the reason. What if you just omit the relay_domains = regexp:/var/mailman-data/postfix_domains setting. This may cause all list mail to be rejected, but it may work (I'm not sure if transport_maps takes priority). -- 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: Hyperkitty search on Message-ID?

by Mark Sapiro

On 12/5/24 04:25, Bryan Fields wrote: > I've been working with a rather large import and am finding that I can't seem > to get the search on a Message-ID: to return anything. ... > Any ideas how to get it indexing the ID so a layperson can search on it? Message-ID is not one of the fields indexed. These are defined at https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/search_index… A bit obscure for laypersons, but one can compute the message_id_hash from the Message-ID ``` from base64 import b32encode from hashlib import sha1 def get_message_id_hash(msg_id): return b32encode(sha1(msg_id).digest()).decode() ``` I can't help but wonder though how one has the Message-ID without having the message. I'm wondering in general how often if ever the layperson would be searching the archive for a Message-ID. -- 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: Mm3 - new adventure

by Mark Sapiro

On 03/15/2017 07:35 AM, SP2L wrote: > > Today started reading belows document: > > http://docs.mailman3.org/en/latest/devsetup.html > > There is evidently misleading command > repeated more than once: > > $ git clone git@gitlab.com:mailman/mailman.git > > (at least, above is not working from Debian command line) > > which should read: > > $ git clone https://gitlab.com/mailman/mailman.git In order to use the former command, you must register for a gitlab account and install your ssh public keys there. This is mentioned in two places in the document at https://wiki.list.org/DEV/SetupDevEnvironment which is the first thing referenced in the document at http://docs.mailman3.org/en/latest/devsetup.html It also needs to be mentioned at http://docs.mailman3.org/en/latest/devsetup.html Thanks for pointing that out. This is now reported at https://gitlab.com/mailman/mailman-suite-doc/issues/3 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 7 months

[MM3-users] Re: mailman.cfg (use_https: yes) fails

by Mark Sapiro

On 11/16/19 4:54 AM, Wolfgang Bock via Mailman-users wrote: > I will look at the https issue further when I get time. > In this context I faced a strange behavior: > > In the database mailman3web in table django_site are listed several > domains, either in the django-domain-management site > https://[mydomain]/mailman3/admin/sites/site/ > > id domain name > 1 example.com Example.com > 2 [mydomain-1] [mydomain_name_1] > 3 [mydomain-2] [mydomain_name_2] > 4 [mydomain-3] [mydomain_name_3] > > In case I delete line 1 with the id 1, in the database or in the > django-web-site, postorius fails to work. After re-inserting this line, > postorius works again. In your settings.py, you probably have SITE_ID = 1. Thus, when you delete the site with id = 1, Postorius fails. You need to set SITE_ID to an existing site in settings_local.py. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 11 months

[MM3-users] Re: Mailman REST API not available. Please start Mailman core.

by Mark Sapiro

On 7/28/20 1:07 PM, joseverde(a)gmail.com wrote: > [Does your systemd script set the user to the Mailman user, and does the > Mailman user have read/write permission on Mailman's var/locks/?] > > How do I check for that? ls -la /path/to/mailman/var/locks > Also, what's the difference between the mailman command and the systemctl mailman3? Are they the same processes? Presumably your mailman3.service actually uses the `mailman start` command to start Mailman. The `mailman` command is a shell with many subcommands for various purposes including starting and stopping Mailman. > Oh and does the /3.1 matter at the end of the Rest url for Django? Do not put the 3.1 at the end of your MAILMAN_REST_API_URL. Postorius adds it. See <https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/utils.py#L…>. -- 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: web api

by Mark Sapiro

On 8/4/21 10:44 AM, Ethan Furman wrote: > Greetings again! > > Is there a remote API I can use to manage a list? Mailman core's REST API is documented at <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…>. By default it listens only on localhost:8001 and requires authentication with user = restadmin and password = restpass but these are all settings in the webservice section of mailman.cfg. See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.…> for the settings and their defaults. You could set [webservice] hostname: 0.0.0.0 admin_pass: My_Secret in mailman.cfg to have it listen for connects from anywhere and require a different password. You'd also need to adjust some or all of the settings for MAILMAN_REST_API_URL MAILMAN_REST_API_USER MAILMAN_REST_API_PASS In your Django settings. There is also <https://gitlab.com/mailman/lemme> however, that's only a skeleton and not useful as is. -- 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: OK, so I backed out completely and re-installed. Here's my *original* error. Should I modify virtual mailbox maps?

by Mark Sapiro

On 10/16/24 10:26, Bill Oliver wrote: > > 1) I set up a mailinglist (tradfp(a)forensicpath.us) for "old school" > forensic pathologists to discuss cases. Does the forensicpath.us domain have an alias_domain configured in mailman causing mailman to create /opt/mailman/mm/var/data/postfix_vmap and /opt/mailman/mm/var/data/postfix_vmap.db? You need this. > In my previous attempt, I added > > hash:/opt/mailman/mm/var/data/postfix_lmtp > > to both virtual_mailbox_maps and virtual_alias_maps, but I haven't > done that yet here. I thought I'd ask and make sure I should. > > Should that be my next step? You should add hash:/opt/mailman/mm/var/data/postfix_vmap to virtual_alias_maps only. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users]Re: Installation issues

by Mark Sapiro

On 04/20/2016 01:11 AM, Andrew Hodgson wrote: > > My next stab at this was going to be using venvs, but creating the venv as the directory /opt/mailman which gives cleaner paths (to my mind anyway), but haven't got round to doing it yet. You should be aware that mailman-bundler uses two venvs, one for Python 2 and one for Python 3. The idea is you create the Python 2 venv and activate it when running mailman-bundler's buildout, but that process will also create a venv-3.x venv in the bundler directory. I think what may make sense is to clone mailman-bundler directly into /opt/mailman rather than /opt/mailman/mailman-bundler. Then follow the docs from there. This should give you paths like /opt/mailman/venv/, /opt/mailman/venv3.x/, /opt/mailman/deployment/, /opt/mailman/mailman-web/, /opt/mailman/bin/, /opt/mailman/var/ and so on without the extra mailman-bundler/ level. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 years, 6 months

[MM3-users] Re: Installing mailman 3

by Mark Sapiro

On 07/25/2017 12:35 PM, Rafael Mora wrote: > This is from the file /var/log/maillog: > > Jul 24 17:29:21 localhost postfix/postfix-script[2092]: starting the > Postfix mail system > Jul 24 17:29:21 localhost postfix/master[2096]: daemon started -- version > 2.10.1, configuration /etc/postfix > Jul 25 03:30:05 localhost postfix/pickup[2785]: 03F4160D143F: uid=0 > from=<root> > Jul 25 03:30:05 localhost postfix/cleanup[3191]: 03F4160D143F: > message-id=<20170725073005.03F4160D143F(a)localhost.localdomain> > Jul 25 03:30:05 localhost postfix/qmgr[2113]: 03F4160D143F: > from=<root(a)localhost.localdomain>, size=508, nrcpt=1 (queue active) > Jul 25 03:30:05 localhost postfix/local[3195]: 03F4160D143F: > to=<root(a)localhost.localdomain>, orig_to=<root>, relay=local, delay=0.11, > delays=0.07/0.03/0/0.01, dsn=2.0.0, status=sent (delivered to mailbox) > Jul 25 03:30:05 localhost postfix/qmgr[2113]: 03F4160D143F: removed > > > It seems that postfix is working, isn't it? At least for receiving mail queued by the sendmail command and delivered to root. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 2 months

Search results for query "sapiro"