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

[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

5 years, 1 month

[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

3 years

[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, 11 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, 8 months

[MM3-users] Re: adding personalized email header/content in mailman 3

by Mark Sapiro

On 10/16/24 08:42, Alex I wrote: > > I tried creating a custom Handler (custom_header.py) in 3.3.19, adding outgoing_pipeline = custom_header in config [mta] section but it doesn't seem to be activating. First, can you accomplish what you want with a custom list:member:regular:header template? See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… If not and you need a custom handler, you have a couple of choices. You can patch the default_posting_pipeline at mailman/pipelines/builtin.py to add your handler to the _default_handlers after installing it in mailman/handlers/. This will require you to reapply the patch after any upgrade. You can create a plugin which defines a new pipeline which includes your new handler and set the posting_pipeline attribute of your list(s) to the name of your new pipeline. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/plugins/do… for some documentation and https://gitlab.com/mailman/example-mailman-plugin/-/tree/master for an example. -- 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: Adding user - Error 409 Subscription request already pending

by Mark Sapiro

On 4/20/19 8:55 AM, Kevin Hurtley wrote: > > It sounded on Github that some opinion was that it wasn't necessary to see these pending requests, but as "users will be users" I think would be useful to see what is in queue for subscription requests, it would be better yet to be able to either clear them out or accept them there. But at very least seeing them there would go a long way helping out my moderators troubleshoot. The issue with the way Postorius displayed all the subscription requests was that it wasn't possible for the moderator to distinguish request waiting moderator approval from those waiting user confirmation, and in general a moderator shouldn't approve a request waiting user confirmation, but this thread shows there is sometimes a need for a moderator to be able to deal with these. I have reopened <https://gitlab.com/mailman/postorius/issues/314>, and will look at fixing this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

[MM3-users] Re: Hyperkitty fulltext search performances

by Mark Sapiro

On 10/4/20 8:07 AM, Brian Carpenter wrote: > > On 10/4/20 8:59 AM, Loïc Dachary wrote: >> After a little digging it turns out the mailman3-web Debian GNU/Linux >> package I'm using is configured to use Woosh as a haystack backend. >> And it is not fit for volumes greater than a few hundred mega bytes. I >> should switch to something else from the list of supported >> backendshttps://django-haystack.readthedocs.io/en/master/backend_support.html >> > For our servers running Postorius/Hyperkitty, we use Xapian. I believe > the mailman-users (MM3) list also uses Xapian. It is a lot quicker. For > our Affinity/Empathy servers, we use Elasticsearch which we are very > happy with. Elasticsearch does have a higher memory requirement I > believe than Xapian. Brian is correct about this list. We started with Whoosh, then went to Elasticsearch and ultimately to Xapian. Each step gave better performance and a smaller footprint than the one before. -- 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: Handling of SPAM mails in mailman3 - Check for X-Spam Header

by Mark Sapiro

On 1/18/20 6:58 AM, Torge Riedel wrote: > Am 16.01.20 um 21:43 schrieb Mark Sapiro: >> >> This won't work for posts from members because the header checks are >> done between member moderation checks and non-member moderation checks, >> but if you create a Header Filter for header 'x-spam' and pattern 'yes' >> with action hold, a message from a non-member which has an X-Spam: Yes >> header should be held for that reason. >> >> > Hi Mark, > > thank you for your answer. Just to understand that right: In case a > posting with an "X-Spam: Yes" header comes from a member, it will not be > held? It will be directly forwarded to the list? No. I apologize for being unclear. A post from a member will first be handled according to that member's moderation action which may be the list's default action for posts from members or a specific action for that member. If that moderation action is reject, discard or hold, the post will be rejected, discarded or held as a moderated member post regardless of any header filters. If the action is accept, the post will be accepted without any further checks including the header checks. If the action is defer (default processing) the message will be held for matching the X-Spam: Yes header. What I meant was if the member's (or default) action was hold, the post would be held, but the reason would be moderated member, not header match. The bottom line here is the moderation action of accept should only be used in cases of a highly trusted member (such as a list owner) because it bypasses other checks, but the address is still subject to spoofing. In the normal case where a moderation hold is not desired, use the defer (default processing) action. -- 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: mailman2 import not working

by Mark Sapiro

On 7/29/20 9:33 AM, Abhijith PA via Mailman-users wrote: > > ------------------------------------------- > mailman create -o <foo(a)example.com> foo-bar(a)lists.example.com > mailman import 21 foo-bar(a)lists.example.com path/to/config.pck > ------------------------------------------- You don't need to specify an owner for `mailman create`. The owners will be imported. > After everything done tried a test mail, but didn't reach any of the > inbox though mail is archived. mailman.log says message is accepted > > ACCEPT: <FEE2E515-C054-41E6-9853-744D3312A137(a)xxxxxx.org> > Nothing after this. It is surprising that no exception/traceback/SHUNTING message(s) are logged. That would seem to say that Mailman's `out` runner is not running. I think Mailman's var/ directory in the Debian package is /var/lib/mailman3/, so what does `ls -aR /var/lib/mailman3/queue` show? Is there a .pck file either in shunt/ or in out/? what does `ps -fwwu list` show? There should be a lot of runner processes. Is there one with argument --runner=out:0:1? -- 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: New messages not being archived

by Mark Sapiro

On 7/22/21 11:41 AM, Sarah H wrote: > here is the full error message. Nginx proxies on http. > > https://pastebin.com/raw/TUf5dYi8 Thanks for the log. It is basically just confirming what we see with this. > the curl commands above result in. > ... > (venv) [mailman@sysname sarah]$ curl -X POST http://127.0.0.1:8000/hyperkitty/api/mailman/archive > curl: (52) Empty reply from server I am at a loss to understand why HyperKitty isn't responding. Are you able to access HyperKitty normally from a web browser? Do you get a response from ``` curl http://127.0.0.1:8000/hyperkitty/ ``` If so, what? What you should get from ``` curl -X POST http://127.0.0.1:8000/hyperkitty/api/mailman/archive ``` is ``` <html><title>Auth required</title><body> <h1>Authorization Required</h1><p>Please check whether the MAILMAN_ARCHIVER_KEY is provided by you and it is correct. </p></body></html> ``` You should get the same response as a web page if you go to https://example.com/hyperkitty/api/mailman/urls. Do you? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

Search results for query "sapiro"