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

[MM3-users] Re: Email to list owner on list creation only sent when using mailman create --notify command

by Mark Sapiro

On 6/9/24 5:26 PM, Perry Kollmorgen wrote: > Hi, > > This is only a minor issue, however as a nicety for new list owners I am hoping there is work around or something I have missed. > > I have the following file: templates/domains/<fqdn_listname/en/domain:admin:notice:new-list.txt > > When I use the mailman create command with the --notify option the new owners receives an email with the correct template info from the above file. > > However when I use mailmanclient python bindings or Postorius to create an list, there is no email sent. This is a bug. Currently only `mailman create` sends this notice, but as you note, list creation via rest should do it too. I have created https://gitlab.com/mailman/mailman/-/issues/1156 for this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

[MM3-users] Re: Mailing list welcome message won't update

by Mark Sapiro

On 1/9/25 13:58, via Mailman-users wrote: > > I have updated the welcome message for a mailing list by directly updating the file at: > file:///var/lib/mailman3/templates/lists/[redacted].lists.[redacted].org.au/en/list:user:notice:welcome > > I then restarted theses services: mailman3, mailman3-web and nginx. > > But when I test subsribe to the mailing list, the welcome message does not update. > > GNU Mailman 3.1.1 (Between The Wheels) > Postorius Version 1.1.2 These are extremely old - over 7 years. This may have something to do with the issue. There may be an issue in that the template table in the database is saying to look elsewhere. What do you get for a database query like ``` SELECT uri FROM template WHERE name = 'list:user:notice:welcome' AND context = '[redacted].lists.[redacted].org.au'; ``` where `[redacted].lists.[redacted].org.au` is the actual list-id. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 1 week

[MM3-users] Re: Installation problem: Ubuntu 18.10 mailman3-full. EMAIL_HOST_USER

by Mark Sapiro

On 2/4/19 6:30 PM, worik wrote: > Friends > > I am installing on a fresh ubuntu 18.10 using mailman3-full. > > Following http://docs.mailman3.org/en/latest/config-web.html after > http://docs.mailman3.org/en/latest/config-core.html and I have got to > point where I am a bit stumped. > > I have to set EMAIL_HOST_USER and EMAIL_HOST_PASSWORD > > I am unsure what I should use here. What sort of user? First of all, your primary resource for support of this package should be the packager, i.e. Debian. That said, presumably these are used to set smtp_user and smtp_pass in Mailman's config. These are described as: > # How to connect to the outgoing MTA. If smtp_user and smtp_pass is given, > # then Mailman will attempt to log into the MTA when making a new connection. > smtp_host: localhost > smtp_port: 25 > smtp_user: > smtp_pass: -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 7 months

[MM3-users] Re: Cannot setup announce-only mailing list

by Mark Sapiro

On 1/30/20 5:42 AM, Alberto Granzotto wrote: > > Of course, I want to keep this mailing list "read only" for members, and > I want only selected people to post to that mailing list. > > Any idea on how to achieve that? There is only one difference between the `Discussion` and `Announce` list styles, and that is for an `Announce` list, the `allow_list_posts` attribute is set to `False`. In turn, all that does is cause the List-Post: header to be set to NO rather than the list posting address. There is a discussion at <https://wiki.list.org/x/4030685> of how to set up an announce list for Mailman 2.1. Most of this translates straightforwardly to Mailman 3, although not all the relevant settings are exposed in Postorius. In short, you need to set this up manually using things like moderation settings and custom templates for the welcome message. -- 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: mailman not starting, status is active (exited)

by Mark Sapiro

On 8/19/20 10:26 AM, Ricardo Kleemann wrote: > Hi, > > After quite a long time with no issues, I’ve started having a problem where mailman won’t start and I don’t see any clear error message Is this Mailman 3 or Mailman 2.1? If Mailman 2.1, the appropriate list in mailmain-users(a)python.org <https://mail.python.org/mailman3/lists/mailman-users.python.org/>. The usual cause of Mailman not starting in either case is a stale master lock. In either case, the locks are in a directory named locks/ in Mailman's hierarchy. In the Mailman 3 case if that directory contains files master.lck and master.lck|hhhh|pppp|tttttt (hhhh is the host name, pppp is a PID and tttttt is a timestamp) and the PID pppp is not running on the host, just remove those files. For Mailman 2.1, its the same except the names are master-qrunner master-qrunner.hhhh.pppp -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: Alias for a list name

by Mark Sapiro

