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

[MM3-users] Re: Hyperkitty Error Curiosity

by Mark Sapiro

On 11/11/20 4:18 PM, Brian Carpenter wrote: > > Some sort of auto-discard procedure after a number of retries? Is it > possible to detect a message with a null characters and automatically > discard them? Do such messages make it into the thread table? The message has been delivered to the list, but it is not archived. The list post has an Archived-At: header with a URL, but the message isn't there at all. The only way to get it archived is to correct the message defect. Thus, I don't think it's good to just discard the message at that point. I'm fine with moving out of or not queueing it in the first place in var/archives/hyperkitty/spool, but I think it should be preserved somewhere, say in var/archives/hyperkitty/bad, and along with that, some kind of notice sent to the site admin so bad messages don't just accumulate without being seen. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

[MM3-users] Re: Maximum number of recipients Setting

by Mark Sapiro

On 4/3/21 1:45 PM, Brian Carpenter wrote: > I have run several tests. It looks like on the 'Maximum number of > recipients' setting, a 2 means 1. If I set it to 2, I can have the > listname(a)listdomain.com only. If I have a CC, it comes to me for > moderation. If I set it to a 3, I can send out to > listname(a)listdomain.com plus a CC. If I set it to 3 and add 2 CC's plus > the listname(a)listdomain.com address, it comes to me for moderation. I understand it's confusing, but it's been that way since the beginning of Mailman 2.1. The docs at <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rules/docs…> say "For backward compatibility, the message must have fewer than the maximum number of explicit recipients." I agree the description in Postorius could be clarified see <https://gitlab.com/mailman/postorius/-/issues/515>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: Mailman3 Setup

by Mark Sapiro

On 6/5/22 06:26, George R. Kasica wrote: > Hello: > > I'm in the process of setting up Mailman3 on Ubuntu 20.04. I have the following Environment, and please ask if I left something needed out: > Postfix > Apache2 > MySQL > Mailman3 (all 3 bits mailman3, mailman3-web, python-mailman-hyperkitty) > The install SEEMS to have worked, but I'm looking for a guide for setup now. I used to run 2.1 about 18 months ago, but the server failed, and I never reinstalled it. I figured now, with a newish Ubuntu 20.04LTS Server, I'd go the mailman3 route...I've seen MANY posts of issues getting MM3 working with 20.04. Should I go back to 2.1, or what is the best way to get mailman-3 configured? You should definitely go with Mailman 3. The docs are at https://docs.list.org/ (redirects to https://docs.mailman3.org/en/latest/) I suggest you start by looking at https://docs.mailman3.org/en/latest/install/virtualenv.html -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: Importing mbox files into archive defect with lines with From

by Mark Sapiro

On 9/19/23 2:25 AM, Alex Schuilenburg via Mailman-users wrote: > > Prefixing the line with '>' allows the hyperkitty_import to partially succeed - partially as the line and everything below it is omitted from message in the archive. Presumably because the archiver thinks the remainder is a quote which it omits? > > Prefixing with a single whitespace was the best work-around, since the renderer ignores it when viewing the message from the archive. As discussed earlier in this thread, issues with unescaped 'From ' lines in message bodies exist because of the format of *nix mbox files where lines beginning with 'From ' are message separators by definition. Escaping such lines by prefixing them with `>` is a defacto standard. As far as this causing HyperKitty to ignore the rest of the message is concerned, I do not see that with current 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, 1 month

[MM3-users] Re: Cannot Create New List

by Mark Sapiro

On 11/3/25 08:01, dap1--- via Mailman-users wrote: > > Anyway, I still need help. I migrated my mailman2 to mailman3 per the documentation and all seemed to go well. However, now that I have the web UI working, no lists show up. Indeed, using mysql, all the relevant tables in mailman db are empty. How do I figure out if the import really worked when there are no error messages? If `mailman import21` didn't report any errors, it really did the import. Likewise if `mailman-web hyperkitty_import` didn't report any errors, it really did the import. If you followed https://docs.mailman3.org/en/latest/install/virtualenv.html your database is postgreSQL, not MySQL. What do you have in the [database] section in /etc/mailman3/mailman.cfg and in the DATABASES definition in /etc/mailman3/settings.py? Based on https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… I think you have more than one configuration and things are confused between them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 2 weeks

[MM3-users] Opinions wanted.

by Mark Sapiro

