Search results for "Postorius" - Mailman-users

Re: MM3 templates

by Odhiambo Washington

On Wed, Feb 15, 2023 at 6:35 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/15/23 05:22, Odhiambo Washington wrote: > > > > 1. Where is this template that the system used and can I edit it? > > > /opt/mailman/mm/venv/lib/<python_version>/site-packages/mailman/templates/en/list:user:action:subscribe.txt > > You can edit it, but your edits will be overwritten if you upgrade. > I will not touch that. > > 2. Why is it not using the template I created? > > Is the template you placed in > /opt/mailman/mm/var/templates/lists/kictanet.lists.kictanet.or.ke/en/ > named list:user:action:subscribe.txt and does Mailman have permission to > read it? > Yes. [18:47 ~ ]$ ls -al /opt/mailman/mm/var/templates/lists/ kictanet.lists.kictanet.or.ke/en/ total 48 drwxr-xr-x 2 mailman mailman 512 Feb 14 08:53 . drwxr-xr-x 3 mailman mailman 512 Feb 14 08:54 .. -rw------- 1 mailman mailman 615 Jan 17 13:57 domain:admin:notice:new-list.txt -rw------- 1 mailman mailman 341 Jan 17 13:54 list:admin:action:post.txt -rw------- 1 mailman mailman 158 Dec 17 13:32 list:member:digest:footer.txt -rw------- 1 mailman mailman 452 Jan 17 13:54 list:member:digest:masthead.txt -rw------- 1 mailman mailman 137 Jan 17 13:55 list:member:generic:footer.txt -rw------- 1 mailman mailman 1219 Dec 8 15:12 list:member:regular:footer.txt -rw------- 1 mailman mailman 944 Jan 17 15:50 list:user:action:subscribe.txt -rw------- 1 mailman mailman 247 Jan 17 13:56 list:user:notice:post.txt -rw------- 1 mailman mailman 802 Jan 17 13:56 list:user:notice:probe.txt -rw------- 1 mailman mailman 639 Jan 17 13:57 list:user:notice:welcome.txt > Did you try to create a template in Postorius? If you did, that one will > take precedence. > Not at all. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 6 months

Re: Invalid confirm text

by Mark Sapiro

On 8/14/20 3:28 AM, w.schoener(a)alp.dillingen.de wrote: > > Now, when I try to subscribe to the list, I get my first message in german language, with the confirm request: > return the message unchange. > > When I return the message, I get an answer: > Invalid confirm text. With current releases of Mailman, the confirm request you receive should be: From: <listname>-confirm+<hex-token>@<list.domain> Subject: confirm <hex-token> with actual values for <listname>, <hex-token> and <list.domain>. This will change in Mailman 3.3.2, see <https://gitlab.com/mailman/mailman/-/merge_requests/678> > My request is pending. And there is no way to solve this pending request, in the webinterface, no subscription request is shown, no member is shown and no no-member is shown. Your reply should go to <listname>-confirm+<hex-token>@<list.domain>. Some MTA/MDA in the delivery chain may drop the ++<hex-token> suffix. If this is the issue, you can send a message with the one line confirm <hex-token> as either the Subject or body of the message to <listname>-request@<list.domain>. That should work. Note in the web UI (Postorius), at least in recent versions, even though it shows "Subscription requests 0" that should be a pull-down with the two choices Pending Approval and Pending Confirmation and selecting Pending Confirmation should show yours. The count badge only counts Pending Approval. > Have you any hint, what is going wrong. What do I have to respect to create a message, where the confirmation is working. See the current English confirmation template at <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/templates/en/l…> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

Re: Please help - Held message is crashing mailman.

by Alex King

