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

[MM3-users] Re: integrating mm3 with postfix / lmtp

by Mark Sapiro

On 10/26/2017 06:16 PM, Fabian A. Santiago wrote: > > But in my testing, I replied to a subscription confirmation message and received back an undeliverable looping email error message from postfix. Any clues there you can offer? I can post to the list from any email added via the admin console. The test subscriber address was local to my server. From an outside address, same error. This usually means that postfic is trying to deliver to an address and the message already has a Delivered-To: header with that address. What are the headers of the "looping" message in the report? What are the Postfix log messages related to that message? > Once I registered the new email domain, I reverted my postfix config back to the default suggested by maxking's docker instructions. > > https://github.com/maxking/docker-mailman I have essentially no knowledge of the docker container images, so I can't be much help with issues specific to them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 4 months

[MM3-users] Re: hidden list is hidden even to the owner

by Mark Sapiro

On 7/1/20 2:05 PM, Abhilash Raj wrote: > > Which version of Postorius are you running? > > Newer version shows all the lists you are related to by default when you are logged-in. So, the ones you own, moderate, subscribe to. That's correct, but it's tricky. If as an owner of an unadvertised list, you go to a URL like https://www.example.com/postorius/lists/ you will see the unadvertised list(s) that you own as well as any that you are a member or moderator of. Likewise you will see the unadvertised list(s) you own at https://www.example.com/postorius/lists/?role=owner and if you are a member as well as owner of an unadvertised list, you will see it at https://www.example.com/postorius/lists/?role=member. But (here's the tricky part) if you go to https://www.example.com/postorius/lists/?all-lists, you will not see any unadvertised lists, not even ones you own. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

[MM3-users] Re: Mailman3 not delivering list mail

by Mark Sapiro

On 10/2/20 4:53 AM, gordon(a)dickens.com wrote: > Hi Mark, > > BTW, as an aside, there is not any mention of admin users needing to be logged in as user=list instead of user=root in the documention here: > > https://docs.mailman3.org/en/latest/migration.html > > I highly recommend that the documentation be amended to clearly state that the admin users need to be logged in as user=list. The `list` user is a Debian/Ubuntu package thing. The Mailman user can actually be anything. I have added a note at <https://docs.mailman3.org/en/latest/migration.html#fn1> saying that these commands should be run as the Mailman user and not as root. The mailman command itself, if run as root, should probably set the effective user:group to the Mailman user:group. We don't know that from the Mailman config, but maybe use the owner and group of the mailman command file. This is now <https://gitlab.com/mailman/mailman/-/issues/776>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

[MM3-users] Re: Problem user

by Mark Sapiro

On 5/18/23 04:33, Itay Malka wrote: > Hello everyone, > > I use mailman3 > And I have one user who every time receives reports on a mailing list that he is not the administrator of, he is only registered to it > How can I cancel it? > could not find > > This is the email > Message-ID: > <CABPnsAo5vT8YKXiaHk0E2qs8CRs8nP13B9T9n5x4Yc8n7iLV3Q(a)mail.gmail.com> > Content-Type: multipart/alternative; > boundary="00000000000069e01c05fbde1416" > > --00000000000069e01c05fbde1416 > Content-Type: text/plain; charset="UTF-8" > Content-Transfer-Encoding: base64 > > 16rXldeT15QNCg== > --00000000000069e01c05fbde1416 > Content-Type: text/html; charset="UTF-8" > Content-Transfer-Encoding: base64 > > PGRpdiBkaXI9ImF1dG8iPteq15XXk9eUPC9kaXY+DQo= > --00000000000069e01c05fbde1416-- The message above is not from Mailman. It is simply a message originally from Gmail that says :"Thank you" in hebrew. I can't say much more without seeing the entire raw email. > End of Dental-medicine-faculty-council Digest, Vol 1, Issue 1 > ************************************************************* This is the final part of a plain format digest. Was it part of what was received? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: Can't add emails to accept_these_nonmembers

by Mark Sapiro

On 2/25/26 2:43 PM, Ibiam Chihurumnaya via Mailman-users wrote: > I need to set some nonmembers to a list as these members send message to the list, but don't need to receive any message from the list. > > I've used list_name.settings['accept_these_nonmembers'].append to add members to the list, but it gets discarded once I run list_name.settings.save(). I don't understand what you are doing. The above makes no sense to me. Please provide more detail on exactly what it is you are doing. However, `accept_these_nonmembers`is an artifact from Mailman 2.1 and only exists in Mailman 3 to support patterns as opposed to individual email addresses. In Mailman 3, there are two ways to accomplish this. One way is to subscribe the user as a member and set the member's delivery to disabled. The other way is to add the user as a nonmember and set the nonmember's moderation_action to default processing. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 day, 19 hours

