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

[MM3-users] Re: Moderate first postings of new members

by Mark Sapiro

On 11/3/22 13:39, peter(a)chubb.wattle.id.au wrote: > > If you've set the default processing to 'hold for moderation' won't > this just continue to moderate the member? Ive been selecting 'Accept > immediately' in the dialog. "Default action to take when a member posts to the list" will only continue to be applied to the member if you select "List default". The difference between "Default processing" and "Accept Immediately" is "Default processing" passes the moderation check but continues to check other rules which are header-match, administrivia, implicit-dest, max-recipients, max-size, news-moderation, no-subject, digests and suspicious-header. "Accept immediately" bypasses all those additional checks. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: Maximum recipients in an email.

by Mark Sapiro

On 11/12/24 02:14, via Mailman-users wrote: > Hello, > > where can I configure the maximum recipients in an email in mailman3? > > In my postfix configuration is set a limit "smtpd_recipient_limit = 200" and in the mailman3 smtp.log i will get a error message like "failed with code 452, b'4.5.3 Error: too many recipients'". Mailman3 repeats the delivery for these addresses, but i would like to configure correctly. The delivery of mails is then faster. This is the `max_recipients` setting in the `[mta]` section of mailman.cfg. Prior to 3.3.9 it defaulted to 500, but currently it defaults to 10 as a fix for https://gitlab.com/mailman/mailman/-/issues/1083 which is a slightly different issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months

[MM3-users] Re: Clearing webserver cache - Nginx

by Mark Sapiro

On 8/6/24 14:27, Mark Sapiro wrote: > > Is this with only one browser? It's a long shot, but clearing browser > cache might work. Actually, I see the same issues from my browsers, so it's not a browser caching issue. The only thing left is nginx caching, but, while I know very little about nginx, I think it doesn't cache by default and I don't see where in your posted config it's enabled. Perhaps there's more in your config that you didn't post. If there is a proxy_cache_path directive in your config try find /the/proxy/cache/path -type f -delete to clear the cache. As a last resort, your /opt/mailman/mm/static/CACHE/ directory should contain a css/ directory with 3 files and a js directory containing one file and a manifest.json file with a template for the `link` directives referencing those files. The js/ directory is easy as its only one file, so your server is looking for /static/CACHE/js/output.3aaa7705d68a.js and you could create a symlink in the js/ directory from output.3aaa7705d68a.js to the actual file. For the css directory, your server is looking for output.158acc288604.css and output.6dab123e4897.css, and I don't see the third file in the logs you posted, but if I go to pages in your archive that I see as unstyled and look at the stylesheet references, they are to output.44ea6c55e917.css, output.e68c4908b3de.css and output.9efeb5f3d52b.css so you could just symlink those to the actual files, it doesn't matter which as all three are loaded on each page. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 1 week

[MM3-users] Re: Confirm on mass subscription

by Mark Sapiro

On 7/5/17 1:48 PM, David Krantz wrote: > > Is there a way of requiring all mass subscribed users to confirm their > email adress? I have an use case where we have a current mail list but > when moving it to mailman I for different reasons would like to > confirm all subscribers. Some very shallow testing suggests that if I > just add them using mass subscribe, they will not have to confirm at > all. > > I have yet to upgrade to 3.1 but I will do so in due time. In MM 2.1, you just send the users invitations rather than subscribing them. In MM3/Postorius, this does not seem to be an option at present. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 10 months

[MM3-users] Re: Apache Conf

by Mark Sapiro

On 10/19/18 10:29 AM, Guiseppin Thomas wrote: > Hi, > Currently, I use a nginx configuration for mailman. It's work perfectly. > > I tried to do the same with Apache, but the statics files are not > delivered (404). ... > <VirtualHost *:80> > ServerName mailing.ddd.fr > > ErrorLog ${APACHE_LOG_DIR}/mailing.error.log > CustomLog ${APACHE_LOG_DIR}/mailing.access.log combined > > <Location /static/> > Alias "/opt/mailman/static/" > </Location> > > <Location /> > ProxyPass http://localhost:8000/ > ProxyPassReverse http://localhost:8000/ > ProxyPreserveHost On > </Location> > </VirtualHost>/ In Apache, location <http://httpd.apache.org/docs/2.4/mod/core.html#location> is not appropriate for resources in the file system. Try Alias /static/ /opt/mailman/static/ not within a location block. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