There is currently a merge request at <https://gitlab.com/mailman/django-mailman3/-/merge_requests/345> to hide the "Results per page:" dropdown from some Postorius and HyperKitty pages when the full list of items (lists) is on the page. I.e. when the number of items is <=10 and the "Results per page:" is the default 10, don't display the dropdown. However there is some controversy over whether this should also apply say when the number of items is > 10 but still is on one page. So the question is if we are going to hide the dropdown when "Results per page:" is the default 10 and there are <= 10 items so all are on the page, should we also hide it when say "Results per page:" is 25 and there are 22 items all on the page. Your opinion on this is requested via a reply in this thread. See the merge request (link above) for arguments pro and con. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 1 week

[MM3-users] Re: How to Increase outgoing mail volume for Mailman 3

by Mark Sapiro

On 11/10/20 12:30 PM, Brian Carpenter wrote: > Hello everyone, > > We had a new client come on board that brought a list that had the > largest out-going mail volume that I have ever dealt with. So I did what > any sane server administrator would do that is running Mailman 3: I ran > to Mark Sapiro for help! Here is what the Sage of all things Mailman > counseled me to do: Thank you <blush> > 1. Disabled VERP delivery. VERP can help improve mail delivery by > delivering 1 message per SMTP transaction (I think I got that right). > Using VERP is counter-productive as it can seriously delay outgoing mail > delivery for a high-volume list. So you can use something like the > following in the MTA section of your mailman.cfg: Actually, I mentioned VERP, but I don't think I recommended disabling it. Also note that these settings: > [mta] > verp_confirmations: no > verp_personalized_deliveries: no > verp_delivery_interval: 0 are the defaults. Further, verp_confirmations is a holdover from MM 2.1 and has no effect, although prior to Mailman 3.3.2 confirmations were sent with `confirm <token>` as the Subject: and beginning with Mailman 3.3.2, confirmations are sent with `Your confirmation is needed ...` as the Subject:. Actually, I think enabling VERP with [mta] verp_delivery_interval: 1 is generally a good idea for more reliable bounce detection. > 2. I configured Mailman 3 to run 4 outgoing runners. The default is 1. > This action was the game changer. It allows Mailman to handle 4 incoming > messages at a time instead of 1. My client's incoming list volume was > high enough where it was overwhelming the single outgoing runner. Here > is what I added to the mailman.cfg file: > > [runner.out] > instances: 4 > > Doing this step immediately solved the backlog in var/queue/out. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

[MM3-users] Re: From address of subscription notifications

by Mark Sapiro

On 2/26/19 2:11 PM, worik wrote: > > When I subscribe some body to to a list I on I get a notification that > says it comes from changeme(a)example.com > > As far as I can tell no subscribers are getting mail with that, so this > is not a crises. But it is untidy and I cannot find where to change it. > > SERVE_FROM_DOMAIN is set in the mailman-web/environment section of > docker-compose.yaml (I am using the docker distribution...) You set it in your mailman.cfg. As it says in mailman/config/schema.cfg > [mailman] > # This address is the "site owner" address. Certain messages which must be > # delivered to a human, but which can't be delivered to a list owner (e.g. a > # bounce from a list owner), will be sent to this address. It should point to > # a human. > site_owner: changeme(a)example.com -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 7 months

[MM3-users] Re: how to delete a list member using the Linux command line

by Mark Sapiro

On 6/19/20 7:29 AM, Mike Wertheim wrote: > I have Mailman 3.2.1 installed (on Debian Linux), using exim4 as the MTA. > > I have been trying to figure out how to use the Linux command line to add > members to a list and delete members from a list, but am having trouble > with deleting. The --delete option to `mailman members` was introduced in Mailman 3.3.0. Your version doesn't have it. Note that as of the next (3.3.2) release, the --add, --delete and --sync options to `mailman members` are deprecated in favor of new `mailman addmembers`, mailman delmembers` and `mailman syncmembers` commands. It should be possible for you to install the current versions of all of these without upgrading just by copying the `cli_*members.py` files from <https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/commands> to the `mailman/commands/` directory in your current installation. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

[MM3-users] Re: Mysterious Bounces Being Logged

by Mark Sapiro

On March 26, 2021 2:08:01 PM PDT, Brian Carpenter <brian_carpenter(a)emwd.com> wrote: > >I would think any mail administrator for a mailman server would want to > >know why bounces are happening. I never saw this issue with Mailman 2. >Did it exist? No. Mailman 2.1 always included the DSN in notices to the admin. >Is the patch going to make it to the next version of Mailman 3 core? No. I don't think it's generally useful. It's use is too obscure. >Are >there any plans to make bounce processing more transparent to server >admins so we can troubleshoot delivery issues? Absolutely. At first MM3 wasn't processing bounces at all. A GSOC student did the bulk of the current implementation and we were happy to get that even though this piece was missing. We know we need it. If you don't think we're working fast enough, you can submit a merge request or dock our pay. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

5 years, 6 months

Search results for query "sapiro"