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

[MM3-users] Bug in email.generator:_handle_text? [was: store/export existing Mailman lists ...]

by Stephen J. Turnbull

Oops, premature send. I did grep through the whole mailman core code base for "del", and didn't come up with anything that looks like it would delete fields like Content-Type and Message-ID (assuming the default for anonymous_list_keep_headers, I wish I had thought to ask about that, but who changes it?) I assumed Content-Type is modified by direct assignment in handlers that delete parts or transform them to a different MIME type. I wonder if his Python is old enough to not recognize negated regexps? That should be logged in errors. Or (as you guessed), the '(?!x-)' regexp (or the whole content of anonymous_list_keep_headers) has been removed? Stephen J. Turnbull writes: > Mark Sapiro writes: > > > This apparently confuses the Python email package so that the > > get_payload() method returns a list of strings rather than a list of > > message objects. > > Yes, I got that far too. I'm guessing that in the absence of a > Content-Type, which then *should* default to text/plain, the email > package goes ahead and detects the MIME headers anyway (although I > don't think it should do that) and breaks the message into MIME > parts. I would think we'd raise an Exception here. > > If there's a reason for the email package to do that detection > (*shrug*, it seems to work), then the dispatching in _handle_text > should be done on the Python type rather than the MIME Content-Type. > > I forget exactly how the code is structured, the relevant dispatching > may be in _dispatch or in _dispatch_meth. > > Steve > _______________________________________________ > 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/ >

3 years, 6 months

[MM3-users] Re: Huge performance issue: Mailman doesn't (seem to) receive any mails.

by Henrik Rasmussen

Abhilash Raj wrote: > On Wed, Sep 18, 2019, at 8:14 AM, Mark Sapiro wrote: > > each other, but Postfix is trying to deliver mail via lmtp to > > [172.19.199.2]:8024. Mailman's lmtp runner should be running and > > listening on port 8024. Either that is not the case or that port is not > > exposed to Postfix on IP 172.19.199.2. > > Right, that is what I was wondering, you verify that by using telnet > on the specified IP and Port (172.19.199.2:8024). Yes, the postfix container listens on 172.19.199.2:8024 ``` [root@postfix /]# nc -v 172.19.199.2 8024 Ncat: Version 7.50 ( https://nmap.org/ncat ) Ncat: Connected to 172.19.199.2:8024. 220 mailman-core GNU Mailman LMTP runner 2.0 ``` > docker-compose ps lists all the running containers, do you see all > the containers running? That also seem to be okay ``` [root@lstapp01pl ~]# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES bddc80799b8c maxking/mailman-web:0.2 "docker-entrypoint.sh" 16 hours ago Up 16 hours 8000/tcp, 8080/tcp mailman-web be098b18aeca maxking/mailman-core:0.2 "docker-entrypoint.sh" 16 hours ago Up 16 hours 8001/tcp, 8024/tcp mailman-core c47fd8ccf19d postgres:9.6 "docker-entrypoint.sh" 16 hours ago Up 16 hours 5432/tcp mailman_database_1 699264501acd mailman3-mime_htmlizer "container-entrypoint" 16 hours ago Up 16 hours 8080/tcp postmime 90f381a74709 mailman3-postfix:v1.1 "./entrypoint.sh" 16 hours ago Up 16 hours 0.0.0.0:465->465/tcp, 0.0.0.0:587->587/tcp, 0.0.0.0:26->25/tcp postfix ``` And netstat in the mailman-core container shows: ``` Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 172.19.199.2:8024 0.0.0.0:* LISTEN` ``` > You mentioned that Mailman is not receiving enough emails, do you get > any emails from Mailman? I am trying to see if this is a perf problem > or if Mailman's LMTP isn't reachable at all. Mailman do send out mails like when someone signs up for an account. Thanks to both.

6 years, 6 months

[MM3-users] Re: Speed up importing mailman2 lists

by Stephen J. Turnbull

Mark Sapiro writes: > On 2/19/25 06:08, t.maintz(a)fz-juelich.de wrote: > > We are currently planning to migrate from mailman2 to mailman3 as > > a container, have around 1500 lists and would like to complete > > the migration ideally in a few hours. I've done two massive migrations in the last year. In the first (~20k lists), the lists were down for maybe two hours, but it took 22 hours for HyperKitty to populate, mostly in Xapian indexing we realized in post-mortem analysis. In the second (~1k lists), no perceptible downtime because they have their own bespoke archiver that has a list-manager-agnostic API. The trick to zero delivery downtime is that you can configure your MTA to route to Mailman 3 if the list exists there, if not route to Mailman 2 if the list exists there, and if not continue to any lower priority routes. It worked as designed (mops sweat off brow ;-). We did take Postorius and the Mailman 2 management CGIs and email command addresses offline for the duration (3 hours in the first case, 30 mminutes in the second). This is sraightforward if Mailman 2 and Mailman 3 are running on the same host. Life is more complex if you're spinning up Mailman 3 in a separate node but it should be possible. I think if you're migrating to HyperKitty you can speed up the migration by shutting off indexing, and doing that later at the cost of confusing people who expect the lists to be indexed. I'm not sure if it's possible to migrate the archives concurrently with accepting new posts, or maybe to migrate archives in advance and backfill any posts that arrive during the list migration. And there's no reason why you can't leave the legacy Mailman 2 archives up for browsing as a backup for as long as needed. Steve

1 year, 1 month

[MM3-users] Re: Invalid FilterAction: discard. Treating as discard

by Henrik Rasmussen

Mark Sapiro wrote: > I don't understand the question? Are you asking why the log contains > "invalid FilterAction: discard. Treating as discard"? If so, that's a No, that was just log messages I thought would help explain the problem. > If you are asking why the message is empty after filtering and > discarded, It is presumably because it is a text/html message as opposed > to a multipart/alternative message with text/plain and text/html > alternative parts. The Content-Type of the mail sent to the list is multipart/mixed From: SENDER <sender(a)senderdep.example.com> To: "LISTNAME(a)lists.example.com" <LISTNAME(a)lists.example.com> Subject: =?utf-8?B?QW50cm9wb2xvZ2VyIGkgcHJha3NpczogVGlsbWVsZGluZyDDpWJlbg==?= Thread-Topic: =?utf-8?B?QW50cm9wb2xvZ2VyIGkgcHJha3NpczogVGlsbWVsZGluZyDDpWJlbg==?= Thread-Index: AdT/QIb18JA+6hcSTYycFCI+5NuYoQEwPZ/Q Date: Mon, 6 May 2019 13:53:23 +0200 Message-ID: <250E794B36C1E646AF3D81E1F15348C79DA8CA83(a)P2KITMBX06WC03.unicph.domain> Content-Language: en-US X-MS-Has-Attach: yes X-MS-Exchange-Organization-SCL: -1 X-MS-TNEF-Correlator: Content-Type: multipart/mixed; boundary="_006_250E794B36C1E646AF3D81E1F15348C79DA8CA83P2KITMBX06WC03u_" MIME-Version: 1.0 > There are list attributes filter_types and pass_types (also > filter_extensions and pass_extensions, but those probably aren't My Python isn't that great, but this looks like i'm missing something >>> m.filter_content True >>> m.pass_types <generator object pass_types at 0x7f66d407bba0> >>> m.filter_extensions <generator object filter_extensions at 0x7f66d407bdb0> m.pass_extensions <generator object pass_extensions at 0x7f66d407be08> > Presumably, the combination of filter_types and pass_types is not > allowing text/html. I am thinking that as the "Filter content" (postorius) refers to "the settings below", this setting is needed in case list admin wants an explicit reply-to address or change other switches in Alter Messages. But this shouldn't affect the content, even it is text/html, I think, at least not emptying the mail, I think. > You need to examine these settings in mailman shell, e.g. > > list(m.pass_types) >>> list(m.pass_types) ['multipart/mixed', 'multipart/alternative', 'text/plain'] -- Henrik Rasmussen

6 years, 10 months

[MM3-users] Re: MM3 on debian - redirect problem

by Gelpi Andrea

Il 28/04/20 18:31, Mark Sapiro ha scritto: > On 4/27/20 8:17 AM, Gelpi Andrea wrote: >> Hi, >> on a debian10 I have mm3 installed via apt-get >> >> apt-get install mailman3-full >> dpkg-reconfigure mailman3 >> dpkg-reconfigure mailman3-web >> >> I have this minor issue >> >> https://webserver/mailman3 redirects to >> http://webserver/mailman/postorius/lists/ >> >> that doesn't exist. >> >> The same problem form django admin page to return to lists >> >> https://website/mailman3/admin/sites/site >> >> In the upper right corner I have a link to https://webserver/mailman3 >> that redirects to https://mailman/postorius/lists/ >> >> I searched for a redirect but without success. > > > The redirection must be a web server issue. > > There is a urls.py file probably in the same directory as your django > settings - probably /usr/share/mailman3-web/urls.py in your case. > > You can make a URL like http://webserver/mailman/postorius/lists/ work > by adding > > url(r'^mailman/postorius/', include('postorius.urls')), > > to the urlpatterns list in the urls.py file. > > The problem seems to be inside the uwsgi proxy. Also django admin web interface has the some problem. I add /mailman in the apache mailman config installed by the debian package. --------------------------------------- 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/ ProxyPass /mailman unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ </IfModule> ------------------------------------- -- Gelpi ing. Andrea -------------------------------------------------------------- It took the computing power of three C-64s to fly to the Moon. It takes a 486 to run Windows 95. Something is wrong here. --------------------------------------------------------------

5 years, 11 months

[MM3-users] Re: templates

by Christian

Okay I sent a test message this morning and subscribers are reporting they did not receive it. The smtp.log shows 'smtp to degrowcali(a)lists.ccalternatives.org for 25 recips, completed in 3276.275292634964 seconds' (see below) I alone received it however and it is listed in the archive. Below is the excerpt from smtp.log. Two of my 5 lists are exhibiting this behavior, while 2 other lists are working normally. Please advise. Thank you. root@zarathustra:/opt/mailman/mm/var/logs# vi smtp.log May 05 08:09:24 2023 (768) ('127.0.0.1', 48706) recip: degrowcali-bounces+vortexanthony=hotmail.com(a)lists.ccalternatives.org May 05 08:09:24 2023 (768) ('127.0.0.1', 48706) >> b'DATA' May 05 08:09:24 2023 (768) ('127.0.0.1', 48706) >> b'QUIT' May 05 08:09:24 2023 (768) ('127.0.0.1', 48706) connection lost May 05 08:09:24 2023 (768) ('127.0.0.1', 48706) Connection lost during _handle_client() May 05 08:11:35 2023 (768) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) May 05 08:11:35 2023 (768) Peer: ('127.0.0.1', 60312) May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) handling connection May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) >> b'LHLO zarathustra.ccalternatives.org' May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) >> b'MAIL FROM:<> SIZE=9885 BODY=8BITMIME' May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) sender: <> May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) >> b'RCPT TO:<degrowcali-bounces+alaitz.aritza=gmail.com(a)lists.ccalternatives.org>' May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) recip: degrowcali-bounces+alaitz.aritza=gmail.com(a)lists.ccalternatives.org May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) >> b'DATA' May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) >> b'QUIT' May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) connection lost May 05 08:11:35 2023 (768) ('127.0.0.1', 60312) Connection lost during _handle_client() May 05 08:13:46 2023 (771) <046f01d97f5c$27c4ada0$774e08e0$(a)degrowthcalifornia.org> smtp to degrowcali(a)lists.ccalternatives.org for 25 recips, completed in 3276.275292634964 seconds May 05 08:13:46 2023 (771) <046f01d97f5c$27c4ada0$774e08e0$(a)degrowthcalifornia.org> post to degrowcali(a)lists.ccalternatives.org from christian(a)degrowthcalifornia.org, 5012 bytes May 05 08:13:46 2023 (771) <168329874052.765.12737190159456781981(a)zarathustra.ccalternatives.org> smtp to degrowcali(a)lists.ccalternatives.org for 1 recips, completed in 0.011698722839355469 seconds May 05 08:13:46 2023 (771) <168329874052.765.12737190159456781981(a)zarathustra.ccalternatives.org> post to degrowcali(a)lists.ccalternatives.org from degrowcali-bounces+6397d6fde210be0b39dbf22a9868e61d6e2d0f23(a)lists.ccalternat ives.org, 11445 bytes May 05 08:13:46 2023 (771) <168329886073.765.17844938860507947692(a)zarathustra.ccalternatives.org> smtp to degrowcali(a)lists.ccalternatives.org for 1 recips, completed in 0.00799560546875 seconds May 05 08:13:46 2023 (771) <168329886073.765.17844938860507947692(a)zarathustra.ccalternatives.org> post to degrowcali(a)lists.ccalternatives.org from degrowcali-bounces+62749dfe16f9d39e2cd0c3e94754723efbe8169d(a)lists.ccalternat ives.org, 11400 bytes May 05 08:13:46 2023 (771) <168329958151.765.3625387421642934590(a)zarathustra.ccalternatives.org> smtp to degrowcali(a)lists.ccalternatives.org for 1 recips, completed in 0.008965730667114258 seconds May 05 08:13:46 2023 (771) <168329958151.765.3625387421642934590(a)zarathustra.ccalternatives.org> post to degrowcali(a)lists.ccalternatives.org from degrowcali-bounces+8890cbead24710cdebeedbbd96d99fcd7f6f1343(a)lists.ccalternat ives.org, 11426 bytes May 05 08:13:46 2023 (768) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) May 05 08:13:46 2023 (768) Peer: ('127.0.0.1', 39046) May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) handling connection May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) >> b'LHLO zarathustra.ccalternatives.org' May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) >> b'MAIL FROM:<> SIZE=15076 BODY=8BITMIME' May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) sender: <> May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) >> b'RCPT TO:<degrowcali-bounces+6397d6fde210be0b39dbf22a9868e61d6e2d0f23(a)lists.ccalte rnatives.org>' May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) recip: degrowcali-bounces+6397d6fde210be0b39dbf22a9868e61d6e2d0f23(a)lists.ccalternat ives.org May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) >> b'DATA' May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) >> b'QUIT' May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) connection lost May 05 08:13:46 2023 (768) ('127.0.0.1', 39046) Connection lost during _handle_client() May 05 08:13:46 2023 (768) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) May 05 08:13:46 2023 (768) Peer: ('127.0.0.1', 39050) May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) handling connection May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) >> b'LHLO zarathustra.ccalternatives.org' May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) >> b'MAIL FROM:<> SIZE=15049 BODY=8BITMIME' May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) sender: <> May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) >> b'RCPT TO:<degrowcali-bounces+8890cbead24710cdebeedbbd96d99fcd7f6f1343(a)lists.ccalte rnatives.org>' May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) recip: degrowcali-bounces+8890cbead24710cdebeedbbd96d99fcd7f6f1343(a)lists.ccalternat ives.org May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) >> b'DATA' May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) >> b'QUIT' May 05 08:13:46 2023 (768) ('127.0.0.1', 39050) connection lost -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, May 4, 2023 12:19 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: templates On 5/4/23 11:15, Christian via Mailman-users wrote: > In March when I started troubleshooting my lists, you stated: > > "Also, one other thing you might check. Do these non-working lists > have templates defined in postorius, in particular, one for > list:member:regular:footer, and if not, are there any in Mailman's > mailto:var/templates/lists/redlatinleg@lists.ccalternatives.org/ derectory > that Mailman doesn't have permission to find and read?" > > There are no other templates listed in either Postorius nor in > Mailman's var/templates (as I stated, I do not even lave a 'lists' > subdirectory under Mailman's var/templates). My subscribers are not > receiving message distributions from my lists, even while some of them > are listed in the archives. See the original thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/U HWOG6S57FM2SIQWHEPWM3CDUSAMLOOP/ (which you hijacked about 4 messages in) and particularly the message at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ NZ7G3JMYXFTQNVJ2DYGJ6PETEQT55SKB/ Without further information, I can't say more than that. -- Mark Sapiro <mailto:mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailto:mailman-users@mailman3.org To unsubscribe send an email to mailto:mailman-users-leave@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/ GJNYZK3DK4UZYAILV7JZ62PPVPDPKNOZ/ This message sent to mailto:csa@web-analysts.net

2 years, 10 months

[MM3-users] Re: Unknown templates being used

by Tom Stoddard

On 2/14/2021 1:31 PM, Mark Sapiro wrote: > That message is not built from a template. It comas from the `mailman > notify` command which currently says > ```> def _send_notice(mlist, count, detail): >> """Creates and sends the notice to the list administrators.""" >> subject = _('The {} list has {} moderation requests waiting.').format( >> mlist.fqdn_listname, count) >> # XXX This should be a template. >> text = _("""The {} list has {} moderation requests waiting. > ``` > I.e., we know it should be a template, but it currently isn't. That's fine but it doesn't explain why I have received messages that were built by a template for some subscription requests. In other words, why is there a template being used in some instances and on others a "mailman notify command" is being used? Are there different methods for people to use to request a subscription? Please understand that I'm new to mailman 3 and don't have knowledge of its source code. From reading some of the messages that have been sent by this list, I assume it's written in python, which is a language I have not year learned. I'm asking this because I help to administer several different lists and there are some other moderators who have very limited technical skills. I try to help them the best I can, which is why I'm trying to understand why these messages seem to differ so that I can explain it to others. By the way, Brian at EMWD has been extremely helpful to me already and, as he stated, he informed me that this is an issue with Mailman 3 so I thought I'd try getting the answer directly from this group. Thank you for your time. I do recognize and appreciate the time and effort that goes into creating and maintaining open source software.

5 years, 1 month

[MM3-users] Re: Mailman3 is wrongly display name a list member

by Allan Hansen

Thank you, Mark. I have Postorius Version 1.3.4 I see no 'Users' in Postorius, but I do see it in Django. I'll assume that my Postorius is out of date and will take steps to update it. Yours, Allan On 1/11/22, 10:38 , "Mark Sapiro" <mark(a)msapiro.net> wrote: On 1/11/22 9:24 AM, Allan Hansen wrote: > Thank youi, Stephen. > > Oops. When I wrote below that I set the name 'B' in the account, I did describe it wrongly. Sorry. > The member just wants one name, 'A' for all her subsriptions. Somehow the 'B' got into the system when we upgraded from Mailman 2 to Mailman 3. > > I removed the address from all the lists, set the account display name to 'A' in Django, verified that she was not subscribed to any list at all, and then resubscribed her again as 'A'. In other words, no 'B' anywhere - straight 'A's. > Nevertheless, the new subscriptions still show up as 'B'. A user has a user record and one or more address records. Each of these has a display name. Removing users from lists does not remove these records. If you have recent Postorius, you should have a `users` item at the top of Postorius pages. Go there, find the user and click "Manage". You can change Display Name there. Otherwise, in `mailman shell` for example ``` >>> usr = getUtility(IUserManager).get_user('user(a)example.com') >>> usr.display_name = 'First Last' >>> for adr in usr.addresses: ... adr.display_name = 'First Last' ... >>> commit() ``` -- 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, 2 months

[MM3-users] Re: Mailserver Log entries following through mailman?

by Andreas Barth

* Mark Sapiro (mark(a)msapiro.net) [231110 23:54]: > On 11/10/23 12:39, Andreas Barth wrote: > > > >is there some way to find an ID to follow an email through mailman? In > >the exim logfile there is only something like C="250 Ok" (whereas in > >mails sent to another exim there is something like C="250 OK id=…"). > >(What I sometimes need to do is to follow an mail whether it is sent > >through mailman and to where.) > > Every message should have a unique Message-ID: header. According to > my reading of https://www.exim.org/exim-html-current/doc/html/spec_html/ch-log_files.html > Exim should create a => log entry with an id= field containing the > Message-ID when the message is received for delivery to Mailman and > another similar entry when the message is received from Mailman for > delivery to one or more list members. There is the message-id as part of the mail itself, and set by the user. That one is not unique, e.g. if a mail is bounced to the list. Exim has an internal id, and that is also part of the log (also if a mail is delivered to a remote mailserver, the id there is logged). This works fine. However, mailman doesn't have an internal id I can use to follow the message (or at least, it doesn't transfer one to exim upon delivery). I can indeed use the user set message id for following mail. However, I would prefer some internal id, and also to have logged the IDs exim (or probably any other MTA) transmits upon delivering the mails when handing the mails over to the MTA again. (Probably in some format as "mailman-ID recepient MTA-id" so that it's easy for me to grep for message if a user complains.) Regards, Andi

2 years, 4 months

[MM3-users] Re: Auth question

by David Krantz

On Thu, Mar 30, 2017 at 1:06 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > To be more specific, the projects that are required for a fully > functioning Mailman installation with Postorius and Hyperkitty are > > Mailman (the core) > > Hyperkitty (the archiver) > > Postorius (the web list management UI) > > django-mailman3 (common django things used by Postorius and Hyperkitty) > > MailmanClient (python bindings for the core REST API used by Postorius > and Hyperkitty) > > HyperKitty - Mailman plugin (plugin for the core to communicate with > Hyperkitty) > I tried to upgrade today. The result is a broken install which fails when trying to upgrade the database. $> ./bin/mailman-post-update [...] File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/db/backends/base/base.py", line 236, in _commit return self.connection.commit() File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/db/utils.py", line 94, in __exit__ six.reraise(dj_exc_type, dj_exc_value, traceback) File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/db/backends/base/base.py", line 236, in _commit return self.connection.commit() django.db.utils.IntegrityError: update or delete on table "auth_user" violates foreign key constraint "social_auth_usersocial_user_id_193b2d80880502b2_fk_auth_user_id" on table "social_auth_usersocialauth" DETAIL: Key (id)=(3) is still referenced from table "social_auth_usersocialauth". I have tried to drop and recreate the databases but I get the above result anyway. The description in https://wiki.list.org/DOC/Mailman%203%20installation%20experience is very hazy. The process of symlinking in libraries is fiddly to say the least. I get mailman to start but not any web interface. I have not tested mailman so if it works rather than just start I do not know. There is a description for a clean install for development at http://docs.mailman3.org/en/latest/devsetup.html, but I suspect that it isn't usable for anything other than development. I have read it parallell to try to interpret the installation experience description which in turn describes more of what I am trying to do. No luck though. regards // David

9 years

Search results for query "sapiro"