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

[MM3-users] Re: warning: database postfix_domains.db is older than source file postfix_domains

by Torge Riedel

Am 27.10.20 um 00:45 schrieb Mark Sapiro: > Note that the only times both the `postfix_domains` and `postfix_lmtp` > are updated together is when one of the `mailman` subcommands `aliases` > or `start` is run. Are you possibly running both these at the same time > causing some kind of race condition? Hi Mark, thanks for your answer. First of all I ran a 'systemctl restart mailman', which now gives expected timestamps via 'stat' on the four files. I then checked what could cause a kind of race condition (there is only one server involved): - I have logrotate configured for daily rotate (which includes a 'systemctl reload mailman') - I have the cron jobs configured for mailman-web So it could be that cron jobs for mailman-web are running at the same time when mailman-core is asked to reload after log rotation. Could this lead to a race condition? But as you said: A 'reload' should not update the files. Kind regards Torge

4 years, 8 months

[MM3-users] Re: Multi-domain oddities in Hyperkitty and Postorius

by Jeremy Stanley

On 2023-02-16 11:06:40 -0800 (-0800), Mark Sapiro wrote: [...] > Yes, that doc really isn't appropriate for your purpose, but it's > the only one I could find on Django sites. Most of what it talks > about is for more complex situations than ours and whatever bits > are relevant are already done in Postorius/HyperKitty. Sorry for > leading you astray. [...] Please don't apologize, you've gone well out of your way to be helpful and it's very much appreciated. I've been on the other side of this conversation for plenty of projects and understand the challenges. > I don't think Django's docs address the simple task of adding a > site. While part of me wants to find that hilarious, I can't honestly claim the projects I work on are any better in that regard. Your latest recommendations have me un-stuck and left with a far better sense of how this fits together now. -- Jeremy Stanley

2 years, 4 months

[MM3-users] Re: MM3 generates long lines?

by Jörg Schulz

Maybe the solution would be to change the calls to email.sendmail like: results = self._connection.sendmail(envsender, recipients, msg.as_string(maxheaderlen=XXX) ) ? This error comes from some ios mail users after a number of answer/reply sessions; the References: in the header grow. Is this of any help? Am 09.02.24 um 23:07 schrieb Mark Sapiro: > On 2/9/24 13:50, Jörg Schulz wrote: >> did you ever find a solution to the issue "maximum allowed line >> length is 998 octets, got ... "? In the last days, I had some apple >> iphone originating emails in longish email threads where this happened. > > I'm not aware of a solution other that fixing the email clients involved. > >> Can the prototype archiver be activated additionally to hyperkitty or >> only as alternative? In the latter case: (how) can I archive the >> messages in question manually afterwards? > > It can be active additionally to hyperkitty. There's nothing that > prohibits all enabled archivers from being active on a list. >

11 months, 1 week

[MM3-users] Re: very few moderation capabilities for moderators

by Guillermo Hernandez (Oldno7)

On 18/9/21 20:42, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > On 18/9/21 20:27, Mark Sapiro wrote: >> from mailman.interfaces.action import Action >> def moderar(mlist, member): >> memb = mlist.members.get_member(member) >> if not memb: >> print('{} is not a list member.'.format(member)) >> return >> memb.moderation_action = Action.hold >> print('{} moderation_action set to hold.'.format(member)) > Just a one more silly question: Where do I can find the diferent values that memb.moderation_action can take? (I want to prepare the "unhold" script too) Thanks in advance. > That completely did it. The problem about finding the module was > completely gone when I made a soft link in the same directory where > mailman command is (in /usr/local/bin, for your info). > > Thank you very, very much. > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

3 years, 9 months

[MM3-users] Re: Mailman3 reinstall fail, need some help

by Yvan ♞

Yes, always this folder file problem, if I create the folder, when trying install answer is "mailman allready installed" https://paste.yunohost.org/raw/avaweyiqom Still searching... But I'm really not an expert... Yvan Le 12/03/2022 à 21:32, Mark Sapiro a écrit : > On 3/12/22 08:38, Yvan ♞ wrote: >> Yes it's debian and I have root access but it's a more "user >> friendly" server release. >> I tryed this but it block >> https://github.com/YunoHost-Apps/mailman3_ynh/blob/master/README.md >> >> https://yunohost.org/en/administrate/whatisyunohost >> Sincerely > > I don't read French very well, but your original logs at > https://paste.yunohost.org/raw/xiqoyajegi and > https://paste.yunohost.org/raw/hujesebita show installation failing > because it fails to create /etc/mailman3/mailman.cfg. > > This is either an issue with the Debian package or the YunoHost > installer or an incompatibility between them. > > I would go first to YunoHost for help and then to Debian if necessary. >

3 years, 3 months

[MM3-users] Re: Delete Django profiles not signed up to a list

by Andrew Hodgson

