Search results for "Postorius" - Mailman-users

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

2 years, 2 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

10 months

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, 10 months

Re: problem configuring mailman3 on debian bullseye

by Odhiambo Washington

On Wed, Mar 15, 2023 at 6:21 PM Servizio Informatico U.I.C.I. Sezione territoriale di Brescia <servizioinformatico(a)uicibrescia.it> wrote: > Hello all, > > I'm a blind server administrator living in Italy. I use mailman since > 2010 and I was very happy for this list manager. > > When was released the version 3 I started to have many problems to > configure it. > > In this days I installed a new server for my association and I have this > problem that I don't know to solve. > > The server is a debian bullseye. > > I installed mailman3-full from the standard packege. > > I'm using nginx as web server. > > I configured mailman3 and mailman3-web wit https support. > > All is working fine, but if I attempt to subscribe someone it does not > work. > > I send a subscription e-mail to the address list and I receive correctly > the request to confirm subscription. When I reply to the request mailman > log gives this error: > > requests.exceptions.SSLError: HTTPSConnectionPool(host='localhost', > port=443): Max retries exceeded with url: > /postorius/api/templates/list/listname.domain/list:user:notice:welcome > (Caused by SSLError(SSLCertVerificationError("hostname 'localhost' > doesn't match either of 'example.com', 'www.example.com'"))) > > The strange thing is that I configured a domain list.example.com and in > the configuration files I put this domain. > > Mailman3-web works fine I can create lists and make settings. > > Have you an idea about this issue? > Assuming that you created this template - list:user:notice:welcome - what are its contents? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 1 month

SMTPAuthenticationError at /accounts/login/

by Stephen J. Turnbull

mmasoudf(a)aaas.org writes: > I have setup the stack according to: > Mailman Suite Documentation. Release 3.3 PDF file. > I configured > EMAIL_HOST_USER and > EMAIL_HOST_PASSWORD > in Django settings.py. I could not find the place that I might > configure it for Postfix I think it helps to start thinking about it from the other end. That is, Postfix is the mail server for all users on a multiuser system. Therefore in "normal" configurations it will use the authentication mechanisms provided by the host operating system.[1] You need to have a user for Mailman in any case, typically called "mailman" or "list".[2] Once you've configured a user for Mailman on the Postfix side, you use that user and authentication data for Mailman core, Postorius, and HyperKitty to send mail via Postfix. > I am running the site on AWS and to be able to use AWS mail-servers > I have to define following parameter for AWS: > smtp_sasl_password_maps which points to a hash for AWS 'ACCESS KEY > ID' and 'SECRET ACCESS KEY' I don't think that has anything to do with the Mailman-to-Postfix side of things; that's for Postfix to send to AWS's mail exchanger (aka MX). Steve Footnotes: [1] It may also be possible to create Postfix-only "virtual" users who have no existence as far as the OS is concerned, but I don't know anything about that. [2] I haven't thought carefully about whether using Mailman's user in Django would be a security risk, but as long as it only has access to Mailman I don't see how it can do more harm than Mailman itself can, and I don't see why it would be more subject to exploitation than Mailman itself is. Anybody with security chops who wants to weigh in, please do.

6 years

Re: Could not locate column in row for column 'user.id'

by Shashikanth Komandoor

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.* I have not done any changes. Few days back I made DR machine up as I am taking primary into maintenance. The entire database was running streaming replication and I even kept the /var/lib/mailman directory in sync where all the components are installed. Please let me know if any more things I need to share. On Mon, Jul 27, 2020 at 7:45 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/26/20 10:56 AM, Shashikanth Komandoor wrote: > > Hi Team, > > > > I am currently running Mailman 3 with version 3.3.1 and in built > postfix > > version 2.10.1-6 on RHEL 7.5 in production environment from the past 2 > > months almost. > > > > From the past few days, I found my server is responding to the users > > very slowly and throwing the Server Error page (of course getting the > > required page after multiple refreshes) for almost every click on the > > postorius pages (not yet observed on hyperkitty front end which in fact > is > > not so important for me as of now). > > > > During that time, I observed in the mailman.log an error message > saying > > "Could not locate column in row for column 'user.id'". The complete > > traceback log is attached with the mail. The error message is generated > for > > almost all the lists and all the clicks. > > > I don't understand what's going on. I suspect some kind of database > corruption, but I don't know what. > > The traceback indicates Mailman is getting the Members of a list and in > this process is trying to get the display_name for a member. The > member's subscriber attribute doesn't have a display_name so it is > trying to get is from the member's user attribute so it is trying to get > the user record for the member's email address via > IUserManager.get_user(). This in turn gets the Address record for the > email address and returns it's user attribute. > > This leads to the > > sqlalchemy.exc.NoSuchColumnError: "Could not locate column in row for > column 'user.id'" > > error which I don't understand. There is no table with a 'user.id' > column. user.id refers to the id column in the user table which comes > from the user_id column in the address table which should be a reference > to the id column in the user table, not a reference to ay 'user.id' > column. > > What is your backend database and what is the structure of the address > table in that database. Have you done any kind of direct database query > that might have affected this? > > -- > 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, 9 months

