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

[MM3-users] Re: hyperkitty won't list more than 5 posts and shows empty grey Activity Summary box

by Abhilash Raj

On Wed, 9 Aug 2017 15:45:48 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 08/09/2017 02:35 PM, Abhilash Raj wrote: > > Hi, > > > > On Wed, 9 Aug 2017 13:42:20 -0700 > > Mark Sapiro <mark(a)msapiro.net> wrote: > [...] > > > > I wasn't aware that Core needed cron jobs too, is that true for 3.1 release as > > well? > > > It's only that one and whether it's needed or not depends on list > configuration. The list has attributes digest_send_periodic and > digest_size_threshold. When a post is received it is added to the list's > digest mbox, and if that causes the size of the mbox to reach > digest_size_threshold K bytes, a digest is sent. Additionally, if > digest_send_periodic is true, a digest is sent periodically whether or > not it has reached digest_size_threshold. > > However, the sending of periodic digests depends on cron running > something periodically to actually trigger the sending. Can this be done using the REST API? If not, maybe we should do that so that Postorius can take of the periodic tasks? I am thinking mostly about the container images because the mailman-core container runs nothing else other than Core. I'd have to another cron for this which isn't a lot of overhead but since mailman-web container already has periodic tasks, it would be great if I could trigger it from there. > > Note: I've just looked at the code and there seems to be an issue with > using 'mailman digests --send' to send the periodic digests. It appears > that if a list's digest mbox has any messages, 'mailman digests --send' > will send a digest even if digest_send_periodic is false. I've just > reported <https://gitlab.com/mailman/mailman/issues/384> for this issue. Also, it seems that Postorius doesn't have any way to set `digest_send_periodic` and only has a setting to set the max_threshold for the digest. I opened another issue (https://gitlab.com/mailman/postorius/issues/211) to add this feature. -- thanks, Abhilash Raj

7 years, 10 months

[MM3-users] Re: Missing whitespace in postfix_vmap after mailman genaliases

by Wolfgang Bock

Dear Mark, I am running mailman3 (version 3.2.1) on debian buster. Created yesterday a Test mailinglist and faced the same problem in postmapping postfix_vmap again. Is the debian buster version of mailman3 not uptodate?? Regards Wolfgang -----Ursprüngliche Nachricht----- Von: Mark Sapiro <mark(a)msapiro.net> Gesendet: Sonntag, 20. September 2020 00:43 An: mailman-users(a)mailman3.org Betreff: [MM3-users] Re: Missing whitespace in postfix_vmap after mailman genaliases On 9/19/20 3:05 PM, Wolfgang Bock via Mailman-users wrote: > > after creating a new list I got the following errormessage: > > mailman aliases -> postmap: warning: > /var/lib/mailman3/data/postfix_vmap, > line 17: expected format: key whitespace value > > /var/lib/mailman3/data/postfix_vmap > # AUTOMATICALLY GENERATED BY MAILMAN ON 2020-09-19 07:44:34 .... > xxxxxxxxxxx(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-bounces(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-bounces(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-confirm(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-confirm(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-join(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-join(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-leave(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-leave(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-owner(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-owner(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-request(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-request(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-subscribe(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-subscribe(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-unsubscribe(a)lists.xxxxxxxxxxxxxxxx.dexxxxxxxxxxx-unsubscri > be@xxx > xxxxxxxxxx.de > > The last line in the left part contains 48 chars. It isn't clear what you really have, but I'm guessing that in each case except the last, what you show as two lines is actually a single line with whitespace between and the last line has no whitespace. This is <https://gitlab.com/mailman/mailman/-/issues/651>, fixed in Mailman 3.3.1 by <https://gitlab.com/mailman/mailman/-/merge_requests/576>. > I solved the problem by adding a whitespathe last line has no > whitespace.ce in the last line and I made a new postmap for postfix_vmap. > > But it would be better to solve the problem by changing the genaliases > process in the next update. Already fixed and released in the last update. -- 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/

4 years, 8 months

[MM3-users] Re: Using the API to create nonmembers with a different moderation action than the list default

by Perry Kollmorgen

Oh great, that will be very useful when it is ready. It is easy for standard users to maintain a list which can be used also for sending access to other lists, particularly when nested. This along with the extra URL variables for use in templates look handy also. I already have added some URLs to our templates manually however if we expand to other domains it would save on some updating of templates. Usually, I would look to merge in useful PRs to my own branch of the source code used in production however with the use of docker this time around it isn't quite as easy. Likely not too difficult, but it might be good to wait too. Regards, Perry ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Saturday, June 8, 2024 3:59:46 AM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Using the API to create nonmembers with a different moderation action than the list default On 6/6/24 11:36 PM, Perry Kollmorgen wrote: > Hi, > > My next challenge is to script the setup of a bunch of nonmembers who have a moderation action of accept (or maybe defer) whilst the list itself has a nonmember action of hold. > > This is due to a relatively heavy use of nested lists, and have a fair number of people who might possibly send to all lists, and are important enough they wouldn't want to be manually allowed each time even if it only once. Note that beginning with Mailman 3.3.10 (not yet released) you can put things like @list2@example.com in accept_these_nonmembers of list1(a)example.com to accept posts from non_members who are members of list2(a)example.com. See https://gitlab.com/mailman/mailman/-/merge_requests/1154 -- 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/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to pcjkollmorgen(a)hotmail.com

1 year

[MM3-users] Re: sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none()

by Shashikanth Komandoor

Thank you Mark. What you have said is right.. I found a list with two "hyperkitty" records in the listarchiver in the database. I had removed the list and recreated it and now I found it is working fine. The recreated list is having only one record. After searching the links you provided I found there is just a work around but not the precaution to be taken for not getting the duplicate record. Can you say what might be the reason for this duplication? If I need to provide any details, please let me know. On Fri, Jul 24, 2020 at 11:50 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/24/20 10:34 AM, Shashikanth Komandoor wrote: > > Hi Team, > > > > Today, I found an error message like "Multiple rows were found > > for one_or_none()" when a hold message is approved for a list. Until > > yesterday the mails were accepted and delivered fine. > > > We have seen this issue before. See > <https://gitlab.com/mailman/mailman/-/issues/657>. There are also > multiple threads on it in the archive, e.g., > < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > >. > > We don't know how it happens, but the issue is that the `listarchiver` > table in the database has multiple `mhonarc` entries for the same > `mailing_list_id`. > > You can see the problem with the query > > select * from listarchiver where name = 'mhonarc'; > > There will be two entries with the same `mailing_list_id` and deleting > one of them will fix this and you can run `mailman unshunt` to reprocess > the shunted messages. > > The above referenced issue contains a script that can be run to remove > the extra entry. > > -- > 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/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

4 years, 10 months

[MM3-users] Re: Mailman 3, postfix domains, and postgresql cannot authenticate user

by Keith Christian

Odhiambo, Yes, trying to. Mark, I'll review your suggestions. Thanks. On Wed, Jul 3, 2024, 12:52 Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/3/24 09:22, Keith Christian via Mailman-users wrote: > > > --------------------------------------------------------------------------- > > First issue:Postfix v3.5.8 on RHEL 8. > > The below is from journalctl -xe: > > > --------------------------------------------------------------------------- > > Jul 03 08:12:04 somehost.somedomain postfix/qmgr[947499]: error: open > > database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or > > directory > > Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open > > database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or > > directory > > Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open > > database /opt/mailman3/mm/var/data/postfix_lmtp.db: No such file or > > directory > > > > I manually created the var_dir: /opt/mailman3/mm/var directory > > specified in the mailman.cfg file. > > How do I find out how to populate the postfix_domains.db files, and > > the postfix_lmtp.db file? > > > The `mailman aliases` command generates the postfix_domains and > postfix_lmtp files and calls the configured postmap_command (default > /usr/sbin/postmap) to create the .db files. `mailman start` also > generates these files by default. > > > > > --------------------------------------------------------------------------- > > Second issue: Postgresql authentication. > > PostgreSQL v10.23. > > > --------------------------------------------------------------------------- > > I have this in the active mailman3.cfg file, where xxxxxxxxxx is the > > same complex password in the mailman3 config file: > > url: postgresql://mailman3:xxxxxxxxxx@localhost/mailman3/mailman3 > > > I don't think you should have two /mailman3 at the end > > the form is `postgresql://user:password@host:port/database_name` The > default port is 5432. > > -- > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to keith1christian(a)gmail.com >

11 months

[MM3-users] Re: Help with fresh debian install

by Mark Sapiro

On 10/3/19 5:17 PM, Mark Dadgar wrote: > > I brought up a fresh install of Mailman3 via the current Debian package alongside my current 2.1 setup (installed and updated from source since 2002) on Ubuntu 18.04 LTS. > > Importing lists from 2.1 has been a real problem. > > I am trying to import a list with no archives to keep it simple while I prove out the process. If I run the mailman import21 comment as my user, I get the following errors: > > — > mark@mail:/tmp$ mailman import21 announce(a)pdc-racing.net ./announce-config.pck > Traceback (most recent call last): > File "/usr/bin/mailman", line 11, in <module> > load_entry_point('mailman==3.1.1', 'console_scripts', 'mailman')() > File "/usr/lib/python3/dist-packages/mailman/bin/mailman.py", line 94, in main > initialize(config_path) > File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 189, in initialize > initialize_2(propagate_logs=propagate_logs) > File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 152, in initialize_2 > mailman.core.logging.initialize(propagate_logs) > File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 157, in initialize > _init_logger(propagate, sub_name, log, logger_config) > File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 110, in _init_logger > handler = ReopenableFileHandler(sub_name, path_abs) > File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 50, in __init__ > self._stream = self._open() > File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 53, in _open > return codecs.open(self.filename, 'a', 'utf-8') > File "/usr/lib/python3.6/codecs.py", line 897, in open > file = builtins.open(filename, mode, buffering) > PermissionError: [Errno 13] Permission denied: '/var/log/mailman3/mailman.log' This is the issue. I don't know how the Debian packages do this, but I recommend having a 'mailman' user that owns everything and running commands as that user. > Error in atexit._run_exitfuncs: > Traceback (most recent call last): > File "/usr/lib/python3.6/logging/__init__.py", line 1945, in shutdown > h.flush() > File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 56, in flush > if self._stream: > AttributeError: 'ReopenableFileHandler' object has no attribute '_stream' This is due to the prior permissions error. > If I run it as root, it runs for a long time but spews a HUGE stream of these errors to /var/log/mailman3/mailman.log: If there are a lot of members to add, that can take a long time. The current version of import21 has a progress thermometer for this. > — > Oct 03 17:08:48 2019 (19118) Skipping and preserving unparseable message: 1570147727.3029191+80f1cc4d18f54868ad6162e8e41e52567185e983 > Oct 03 17:08:49 2019 (19118) Uncaught runner exception: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1570147728.618866+174175d39c301feab4ebb2aac0a51226334fa54c.pck' > Oct 03 17:08:49 2019 (19118) Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 156, in _one_iteration > msg, msgdata = self.switchboard.dequeue(filebase) > File "/usr/lib/python3/dist-packages/mailman/core/switchboard.py", line 150, in dequeue > with open(filename, 'rb') as fp: > PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1570147728.618866+174175d39c301feab4ebb2aac0a51226334fa54c.pck' First, I don't know what these messages are. Normally import21 doesn't send any mail. I'm guessing it's trying to send 'you are subscribed' notices to the users, but it shouldn't be doing this. All these files should wind up in Mailman's var/queue/bad/ directory with a .psv extension. You should be able to examine them with the 'mailman qfile' command. Whatever they are, the error comes from virgin runner so import21 should have actually succeeded. Did it import the list? > It also dumps some mail footer templates into the template directory that are owned by root, which seems … incorrect? It makes a weak effort at converting the list's msg_footer and digest_footer into MM 3 templates in templates/list/<list-id>/<list-lang>/. These are owned by root in your case because you ran import21 as root. > Any thoughts on what’s going wrong here? It looks like this may be an issue with the Debian package, at least the sending of messages part. As for the rest, the Debian package should install stuff as a Mailman user, perhaps 'mailman' or 'list', and you should be running all commands as that user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

[MM3-users] Re: Subscription request cannot be moderated: 404 Not Found

by Eric Broens

Hi Mark, I can't find any log entry which indicate a problem with this subscription request. The _request table does not contain a request for the specific mailinglist, but I am not sure if subscription requests are included in this table. The token is found in the pended table: +-----+------------------------------------------+---------------------+ | id | token | expiration_date | +-----+------------------------------------------+---------------------+ | 115 | 4d6b4b11266c7332684c5a492eb3f92c531f761b | 2031-01-04 16:17:38 | +-----+------------------------------------------+---------------------+ These are the relevant entries in the pendedkeyvalue table: +------+--------------+-------------------------------------+-----------+ | id | key | value | pended_id | +------+--------------+-------------------------------------+-----------+ | 1130 | type | subscription | 115 | | 1131 | list_id | "********************" | 115 | | 1132 | email | "***********************@*********" | 115 | | 1133 | display_name | "" | 115 | | 1134 | when | "2021-01-06T16:17:38" | 115 | | 1135 | token_owner | "moderator" | 115 | +------+--------------+-------------------------------------+-----------+ Can I workaround this problem for this specific subscriber by adding entries in the _request table, and if so what do I need to add? Thanks in advance, Eric On Friday, January 15, 2021, 11:42:47 PM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 1/14/21 3:43 PM, Eric Broens via Mailman-users wrote: > Hi Mark, > The link that shows the subscription request pending approval is as follows: 'https://<host_url>/postorius/lists/<listname>.<domain>/subscription_requests' > > The link behind the accept button is as follows. 'https://<host_url>/postorius/lists/<listname>.<domain>/handle_subscription_request/4d6b4b11266c7332684c5a492eb3f92c531f761b/accept' > > I have checked if there is already a subscription with that email address, but that's not the case. I don't know why that would 404 unless the token 4d6b4b11266c7332684c5a492eb3f92c531f761b didn't exist, but since it came from a "current" view, it should be good. I have seen occasional issues where two moderators attempt to handle the same request in close succession - i.e. both get the pending request and try to handle it and the second fails because the request is gone, but that appears not to be the case here. You might check the web server logs, the Django log and Mailman's logs to see if there is any more of a clue. -- 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/

4 years, 4 months

[MM3-users] Re: How to identify the exact reason behind the shunting of the mails ?

by Shashikanth Komandoor

Thank you Mark for your immediate response. The below are the tracebacks I could find in the mailman log. *Jun 17 19:04:08 2021 (8642) Uncaught runner exception: sequence item 0: expected str instance, Header foundJun 17 19:04:08 2021 (8642) Traceback (most recent call last): File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/var/lib/mailman/mailman/src/mailman/runners/pipeline.py", line 37, in _dispose process(mlist, msg, msgdata, pipeline) File "/var/lib/mailman/mailman/src/mailman/core/pipelines.py", line 50, in process handler.process(mlist, msg, msgdata) File "/var/lib/mailman/mailman/src/mailman/handlers/avoid_duplicates.py", line 59, in process addrs = getaddresses(msg.get_all(header, [])) File "/usr/lib64/python3.6/email/utils.py", line 112, in getaddresses all = COMMASPACE.join(fieldvalues)TypeError: sequence item 0: expected str instance, Header foundJun 17 19:04:08 2021 (8642) SHUNTING: 1623936848.367641+4753f8127953071ddcabfe828ebe72fcf04d0ae2* In the shunt file, I see something like this as below in CC while To is good: *Cc: =?unknown-8bit?q?=22Support_Zimbra=22_=3Csupport-zimbra=40nic=2Ein=3E=2C?= =?unknown-8bit?b?ICLgpLbgpLDgpKYg4KSu4KS+4KSl4KWB4KSwIC0gU2hhcmFkIE1hdGh1ciIgPHN1cHBvcnQtdmFqcmFAc3VwcG9ydGdvdi5pbj4s?= =?unknown-8bit?b?ICLgpLDgpL7gpJzgpYfgpLYg4KS44KS/4KSC4KS5IC0gUmFqZXNoIFNpbmdoIiA8cmFqc0BuaWMuaW4+LA==?= =?unknown-8bit?b?ICJTYWJ5YXNhY2hpIENob3VkaHVyeSIgPHNhYnlhQG5pYy5pbj4sIG1haWxhZG1pbkBuaWMuaW4s?= =?unknown-8bit?b?ICJNUklUVU5KQVkgS1VNQVIiIDxta0BuaWMuaW4+LCAiQmhyaWd1IEt1bWFyIiA8YmhyaWd1QG5pYy5pbj4s?= =?unknown-8bit?b?ICJPbSBQcmFrYXNoIiA8b3AubmhxQG5pYy5pbj4sICJIYXJpaGFyYW4gTSIgPGhhcmloYXJhbi5tQGdvdi5pbj4s?= =?unknown-8bit?b?ICJQaGlzaGluZyBQaGlzaGluZyIgPHBoaXNoaW5nQG5pYy5pbj4sICJpbmNpZGVudCIgPGluY2lkZW50QG5pYy5pbj4s?= =?unknown-8bit?b?ICJNYW5hdiBSYWtoZWphIiA8bWFuYXYucmFraGVqYUBuaWMuaW4+?=* Also, I came to know that two of the recipients in CC block have their mail ID display name in their local language. While I am not sure, I doubt if it could be the issue of getting shunted. Please confirm and suggest any solution. On Thu, Jun 17, 2021 at 8:48 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/17/21 6:56 AM, Shashikanth Komandoor wrote: > > > > Is there any chance to find out the reason for shunting of the > > mails through any means ? > > > > > Look in Mailman's var/logs/mailman.log for the tracebacks associated > with the shunted messages. > > -- > 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/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

3 years, 11 months

[MM3-users] Re: lmtp runner not starting

by Guillermo Hernandez (Oldno7)

El 1/4/23 a las 21:14, Mark Sapiro escribió: > On 4/1/23 12:00, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> >> El 1/4/23 a las 20:44, Mark Sapiro escribió: >>> ... >>> lmtp runner did not start because at some point it had died and >>> restarting Mailman won't restart a runner that died and was marked >>> to not restart. >>> >>> You need to stop Mailman and make sure when mailman is stopped that >>> there are no files in mailman's var/locks/ directory (remove any >>> that are there) and then start Mailman and lmtp runner should start. >>> >> I stopped mailman and removed all that was in there (there were many >> locked registers). Restarted mailman, and it shows the same error >> that in my previous mail. >> >> Now there is two new locked files, one (master.lck) which its content >> is the name of the other file. And the second one has the same content: >> >> master.lck|www.proteccion-civil.eu|9389|7022761192045613065 > Sorry, I sent my previous mail, and then received this > > Those are the master lock that prevents Mailman core from starting > when it is running. They should not be removed unless Mailman core is > stopped. Everytime I deleted that files I previously have stopped mailman, yes > >> will try deleting the content of var/locks and restarting the server > > If you had completely stopped Mailman core and then started it, lmtp > runner should have started. What are the complete log messages from > mailman.log following the start? > I sent them before > What does `mailman conf -s runner.lmtp` show? > Here it is: root@www:/usr/local/mailman3 # /usr/bin/su -m mailman3 -c "/usr/local/bin/mailman -C /usr/local/mailman3/var/etc/mailman.cfg conf -s runner.lmtp" [runner.lmtp] class: mailman.runners.lmtp.LMTPRunner [runner.lmtp] instances: 1 [runner.lmtp] max_restarts: 10 [runner.lmtp] path: [runner.lmtp] sleep_time: 1s [runner.lmtp] start: yes -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

2 years, 2 months

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

by Abhilash Raj

On Thu, Aug 13, 2020, at 10:04 AM, Mark Sapiro wrote: > 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 If this is one-click, can't this URL be hit by anyone trying to remove the user from any MailingList without any auth or anything? > > 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 > _______________________________________________ > 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)

4 years, 9 months

Search results for query "sapiro"