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

[MM3-users] Re: Subscription requires confirmation when list is set as Open

by Joachim Schrod

Mark Sapiro writes: > > It is not the subscription that requires confirmation. It is the user's > email address. Even though the list's subscribe policy is open, a > previously unknown email address has to be confirmed. I assume that's the verification that one can turn off in Postorious `Mass Suscription' with the checkbox "Pre Verified". I maintain a mailing list for a private holiday where people don't subscribe themselves; I subscribe them. I have vetted their email address beforehand. (The subscribers are mostly not able to handle a verification email, nor any email-based workflow at all.) Is there a configuration option for a mailing list that sets "Pre Verified" to true as a default? I checked the options of "mailman conf" and "mailman-web help" (the latter seems to be Postorious' manage.py on my Debian system), but to no avail. Cheers, Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod <joachim(a)schrod.org>

6 months, 2 weeks

[MM3-users] Re: Subscription issue with ghost confirmations

by Brian Carpenter

Hi Mark, This has occurred again. A person sends an email to listname-subscribe@listdomain and the subscription policy of said list is set to moderate only. Instead of honoring this, a confirmation email is sent out. Now the email address that made this request does not show up at all in any of my logs. There is no record of them making a previous subscription attempt before the subscription policy was changed to moderate. Here are some observations: 1. The two occurrences of this happening was to Gmail users. 2. The two occurrences of this happening was when an email is being sent to the listname-subscribe@listdomain address. 3. This is only happening on 1 list. This may have no bearing on the issue but the list address of this problematic list is ******-owners@listdomain. I know there is an alias created for each list that is listname-owner@listdomain. Just throwing that out there. <princess-leia-voice>Help me Obi-Wan Sapiro. You are my only hope.</princess-leia-voice>

4 years, 8 months

[MM3-users] Re: Outgoing messages fro Mailman fails DMARC

by Henrik Rasmussen

> On 04/10/2018 06:53 PM, Mark Sapiro wrote: > > I'm not sure I understand what you are saying. Mailman's (both 2 and 3) > DMARC mitigations allow modifying the outgoing message in some or all > cases so the From: domain is the list's domain so the message won't be > dealt with by the recipient MTA according to the original From: domain's > DMARC policy. > > See <https://wiki.list.org/DEV/DMARC>;. Also, > <https://wiki.list.org/x/17891458> may be of interest. Thanks you for the links. According to https://wiki.list.org/DEV/DMARC the MM3 list setting "DMARC mitigation action" (which actually say "Replace From: with list address" in Postorius) should change the From: header. This doesn't seem to work if I don't also set "DMARC Mitigate unconditionally" to Yes, but does if I do. Where do I change defaults for all lists, instead of a per list change in settings/dmarc_mitigations ? Henrik Rasmussen

7 years, 2 months

[MM3-users] Re: How to hide sender completely

by Odhiambo Washington

On Wed, May 10, 2023 at 2:08 PM Roland Miyamoto via Mailman-users < mailman-users(a)mailman3.org> wrote: > Thanks, Mark, > > On 10/05/2023 01:50, Mark Sapiro wrote: > > Both this and all other incoming Received: headers are removed from > > posts to anonymous lists beginning with Mailman 3.3.4. > > X-MailFrom: headers are also removed as of Mailman 3.3.4. > > For clarifying. > > I am currently running > > GNU Mailman 3.2.1 (La Villa Strangiato) > > under Debian buster (10). > Seems I will have to upgrade to Debian bookworm (12) > if I want to stick with the deb package > and want complete anonymity to work. > > Or else dive into the virtualenv, which seems to be recommended option > anyway. > And virtualenv gives you more freedom. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years, 1 month

[MM3-users] Re: Feature request, hyperkitty, low volume lists

by Alain D D Williams

On Thu, Jan 09, 2025 at 09:06:56AM -0800, Mark Sapiro wrote: > On 1/9/25 06:07, Alain D D Williams wrote: > > > > For an example see: > > > > https://fridayfolk.phcomp.co.uk/mailman3/hyperkitty/list/announce@fridayfol… > > The above URL and also https://fridayfolk.phcomp.co.uk/mailman3/hyperkitty/list/announce@fridayfol… > and even https://fridayfolk.phcomp.co.uk/mailman3/hyperkitty/ all give a 500 > internal server error response. Sigh - try again. The 500 error happens several times a day. After 5 minutes it behaves as it should ... until it happens again some time later. I have not found out what is happening; nothing obvious in the logs, not high system load. I can live with it for now as I am busy elsewhere. -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

5 months, 4 weeks

[MM3-users] Re: changing the main template for subscriptions and more