Thanks for your help Mark, it's ideal having the pointer to the issue in gitlab. I'll raise a bug with Ubuntu because this makes mailman3 in their LTS version unusable for me. Perhaps they can backport a fix for their version in LTS, otherwise they may have a backport or PPA source where I can get a 3.2 version, or just pin some packages from cosmic or disco. I think documenting this will be useful to people who hit the issue in future (Bionic/18.04 is supported until 2023, and likely the most used until 20.04 is released). Thanks, Alex On 7/04/19 4:29 AM, Mark Sapiro wrote: > On 4/5/19 10:27 PM, Alex King via Mailman-users wrote: >> Hi, >> >> I've used mailman a lot in the past, and decided to install mailman3 in >> a recent install. I'm unimpressed so far, it seems buggy. >> >> Running on Ubuntu 18.04.2 LTS from packages, mailman3 3.1.1-9, >> mailman3-web 0+20170523-14, python-django-postorius 1.1.2-3. >> >> After a few messages, I now can't go to the "Held Messages" in >> postorius, I get a 500 error. >> >> I tried to interact on the command line, but could not work out how. >> Reading >> https://mailman.readthedocs.io/en/latest/src/mailman/docs/install.html >> and >> https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/shell.ht…, >> I tried: >> >> # mailman shell >> Welcome to the GNU Mailman shell >> >>>>> command = cli('mailman.commands.cli_withlist.shell') >> Traceback (most recent call last): >> File "/usr/lib/python3.6/code.py", line 91, in runcode >> exec(code, self.locals) >> File "<console>", line 1, in <module> >> NameError: name 'cli' is not defined >> >> I did a lot of reading of the manual and googled, but I have no idea >> where the cli object is supposed to come from.....? The documentation >> is confusing. > > The line > > command = cli('mailman.commands.cli_withlist.shell') > > in > <https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/shell.ht…> > is dependent upon some behind the scenes setup to make the doctests > work. Granted this is confusing, but basically all that does is set > things up for the doctests to run the 'mailman shell' command. It is not > intended to be run from within 'mailman shell'. > > >> Anyway, after some trial and error, i found: >> >> # mailman shell >> Welcome to the GNU Mailman shell >>>>> list_manager = getUtility(IListManager) >>>>> m=list_manager.get("committee(a)[redacted].org") >>>>> from mailman.interfaces.requests import IListRequests >>>>> requests = IListRequests(m) >>>>> [x for x in requests.held_requests][0].id >> 8 >>>>> requests.get_request(8) >> Traceback (most recent call last): >> File "/usr/lib/python3.6/code.py", line 91, in runcode >> exec(code, self.locals) >> File "<console>", line 1, in <module> >> File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", >> line 85, in wrapper >> return function(args[0], config.db.store, *args[1:], **kws) >> File "/usr/lib/python3/dist-packages/mailman/model/requests.py", line >> 120, in get_request >> result.data_hash, expunge=False) >> File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", >> line 85, in wrapper >> return function(args[0], config.db.store, *args[1:], **kws) >> File "/usr/lib/python3/dist-packages/mailman/model/pending.py", line >> 138, in confirm >> value = json.loads(keyvalue.value) >> File "/usr/lib/python3.6/json/__init__.py", line 354, in loads >> return _default_decoder.decode(s) >> File "/usr/lib/python3.6/json/decoder.py", line 339, in decode >> obj, end = self.raw_decode(s, idx=_w(s, 0).end()) >> File "/usr/lib/python3.6/json/decoder.py", line 355, in raw_decode >> obj, end = self.scan_once(s, idx) >> json.decoder.JSONDecodeError: Unterminated string starting at: line 1 >> column 1 (char 0) >> >> It seems something was written out to disk that can't be read in for >> some reason (assuming a json object on disk?) > > This is <https://gitlab.com/mailman/mailman/issues/385> which should be > fixed by <https://gitlab.com/mailman/mailman/merge_requests/333>. The > fix in in Mailman core version 3.2.0 > > >> How do I debug this further? How do I find the json being decoded? Any >> help would be appreciated. (I found mailman2 just worked, I was happy >> with that.) > > The issue is in storing a pickled representation of the json encoding of > 'rule_misses'. This gets very long if you have lots of header filters, > and with at least the mysql backend gets truncated in the database which > causes the Unterminated string error. > > I'm not sure what your options are for upgrading. The current Debian > packages are all >= 3.2.0 [1], but Ubuntu doesn't get 3.2.0 until cosmic > (18.10) [2]. > > [1] https://packages.debian.org/search?keywords=mailman3 > [2] https://packages.ubuntu.com/search?keywords=mailman3 > >> (My colleague posted a bug about this I believe but I don't have the >> link to that.) > > I haven't seen it. > >