Re: Mailing lists as the main collaboration centre at SME

by Stephen J. Turnbull

Rodrigo Camacho writes: > Currently I’m recommending mail.app for our mac users and > thunderbird for windows. Mail.app has a very annoying bug and a minor lacking feature. They probably won't affect you at all, but just in case: - Mail.app can produce "MUST NOT" mail, specifically it will specify Content-Transfer-Encoding: quoted-printable on multipart messages and parts. Mailman (2.1 as well as 3) will reject that. Since it is implemented in the Python stdlib, it's a wontfix for us. It's rare, so just be aware that if somebody's mail gets occasionally rejected at the SMTP level (not Mailman moderation), that might be the cause. I don't have a work around for users. - Mail.app cannot handle encapsulated message/rfc822 parts, at least on handheld devices like iPhone and iPad. This annoys me NO END :-) because I originated the "wrapped" option for DMARC mitigation. But in practice nobody uses it, so ... don't you either. ;-) > It’s truly rare to find GUI email clients which show threads > properly (who answered to what message precisely). It's weird: JWZ threading (https://www.jwz.org/doc/threading.html) was standardized for IMAP (RFC 5256) and I believe both Cyrus and Dovecot implement that extension. But I'm an Emacs person, so I rarely have a clue what developers of "popular" user clients think is good UI. I just know they pretty much invariably do something else. > For now, I have settled on the practices suggested by the LKML. We > will modify these to fit our specific needs as we notice they are > lacking. Seems reasonable. > > 4. The HyperKitty archiver was designed with the "we demand Discord" > > crowd in mind. > > I find that HyperKitty is difficult to read - the indentation on > threads is not clear enough to understand complicated threads. I'll keep that in mind. I don't know if any of the active devs deeply understand HyperKitty (it was a contribution by Red Hat, once they had it where they wanted, the devs became much less active). But it might be as simple as new CSS, or maybe new templates and a little CSS. > I find it very useful to see a graph which shows the precise > hierarchy of a thread. From an archive I’m looking only for ease of > navigation, robust search and easily being able to send a link to a > particular message, I find that https://lkml.org/lkml/2008/7/4/174 > has a super clear archive. That *is* *very* nice. Perhaps that archiver is open source, If not, it might not be hard to substitute similar page templates in HyperKitty. Not clear if you've already visited, so; Mailarchive (git@github.com:ietf-tools/mailarchive.git) is available from the IETF. You can check it out: https://mailarchive.ietf.org/. If you don't know what else to search for, there's a list named "ietf" to see the list-level interface. > If you know of any good netiquette practices which have been > documented (à la https://subspace.kernel.org/etiquette.html) please > let me know! Well, there's always ESR's how to ask questions: https://www.catb.org/~esr/faqs/smart-questions.html, but I think of that more as a threat than advice. There are a lot of netiquette posts out there. I love Brad Templeton's "Emily Postnews Answers Your Questions About Netiquette" (https://www.templetons.com/brad/emily.html) but it might be a little too tongue in cheek for the young'uns. > We are looking for a service which would host and manage our > mailing list setup (like mailmanlists.net) If you own or run such > a service, we are interested in being a client! Please let me know! First look at https://wiki.list.org/COM/Mailman%20hosting%20services, On that list EMWD was the odds-on recommendation, as the previous proprietor Brian was a frequent contributor to the lists and had a lot of support from their users. They were early adopters of Mailman 3 among hosting services and Brian went to the extent of creating alternative (simplified, proprietary) web UIs for archiving and administration. They also support Postorius and HyperKitty, I think. The principal of the mailman3.com and mailman4.com services (same dude) also regularly contributes on the lists, but I don't have direct knowledge of their services. I have nothing good or bad to say about the other services, I assume most are competent. Most use something like cPanel, and many are not Mailman specialists. Make sure they provide Mailman 3; not all do because cPanel decided to port Mailman 2.1 to Python 3 rather than make all their users migrate to Mailman 3. For custom and managed services, see https://wiki.list.org/COM/Mailman%20consulting%20services. Can't really be specific, because it's not clear at this point what you might want from a managed service that a list hosting service wouldn't provide. If you're not clear about yourself and want to explore what a managed service might do, we can discuss that here to the extent it would be of general interest. As for Sirius, yes, we're open for business, and I'm happy to talk about how Sirius Open Source can work with you offlist. See also https://www.siriusopensource.com/en-us/opensource/mailman. Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

