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

[MM3-users] Re: Hyperkitty CPU usage

by Abhilash Raj

On Sat, Apr 27, 2019, at 9:40 AM, Alain Kohli wrote: > I have run "python manage.py rebuild_index" before, doesn't that do > clear_index as well? Apart from that, I run hyperkitty in a docker > container and didn't know fulltext_index should be persistent, so that > got deleted after every version update for sure. Which images are you using and how are you deploying them? You should persist fulltext_index, yes, and possibly logs if you need them for debugging later. Can you paste the entire error traceback? > > > On 4/26/19 10:18 PM, Mark Sapiro wrote: > > On 4/26/19 11:14 AM, Alain Kohli wrote: > >> I see loads of "A string literal cannot contain NUL (0x00) characters." > >> messages, but I haven't found missing messages in the archives yet. Not > >> sure how that could be related, though. Apart from that I don't see > >> anything unusual. The other jobs (quarter_hourly, hourly, etc.) seem to > >> run and finish normally. > > > > Did you upgrade from a Python 2.7 version of HyperKitty to a Python 3 > > version? The Haystack/Whoosh search engine databases are not compatible > > between the two and "A string literal cannot contain NUL (0x00) > > characters." is the symptom. > > > > You need to run 'python manage.py clear_index' or just remove all the > > files from the directory defined as 'PATH' under HAYSTACK_CONNECTIONS in > > your settings file (normally 'fulltext_index' in the same directory that > > contains your settings.py. > > > _______________________________________________ > 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)

7 years, 2 months

[MM3-users] Re: Could not locate column in row for column 'user.id'

by Shashikanth Komandoor

Thank you Mark for your response. I tried for the command to know if any entry in the "address" table for which 'id' is not an integer. But unfortunately, I could not get any command or idea how to find that. But out of my extra talent, I tried the below commands which, I thought, may print the records which contain a non integer id value. *mailman=# select count(*) from address; count------- 82387(1 row)mailman=# select id,email from address where id NOT BETWEEN 1 AND 84203; id | email----+-------(0 rows)mailman=# select id,email from address where id NOT BETWEEN 1 AND 84202; id | email-------+----------------------------- 84203 | cons3.birmingham(a)mea.gov.in <cons3.birmingham(a)mea.gov.in>* *1 and 84203 are the minimum and maximum values of the id:* Please see the above outputs and suggest if anything possible or please let me know the command what should I run to find a non integer id value. I also doubt this error as if my REST API is contacting postgresql in a delayed manner. If possible, can you say what optimal setting I can do at Postgresql so that faster responses would be given to REST API. The above things are only my doubts. Please correct me if I am wrong. On Tue, Jul 28, 2020 at 7:31 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/27/20 2:48 AM, Shashikanth Komandoor wrote: > > Hi Mark, > > > > Thank you for your response. And sorry for not giving you > > complete information as I am not sue what to share with you. > > > > I am using Postgresql-11.7 as my backend database. The below is > > the structure of the address table in* mailman *database: > > > > mailman=# \d address; > > Table "public.address" > > Column | Type | Collation | Nullable | > > Default > > > ----------------+-----------------------------+-----------+----------+------------------------------------- > > id | integer | | not null | > > nextval('address_id_seq'::regclass) > > email | character varying | | | > > _original | character varying | | | > > display_name | character varying | | | > > verified_on | timestamp without time zone | | | > > registered_on | timestamp without time zone | | | > > user_id | integer | | | > > preferences_id | integer | | | > > Indexes: > > "address_pkey" PRIMARY KEY, btree (id) > > "ix_address_email" UNIQUE, btree (email) > > "ix_address_preferences_id" btree (preferences_id) > > "ix_address_user_id" btree (user_id) > > Foreign-key constraints: > > "address_preferences_id_fkey" FOREIGN KEY (preferences_id) REFERENCES > > preferences(id) > > "address_user_id_fkey" FOREIGN KEY (user_id) REFERENCES "user"(id) > > Referenced by: > > TABLE ""user"" CONSTRAINT "_preferred_address" FOREIGN KEY > > (_preferred_address_id) REFERENCES address(id) ON DELETE SET NULL > > TABLE "autoresponserecord" CONSTRAINT > > "autoresponserecord_address_id_fkey" FOREIGN KEY (address_id) REFERENCES > > address(id) > > TABLE "member" CONSTRAINT "member_address_id_fkey" FOREIGN KEY > > (address_id) REFERENCES address(id) > > TABLE "onelastdigest" CONSTRAINT "onelastdigest_address_id_fkey" > > FOREIGN KEY (address_id) REFERENCES address(id) > > > > The below is the structure of *user* table: > > > > mailman=# \d user; > > Table "public.user" > > Column | Type | Collation | > Nullable > > | Default > > > -----------------------+-----------------------------+-----------+----------+---------------------------------- > > id | integer | | not > null > > | nextval('user_id_seq'::regclass) > > display_name | character varying | | > > | > > password | character varying | | > > | > > _user_id | uuid | | > > | > > _created_on | timestamp without time zone | | > > | > > is_server_owner | boolean | | > > | > > _preferred_address_id | integer | | > > | > > preferences_id | integer | | > > | > > Indexes: > > "user_pkey" PRIMARY KEY, btree (id) > > "ix_user__user_id" btree (_user_id) > > "ix_user_preferences_id" btree (preferences_id) > > Foreign-key constraints: > > "_preferred_address" FOREIGN KEY (_preferred_address_id) REFERENCES > > address(id) ON DELETE SET NULL > > "user_preferences_id_fkey" FOREIGN KEY (preferences_id) REFERENCES > > preferences(id) > > Referenced by: > > TABLE "address" CONSTRAINT "address_user_id_fkey" FOREIGN KEY > (user_id) > > REFERENCES "user"(id) > > TABLE "domain_owner" CONSTRAINT "domain_owner_user_id_fkey" FOREIGN > KEY > > (user_id) REFERENCES "user"(id) > > TABLE "member" CONSTRAINT "member_user_id_fkey" FOREIGN KEY (user_id) > > REFERENCES "user"(id) > > > > mailman=# \dn > > List of schemas > > Name | Owner > > --------+---------- > > public | postgres > > (1 row) > > > > mailman=# select * from user; > > user > > ---------- > > postgres > > (1 row) > > > > *The above command output is not showing any fields. But if use the > table > > as public.user (schema.tablename) with select command, it is showing the > > data. But without schema name this table is not showing those fields. Not > > sure if this the expected behavior or not.* > > > This is expected. psql gets confused because it has its own user table. > > The above table definitions look fine. > > Is there any entry in the `address` table for which `id` is not an integer? > > -- > 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