On 10/6/23 09:49, Lars Bjørndal wrote: > > To run mm 3 through Postfix, I use local_recipient_maps and > transport_maps. > > What I want to achieve, is alias medlem(a)list.saf-org.no to > saf-medlem(a)list.saf-org.no > > I tried to put > > medlem(a)list.saf-org.no: saf-medlem(a)list.saf-org.no > > and get the following error when running newaliases: > > postalias: warning: /etc/aliases, line 231: name must be local > > Is it possible to do this aliasing in a simple way? If list.saf-org.no is a local domain, i.e. in mydestination, the alias would be medlem: saf-medlem(a)list.saf-org.no or more simply medlem: saf-medlem If list.saf-org.no is not a local domain it needs to be a Postfix virtual (alias or mailbox) domain and you need a virtual_alias_maps with an entry like medlem(a)list.saf-org.no saf-medlem(a)list.saf-org.no -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: Issue with mailman auto subscription

by Mark Sapiro

On 8/20/24 2:45 AM, Francisco Paco López wrote: > > I migrated my mailman 2 instance to mailman 3 some months ago. Some users have been reporting lately that auto subscriptions don't work anymore. In the affected list both the Subscription and un subscription policies are open, which means that normally a user that sends a "subscribe" mail automatically subs to the list. This works fine for users that have been subscribed in the past but not for new users. The latter get a mail stating that a confirmation is needed ("Your confirmation is needed to join the XXXX(a)my.lists.com mailing list"). I see nothing out of the ordinary in the mailman.log file and co. In Mailman 3 addresses need to be verified. Even if a list's subscription policy is open, if the request is from an unverified address, a confirmation request is sent to verify the address. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: Mailing list welcome message won't update

by Mark Sapiro

On 1/21/25 20:26, via Mailman-users wrote: > > I also found that the actual file containing the welcome message and footer message does not have the .txt extension for my dev instance. The files will not be used unless they have the .txt extension. You need to rename them to add the .txt extension. > root@mailman-dev:/var/lib/mailman3/templates/lists/[redacted].mailman-dev.dev.aws.[redacted].org.au/en# ll > total 12 > drwxr--r-- 2 mailman operations 4096 Jan 22 14:14 ./ > drwxr--r-- 3 mailman operations 4096 Oct 1 13:50 ../ > -rwxr--r-- 1 mailman operations 0 Oct 1 13:50 list:member:regular:footer* > -rwxr--r-- 1 mailman operations 506 Jan 22 14:12 list:user:notice:welcome* > > What is that * at the end of the file name mean? It means the file is executable. It shouldn't be so you can change the mode from rwxr--r-- to rw-r--r-- -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 3 weeks

[MM3-users] Re: What to backup?

by Mark Sapiro

On 5/27/19 3:05 PM, Alain Kohli wrote: > Thank you, that's perfect! For anyone that might stumble upon this, I > had to make two minor adjustments to automate it. > snipped because formatting was off. > > # I couldn't run it with '--run' and if you pipe it into 'mailman > shell' # I needed this or the loop above wouldn't execute. pass It won't run with --run as I wrote it because `mailman shell` only predefines the various interface names and getUtility when entering interactive mode. To use --run, you need to import those. I have attached msgs_del.py which will run with --run. It incorporates the test for msg not None (thank you), makes a minor variable name change (file -> fn) and adds a print of the number of files removed. It has my path to var/messages hard coded, so that may need to be changed. -- 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: Out runner not sending emails, stuck on recvFrom.

by Mark Sapiro

On 10/20/21 11:03 AM, 01ste02(a)gmail.com wrote: > My mta is logging a connection, which times out every three minutes. The strace for the out runner shows the following: > ... > connect(21, {sa_family=AF_INET, sin_port=htons(465), sin_addr=inet_addr("127.0.0.1")}, 16) = 0 > recvfrom(21, > > And the mailman smtp-log shows: > > Oct 20 19:58:04 2021 (1262375) <163474270655.1243104.7078333516263200191@xxx> delivery to xxx@xxx failed with code 444, Connection unexpectedly closed > Oct 20 19:58:04 2021 (1262375) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7f219bf93310> > Oct 20 19:58:04 2021 (1262375) Connecting to 127.0.0.1:465 Is the local MTA listening on 127.0.0.1:465? If so, is some firewall blocking that connect? We are waiting for a response from the MTA to the connect and it never comes, Even if [mta] settings like smtp_user: smtp_pass: smtp_secure_mode: smtp_verify_cert: smtp_verify_hostname: are somehow not correct or appropriate, we don't seem to be getting that far. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

Search results for query "sapiro"