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

[MM3-users] Re: Replace "visit your dashboard" with URL link, like in Mailman 2.

by Mark Sapiro

On 5/8/23 09:52, Mark London via Mailman-users wrote: > Has anybody attempted to change the format of the emails that are sent > to the owner of a mailing list, to include a URL, instead of stating > "visit your dashboard"? The former is the behavior of Mailman 2. Many users, e.g. Jens Günther whose replied to this thread, have made custom templates to do this. > Is there any reason why this can't be done? If nobody has tried to do > so yet, I'll give it a try myself, as I'm familiar with django. Thanks. See https://gitlab.com/mailman/mailman/-/issues/901 and https://gitlab.com/mailman/mailman/-/issues/1055 Also see https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for some documentation of templates, but note that you don't need to set URI's via REST, You can place list specific templates in Mailman's var/templates/lists/<list-id>/<lc>/ directory, domain specific templates in var/templates/domains/<domain-name>/<lc>/ and sitewide templates in var/templates/domain/site/<lc>/ or you can create list and/or domain specific templates via Postorius but see https://gitlab.com/mailman/postorius/-/issues/366 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: Fwd: Re: Removing a mail addresses and users

by Mark Sapiro

On 6/10/20 3:33 PM, Allan Hansen wrote: > > Some dedicated and skilled developers are currently investing heavily in a replacement for Postorius, but I really believe that any work is better spent transforming Mailman Core etc. into a true account-based system. Then, and only then, will it make sense to build new and better interfaces on top, as, without a healthy core, such interface will currently may have to inherit the confusion and disconnect that currently is so aggravating. I think you misunderstand what Mailman Core currently is. I think Mailman Core's concept of User is exactly what you are talking about when you ask for a "true account-based system". The problem is that Mailman Core was intentionally designed without any web UI and a RESTful API for separate web based UIs or whatever to use to communicate with it. Then the people who developed the web based management UI (Postorius) and archive UI (HyperKitty) chose to develop those within a Django framework and Django has its own concept of User separate from Mailman Core and that is where the disconnect occurs. It's not that Mailman Core lacks what you want. It's that Django doesn't use it. -- 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: Mailman3 don't work if aliases are enabled

by Mark Sapiro

On 10/9/20 3:37 PM, Massimo Zappalà wrote: > > If I try to uncomment the last two rows in main.cf > virtual_alias_maps = mysql:/etc/postfix/mysql_virtual_alias_emails.cf, mysql:/etc/postfix/mysql_virtual_alias_maps.cf > virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailbox_maps.cf > The aliases and email messeges works fine but the mailman3's mailinglist don't work. > > How can I solve this? I'm not certain about this. The Postfix log entries for the failed delivery to Mailman may help, but I think you deed to configure an alias domain or domains for your list domain(s). The alias domain is not a real domain and is not in DNS. it is any unused domain name and will be known only to Postfix. I typically use x.example.com where example.com is the real list domain. You can set the alias domain for the real domain in the domains view in Postorius. Then you need to add `hash:/var/lib/mailman3/data/postfix_vmap` to your main.cf virtual_alias_maps setting and run Mailman's `mailman aliases` command to generate the proper /var/lib/mailman3/data/postfix_* files. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…>. You may also need to set relay_domains = hash:/var/lib/mailman3/data/postfix_domains -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Re: Set domain inactive / archive import from other domain.

by Mark Sapiro

On 09/15/2018 07:15 AM, Johannes Winter wrote: > > we've migrated a list from another domain and would like to keep the > archives. Hyperkitty doesn't recognize the emails in the mbox archive > during import due to the other domain name. I don't understand the problem. I just ran a test where I imported a mbox containing 3 messages which were not even list posts and in which I had changed all the domain names to 'example.com'. I.e., in the mbox I imported, the headers containing domain names looked like From root(a)example.com Sun Aug 26 09:12:06 2018 Return-Path: <root(a)example.com> Delivered-To: root(a)example.com Received: by example.com (Postfix, from userid 0) From: Anacron <root(a)example.com> To: root(a)example.com Message-Id: <20180826161158.F154D34010C(a)example.com> X-msapiro-MailScanner-From: root(a)example.com and the 3 messages were all added to the archive. Why do you think the domain name is an issue? Perhaps the issue is there is already one or more messages in the archive and the messages you are importing are older. If you don't specify --since to hyperkitty_import it won't import messages older than the newest message in the existing archive. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 1 month

[MM3-users] Re: non-member moderation: list default vs default processing

by Mark Sapiro

On 5/21/21 3:58 PM, dancab(a)caltech.edu wrote: > > Each time this problem has come up I've had to change the moderation setting from "List Default" to "Default Processing". > But I've also noticed that some non-members were imported and already have "Default Processing" configured. > > Can you help me understand what determines this setting in Mailman3? > > It seems this would be something addressed via the mailman import21 option I've been using to import the lists. It depends in part on the version of Mailman core as `mailman import21` has had some changes, but here's how it should work. Regexps in MM 2.1 *_these_nonmembers are imported into the corresponding MM 3 *_these_nonmembers. Addresses in MM 2.1 *_these_nonmembers are imported into MM 3 as non-members with their moderation_action set to `defer`, `hold`, 'reject` or `discard` according to which *_these_nonmembers they came from. `accept` maps to `defer` and the others to the same. Prior to Mailman 3.3.0, `accept` mapped to `accept` but `defer` is better. This can get very convoluted if the same address is both a member and in *_these_nonmembers, but in both MM 2.1 and MM 3, the member takes precedence. Is this not what you are seeing? -- 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: How to store additional information about lists?