5 years, 11 months

[MM3-users] 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

1 year, 1 month

[MM3-users] Re: URL-lines in templates get folded

by Frank Steinberg

> Am 18.10.2022 um 18:37 schrieb Mark Sapiro <mark(a)msapiro.net>: > > On 10/18/22 06:52, Frank Steinberg wrote: >> Hi, >> I’ve added links to some templates to give owners and moderators >> shortcuts to the postorius UI for moderation tasks, e.g., I’ve added >> https://lists.xxx.de/postorius/lists/$list_id/held_messages <https://lists.xxx.de/postorius/lists/$list_id/held_messages> >> Unfortunately those lines seem to exceed a certain limit and get >> folded, so that they appear as, e.g. >> https://lists.xxx.de/postorius/lists/$list_id/held_ <https://lists.xxx.de/postorius/lists/$list_id/held_> >> messages >> (or similar) and are not directly useful. > > How are you editing the templates? I.e., are you editing them via Postorius or by putting them in Mailman's var/templates/ directory or ?? I am using the docker containers and have been putting files into the directory mapped to var/templates/site/. > Also are those lines of the form > > https://... <https://...> I am sorry, my Mail program changed the encoding here. In fact the template files just contain the plain URL. No blanks no angle brackets. Just one URL containing the $list_id variable. > what you are entering or is that duplication and artifact of your mail client? You should be entering just a URL either with or without angle brackets, but not both. > > Is the folding actually in the raw message or is it an artifact of the mail client viewing the message? The folding appears in the raw message sent by Mailman and put into the users INBOX. I thought there could be a kind of filter in Mailmans mailout processing that cares for line breaks in order to not exceed approx. 75 chars per line? I will do some more testing tomorrow (european time).

3 years, 9 months

[MM3-users] Re: Problem with redirection when entering alias without a / at the end

by Jens Günther

Am 19.03.21 um 23:04 schrieb Mark Sapiro: > On 3/19/21 2:55 PM, Jens Günther wrote: >> >> When I want to get to Mailman Starting Page now I need to Enter the >> following URL: https://mailman.xyz.de/mailman3/ to be directly >> redirected as expected to >> https://mailman.xyz.de/mailman3/postorius/lists/ -> works. >> >> Problem: When leave out the slash at the end and I ONLY enter the >> following URL: https://mailman.xyz.de/mailman3 -> then I'm wrongly >> redirected to a page, taht does not exist: >> https://mailman.xyz.de/mailman/postorius/lists/ -> 404 > > > Huh? that is the same URL as the one above that you say works. Do you > mean https://mailman.xyz.de/mailman/postorius/lists without the slash or > what. Here is the difference: https://mailman.xyz.de/mailman3/ https://mailman.xyz.de/mailman3 -> the first one works and leeds to https://mailman.xyz.de/mailman3/postorius/lists -> the second one redirects to https://mailman.xyz.de/mailman/postorius/lists -> which does not exist, since Apache-alias is only for mailman3 >> Where can I change this misbehaviour? In Apache-conf everything seems as >> it's in the docs, for the vHost I do not have any other custom settings. > > > What is the exact content of your RedirectMatch or ReweriteRule or > whatebver you are using? > I only use the apache-conf given in the documentation: <code> Alias /mailman3/favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico Alias /mailman3/static /var/lib/mailman3/web/static <Directory "/var/lib/mailman3/web/static"> Require all granted </Directory> <IfModule mod_proxy_uwsgi.c> ProxyPass /mailman3/favicon.ico ! ProxyPass /mailman3/static ! ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ </IfModule> </code>