by Andreas Barth

* Mark Sapiro (mark(a)msapiro.net) [210622 14:22]: > It isn't necessary to patch the source in this way. If you put the > modified templates in Mailman's var/templates/site/de/ directory, > ensuring that the Mailman user can read them, they will be used and > you won't have to patch the source every time you upgrade. Thanks Mark for pointing that out. I also should have mentioned that this would be the recommendation for operations, especially if mailman is install by some normal means (pip, distribution packages, etc). I perhaps took it for granted too much to never touch files coming out of automated systems by hand (except where the automated system caters for, e.g. debian conffiles), because that is a sure way to get into trouble with the next upgrade. (My mailman installation is the exception and not the rule, so unless you know what you're doing and have done similar before, just follow Marks advice) Andi

4 years

[MM3-users] Re: AttributeError: ,> 'ReopenableFileHandler' object has no attribute '_stream'

by David Newman

On 11/19/21 10:04 PM, Mark Sapiro wrote: >> but then mailman3 wanted me to create a bunch of directories under >> /etc, even though $var_dir was set to /var/lib/mailman3. Things seem >> to go better, except for the confusion between lists/mailman >> ownership, when I set layout to "debian", which was the default. > > > It seems you may be using the Debian packages as our source has no > `debian` layout. Thank you for spotting that. I'd cloned a test server from a production machine that did have the Debian mailman3 package installed, something I should have checked first. The rest of the installation went OK. I'm using MariaDB and not Postgres, and that required a few deviations from the Virtualenv Installation documentation, but those tweaks things went OK from there. I have a follow-up question about post-installation setup but will start a new thread for that. Thanks again! dn

3 years, 7 months

[MM3-users] Re: re-sending confirmation mails (was Re: Re: pending subscriptions lost?)

by Andreas Barth

* Mark Sapiro (mark(a)msapiro.net) [220315 23:31]: > I understand that, but even Debian sid has mailman3 3.3.3-1 and > mailman3-web 0+20200530-2 which are quite old for a package like > Mailman 3 which is still in active development. If we speak about unstable, that's something else. However, Debians next stable release won't release with mailman 3.3.3, as this package is removed from testing at the moment. I'd be happy if someone would update this package, however, I don't think I should get myself also involved there. ('Removed from testing' means: the current unstable package is considered not to be in shape to be released with the next stable release). So, if someone wants to get involved into Debian package maintainership with mailman3 (and related packages), that would be great, and I'm happy to support. As said, the most easiest way to get things fixed in Debian is by doing it. Andi

3 years, 3 months

[MM3-users] Re: Mailman web interface / uwsgi

by Jan Eden

On 2022-11-27 07:08, Mark Sapiro wrote: > On 11/27/22 00:19, Jan Eden via Mailman-users wrote: > > > > I see. But the mailman.cfg is placed in /etc/mailman3, and this file > > also belongs to the core, doesn't it? In any case, I changed the > > configuration parameter for [archiver.hyperkitty] as you suggested and > > all settings are in one place now. > > > In that case, it's probably just an oversight. The instructions at > https://docs.mailman3.org/en/latest/install/virtualenv.html are an evolution > of a process that started with an obsolete mailman-bundler package, the > initial iterations of which are documented at > https://wiki.list.org/x/17891998 and prior revisions of that page. > https://docs.mailman3.org/en/latest/install/virtualenv.html is still a work > in progress. Ok – as long as I can consolidate all settings in one place for backup purposes (with symlinks, if need be), any layout is fine. Thank you, Jan

2 years, 7 months

[MM3-users] Re: RemoteUserBackend for Mailman3?

by Markus Grandpré

Dear Mr Spiro, thank you so much for your reply. On my Debian 11 system I don't find 'django_mailman3.lib.auth.fedora' in my Django settings in </usr/lib/python3/dist-packages/django/conf/global_settings.py>: # List of strings representing installed apps. INSTALLED_APPS = [] But I find: INSTALLED_APPS = ( ... #'django_mailman3.lib.auth.fedora', ... ) in </etc/mailman3# less mailman-web.py>. After commenting this line out I restarted the mailman3 application by restarting the apache2 web server. Unfortunately, the Fedora button is still visible on login site of mailman3 and a server error occurs when I click the button. Best regards, Markus On 27.03.23 19:22, Mark Sapiro wrote: > On 3/27/23 06:00, Markus Ludwig Grandpré wrote: >> >> Btw. how can I disable and remove the Fedora button from Maliman3's >> login page? > > > remove 'django_mailman3.lib.auth.fedora' from INSTALLED_APPS in your > Django settings. > -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

2 years, 3 months

Search results for query "sapiro"