by Mark Sapiro

On 5/29/21 7:31 PM, Stephen J. Turnbull wrote: > > There won't be a membership adapter in Systers Mailman if there isn't > one in GNU Mailman, because they used the stock user database and > added fields to the User record to implement their membership > extensions. > > Membership adapter is a Mailman 2 feature that allowed use of an > external membership database (such as a corporate LDAP system). I > thought it was ported to Mailman 3 but maybe not. Actually, it's not quite that simple. Mailman 2.1 defines a MemberAdaptor class, the methods of which are used for everything to do with list members and memberships and are all documented in the base definition in Mailman/MemberAdaptor.py and all raise `NotImplementedError`. Also included in Mailman 2.1 is Mailman/OldStyleMemberships.py which subclasses MemberAdaptor and actually implements the methods, storing the data in the same config.pck pickle as the list settings. Various people have implemented various other MemberAdaptor classes for various purposes. https://bugs.launchpad.net/mailman/+bug/558106 contains several revisions of one using LDAP for the (read only) membership data. The Mailman 3 analog of this is the IMember interface defined in mailman/interfaces/member.py and implemented in mailman/model/member.py -- 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]Incorrect URLs

by Mark Sapiro

There are various URLs exposed in various emails from the list, many of which are wrong. The underlying issue is there are generic replacements such as $listinfo_uri and $user_options_uri in various templates such as the welcome.txt list welcome message and the footer-generic.txt message and digest footer. Now that the Mailman 3 core engine has been separated from the web UI, the core doesn't know what these replacements should be and there is not yet an interface to get them from Postorius or whatever the web UI is. In the mean time, I have made list specific versions of welcome.txt (done before announcing the list) and footer-generic.txt (just now) with the correct URLs hard coded. The purpose of this post is two-fold. To explain the issue, and to test the footer. There are probably more of these incorrect replacements and I will fix them as I notice them or they are pointed out to me. Note that I am aware that the https URLs in the List-Subscribe: and List-Unsubscribe: headers added to posts are wrong, but I haven't got a handle on this yet. The mailto: links in those headers are correct as are the Archived-At: and List-Archive: URLs as there is an interface to get those from the archiver. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 years, 6 months

[MM3-users] Re: What implications do GDPR have on Mailman, and how to requiring members to accept registration

by Mark Sapiro

On 5/17/18 3:35 AM, Henrik Rasmussen wrote: > > I am also concerned that new lists are created with a subscription policy "Confirm" as default, rather than at least "Moderate", which can cause people to be subscribed by others against there will. I'm confused. Confirm sends a confirmation request to the subscribed address which must be acted upon by the user before she is added to the list. Moderate just means approval by an owner/moderator which, it seems to me is more susceptible to a 3rd party subscribe succeeding - i.e., subscription requires membership in some organization. A subscribes B who is a member of the organization but doesn't want to be on the list. The moderator verifies that B is an organization member and approves the subscription. Granted, it may be possible for some brain-dead vacation responder to confirm a subscription request, but that's a separate issue. > Also, regardless of this setting, administrators can subscribe people without their knowledge. Granted that this can be abused, but not allowing admins to directly add members will probably create more problems than it solves. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 5 months

[MM3-users] Re: mail stuck in "out" queue

by Mark Sapiro

On 6/13/20 6:30 PM, Kareem Zidane wrote: > Hi Mark, > > Sorry to bother you! Just wanted to loop back on the above to see if you might have any thoughts on that by chance? I'm sorry, I thought I had replied, but clearly I hadn't. So as I understand it, you have multiple lists in this Mailman 3 installation, and only one list has this issue, and mail to this list gets archived, but not delivered but is queued in var/queue/out and remains there. This is hard to understand. When Mailman's out runner processes its queue, it processes messages in chronological order without regard to which list they are from, so it must be at least attempting to deliver these messages, and somehow failing and requeueing them. I do see this Jun 09 17:36:31 2020 (82) Cannot connect to SMTP server postfix on port 25 in the log excerpt you posted. What's in Mailman's smtp.log and the postfix mail.log that might be related to this? It's hard to understand how an MTA connect issue could affect only one list. If it is accepting the connict and then dropping the connection for too many invalid RCPT addresses, that's a possibility. -- 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: Mailserver Log entries following through mailman?

by Mark Sapiro

On 11/10/23 12:39, Andreas Barth wrote: > > is there some way to find an ID to follow an email through mailman? In > the exim logfile there is only something like C="250 Ok" (whereas in > mails sent to another exim there is something like C="250 OK id=…"). > (What I sometimes need to do is to follow an mail whether it is sent > through mailman and to where.) Every message should have a unique Message-ID: header. According to my reading of https://www.exim.org/exim-html-current/doc/html/spec_html/ch-log_files.html Exim should create a => log entry with an id= field containing the Message-ID when the message is received for delivery to Mailman and another similar entry when the message is received from Mailman for delivery to one or more list members. Mailman itself logs ACCEPT:, HOLD:, DISCARD:, REJECT: and OWNER: entries in mailman.log for those events (OWNER: indicates a message to list owners). All these entries contain the Message-ID. Mailman's smtp.log contains 'post to' and 'smtp to' entries with Message-IDs for all outgoing messages. > Or should I raise an issue as whishlist request? What exactly would you wish for that Mailman can do. -- 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

Search results for query "sapiro"