5 years, 4 months

[MM3-users] Re: getting all registered users and their lists

by IOhannes m zmoelnig

On 1/26/22 17:19, Mark Sapiro wrote: > On 1/26/22 00:16, IOhannes m zmoelnig wrote: > > You can do this in mailman shell[...]> ``` > >>> from datetime import datetime > >>> um = getUtility(IUserManager) > >>> for usr in um.users: > ... if len(list(usr.memberships.members)) > 0: > ... continue > ... if usr.created_on < datetime(2022, 1, 1): > ... continue > ... adr = usr.addresses[0] > ... print(f'Name: {adr.display_name}, Email: {adr.email}, Created: > {usr.created_on}') > ... > ``` > perfect. that did the trick, thanks a lot. >> is there a scriptable way to get all users that have registered in my >> mailman3 (3.2.1) instance and which lists they are subscribed to (if >> any)? > > It's in Postorius >= 1.3.6 i'm not entirely sure how this relates to the above (working) snippet. is it, that with postorious>=1.3.6 i would be able to perform that task from the webinterface, rather than having to resort to 'mailman shell'? in any case, this might be related: before i received your email with the 'mailman shell' snippet, i scraped some bits of my django knowledge and visited <https://lists.example.com/admin> (the django admin interface), and noticed the list of users there. so i scraped that page for users (assuming that this was the list of registered users). then i get myself a list of all subscribers in my instance, using a crude `mailman lists | grep "@" | while read l; do mailman members "${l}"; done | sort -u`. finally i calculated the difference between the two sets. interestingly the results are quite different from the ones i got from your script: both sets contain users that are not in the other set. how come? gfmdras IOhannes

4 years, 6 months

[MM3-users] Re: message duplication and an NNTP related error

by Laurens Kils-Hütten

Am Tue, Feb 24, 2026 at 01:16:45PM -0800 schrieb Mark Sapiro: > On 2/24/26 09:23, Laurens Kils-Hütten wrote: > > > > I've used the debian packages: > > > > apt install mailman3-full mailman3-web > > Then this may be a Debian issue and should be reported there in any case. > See <https://wiki.list.org/x/12812344>. I will, once I convinced it's really a bug. Right now I'm thinking it's a misconfiguration on inn2's side. From scrutinising the message headers this is what happens: mailman sends the message to the newsserver where it get's injected properly receiving an Injection-Information: header field. Then however this new message is sent back to mailman. Now there's a duplicate with identical message ID. Mailman then sends it back to inn2 which refuses to take it and the python nntp client throws an error, thus preventing an endless loop. Why inn2 even sends the message back to mailman I can't tell right now. These are the relevant snippets from my inn2 setup: # this is from /etc/news/news2mail.cf # no surprises, and it basically works. News from the grenzland.test # group is forwarded to the proper list address test-grenzland-club test(a)grenzland.club # this is in /etc/news/newsfeeds news2mail!:!*:Ac,Tc,Wn*:/usr/lib/news/bin/news2mail test-grenzland-club/grenzland.club:!*,grenzland.test:Ap,Tm:news2mail! # this last line should do two things: forward messages from the # test(a)grenzland.club list to the grenzland.test newsgroup, # AND don't send any messages back which have grenzland.club # in their Path header. This last bit seems to fail however, # and I fail to spot the error. I'll ask about this in the inn2 places I known of. Cheers, lkh -- Laurens Kils-Hütten https://lkh.sdf-eu.org

5 months

[MM3-users] Re: Set domain inactive / archive import from other domain.

by Johannes Winter