7 months, 4 weeks

Re: mailman-web migrate error

by Mark Sapiro

On 11/12/25 11:48, pashdown(a)xmission.com wrote: > I'm migrating from Ubuntu 20.04, mailman 3.2.2, postgresql 12 to Debian 13, mailman 3.3.10, postgresql 17. > > After migrating the postgresql databases and assuring the perms and passwords work, this is what I get with a "mailman-web migrate": > > (user(a)domain.com) redacted from the original > > # mailman-web migrate > Operations to perform: > Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, \ > sessions, sites, socialaccount > Running migrations: > Applying account.0003_alter_emailaddress_create_unique_verified_email... OK > Applying account.0004_alter_emailaddress_drop_unique_email... OK > Applying account.0005_emailaddress_idx_upper_email... OK > Applying account.0006_emailaddress_lower...Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 89, in _execute > return self.cursor.execute(sql, params) > ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^ > psycopg2.errors.UniqueViolation: duplicate key value violates unique constraint "account_emailaddress_user_id_\ > email_987c8728_uniq" > DETAIL: Key (user_id, email)=(24, user(a)domain.com) already exists. This is actually a django-allauth issue. This issue is due to changes in Django allauth to prevent creating multiple addresses differing only in case. The problem is if you have such multiple addresses in your account_emailaddress table, this migration fails. There is a script at https://www.msapiro.net/scripts/UC_fix that will fix this. You may need to adjust the shebang and replace psycopg2 with sqlite3. See https://github.com/pennersr/django-allauth/issues/3019 perhaps starting at This issue is due to changes in Django allauth to prevent creating multiple addresses differing only in case. The problem is if you have such multiple addresses in your account_emailaddress table, this migration fails. There is a script at https://www.msapiro.net/scripts/UC_fix that will fix this. You may need to adjust the shebang. See https://github.com/pennersr/django-allauth/issues/3019 perhaps starting at https://github.com/pennersr/django-allauth/issues/3019#issuecomment-1748028… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 2 weeks

Getting original message headers

by Stephen J. Turnbull

Peter Chubb via Mailman-users writes: > To do that I need to find the original message headers. By the time > the message gets to the archive, or to the mailing list recipients, > all the Received: headers seem to have been deleted, leaving only > the ones from my list server outwards. That's not something Mailman does by default (maybe it does for anonymous lists?) For example, the Received chain in your post as I received it goes back through several subdomains of "chubb" before getting to mailman3.org. > Is there a way to access the original incoming email, before DMARC > mitigation etc., has changed the headers? What are you looking for in the received chain? If you just need the malicious source addresses and message-ids, those should be in the MTA log already. The only ways I can think of in a stock Mailman to preserve the original message are (1) emergency moderation, which should catch the mail before anything is done to it, and (2) reverting the anonymous configuration to default. In case (1) you can see the headers of held messages in Postorius, or with the "mailman qfile" subcommand. The held message remains in the "in" queue until its disposition is decided, I think. If you don't find it there, look around the queues (not bad or shunt, those have a different purpose) for messages that have been there for a while. In case (2), end recipients should get the whole received chain with the original from heder. The less disruptive way to do it involves configuring the MTA to both log the whole message to a file and send it to Mailman. To say more we'd need to know about your MTA. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

3 months, 3 weeks

Re: Add old email address

by Quanah Gibson-Mount

--On Friday, March 13, 2020 4:18 PM +0900 "Stephen J. Turnbull" <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > You can certainly add extra addresses to a Mailman 3 user (I don't > know offhand whether/how an admin can do it through Postorius, but the > core database certainly has that facility and the REST API allows it). I was able to resolve this via the Django admin interface. > However, this doesn't have the same semantics as in Mailman 2 because > Mailman 2 doesn't have users at all. So as an admin how do you know > which addresses correspond to particular users? More generally, what > do you mean by "associate with an account", and why do you want to do > it? > > Normally I would not ask the latter question, it's your business why > you want to do it. But here I'm trying to get at what semantics you > want. If I were going to do this for the kind of purposes I can > imagine, it would be a matter of informing the users that this feature > is available, and I'd ask the users to do it if they care. It seems > you have some project goal in mind though. Because I've been a member of the project for close to 20 years, and the email addresses I've had over that time have changed in relation to the jobs I've had. Same deal for other long time members of the project. By adding addresses I no longer have to my account and marking them verified, I can easily associate nearly 20 years of postings that I've made with myself when I look at the archives. --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

6 years, 1 month

Mailman-users search results for query "Postorius"