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

[MM3-users] Re: Mailman3 not able to deliver emails sent through list, but moderation notifications

by Mark Sapiro

On 11/26/22 05:09, Daniel Böhmer wrote: > > During startup /var/log/mailman3/mailman.log receives: > >> Cannot connect to SMTP server localhost on port 25 ... > I found this article stating the the SMTP error message > might be misleading: > https://blog.tfiu.de/mailman3-cannot-connect-to-smtp-server-localhost-on-po… > > How to further debug this? > What could be wrong with my Mailman3 instance and how to fix it? The article is relevant and mentions the most likely issue which is lack of permission on one or more message templates. Everything in Mailman's var/ directory should be owned by Mailman's user:group - normally `list:list` in Debian packages. I'm only guessing here, but I suspect you ran `mailman import21` at some point as `root`. Never run `mailman` commands as `root`. Only run them as the Mailman user - `list` in Debian packages. Note that Mailman core in Debian Buster is 3.2.1. Since 3.3.5, "The mailman command will refuse to run as root unless the new --run-as-root option is specified." in order to help avoid this issue. -- 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

[MM3-users] Re: [Mailman-Users] Re: Member posting to a list but address not in membership list.

by Mark Sapiro

On 1/12/22 7:42 PM, Adam Morris wrote: > Hi Mark, > I've looked in all these places and the address isn't anywhere. (please keep the thread on the list) Then the address that's posting isn't what you think it is or something in your installation is broken. As I said, it could be that Reply-To: or Sender: is the list member, but depending on list settings, these things get overwritten in mail from the list, so you can't really know. If something is broken, you need to discuss this with your hosting provider who, unfortunately, may be no help. Many, not all, cPanel hosts offer mailman because it comes with cPanel, but actually know nothing about Mailman. See https://wiki.list.org/DOC/Mailman%20and%20CPanel > On 13-January-2022 11:31, Mark Sapiro wrote: >> On 1/11/22 7:51 PM, Adam Morris wrote: >>> I have someone who is posting to a list I run. >>> I subscribed them originally but their address doesn't show up in the >>> list of members so I can't change moderation status etc. >>> Where else could I look to find their address? >> >> >> The first check on a post is if any of the address in From:, Reply-To: >> or Sender: headers or the envelope sender is a list member, i.e. in >> the web admin Membership List. If so, that member's moderation is >> applied. If not, the next check is if the From:the *_these_nonmembers >> lists under Privacy options... -> Sender filters and finally Privacy >> options... -> Sender filters -> generic_nonmember_action. >> >> If a post to the list is being accepted without being held for >> moderation, either some address in From:, Reply-To: or Sender: headers >> or the envelope sender is in the Membership List with `mod` unchecked, >> or the From: or possibly Sender: address is in accept_these_nonmembers >> or generic_nonmember_action is Accept. >> > > -- > > Adam Morris > Mobile: 0414 431105 > Email, iMessage & FaceTime > adam(a)damorris.com > -- 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

[MM3-users] Re: Inaccessible User Profile

by Mark Sapiro

On 2/14/26 08:02, awingnut wrote: > I have a long time user that cannot access their profile. When I click > on users/members then that user as superuser, I get this error. > > Page not found > > This page either doesn't exist, or it moved somewhere else. It appears you may have an older version of the Users->members page cached in your browser or somewhere. > When I click that uers manage button, the page comes up but it says > there are no subscriptions. This user was subscribed as of couple of > days ago. Can this be fixed via admin functions? It appears the user was somehow unsubscribed. Unfortunately, Mailman's subscribe.log (by default part of mailman.log) is incomplete. See https://gitlab.com/mailman/mailman/-/issues/1143 This is fixed for the next release (3.3.11) but unless you've installed Mailman core from the head of the GitLab branch you don't have the fix. Even so, grepping Mailman's logs for the user's address may give a clue as to how the user was unsubscribed. To re-subscribe the user, you can use Postorius Mass operations->Mass subscribe or the command line `mailman addmembers`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months

[MM3-users] Re: WEB UI fail to reply and create new thread

by Mark Sapiro