Mark Sapiro wrote: >On 1/1/21 4:41 PM, Andrew Hodgson wrote: >> I don't want to add captchas to the form right now but is there any way to clean out these users from the database perhaps periodically based on whether the accounts are subscribed to any list? >I have attached a script that will delete users from Django's user >database (the auth_user table) if there is no Mailman user with the >Django user's email address or if there is a Mailman user but it's not a >member, nonmember, owner or moderator of any lists. Thanks for this. >The setting DELETE_MAILMAN_USER controls whether it will also delete the >corresponding Mailman user that's not a member, nonmember, owner or >moderator of any lists. If set to True, it will. I did set this to true. The majority of users existed only in Django but around 20 existed in Mailman as well and looked like old addresses. Thanks again. Andrew.

4 years, 6 months

[MM3-users] Re: Problem with digests not being sent daily

by Mark

On 2024-06-23 03:24, Mark Sapiro wrote: On 6/22/24 20:04, Mark wrote: >> >> Oh? I was indeed assuming that 0 meant unlimited. The threshold was >> set at 0. >> My thinking was that meant the file size was not a factor in >> determining when the digest was sent and that the sending would be >> triggered by the daily cron. >> So my understanding of what you are saying is: if the threshold is set >> very large, say 100,000 kB - then a digest will be be sent by the >> daily cron even if it is smaller than 100,000 kB. > Correct. If Send Digest Periodically is Yes, any accumulated digest > will be sent when `mailman digests --periodic` runs, regardless of > size. Mark - Thank you very much for setting me straight on this. I had been stumbling around in the dark for days. With the threshold set extremely high, the daily digests are on track and list members are happy again. Best, Mark

1 year

[MM3-users] Re: Mailman3 via Docker and NGINX

by brian＠emwd.com

Abhilash Raj wrote: > On Wed, Dec 19, 2018, at 8:18 AM, Mark Sapiro wrote: > > On 12/19/18 7:03 AM, brian(a)emwd.com wrote: > > > I have Mailman3 installed on CentOS 7 using maxking's docker image. I believe > > the installation went fine and running "curl > > http://172.19.199.3:8000/postorius/lists/" produces the correct output. I also will > > be using exim and nginx with this installation. > > ... > > > location / { > > > include uwsgi_params; > > > uwsgi_pass 172.19.199.3:8000; > Change this to use port 8080 instead of 8000. 8000 is for HTTP protocol and 8080 is for > uwsgi protocol. > > See the docs[1]. > > [1]: https://github.com/maxking/docker-mailman#setting-up-your-web-server Thanks Abhilash. It is working now. FYI, I made the change directly in the nginx.conf file. I got rid of trying to use the conf.d/sitename.conf file. I now move on to getting exim to work. If I need help, I will start a separate thread. Brian

6 years, 6 months

[MM3-users] Re: mailman-web migrate fails: KeyError: 'django'

by David Newman

On 12/6/21 7:25 PM, Mark Sapiro wrote: > On 12/6/21 6:10 PM, David Newman wrote: >> Following the venv installation docs on a Debian 10 system, the >> command "mailman-web migrate" fails with a "KeyError: 'django'" error. >> >> Output pasted below [1]. > ... >> from mistune.scanner import escape_html, escape_url >> ImportError: cannot import name 'escape_html' from 'mistune.scanner' > > > You need to install > https://gitlab.com/mailman/hyperkitty/-/merge_requests/379 or downgrade > mistune in your venv with > > pip install mistune==2.2.0rc1 Thanks for this. I applied the one-line fix by hand from 379 and the command now runs clean. I first tried the 'pip install' command but it returned this error: venv) mailman@somehost:~ $ pip install mistune==2.2.0rc1 ERROR: Could not find a version that satisfies the requirement mistune==2.2.0rc1 (from versions: 0.1.0, 0.2.0, 0.3.0, 0.3.1, 0.4, 0.4.1, 0.5, 0.5.1, 0.6, 0.7, 0 .7.1, 0.7.2, 0.7.3, 0.7.4, 0.8, 0.8.1, 0.8.2, 0.8.3, 0.8.4, 2.0.0a1, 2.0.0a2, 2.0.0a3, 2.0.0a4, 2.0.0a5, 2.0.0a6, 2.0.0rc1, 2.0.0) ERROR: No matching distribution found for mistune==2.2.0rc1 Thanks again. dn

3 years, 7 months

[MM3-users] Re: Which crontab?

by Pierre Abbat

On Sunday, November 5, 2017 12:09:53 PM EST Mark Sapiro wrote: > When you run > > mailman info > > it will report among other things the location of 'config file:'. The > user who owns this file is the user that should run the > > mailman digests --send > > command. I.e., it should be in that user's crontab or in something like > '/etc/cron.d/mailman' with that user specified. > > Also see <https://gitlab.com/mailman/mailman/issues/436>. /etc/mailman.cfg should be owned by mailman? I checked my primary mailserver, my laptop, and my new Mailman box. ALL files in /etc (except links, which are lrwxrwxrwx and I didn't check what they point to) are owned by root.root or owned by root.<other> and not group writable, except one, the directory /etc/ mailman/, which is owned by root.list and is group writable (drwxrwsr-x). Are you saying that Mailman should be able to change its own config file? Pierre -- Don't buy a French car in Holland. It may be a citroen.

7 years, 8 months

Search results for query "sapiro"