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

[MM3-users] Re: FILTER_VHOST = True doesn't work fine with alias_domain

by Mark Sapiro

On 2/17/22 15:15, Élodie BOSSIER via Mailman-users wrote: > Hello, > > My mailman3 installation is now functional, but the config "FILTER_VHOST > = True" doesn't work fine when I define "alias_domain" for the 2 > domains. I need to define that because I need to get "postfix_vmap" file. > > As you can see, list from others domains are visible on this URL : > https://ml.franceserv.fr/postorius/lists/ > > I would like https://ml.franceserv.fr/postorius/lists/ and > https://ml.viticreation.fr/postorius/lists/ with their own lists. There are issues with FILTER_VHOST due to the fact that mailing lists do not have a web host attribute. This means when you go to HyperKitty or Postorius when FILTER_VHOST is True, we look up the domain record for the web host you are visiting and show you all the lists whose mail host matches the mail host for the web host domain. This has nothing to do with alias domains. What that means is if all your domains records have a unique mail host, FILTER_VHOST will work as you expect, but if multiple domains have the same mail host FILTER_VHOST will show you the lists for the current web host plus all those with a matching mail host. I.e. if in your case, the ml.franceserv.fr domain and the ml.viticreation.fr domain have the same mail host, FILTER_VHOST won't separate them. If they have different mail hosts FILTER_VHOST will separate them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Mailman issues after re-boot

by Mark Sapiro