Am Sat, 15 Sep 2018 09:31:53 -0700 schrieb Mark Sapiro <mark(a)msapiro.net>: > On 09/15/2018 07:15 AM, Johannes Winter wrote: > > > > we've migrated a list from another domain and would like to keep the > > archives. Hyperkitty doesn't recognize the emails in the mbox > > archive during import due to the other domain name. > > > I don't understand the problem. I just ran a test where I imported a > mbox containing 3 messages which were not even list posts and in > which I had changed all the domain names to 'example.com'. I.e., in > the mbox I imported, the headers containing domain names looked like > > From root(a)example.com Sun Aug 26 09:12:06 2018 > Return-Path: <root(a)example.com> > Delivered-To: root(a)example.com > Received: by example.com (Postfix, from userid 0) > From: Anacron <root(a)example.com> > To: root(a)example.com > Message-Id: <20180826161158.F154D34010C(a)example.com> > X-msapiro-MailScanner-From: root(a)example.com > > and the 3 messages were all added to the archive. > > Why do you think the domain name is an issue? Perhaps the issue is > there is already one or more messages in the archive and the messages > you are importing are older. If you don't specify --since to > hyperkitty_import it won't import messages older than the newest > message in the existing archive. Thanks a lot for your excellent and fast support! That was the problem. Maybe it would be wise to include that into the help of the hyperkitty_import command? Although this command successfully imported 3/4 of the huge (1.7GB) mbox, it stumbled upon an error after some minutes: https://gitlab.com/mailman/hyperkitty/issues/200 -- Johannes Winter matrix: @yova:matrix.allmende.io

7 years, 10 months

[MM3-users] Re: SPF check fails for lists subdomain

by Odhiambo Washington

On Thu, Jan 5, 2023 at 10:56 AM Jan Eden via Mailman-users < mailman-users(a)mailman3.org> wrote: > On 2023-01-04 15:07, Mark Sapiro wrote: > > > On 1/4/23 14:02, Jan Eden via Mailman-users wrote: > > > > Although I could specify the IP address in my SPF records directly (as > > > you suggested), I do hope that my understanding of DNS records laid out > > > above is not entirely misguided. My current setup does work as expected > > > for eden.one, after all. > > > > As I said at < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > > I was misreading your DNS and now I am as puzzled as you about the > failure. > > It gets even more mysterious. I tried sending messages from both > lists.eden.one and janeden.net (my other domain) to a gmail account and > to another mail provider. Both messages passed the SPF checks on both > services (s. the relevant headers quoted below). Now because I send > those messages via my SMTP user (smtpuser(a)eden.one) and use SRS, the SPF > check operates (and succeeds) on e.g. > > srs0=jdm+=5c=lists.eden.one=testlist-bounces+gmailuser=googlemail.com(a)eden.one > (and not on somethingsomething(a)lists.eden.one or > somethingsomething(a)janeden.net) Could this be the reason for the failed > SPF checks in Yahoo's and Google's DMARC reports? > > - Jan > Might you be willing to use proven tools instead of trying so hard to understand the myth? I use https://easydmarc.com/tools#spf-tools It allows me to generate, lookup, test SPF, DKIM, DMARC, etc. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 6 months

[MM3-users] Re: Mailman3 not working following distribution upgrade from Debian 10 to 11.

by David Newman

On 1/11/22 12:39 PM, gordon(a)dickens.com wrote: > 2) Install mailman3 using the venv and web instructions as suggested in this thread. I plan to use mysql (mariadb) since my database was originally implemented with mysql. I too use MariaDB. Here are the MariaDB-specific variations from the venv and web docs: 1. Before going through the venv docs I installed these packages: libmariadb3 libmariadb-dev default-libmysqlclient-dev 2. When installing mailman in venv, I did this: (venv)$ pip install --upgrade pip (venv)$ pip install wheel mailman pymysql mysqlclient 3. In /etc/mailman.cfg, the database config looks like this: .. [database] class: mailman.database.mysql.MySQLDatabase url: mysql+pymysql://myuser:mypassword@mymysqlhost/mailman?charset=utf8mb4&use_unicode=1 .. The url is all one line (it's wrapping in my mail client). 4. The [Unit] section of /etc/systemd/system/mailman3.service looks like this: [Unit] Description=GNU Mailing List Manager After=syslog.target network.target mariadb.service .. Note that this is on a Debian 11 system. On Debian 10 and previous, it'd be mysql.service instead of mariadb.service. 5. The settings.py file includes this section: .. # MySQL database setup. DATABASES = { 'default': { 'ENGINE': 'django.db.backends.mysql', 'NAME': 'mailmanweb', 'USER': 'mailman', 'PASSWORD': '<password>', 'HOST': 'localhost', 'PORT': '', 'OPTIONS': {'charset': 'utf8mb4'} # Enable utf8 4-byte encodings. } } .. Note that your NAME, USER, PASSWORD, and possibly HOST may differ. 6. The [Unit] section of /etc/systemd/system/mailmanweb.service looks like this: [Unit] Description=GNU Mailman Web UI After=syslog.target network.target mariadb.service mailman3.service .. Same caveat as with step 4 that this is for Debian 11, and you'd use mysql.service instead on Debian 10 and previous. I think that's all the changes, but if I've omitted something I hope Mark Sapiro or someone else can step in. dn

4 years, 6 months

Search results for query "sapiro"