6 years, 5 months

Re: Apache Conf

by Thomas G

I found ! Based on https://stackoverflow.com/questions/26848945/exclude-an-alias-from-virtualh… We have to exclude /static/ <VirtualHost *:80> ServerName mailing.hatlab.fr ErrorLog ${APACHE_LOG_DIR}/mailing.error.log CustomLog ${APACHE_LOG_DIR}/mailing.access.log combined Alias /static/ /opt/mailman/static/ <Directory /opt/mailman/static/> Require all granted </Directory> ProxyPassMatch ^/static ! ProxyPass / http://localhost:8000/ ProxyPassReverse / http://localhost:8000/ </VirtualHost> Le ven. 19 oct. 2018 à 21:08, Thomas G <thomas82710(a)gmail.com> a écrit : > Same result with Alias "/static/" "/opt/mailman/static/" > > I have sometimes: > [Fri Oct 19 22:05:52.583841 2018] [proxy_http:error] [pid 8328:tid > 140435053815552] (104)Connection reset by peer: [client 1xxxxxxx1794] > AH01102: error reading status line from remote server localhost:8000 > [Fri Oct 19 22:05:52.583874 2018] [proxy:error] [pid 8328:tid > 140435053815552] [client 1xxxxxxx:51794] AH00898: Error reading from remote > server returned by /static/hyperkitty/libs/jquery/jquery-1.10.1.min.js > But it's not systematic. > > Alias seem to be ignored by the proxy. > > > Le ven. 19 oct. 2018 à 20:48, Mark Sapiro <mark(a)msapiro.net> a écrit : > >> On 10/19/18 12:17 PM, Thomas G wrote: >> > Hi tried both. >> > >> > Same result. >> > >> > xxxx - - [19/Oct/2018:21:14:22 +0200] "GET >> /static/postorius/js/script.js >> > HTTP/1.1" 404 4051 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:60.0) >> > Gecko/20100101 Firefox/60.0" >> >> >> What's in the apache error log? >> >> -- >> 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/ >> >

6 years, 10 months

Re: Cannot setup announce-only mailing list

by Abhilash Raj

On Thu, Jan 30, 2020, at 9:58 AM, Mark Sapiro wrote: > 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, do you think we should make the actual announce-only style reflect these settings so folks don't have to manually set these after they create a announce-only list? I am not sure the reason behind these settings lacking for the current announce-only style. Are there situations where announce-only list would have different list setting? > > -- > 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)

5 years, 7 months

Hyperkitty archive: date format in thread overview of list does not honor DATETIME_FORMAT of settings.py

by Christian Schneider

Dear mailman community, with the help of you I was able to set up a new mailman3 environment (a big THANK YOU!!! :-)): OS: Ubuntu 24.04-LTS mailman: GNU Mailman 3.3.10 (Tom Sawyer) Python: 3.12.3 (main, Feb 4 2025, 14:48:35) [GCC 13.3.0] Method: Python Virtual Environment Installation My configuration files are placed in the following directory: /etc/mailman3 - gunicorn.py - mailman.cfg - settings.py The environment is up and running: A list for testing is set up and mails are transfered (and archived) using the test-list - successfully... :-) Looking at the thread overview of the list (in Hyperkitty archives) I realized that the shown date format is unusual (for Germany), like: Do Mai 22, 3:57 nachm. (meaning: Thu May 22, 3:57 p.m.) I would prefer a format like: 22-05-2025 15:57:24 So I tried to reconfigure this setting in settings.py according to this URL: https://docs.mailman3.org/en/latest/config-web.html#configure-postorius-hyp… In settings.py I set DATETIME_FORMAT to 'd-m-Y H:i:s' but the format did not change. (After changing settings.py I initiated a restart of mailman3 and mailmanweb) I also set USE_L10N to False as suggested in Django-Docs: https://docs.djangoproject.com/en/3.1/ref/settings/#std:setting-DATETIME_FO… My /etc/mailman3/settings.py is parsed - as far as I can say because changing USE_I18N to false (in /etc/mailman3/settings.py) switches date to English as this is my locales-setting on Ubuntu... Nevertheless the format stays the same (in this case: Thu May 22, 3:57 p.m.) How can I adjust the date format (in the discussion boxes) at the thread overview page (url: https://my-domain.de/archives/list/test-list@lists.my-domain.de/)? Any hint is appreciated! Thank you very much and kind regards Christian