[MM3-users] Re: Mails are not archived at all -- how to check if Hyperkitty is running or not?

by Mark Sapiro

On 10/30/19 12:52 AM, Franklin Weng wrote: > > If I use > > base_url: https://lists.slat.org/mailman3/hyperkitty/ > > The log became > > Oct 30 15:25:50 2019 (6256) HyperKitty failure on > https://lists.slat.org/mailman3/hyperkitty/api/mailman/urls: > <html><title>Auth required</title><body> > > <h1>Authorization Required</h1> > </body></html> (401) > > In my mailman-web.py: > > MAILMAN_ARCHIVER_KEY = 'my-key,same as in mailman-hyperkitty.cfg' > MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1') > > Not sure what to change here. There have been other reports of authorization failures even though the keys match. See the last few posts at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>. The solution there was to change both the api_key setting in /etc/mailman3/mailman-hyperkitty.cfg and the MAILMAN_ARCHIVER_KEY setting in /etc/mailman3/mailman-web.py to new values. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

[MM3-users] Re: Setting for archiving multi email domains?

by Mark Sapiro

On 3/9/21 12:59 PM, Duane Raymond wrote: >> What is the full error including traceback from Mailman's mailman.log >> for the shunted messages? > > My test just now raised the following error: > ...> File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/model/member.py", line 174, in _lookup > pref = getattr(self.address.preferences, preference) > AttributeError: 'NoneType' object has no attribute 'preferences' > Mar 09 20:52:56 2021 (26271) SHUNTING: 1615323176.8137882+cd8501dd322d0ca6b4a3a187d57bc691cd0ec343 > > and running the following command raised the result below > root@mail:~# mailman qfile var/queue/shunt/1615323176.8137882+cd8501dd322d0ca6b4a3a187d57bc691cd0ec343.pck That result is as expected. It isn't the message that causes the problem. We are now back to <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> As I said there, Mailman is going through the roster of regular (non-digest) list members to find those with delivery enabled and it finds a member that has no associated address. Can you view the members of this list? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: Default Setting for 'Results per Page' and other Web Pull-downs

by Mark Sapiro

On 5/5/23 14:25, Dave Hall via Mailman-users wrote: > > My question: when I go to any page that has a list (of lists, of members, > or archives), there are pulldowns like 'Results per page' that seem to > reset to the minimum number when I refresh the page. There are others like > 'Hide inactive' on the Archives page. What I'm looking for is a per-user > way to customize these values so I don't have to keep on setting them to > the value I prefer. > > If that is available in a later release then I have something to look > forward to. If not, it sure would be nice to have. No, it is not available. You can submit a wishlist issue at https://gitlab.com/mailman/postorius/-/issues/new for Postorius and https://gitlab.com/mailman/hyperkitty/-/issues/new for HyperKitty. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: Alleviating confusion regarding"Subscription options" that are left unselected.

by Mark Sapiro

On 5/31/23 15:41, Mark London wrote: > > So instead I added the following line to the web page. Which is > displayed on other options setting web pages, but is not displayed when > you click "Manage Options" for a specific mailing list. I added this, > to the file list_options.html: > > <p>{% trans 'Any options displayed as not set here, inherit at runtime > from your global preferences (viewable on other tab)' %}</p> > <hr /> More correctly it should say "Any options showing as not set inherit at runtime from your global or address specific preferences (viewable on other tabs)" as it says, e.g., at https://lists.mailman3.org/mailman3/accounts/per-subscription-preferences/. > Although I had to fix the wording, as elsewhere it says: "Any options > showing as not set here have inherit at runtime.." That's been fixed. See https://gitlab.com/mailman/postorius/-/merge_requests/810 -- 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: RDS CA changes

by Mark Sapiro

On 8/12/24 10:23, Hirayama, Pat wrote: > > As near as I can tell from reading the Mailman 3 docs, and looking at my mailman.cfg and settings_local.py ... I don't know that Mailman 3 is using certificate verification for the PostgreSQL connection. At least, I can't see anything in those configuration files that suggest this. Does anyone know if this is the case – or which configuration file I should look at to verify? Will my Mailman 3 be ok if the DBAs go ahead and update the certificates on their end? There are two places where the database access is defined. They are the [database] section in mailman.cfg and the DATABASES definition in Django's settings. I don't see a way in either of these to specify TLS for the connection, possibly it is set on the PostgreSQL side. In any case, I don't think there'd be any issue if the DBAs go ahead and update the certificates on their end. -- 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

Search results for query "sapiro"