On 10/4/23 05:09, paulrubin37(a)gmail.com wrote: > Ok first I tried the force reinstall, that changed nothing. > > (venv) mailman@mail:~> pip install --force-reinstall psycopg2-binary\<2.9 > Collecting psycopg2-binary<2.9 > Using cached psycopg2_binary-2.8.6-cp311-cp311-linux_x86_64.whl You are forcing the version to be <2.9 which is why your venvs have 2.8.6. Note you are installing a cached version. That may be why it's broken. You could try ``` pip install --no-cache-dir --force-reinstall psycopg2-binary\<2.9 ``` or as I note below, if your Django is >=3.1 ``` pip install --no-cache-dir -U psycopg2-binary ``` ... > Here is what is in the file that is failing, If I read this right I need to check every single sub import. > > 50 > 51 from psycopg2._psycopg import ( # noqa > 52 BINARY, NUMBER, STRING, DATETIME, ROWID, > 53 > 54 Binary, Date, Time, Timestamp, > 55 DateFromTicks, TimeFromTicks, TimestampFromTicks, > 56 > 57 Error, Warning, DataError, DatabaseError, ProgrammingError, IntegrityError, > 58 InterfaceError, InternalError, NotSupportedError, OperationalError, > 59 > 60 _connect, apilevel, threadsafety, paramstyle, > 61 __version__, __libpq_version__, > 62 ) > 63 This is way too much detail. This psycopg2-binary is broken. You can't successfully import psycopg2 from it. You need to get a working psycopg2 installed rather than trying to fix your broken one. What is your Django version? The only reason for pinning psycopg2-binary<2.9 is for Django<3.1. See https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mail…. If your Django is >=3.1 try in your venv ``` pip install -U psycopg2-binary ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

[MM3-users] Re: Issues with cross posted emails after upgrading to mailman 3.3.6

by Mark Sapiro

On 11/4/21 12:58 PM, Simon Coggins wrote: > > Please file an issue for this at > https://gitlab.com/mailman/mailman/-/issues<https://gitlab.com/mailman/mailman/-/issues> and I will try to find a > better solution. Your approach of munging Message-IDs will create other > issues. Consider a post to a list with direct CC to userx. userx > replies-all to the message received directly. the In-Reply-To of this > reply is the unmunged Message-ID which will affect threading in the > archives and other recipient's MUAs. I realize this is preferable to > losing the message, but I hope we can do better. > > > Yeah it’s not a great solution but it’s the quickest I could come up with that works “for us”. 99% of our lists are announcement lists only with minimal replies so while this will break some. I’m hoping it will give us enough time to wait out a proper fix. I’ve created a new issue #955 with as much detail as I think you’ll need. Let me know if you need any more. Thanks for filing the issue. I'll work on a solution. My current thinking is to add a `count` column to the message table, set the count to 1 when initially adding a message-id, increment the count when adding an existing message-id, decrement the count when deleting a message-id and only delete the entry and message when the count reaches 0. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: Getting connection timed out

by Mark Sapiro

On 5/22/21 11:29 AM, blackout69 wrote: > Hello everybody, > > for a couple of days I have been seeing several lines calling these on > /var/log/mail.log > > May 22 18:22:57 glugct postfix/qmgr[21205]: 0ACE641C1B: > from=<lug-bounces(a)catania.linux.it>, size=3698, nrcpt=9 (queue active) > May 22 18:23:06 glugct postfix/qmgr[27175]: 0ACE641C1B: > from=<lug-bounces(a)catania.linux.it>, size=3698, nrcpt=9 (queue active) > May 22 18:23:36 glugct postfix/smtp[27177]: 0ACE641C1B: > to=<myaddress(a)simail.it>, relay=none, delay=55152, > delays=55122/0.07/30/0, dsn=4.4.1, status=deferred (connect to > mail.simail.it[217.27.113.30]:25: Connection timed out) ... > But always on a single email address.What could it depend on?Probable > that the mail.simail.it server is blacklisted? It's probably not blacklisting. It's not getting that far. Your `glugct` is attempting to connect to port 25 at mail.simail.it and the connect is not being answered. Normal blacklisting will not occur until after the remote MTA answers the connect and determines the IP of the caller. And in any case, if it is some kind of blacklisting it is your `glugct` server that is blacklisted by mail.simail.it. I just did the following ``` $ telnet mail.simail.it 25 Trying 217.27.113.30... Connected to mail.simail.it. Escape character is '^]'. 220 mail.simail.it ESMTP ready. quit 221 mail.simail.it closing connection Connection closed by foreign host. ``` so it did answer my connect. In any case, this is not a Mailman issue. It is between Postfix on your server and the remote server at mail.simail.it. -- 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: Templates via Webinterface are i) not set, and ii) set templates (files) are not shown in the Webinterface

by Mark Sapiro

On 9/30/23 10:53, Wikinaut wrote: > I use mailman3 since a while, for some of my lists I have been using > > - list:member:digest:footer.txt > - list:member:regular:footer.txt > > When I go to "Vorlagen" (LC: DE) (templates) in the web interface, I do _not_ see these two templates! Postorius templates are handled differently from file system templates. When you set a template in Postorius, that template becomes available in Postorius' API and an entry for the template in the template table in the database is created with a URI pointing to the template in Postorius' API. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for info about template URIs. The fact that Postorius doesn't show the file system template as the initial value when creating a template in Postorius is https://gitlab.com/mailman/postorius/-/issues/366 > When I got o my newest mailing list and when I setup templates via the Webinterfaces, these are shown there, but are neither working nor seen as files. They are not created as files - see above. The fact that they aren't working is probably because your Django setting for POSTORIUS_TEMPLATE_BASE_URL is not correct. This should be set to the scheme and host part of the URL you use to access Postorius, e.g., https://lists.mailman3.org for this list's installation. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

[MM3-users] Re: Single-Sign-out for List member

by Mark Sapiro

On 8/13/20 6:21 AM, w.schoener(a)alp.dillingen.de wrote: > > So I would like to ad a link in the footer of every message, with which every receiver/member can sign out of the newsletter with one click. > It does not seam to be possible, to put this into effect with mailman 3. > Does anybody have any hints, how to create a link, and when this link is called, the user is signed out of the newsletter. You can set the list's unsubscription_policy to open and set the link as a mailto: to the list-leave address, but that still requires a second click to send the mail. The solution is to create a web based CGI script which is called with a URL like <https://example.com/unsub_script/list.example.com/user@example.net> and have that script invoke the appropriate `mailman` command to remove the member from the list. Beginning with Mailman 3.3.2, this would be mailman delmembers -l list.example.com -m user(a)example.net -g to remove the member and send a goodbye message. In older Mailman, it would be something like echo user(a)example.net | mailman members -x - list.example.com I understand you may have a legal requirement do do this, but these "one-click - no user confirmation" links are a bad idea because usera will reply to a list post or forward it and not remove the link and userb will receive usera's reply and click usera's unsubscribe link either maliciously or thinking it will unsubscribe userb. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Re: New releases

by Abhilash Raj

On Thu, Jun 25, 2020, at 8:59 AM, Danil Smirnov wrote: > The issue has confirmed by other users: > > https://github.com/maxking/docker-mailman/issues/382 The issue seems to happen because the static files that are present at the default staticfile locations aren't valid anymore and aren't removed automatically on upgrades. You can run: sudo rm -rf /opt/mailman/web/static To remove them manually and then it should be re-created properly on the next start. I'll try to work on a fix for this in some automated fashion. > > вт, 9 июн. 2020 г., 20:49 Mark Sapiro <mark(a)msapiro.net>: > > > On 6/9/20 10:31 AM, Danil Smirnov wrote: > > > On Tue, 9 Jun 2020 at 20:23, Mark Sapiro <mark(a)msapiro.net> wrote: > > > > > >>> COMPRESS_OFFLINE = True > > >>> COMPRESS_ENABLED = True > > >> > > > > > > These two are commented out. > > > > > > Then compress shouldn't be trying to do anything. I can't explain what's > > going on. > > > > -- > > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > > 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/ > > > _______________________________________________ > 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/ > -- thanks, Abhilash Raj (maxking)

6 years, 3 months

[MM3-users] Re: A little stuck with installation of MM3 - ModuleNotFoundError: No module named 'flufl.lock'

by Mark Sapiro

On 7/30/20 11:24 AM, Odhiambo Washington wrote: > This works - I mean changes the error message to > > [Thu Jul 30 18:11:50.269667 2020] [wsgi:error] [pid 7627] [remote > 197.232.81.246:63962] > /opt/mailman/mm/venv/lib/python3.7/site-packages/readme_renderer-26.0-py3.7.egg/readme_renderer/markdown.py:38: > UserWarning: Markdown renderers are not available. Install > 'readme_renderer[md]' to enable Markdown rendering. > [Thu Jul 30 18:11:50.269700 2020] [wsgi:error] [pid 7627] [remote > 197.232.81.246:63962] warnings.warn(_EXTRA_WARNING) I'm not sure why you are getting this warning, and it's non-fatal, but you can get rid of it by pip install cmarkgfm in your virtualenv. > [Thu Jul 30 21:11:50.573233 2020] [authz_core:error] [pid 10846] [client > 197.232.81.246:63962] AH01630: client denied by server configuration: > /var/spool/mailman-web, referer: > http://mm3-lists.my.server/mm3/mailman3/lists/ > > There is NO /var/spool/mailman-web anywhere. It has not been created. > You mentioned that it should be created automatically, IIRC. No. I think I told you that the references to /var/spool/mailman-web/static in your Apache config should be changed to /opt/mailman/mm/static and that directory would be created/populated by mailman-post-update. I think you still have Alias /static "/var/spool/mailman-web/static" in your Apache config and it needs to be Alias /static "/opt/mailman/mm/static" That may be my fault as when I recently edited <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…>, I missed that line. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Re: Remove old bounces in bouncedir

by Mark Sapiro

On 3/10/22 00:31, Stephan Krinetzki wrote: > Mark Sapiro wrote: > >> If you are referring to messages in Mailman's bounces queue, if these >> are not processed and removed within 15 minutes of arrival, Mailman's >> bounce runner is not running. > > Well, it is the queue.Our var directory is under /opt/mailman/var and the /opt/mailman/var/queue/bounces is over 8GB big. There are *.pck messages and some of them are very old (>3 Years). The bounce seems to be running: > > ``` > Mar 10 09:24:53 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:00 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:06 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:12 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:18 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:24 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:30 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:36 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:43 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:49 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > ``` > > The process it self is there > > ``` > mailman 376 99.4 19.1 6578312 6279000 ? R 09:17 10:52 venv/bin/python3 venv/bin/runner -C mailman.cfg --runner=bounces:0:1 > ``` I don't understand what's happening. If the bounces runner is processing it's queue, those .pck files should be processed and deleted. Are there errors in /opt/mailman/var/logs/mailman? If you examine (some of) those files with `mailman qfile` do you see anything strange? Is there an ownership/permissions issue? Sometimes people run Mailman or some Mailman command as `root` and things get owned by root and then when Mailman is later run as `mailman` it can't delete or maybe even read them. >> If you are referring to bounce messages in the message store >> (var/messages/), there have been issues with those not being removed, >> but Mailman core >= 3.3.5 should clean those up. > > SInce the messages are hashed or otherwise stored, i can't verify or deny this. Is the size of the /opt/mailman/var/messages directory very big? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: Sending a message to a subscription applicant when a subscription request is made

by Mark Sapiro

On 3/28/23 10:45, Allan Hansen wrote: > > a. That we change the lines in the Python program in our installation that send 'list:admin:action:subscribe' to the list admins to instead send the template to the applying subscriber. This patch will do that ``` --- a/src/mailman/app/subscriptions.py +++ b/src/mailman/app/subscriptions.py @@ -338,7 +338,7 @@ class SubscriptionWorkflow(_SubscriptionWorkflowCommon): # This message should appear to come from the <list>-owner so as # to avoid any useless bounce processing. msg = UserNotification( - self.mlist.owner_address, self.mlist.owner_address, + self.address.email, self.mlist.owner_address, subject, text, self.mlist.preferred_language) msg.send(self.mlist) # The workflow must stop running here. ``` Watch for wrapped lines. Note that this only works if Admin immed notify is Yes. > b. That we change the lines in the Python program in our installation that send 'list:user:action:subscribe' to the subscriber with an unverified address to always do this, even when the incoming address has already been verified. I think this patch will do it, but needs testing ``` --- a/src/mailman/app/subscriptions.py +++ b/src/mailman/app/subscriptions.py @@ -285,7 +285,7 @@ class SubscriptionWorkflow(_SubscriptionWorkflowCommon): # If we do not need the user's confirmation, then skip to the # moderation checks. if self.mlist.subscription_policy is SubscriptionPolicy.moderate: - self.push('moderation_checks') + self.push('send_confirmation') return # If the subscription has been pre-confirmed, then we can skip the # confirmation check can be skipped. If moderator approval is ``` Again watch for wrapped lines. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

Search results for query "sapiro"