3 months, 3 weeks

Re: Automatic migration from Mailman 2.1 (Debian buster) to Mailman 3 (Debian bookworm)

by Marc SCHAEFER

Hello, On Sat, May 25, 2024 at 11:38:40AM -0400, Mark Sapiro wrote: > The host name displayed in the web UI is based on the SITE_ID setting in > Django's settings. This is a system configuration not associated with any > lists. it references an entry in the django_sites table in the database. Thank you, will look into this. > As far as the comment/display name in From: is concerned, what specific > emails are you talking about? This. Sorry, I mixed From: with Subject: and the content: Date: Sat, 25 May 2024 13:37:29 -0000 From: postorius(a)lists2.alphanet.ch To: schaefer@XXX Subject: [example.com] Please Confirm Your E-mail Address Hello from example.com! You're receiving this e-mail because user Schaefer-XXX has given your e-mail +address to register an account on example.com. To confirm this is correct, go to [ ... ] Thank you for using example.com! example.com I guess it's the same SITE_ID setting in Django's DB: $ grep SITE_ID /usr/share/mailman3-web/settings.py SITE_ID = 1 However, I guess it's the default creation, by the Debian package, of the SQLite local database which presumably was done with example.com. I will anyway switch to a remote PostgreSQL database, and thus create a new one with the correct names. That should fix it. > for ADMINS in your Django settings. ADMINS = ( ('Mailman Suite Admin', 'schaefer(a)alphanet.ch'), ) That looks correct. > The `mailman import21` command will properly import the Mailman 2.1 > from_is_list and Sender filters -> dmarc_* DMARC mitigation settings. Thank you. Aka mailman-wrapper import21 on Debian so to switch to the correct user. > If you have some customization in this area, that probably won't be handled. Obviously.

1 year, 3 months

Re: Problems with mailman core translation and other details

by Mark Sapiro

On 2/7/24 12:47, Celi via Mailman-users wrote: > yes. thank you for asking. > > > > Em 07/02/2024 16:46, Mark Sapiro escreveu: >> On 2/6/24 2:41 PM, celi--- via Mailman-users wrote: >>> It´s the case below: the pair msgid/msgstr seems to be OK, but this >>> particular sentence is not being translated. >>> >>> #: templates/postorius/lists/summary.html:88 >>> #, python-format >>> msgid "" >>> "\n" >>> " To subscribe you can send an email with 'subscribe' >>> in the" >>> "subject to\n" >>> " <a href=\"mailto:%(address)s?subject=Subscribe\">" >>> "%(address)s</a>\n" >>> " or use the form below:\n" >>> "" ... >> >> >> Is the rest of that page translated appropriately? There is a possible issue with msgid "" "\n" " To subscribe you can send an email with 'subscribe' in the" "subject to\n" " <a href=\"mailto:%(address)s?subject=Subscribe\">" "%(address)s</a>\n" " or use the form below:\n" "" it should be msgid "" "\n" " To subscribe you can send an email with 'subscribe' in the " "subject to\n" " <a href=\"mailto:%(address)s?subject=Subscribe\">" "%(address)s</a>\n" " or use the form below:\n" Ignore the folded line, but note the trailing space in " To subscribe you can send an email with 'subscribe' in the " If that's the issue it is with the Debian package. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

Re: redirecting -bounces replies

by Hirayama, Pat

