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

[MM3-users] Re: Postorius confirmation mails shown in uwsgi-error.log but not sent

by Ralph Seichter

* Mark Sapiro: >> $ grep ^EMAIL settings.py >> EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' >> EMAIL_HOST = 'localhost' >> EMAIL_PORT = 25 > > but is this perhaps overridden in a settings_local.py file? I don't have a local settings file. I cloned the suite from GitLab[1] master branch and modified the existing settings.py, based on Mailman's documentation. [1] https://gitlab.com/mailman/mailman-suite.git I just verified that EMAIL_BACKEND is not redefined anywhere: $ grep -r 'mail\.backends' . Binary file ./__pycache__/settings.cpython-38.pyc matches ./settings.py:EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' ./settings.py:# EMAIL_BACKEND = 'django.core.mail.backends.filebased.EmailBackend' I commented out the "if DEBUG == True" lines, which explains match number three. As far as I can see, the mail backed definition for Django is as it should be. I could provide the differences between my settings.py and the Git HEAD version if you think that might help. -Ralph

5 years, 5 months

[MM3-users] Re: Rebuilding a list index fails

by Mark Dadgar

On Feb 17, 2021, at 9:58 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/16/21 9:59 PM, Mark Dadgar wrote: >> Now that I’ve got my instance back up and running on the latest released code, I am trying to rebuild a list index. I am using Xapian via haystack, which worked beautifully before my recent list meltdown. >> >> Error messages below. >> >> rebuild_index fails with the same error. >> >> This is with django version 3.0.12. > > > django.utils.six was removed in Django 3.0. See > <https://pypi.org/project/django-utils-six/> for a work around > replacement. I.e. in your venv do > > pip install django-utils-six OK, that got me a step further. Then I needed to do a “pip install xapian-bindings” and now I am up and running. I really appreciate the support of this community in general and you in particular, Mark. Thank you. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 6 months

[MM3-users] Re: CSV import for mass subscription

by Odhiambo Washington

On Fri, Sep 20, 2024 at 7:43 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 9/20/24 01:26, Markus Grandpré wrote: > > Dear list, > > > > we noticed that there is a function to convert the member list into a > > CSV format and save it.Therefore, we would like to know if the > > implementation of a CVS import for mass subscription is already planned? > > If not, how can we submit a corresponding feature request? > > The exported CSV is just a list of email addresses, and that could be > easily just pasted into the mass subscription form. > Why was it called a CSV? Appropriateness or future plans to download a true CSV? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

11 months, 1 week

[MM3-users] Re: Post log?

by Mark Dadgar

On May 5, 2020, at 7:06 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/5/20 5:28 PM, Mark Dadgar wrote: >> Is there the equivalent of the post log from mailman 2.x available? > > It's not a separate log as it was in Mailman 2.1, but the information is > in the smtp log. For example, here are a couple of entries relating to > your post to which I'm replying: > > May 06 00:29:15 2020 (27320) > <F0E6ABE3-C0DD-47D9-A527-1BAB77BD84C2(a)pdc-racing.net> smtp to > mailman-users(a)mailman3.org for 238 recips, completed in > 39.014487743377686 seconds > May 06 00:29:15 2020 (27320) > <F0E6ABE3-C0DD-47D9-A527-1BAB77BD84C2(a)pdc-racing.net> post to > mailman-users(a)mailman3.org from mark(a)pdc-racing.net, 4429 bytes Ahh. I saw a ton of entries of the first type but missed the entries of the second type (it was a big file), which were the ones I needed. Thanks for the pointer. The script is up and running nicely now. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 3 months

[MM3-users] Re: User settings triggers error

by Mark Dadgar

On Jun 18, 2020, at 3:27 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 6/18/20 2:23 PM, Mark Dadgar wrote: >> >> There is definitely something sketchy going on here. As an admin, I am not getting accurate subscription status about people on a list. For example, I search for a list member, find their listing, check the box and click Unsubscribe Selected, and get an error because it turns out that they had already unsubscribed themselves previously. But Postorius thought they were still subscribed. >> > ... >> Could this somehow be related to my recent migration from sqlite3 to postgres? > > I think it's quite likely that that migration is involved and your > database is now corrupted in some way. Exactly how or in what way, I > don't know, but it seems likely to me that that's the issue. Oh good. Any thoughts on how to salvage ~20 years of list archives? - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 2 months

[MM3-users] Re: MTA authentication and smtpd_sender_login_maps

by Jan Eden

On 2022-11-25 11:44, Mark Sapiro wrote: > On 11/25/22 11:00, Jan Eden via Mailman-users wrote: > > > > I obviously do not want to add an entry to the map file for each mailing > > list created by someone on the server. Is there a way to > > programmatically create a sender login map with Mailman? > > > You could modify mailman/src/mailman/mta/postfix.py to create a > smtpd_sender_login_maps file with the desired content or you could create a > script that creates the file using data in the generated > var/data/postfix_lmtp. If the latter, you might be able to create a plugin <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/plugins/do…> > to run the script whenever a list is created or deleted Thanks! I feel rather stupid, but the obvious and really simple solution is a wildcard entry for the SASL user in controlled_envelope_senders: @lists.domain.org mailman_sender(a)domain.org Sorry for realizing this *after* bothering you. - Jan

2 years, 9 months

[MM3-users] Re: To have mailman3 start at boot, trying to configure the systemd mailman3.service unit, but having issues

by Ron

On 2024-06-08 14:48, Mark Sapiro wrote: > The "PermissionError: [Errno 13] Permission denied: '//var/templates'" > is what it says. It is trying to create the absolute path /var/templates > and user mailman3 doesn't have permission to create a templates/ > directory in /var. > > I'm not sure why this is. It should be trying > /opt/mailman3/mm/var/templates. What does I experienced the fun of having /var being where mailman3 tried to create files & folders. Some combo of the following worked for me: mailman3.service Environment="MAILMAN_CONFIG_FILE=/etc/mailman3/mailman.cfg" /etc/mailman3/mailman.cfg [paths.here] var_dir: /opt/mailman/mm/var I explicitly set many / most of the other vars in that section too (i.e. lock_dir was one that also caused issues). This might be the Wrong Way, but it solved issues similar to the ones being discussed. rb

1 year, 2 months

[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>

8 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, 10 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, 4 months

Search results for query "sapiro"