On 12/19/20 3:02 AM, Carlo Landmeter wrote: > We are not running in debug mode, we simply set the loggers to log DEBUG or else we don't see much info. > I also doubt the shown error is the problem as I see more template errors. > I have also tried to run the official docker images mailman-docker but im having the same issue. > > When I post via the online form, i can see uwsgi requests with http status 200 from the ajax call, so i would expect it to work, but it does not leave a message in hyperkitty nor sends an email. > > PS emails are send just fine via smtp posting. The error reported from hyperkitty/ajax/temp_message.html in the OP has nothing to do with the replies not being sent or archived. hyperkitty/templates/hyperkitty/ajax/temp_message.html is called to build the HTML response sent to the web browser after the reply has been sent to Mailman core. Abhilash's fix at <https://gitlab.com/mailman/hyperkitty/-/merge_requests/299> will get rid of that error, but I would be very surprised if it fixes the problem. -- 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: Mixing Mailman 3 with AWS SES

by Mark Sapiro

On 3/24/21 7:58 AM, Brian Carpenter wrote: > On 3/24/21 9:54 AM, Ralph Weber wrote: >> Comments received directly from one of the people who developed the >> AWS Marketplace kits for Mailman 3 and Mailman 4 have definitively >> established that AWS Mailman is *not* intended to interact with AWS >> SES when receiving email messages > > I don't think there is a Mailman 4 and the person who is marketing his > services under that name is sending a confusing message to the public. Danil Smirnov owns both the mailman3.com and mailman4.com domains. Mailman 4 is apparently his branding of "Mailman 3 in AWS Marketplace". In response to our request, the following is included at the bottom of <https://mailman3.com/>: Mailman3.com (this site) is unaffiliated with Mailman3.org, the domain used to coordinate development of the Mailman 3 free software suite. The Mailman 3 core developers are not involved with Mailman3.com, and cannot answer any questions or provide any support related to its operations. If you are looking for resources for development of the Mailman 3 free software suite, please see mailman3.org. Yes, this is all ripe for confusion ... -- 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: Upgrading mailman 3 venv installation

by Mark Sapiro

On 9/29/21 10:52 AM, Morris Jones wrote: > > In my virtual environment, I ran `pip list -o` and got a significant > list. I noticed that all of the mailman packages seemed to be "Type > sdist" and the framework packages "Type wheel". (Dunno what "Type" means > in this context.) Type is the package type. sdist is a source distribution. wheel is a form of binary distribution. Older forms are egg and bdist. > So I tried `pip list -o | grep sdist` and got a smaller list: > > (venv) mailman@mail:~$ pip list -o | grep sdist > atpublic 2.1.1 2.3 sdist > django-allauth 0.43.0 0.45.0 sdist > django-mailman3 1.3.4 1.3.7 sdist > flufl.i18n 3.1.3 3.2 sdist > flufl.lock 5.0.3 6.0 sdist > HyperKitty 1.3.3 1.3.4 sdist > lazr.config 2.2.2 2.2.3 sdist > mailman 3.3.2 3.3.5 sdist > mailmanclient 3.3.1 3.3.3 sdist > mysqlclient 2.0.1 2.0.3 sdist > postorius 1.3.3 1.3.6 sdist > > Is this a reasonable list of the packages that I should update? Several of those are dependencies. The packages you should upgrade are mailman, postorius, hyperkitty, django-mailman3 and mailmanclient. Dependencies will be upgraded as required. If a dependency is not upgraded, the older version should work. -- 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: Multiple server replicas

by Mark Sapiro

On 5/23/23 19:33, Dave Hall via Mailman-users wrote: > > With Mailman 3 we would like to keep the same kind of setup. However, > things have changed quite a bit. Having both mailman and mailman-web > instances all share their respective MySql/MariaDB databases is the easy > part. For /var/lib/mailman3 it is a little less clear. So far I have > symlinked messages, archives, lists, data, and templates onto the NFS > share. I'm wondering about cache, locks, queue, and web/fulltext_index. cache is used to store the contents of templates which are retrieved by URI other than mailman:// URIs. I.e. mailman:// URIs refer to templates in the templates directory or in the Mailman installation itself so are cheap to retrieve. Other URIs can refer to possibly remote servers and may be expensive to retrieve so the contents are cached. In short, this should be shared. locks contains the master lock and others locking things used by this instance. This should not be shared. queue is the queues for this instance and should not be shared. In your installation, web/fulltext_index is the search index for whoosh which is apparently the hyperkitty configured search engine. This should be shared. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: Mailman3 doesn't send Mails to users (Debian12 with Plesk)