Hi Mark, Thank you for your reply. I admit that I don't know Mailman 3 as well as I knew Mailman 2. And the 2 -> 3 upgrade was handled by someone else, who has since left the org. As near as I have been able to discern, Mailman 3 is running on a docker host with four containers running, with mailman, postfix, nginx and django-uswgi in separate containers. % sudo docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 1b4262f81b98 mailman-nginx:1.21.3 "/docker-entrypoint.…" 3 years ago Up 3 weeks 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp mailman-nginx a5e4fa75ccb3 mailman-postfix:3.5.10-r0 "postfix start-fg" 4 years ago Up 2 weeks 0.0.0.0:25->25/tcp mailman-postfix 7a358c807714 mailman-django-uwsgi:2.0.19.1 "uwsgi --ini uwsgi.i…" 4 years ago Up 3 weeks 8000/tcp mailman-django-uwsgi 9a917897da10 mailman-core:3.3.1 "master" 4 years ago Up 3 weeks 24/tcp, 8001/tcp mailman-core When I look at main.cf inside mailman-postfix: transport_maps = hash:/opt/mailman/var/data/postfix_lmtp local_recipient_maps = hash:/opt/mailman/var/data/postfix_lmtp relay_domains = hash:/opt/mailman/var/data/postfix_domains virtual_alias_maps = hash:/opt/mailman/var/data/postfix_vmap-exceptions, hash:/opt/mailman/var/data/postfix_vmap When I look at the domains in mailman-core, I see: >>> show_domains() <Domain fhcrc.org> <Domain fredhutch.org> <Domain lists.fhcrc.org, , alias: lists.fredhutch.org> <Domain lists.hanc.info, , alias: > - owner: cit-sys-engineering(a)fredhutch.org >>> When I look at /opt/mailman/var/data/postfix_domains inside the postfix container, that seems to match: fredhutch.org fredhutch.org lists.fredhutch.org lists.fhcrc.org lists.hanc.info lists.hanc.info Now, when I look at the entries for a test list on lists.fhcrc.org, postfix_vmap looks like: pattest(a)lists.fhcrc.org pattest(a)lists.fredhutch.org pattest-bounces(a)lists.fhcrc.org pattest-bounces(a)lists.fredhutch.org pattest-confirm(a)lists.fhcrc.org pattest-confirm(a)lists.fredhutch.org pattest-join(a)lists.fhcrc.org pattest-join(a)lists.fredhutch.org pattest-leave(a)lists.fhcrc.org pattest-leave(a)lists.fredhutch.org pattest-owner(a)lists.fhcrc.org pattest-owner(a)lists.fredhutch.org pattest-request(a)lists.fhcrc.org pattest-request(a)lists.fredhutch.org pattest-subscribe(a)lists.fhcrc.org pattest-subscribe(a)lists.fredhutch.org pattest-unsubscribe(a)lists.fhcrc.org pattest-unsubscribe(a)lists.fredhutch.org and postfix_lmtp looks like: pattest(a)lists.fredhutch.org lmtp:[mailman-core]:24 pattest-bounces(a)lists.fredhutch.org lmtp:[mailman-core]:24 pattest-confirm(a)lists.fredhutch.org lmtp:[mailman-core]:24 pattest-join(a)lists.fredhutch.org lmtp:[mailman-core]:24 pattest-leave(a)lists.fredhutch.org lmtp:[mailman-core]:24 pattest-owner(a)lists.fredhutch.org lmtp:[mailman-core]:24 pattest-request(a)lists.fredhutch.org lmtp:[mailman-core]:24 pattest-subscribe(a)lists.fredhutch.org lmtp:[mailman-core]:24 pattest-unsubscribe(a)lists.fredhutch.org lmtp:[mailman-core]:24 But for a test list on lists.hanc.info (the lists that I want to modify the bounce processing for), there is nothing in postfix_vmap, but there are entries in postfix_lmtp: phtest(a)lists.hanc.info lmtp:[mailman-core]:24 phtest-bounces(a)lists.hanc.info lmtp:[mailman-core]:24 phtest-confirm(a)lists.hanc.info lmtp:[mailman-core]:24 phtest-join(a)lists.hanc.info lmtp:[mailman-core]:24 phtest-leave(a)lists.hanc.info lmtp:[mailman-core]:24 phtest-owner(a)lists.hanc.info lmtp:[mailman-core]:24 phtest-request(a)lists.hanc.info lmtp:[mailman-core]:24 phtest-subscribe(a)lists.hanc.info lmtp:[mailman-core]:24 phtest-unsubscribe(a)lists.hanc.info lmtp:[mailman-core]:24 And in postfix_vmap-exceptions, I added: phtest-bounces(a)lists.hanc.info lmtp:[mailman-core]:24, user(a)gmail.com I tried the above with and without a comma, and moving the email address before the lmtp entry as well. Everything else seems to be working — there are over 40k lmtp: entries in postfix_lmtp, and messages are being delivered. I sort of assumed that the lmtp:[mailman-core]:24 thing was a result of all this being dockerized.... Suggestions appreciated. Thanks, -p Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering Fred Hutchinson Cancer Center O 206.667.4856 phirayam(a)fredhutch.org ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, June 26, 2025 09:33 To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: redirecting -bounces replies CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. On 6/25/25 10:53, Hirayama, Pat wrote: > Thanks, Mark. > > I (finally) started working on this ... and in trying to implement your suggestion — ran into a problem, I think. > > The current postfix_vmap has entries like: > > list-bounces(a)lists.domain.info lmtp:[mailman-core]:24 This looks very strange. It should be something like ``` list-bounces(a)lists.domain.info list-bounces(a)alias.domain ``` where alias.domain is the configured alias domain for the mail host lists.domain.info. > So, when I try adding entries to a separate vmap file, like: > > list-bounces(a)lists.domain.info lmtp:[mailman-core]:24, user(a)gmail.com > > It only goes through normal bounce processing. > > If I do: > > list-bounces(a)lists.domain.info user(a)gmail.com, lmtp:[mailman-core]:24 > > Then it goes to the gmail address, and no bounce processing happens. The issue here is the value `lmtp:[mailman-core]:24` is completely wrong. It should be an email address with a syntactically valid domain name. The domain name isn't a real domain. It is only a name exposed to Postorius in the postfix_vmap and postfix_lmtp files. What do you have configured for the alias domain for the lists.domain.info domain? See https://urldefense.com/v3/__https://docs.mailman3.org/projects/mailman/en/l… If you have this properly configured, adding user(a)gmail.com in either order in postfix_vmap should work. -- 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://urldefense.com/v3/__https://lists.mailman3.org/mailman3/lists/mailm… Archived at: https://urldefense.com/v3/__https://lists.mailman3.org/archives/list/mailma… This message sent to phirayam(a)fredhutch.org

