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

[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

9 years, 10 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

8 years, 7 months

[MM3-users] Re: Adding user - Error 409 Subscription request already pending

by Mark Sapiro

On 4/20/19 10:13 AM, brian(a)emwd.com wrote: > Hi Mark, > > I followed your instructions to confirm the user. When I ran ">> util.confirm('hex_token')" nothing happened which I take it to mean it worked. I then ran ">> list(util.find(mlist=m,pend_type='subscription'))" and the pending member did not show up which I thought was a good thing. But . . . > > I tried to mass subscribe the user and got back: > > "HTTP Error 409: b'{"title": "409 Conflict", "description": "Subscription request already pending"}'" Did you do commit() or exit shell (which does an implicit commit) before trying the mass subscribe? I'm not going to be able to look at this further for some time as I am traveling today, but I will. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

[MM3-users] Re: Subscribing by E-Mail

by Mark Sapiro

On 5/21/20 4:47 PM, Peter Adebahr via Mailman-users wrote: > > on MM2 systems, we used to subscribe people via an external application > by sending an e-mail to the request address with a subject of > "subscribe address=user(a)example.com" > > This returns a "bad argument" in MM3 - any ideas how to solve this? Currently, a subscribe or join command sent to the -request address only supports one argument, `digest=<no|mime|plain>`. To subscribe an arbitrary address, you can send to the -join or -subscribe address with the From: set to the address you want to subscribe, but you say > We cannot set the actual from-address in a foreign application... Modifying mailman/commands/eml_membership.py to accept an address= argument shouldn't be difficult. If you submit an issue at <https://gitlab.com/mailman/mailman/-/issues>, I'll look at it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: "To:" header field

by Mark Sapiro

On 08/05/2018 06:20 AM, Asaf Ohayon wrote: > > Comparing to Mailman 2.1, which we recently upgrading from, > and didn't got spammed, the "To:" field was set to the actual reciever, > While in Mailman 3.2, the "To:" field is set to the list's address. > > How can this be configured ? This is full personalization. See <http://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/cook-head…>. This setting is not yet exposed in Postorius, so you have to set it via 'mailman shell'. E.g. $ bin/mailman shell -l test(a)msapiro.net Welcome to the GNU Mailman shell The variable 'm' is the test(a)msapiro.net mailing list >>> m.personalize <Personalization.none: 0> >>> from mailman.interfaces.mailinglist import Personalization >>> m.personalize = Personalization.full >>> m.personalize <Personalization.full: 2> >>> commit() -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 6 months

[MM3-users] Re: API access to Hyperkitty

by Mark Sapiro

On 2/9/21 10:23 AM, Brian Carpenter wrote: > Is it possible to download Hyperkitty's archives to a remote server via > an API? Is there documentation that explains how to accomplish this task? > I don't think there is documentation, but if you look at the target of any `download` button, it should be obvious. I.e. the link to download the entire archive for this list is https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/export/… The `mailman-users(a)mailman3.org-2021-02.mbox.gz` part is the name of the file to download to and the `-2021-02` part can be anything or nothing, but the name must begin with the list posting address and end with `.mbox.gz`. If the archive is large, this can time out in which case adjust `start` and `end` to download it in pieces. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: Problems with web interface after upgrade

by Mark Sapiro

On 2/9/21 3:26 PM, Victoriano Giralt wrote: > > It's CentOS7, but sassc was already installed and has -t as short for --style. You wrote > ModuleNotFoundError: No module named 'sassc -t compressed {infile} {outfile}' It should be looking for just sassc, not 'sassc -t compressed {infile} {outfile}'. Whats in your settings for COMPRESS_PRECOMPILERS. That may not be the issue. You also wrote > compressor.exceptions.FilterError: Error: It's not clear which file to > import for '@import "../libs/bootstrap/stylesheets/bootstrap"'. > Candidates: > ../libs/bootstrap/stylesheets/_bootstrap.scss > ../libs/bootstrap/stylesheets/bootstrap.scss > Please delete or rename all but one of these files. > on line 4 of static/hyperkitty/sass/hyperkitty.scss You need to remove the older of hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/bootstrap.scss and hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_bootstrap.scss That may be the whole issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: migrate MM3 list from an old server to a new one

by Mark Sapiro

On 8/6/24 01:43, noc(a)iem.at wrote: > > PS: (again) I'm resending this message, as the one i sent yesterday seems to have vanished (i *did* check the archvies). i have no clue why this happens, as i can post via the webinterface just fine (only when using my trusted MUA they just vanish). Your messages are being discarded for matching a header filter rule. The messages contain content-type: application/pgp-keys; name="OpenPGP_0xB65019C47F7A36F8.asc" and the content-type rule regexp is `^ *application(?!.*signature)` I.e we accept things like application/pgp-signature and application/pkcs7-signature, but not application/pgp-keys I have changed that regexp to `^ *application/(?!(pgp|[^ ;]*signature))` so we will now accept `content-type: application/pgp.*` as well so you now should be able to post/reply from your MUA. -- 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: Must issue a STARTTLS command first when forwarding from old server to new server

by Mark Sapiro

On 11/14/24 15:53, jkoral(a)luc.edu wrote: > I have a fully functioning Mailman3 server now and have setup and alias on the old server to forward mail to the new server. We have TLS enabled on the new server, but not the old server, so the new server is rejecting the mail coming through. Our IT security will not allow me to disable TLS on the new server. > > Is there a way to make an exception in mailman3 to allow a specific host to send mail through without using TLS? This is all the MTA, not Mailman. As you suggest in a follow up, you should enable TLS on the old server. In Postfix main.cf, I think ``` smtp_tls_security_level = may ``` should do it. -- 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: Cannot Create New List

by Mark Sapiro

On 11/5/25 09:59, dap1--- via Mailman-users wrote: > As far as I know I did everything (except the /etc/mailman3 stuff) in the venv environment. Pip is not even available outside of mailman user. When I try to run pip again it says requirement already satisfied. I don't suppose there is a checkparms like in mailman2. I'm not aware of any Mailman 2.1 checkparams. There is check_perms, but I don't know if that's what you want. The fact remains that something is checking for `/usr/bin/django-admin`, finding it and then trying to run `flock -n /var/run/mailman3-web/cron.minutely /usr/share/mailman3-web/manage.py runjobs minutely` If everything is in your venv, why is there a `/usr/bin/django-admin` and perhaps a `/usr/share/mailman3-web/manage.py`. These all look like artifacts from an install of the Ubuntu mailman-web package. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 3 weeks

Search results for query "sapiro"