by Mark Sapiro

On 5/24/24 2:18 AM, marcus--- via Mailman-users wrote: > > The problem, however, is that it does not send out any mails, nor do they appear in the archive. > > When I look in the Mailman-Log I find: > > May 16 01:44:55 2024 (6833) Cannot connect to SMTP server localhost on port 25 This is a misleading error message. It can occur when Mailman's out runner can't read a template. You need to check ownership and permissions on mailman/templates in the code tree and Mailman's var/templates directory which probably has permissions errors from running inport21 as root. Also, if you've set any templates in Postorius, they may not be accessable if your setting for POSTORIUS_TEMPLATE_BASE_URL is not good. > May 16 01:48:15 2024 (61252) error opening connection to nntp_host: localhost > [Errno 111] Connection refused > May 16 01:48:15 2024 (61252) NNTP error for list vereinsmitglieder(a)ludothek.de: > [Errno 111] Connection refused Are you gating messages to/from usenet for this list? If so, you have to set host: and port: and maybe user: and password in the nntp section of mailman.cfg -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: Database permission problem?

by Mark Sapiro

On 10/15/24 15:24, Bill Oliver wrote: > > Yeah, I saw that, too. The double db files are created by postmap. I > haven't worried about it too much yet, since the permissions are the > same. I don't know why postmap does this, but it's next on my list of > things to fix. You should not be running postmap manually and never on a *.db file in any case. Mailman should be creating postfix_domains, postfix_lmtp and postfix_vmap and calling postmap on those to create the .db files. > In my main.cf postfix_lmtp is mentioned four times: > > virtual_mailbox_maps = > proxy:mysql:/etc/postfix/sql/mysql_virtual_mailbox_maps.cf, > > proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_domain_mailbox_maps.cf > #added 20241009 for mailman > hash:/opt/mailman/mm/var/data/postfix_lmtp ${dovecot} > > virtual_alias_maps = > proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_maps.cf, > proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_domain_maps.cf, > > proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_domain_catchall_maps.c > f > #added 20241009 for mailman > hash:/opt/mailman/mm/var/data/postfix_vmap > > #Mailman transport stuff > transport_maps = > hash:/opt/mailman/mm/var/data/postfix_lmtp > local_recipient_maps = > hash:/opt/mailman/mm/var/data/postfix_lmtp ${dovecot} Are you adding ${dovecot} to the local_recipient_maps and virtual_mailbox_maps mailman entries or was that there before? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users] Re: Separating Lists by Domain

by Mark Sapiro

On 1/3/19 2:34 PM, Abhilash Raj wrote: > > > On Thu, Jan 3, 2019, at 2:27 PM, brian(a)emwd.com wrote: >> So who manages Postorius? Is that a whole separate application from >> Mailman 3? Is there a way we can get whoever the developer is to update >> it where we can separate lists by domain the way Hyperkitty does? Mark >> Sapiro refers to this in the following post: >> >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > You can file an issue at https://gitlab.com/mailman/postorius/issues Yes, filing a GitLab issue is the best way to get things on the record. It's no guarantee that things will be addressed immediately, but they are there, and merge/pull requests are always welcome. As far as your question goes, Mailman Core, Postorius and HyperKitty are separate entities and they were mostly developed by separate people/groups and some important players have either overtly or implicitly retired from the project. Not long ago I write in another context > MM3 is much more complex than MM2.1 and there's a lot that I don't fully > understand myself. > > There is a basic core engine which does all the work of > creating/managing lists and users and receiving and sending mail. It has > no web UI per se. It exposes a RESTful API on the host server. > > The web management UI is Postorius and it is based on the Django web > framework and communicates with core via the REST API. The Archiver is > HyperKitty and it is fairly independent. It is also based on the Django > web framework. Account creation and web login is via django-allauth. > > Postorius, HyperKitty and the core were all developed separately by > different people and no one understands all of it. That said, Abhilash is currently the lead developer for all of Mailman 3 and he's doing a great job. I and a few others are also involved (I'd be more involved if I didn't have Mailman 2.1 to distract me), but we are a small group and things take time. And as I said, merge/pull requests for GitLab issues are always welcome. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 9 months

Search results for query "sapiro"