[MM3-users] Re: How can I allow members of list A to post to List B and vice versa

by Mark Sapiro

On 11/19/20 3:51 AM, mario.mailman3(a)frese.online wrote: > > The best option I would like to have is to enter the name of List A in the non-members of List B an vice versa. All those nonmembers should not need to be moderated. > How can I manage this? I would be very glad for your ideas. This is a feature in Mailman 2.1 but is not yet available in Mailman 3. There is currently no good solution for Mailman 3 that I am aware of. I've opened <https://gitlab.com/mailman/mailman/-/issues/794> for this. -- 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: Problem updating mailman

by Mark Sapiro

On 1/23/21 2:56 AM, Odhiambo Washington wrote: > I am getting this error after I did a git pull and build. > > (venv) [mailman3@gw ~/git]$ /opt/mailman/mm/bin/mailman-post-update > + '[' False == False ']' > + mkdir -p /opt/mailman/mm/static > + /opt/mailman/mm/bin/django-admin collectstatic --clear --noinput > --verbosity 0 > +* /opt/mailman/mm/bin/django-admin compress* > CommandError: An error occurred during rendering > /opt/mailman/mm/venv/lib/python3.7/site-packages/HyperKitty-1.3.4rc2-py3.7.egg/hyperkitty/templates/hyperkitty/404.html: > /usr/local/lib/ruby/site_ruby/2.7/rubygems/dependency.rb:311:in `to_specs': > Could not find 'sass-listen' (~> 4.0.0) among 4 total gem(s) ... Ruby-sass is no longer supported. Please see the Sass compiler section at <https://docs.mailman3.org/en/latest/install/virtualenv.html#dependencies>. -- 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: MM3 generates long lines?

by Mark Sapiro

On 6/22/21 11:46 PM, peter(a)chubb.wattle.id.au wrote: > > I'm seeing emails being dropped when mm3 talks to the local smtp > server, with log errors like: > > 2021-06-23 15:42:24 1lvvea-007r8u-VN H=localhost (<FQDN>) [::1] > F=<announce-bounces@<FQDN>> rejected after DATA: maximum allowed line length is 998 octets, got 1036 > > The email itself did not have such long lines AFAICT. We would need to see the email itself in order to begin to understand if this is a Mailman issue or some issue withe the mail as received by Mailman. Assuming the prototype archiver is enabled, you should be able to find the messages in Mailman's var/archives/prototype/LIST/new/ directory. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

[MM3-users] Re: Localization of auto-responses, question marks in welcome message

by Mark Sapiro

On 4/25/22 02:52, Claus-Justus Heine via Mailman-users wrote: > > I have installed custom templates using the REST API and pointing MM3 to > some download URIs. So MM3 has custom templates for particular lists, > but I did not yet install different templates for different languages. > Still I would also prefer that MM3 would assume that all template text > are UTF-8, independent from the language. I think in this case the issue is not in the retrieval of the template text, but rather in the representation of the resultant message in the character set of the lists preferred language, us-ascii for 'en' in this case. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

[MM3-users] Re: Trouble in Debian11 after import mailman2 archive

by Mark Sapiro

On 5/25/22 03:21, qro(a)xs4all.nl wrote: > > Question: > Where do I have to look/make changes so I can import the old archive and > can send email to it? You are not looking at the relevant logs. In the first case, mail is delivered to Mailman, but then something happens to it before it is archived and delivered. Look in /var/log/mailman3/mailman.log and wherever Mailman's qfiles are in the Debian install. Assuming the message is not held for moderation, rejected or discarded due to list settings, it is probably queued in Mailman's `shunt` queue, and if so, there will be an exception and traceback logged in mailman.log. -- 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

Search results for query "sapiro"