2 months, 2 weeks

Re: GDPR - save subscriptions confirmation emails

by Mark Sapiro

On 06/03/2018 12:34 PM, contact(a)maadix.net wrote: > Thanks Selva for you answer. > > In my Mailman 3 installation there is no /var/log/mailman/subscribe Correct. Mailman 2.1 had a subscribe log. Mailman 3 does not. Many things are logged in the 'mailman' log, but subscription confirmations are not. > I have logs about confirmations emails in > mailman/var/logs/smtp.log > > the format is the following: > > Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) handling connection > Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'LHLO > mails.example.com' > Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'MAIL > FROM:<contact(a)maadix.net>' > Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) sender: > contact(a)example.net > Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'RCPT > TO:<prueba-confirm+7c010b0d89513b26d72cb4642e80447a2280ac86(a)list.example.org>' > Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) recip: > prueba-confirm+7c010b0d89513b26d72cb4642e80447a2280ac86(a)list.example.org > Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'DATA' > Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'QUIT' > > So, one solution that comes to my mind is to grep this log file. > > This is not a perfect solution and the full confirmation email is still > missing. > > I am not sure if this would be GDPR compliant. Also, while I don't think it is currently possible to confirm a subscription via REST, not to mention Postorius, it may be in the future and this would bypass email all together. I think the best thing is to implement logging. Of course, you might be able to get your MTA to save all mail to the LIST-confirm address to a separate mailbox in addition to delivering it to Mailman. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 3 months

Mailman-users search results for query "Postorius"