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

[MM3-users] Re: Domain Issue with MM3

by Mark Sapiro

On 10/23/19 12:53 PM, Liebeskind Uri (luri) wrote: > > I have setup this mailing list test(a)digital.lists.zhaw.ch but subscribing failed. How did you create the list and the digital.lists.zhaw.ch domain in Mailman? > * Subscribing via the Mass Import Form failed with a Server Error message in the browser. Log messages may help here. I can't tell you where to find them in your installation, but your Django settings or local settings will define LOGGING['handlers']['file']['filename'] which is where your Django logs are. and your various Mailman logs are generally in Mailman's var/logs/ directory. You may find a traceback from this error in the Django log or in Mailman's error.log or access.log. > * Subscribing via e-mail test-join(a)digital.lists.zhaw.ch<mailto:test-join@digital.lists.zhaw.ch> because no response came from MM3. This is Postfix. See below. > The mail to join has been delivered properly to MM3 but MM3 has swallowed the mail w/o response or error message. There also has not been any pending subscription. MM3 did respond. See below. > 2019-10-23T19:51:33.678705+02:00 svma-s-01321 postfix/smtpd[98348]: connect from srv-mail-013.zhaw.ch[160.85.104.123] > > 2019-10-23T19:51:33.692258+02:00 svma-s-01321 postfix/smtpd[98348]: A8EFC3FA6A: client=srv-mail-013.zhaw.ch[160.85.104.123] > > 2019-10-23T19:51:33.693192+02:00 svma-s-01321 postfix/cleanup[98351]: A8EFC3FA6A: message-id=<eb90deb6-58af-a873-3382-c27ce6d05031(a)anydomain.org> > > 2019-10-23T19:51:33.704102+02:00 svma-s-01321 postfix/qmgr[90603]: A8EFC3FA6A: from=<name(a)anydomain.org>, size=5329, nrcpt=1 (queue active) > > 2019-10-23T19:51:33.704864+02:00 svma-s-01321 postfix/smtpd[98348]: disconnect from srv-mail-013.zhaw.ch[160.85.104.123] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 > > 2019-10-23T19:51:33.763670+02:00 svma-s-01321 postfix/lmtp[98352]: A8EFC3FA6A: to=<test-join(a)digital.lists.zhaw.ch>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.08, delays=0.02/0.01/0/0.05, dsn=2.0.0, status=sent (250 Ok) Per the above the message was delivered to Mailman. > 2019-10-23T19:51:33.764485+02:00 svma-s-01321 postfix/qmgr[90603]: A8EFC3FA6A: removed > > 2019-10-23T19:52:29.278529+02:00 svma-s-01321 postfix/smtpd[98348]: table hash:/var/lib/mailman3/data/postfix_lmtp(0,lock|fold_fix|utf8_request) has changed -- restarting Why all these table changes/restarts? > 2019-10-23T19:52:29.286154+02:00 svma-s-01321 postfix/smtpd[98558]: connect from localhost[127.0.0.1] Mailman has connected to Postfix. > 2019-10-23T19:52:29.288612+02:00 svma-s-01321 postfix/cleanup[98351]: table hash:/var/lib/mailman3/data/postfix_domains(0,lock|utf8_request) has changed -- restarting > > 2019-10-23T19:52:29.292655+02:00 svma-s-01321 postfix/smtpd[98558]: 476AD3FA6A: client=localhost[127.0.0.1] > > 2019-10-23T19:52:29.293671+02:00 svma-s-01321 postfix/cleanup[98559]: 476AD3FA6A: message-id=<157185314763.94537.10517326910475727036(a)svma-s-01321.zhaw.ch> And delivered its response, message-id=<157185314763.94537.10517326910475727036(a)svma-s-01321.zhaw.ch> to Postfix. > 2019-10-23T19:52:29.296393+02:00 svma-s-01321 postfix/qmgr[90603]: table hash:/var/lib/mailman3/data/postfix_domains(0,lock|utf8_request) has changed -- restarting > > 2019-10-23T19:52:29.298231+02:00 svma-s-01321 postfix/smtpd[98558]: disconnect from localhost[127.0.0.1] ehlo=1 mail=1 rcpt=1 data=1 commands=4 So the message was delivered to Postfix with the four commands ehlo, mail, rcpt and data. This is normal. What did Postfix do with the message? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Hello, This is what I've got in /var/lib/mailman/var/data: [root@localhost data]# pwd /var/lib/mailman/var/data [root@localhost data]# ls -l total 100 -rw-rw---- 1 mailman mailman 74752 Jul 16 16:44 mailman.db -rw-rw---- 1 mailman mailman 315 Jul 24 10:41 postfix_domains -rw-r----- 1 mailman mailman 12288 Jul 24 10:41 postfix_domains.db -rw-rw---- 1 mailman mailman 318 Jul 24 10:41 postfix_lmtp -rw-r----- 1 mailman mailman 12288 Jul 24 10:41 postfix_lmtp.db What should be the next step? El dom., 23 jul. 2017 a las 20:22, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/23/2017 06:00 PM, Rafael Mora wrote: > > Hello guys, > > > > This is what I've got on ../var/data: > > > > [root@localhost data]# pwd > > /var/lib/mailman/var/data > > [root@localhost data]# ls -l > > total 76 > > -rw-rw---- 1 mailman mailman 74752 Jul 16 16:44 mailman.db > > > > > > What should I do in order to let mailman install the DB files? > > > Run > > bin/mailman aliases > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 10 months

[MM3-users] Re: Deleting A List

by Odhiambo Washington

On Fri, May 3, 2024 at 11:48 PM Mark Sapiro <mark(a)msapiro.net> wrote: > Mark Sapiro wrote: > > > update hyperkitty_email set mailinglist_id = 2 where mailinglist_id = 13; > > update hyperkitty_mailinglist_owners set mailinglist_id = 2 where > > mailinglist_id = 13; > > update hyperkitty_mailinglist_moderators set mailinglist_id = 2 where > > mailinglist_id = 13; > > update hyperkitty_thread set mailinglist_id = 2 where mailinglist_id = > 13; > > delete from hyperkitty_mailinglist where id = 13; > > update hyperkitty_mailinglist set name = 'list(a)lists.nog.ke', list_id = > > 'list.lists.nog.ke' where id = 2; > > Or instead of that you could just go to the new list(a)lists.nog.ke > archive in HyperKitty and delete it and then just do the > ``` > update hyperkitty_mailinglist set name = 'list(a)lists.nog.ke', list_id = > 'list.lists.nog.ke' where id = 2; > ``` > I went with this approach and worked super! Thank you. So, seeing as deleting a list retains its archives, if I want to delete a list together with its archives, do I first delete the archives, then follow with the list? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 1 month

[MM3-users] Re: Migrating mailman3 to latest ubuntu lts

by Helio Loureiro

Hi, I forgot to mention that, but there is no mailman-web on ubuntu packages on 18.04. So I can't find a way to run it. Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro On Thu, 14 Dec 2023 at 18:50, Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/14/23 10:19, Jered Floyd wrote: > > > > Did you run the upgrade steps? > > > > https://docs.mailman3.org/en/latest/upgrade-guide.html > > > > For schema upgrades you will at least need to do "mailman-web migrate", > but please read the entire section as 3.1.1 to 3.3.9 is a big step. > > > These are all important and necessary steps, but "mailman-web migrate" > updates schemas for the mailman-web database. It does not update the > alembic migrations for the mailman database. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to helio(a)loureiro.eng.br >

1 year, 6 months

[MM3-users] Re: Changes in Django admin interface are not syncing to postorius gui /database

by Mark Sapiro

On 11/9/24 06:52, Odhiambo Washington via Mailman-users wrote: > > I looked at Django Admin and Postorius and I see all my MLs in both. What you see in Django admin is in the HYPERKITTY section and corresponds to hyperkitty_* tables in the mailmanweb database. > What I am sure about is that I did NOT create my MLs using Django admin UI. > I either created them using the CLI or Postorius. > Having said that, I did run two tests: > 1. Create a ML in Postorius and check whether it appears in Django admin - > The list was visible in Django Admin Because the list you created had the hyperkitty archiver enabled. > 2. Create a ML in Django admin and check whether it appears in Postorius - > The list was NOT visible in Postrorius Because it's only in HyperKitty. > 3. Create a ML in CLI and check if it appears in both Django admin and > Postorius - List is visible in Postorius, but not in Django admin Becayse this list did not have the hyperkitty archiver enabled. > ``` > MariaDB [mailmansuite]> select list_name, list_id from mailinglist where > list_name like 'ulf%'; > +-----------+-------------------------------+ > | list_name | list_id | > +-----------+-------------------------------+ > | ulftest2 | ulftest2.lists.kictanet.or.ke | > | ulftest3 | ulftest3.lists.kictanet.or.ke | > +-----------+-------------------------------+ > ``` These are only Mailman lists. > The list that I created using Django admin is NOT listed here! Because it's only in HyperKitty. > ``` > MariaDB [mailmansuite]> select list_id, name from hyperkitty_mailinglist > where list_id like 'ulf%'; > +-------------------------------+-------------------------------+ > | list_id | name | > +-------------------------------+-------------------------------+ > | ulftest1(a)lists.kictanet.or.ke | ulftest1(a)lists.kictanet.or.ke | > | ulftest2.lists.kictanet.or.ke | ulftest2(a)lists.kictanet.or.ke | > +-------------------------------+-------------------------------+ > ``` > The list I created using Django admin and the one I created using > Postorius are both listed, but the one I created from CLI is not listed. Because for some reason, the CLI created list does not create the HyperKitty archive until there is a post or until the `new_lists_from_mailman` job runs even though hyperkitty is enabled. > So there must be some logic behind this. However, I don't know what it is. The bottom line is you can have lists in HyperKitty that are not in Mailman and vice versa. The only thing you can't do is create a list in HyperKitty via the HyperKitty web UI, but you can use hyperkitty_import to import a mbox for a list which is not in Mailman and will be only in HyperKitty. Also, while you can create a list in Mailman that isn't in HyperKitty, if the list has hyperkitty enabled it will be created in HyperKitty when the `new_lists_from_mailman` job runs. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months

[MM3-users] Re: FYI: Django security releases issued: 4.0.6 and 3.2.14

by David Newman

On 7/7/22 12:26 PM, Mark Sapiro wrote: > On 7/7/22 11:10 AM, David Newman wrote: >> On 7/7/22 10:25 AM, Mark Sapiro wrote: >> >> pip install -U mailman postorius django-mailman3 hyperkitty >> mailman-web uwsgi >> >> and it downgraded Django back to 3.0.14. > > > Because mailman-web 0.0.5 has in its setup.cfg > ``` > install_requires = > Django<3.1 > ``` > try > ``` > pip install -U git+https://gitlab.com/mailman/mailman-web.git > ``` > to get the latest mailman-web whose Django requirement is > ``` > install_requires = > django >=2.2, !=3.0, <4 That seemed to work OK, thanks. mailman-web is now on a dev version of 0.0.6 and Django is now on 3.2.14. However, pip now throws a warning when looking at package info: (venv) mailman@somehost:/home/dnewman$ pip show mailman-web WARNING: Ignoring invalid distribution -jango (/opt/mailman/venv/lib/python3.9/site-packages) Name: mailman-web Version: 0.0.6.dev9+gc606169 Summary: Mailman 3 Web interface. Home-page: https://gitlab.com/mailman/mailman-web Author: Mailman Developers Author-email: mailman-developers(a)python.org License: GPLv3 Location: /opt/mailman/venv/lib/python3.9/site-packages Requires: django, hyperkitty, postorius, whoosh Required-by: How to correct that so the command runs clean with no warnings or errors? This is on a host running Debian 11 with mailman3 and friends installed in a venv. Thanks. dn

2 years, 11 months

[MM3-users] Re: "to" Headers for Non-Anonymous lists

by Mark Sapiro

On 6/9/25 14:23, Dan Caballero wrote: > Hello, > > At the request of a list owner, we changed the settings on a list to "Anonymous = No" so that list members could see who a message was coming from. > > It seems a side effect of the setting is that users are now using "reply-to" and some messages are going out to the list addressed in the manner below. > > "Last Name, First Name via list-name <list-name(a)caltech.edu>" This is a consequence of DMARC mitigations. > The list owner feels this is confusing and some members may inadvertently email the list when they intend to email the individual. When the From is munged in that way for DMARC the orikinal From is put in Reply-To: or perhaps Cc: depending on other settings. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/handlers/dmarc… for details of this process and its goals. Assuming your list's Reply goes to list setting is No Munging The original From: should be in Reply-To: of the delivered. It appears that the messages that are sent To: Last Name, First Name via list-name <list-name(a)caltech.edu> are sent by an MUA that is ignoring Reply-To: and replying to From:. > I understand this is likely a client side caching issue since most email clients create an index of contacts based on previously received emails. > > Aside from reverting back to "Anonymous = Yes", is there any setting we can change at the list level to force the "to" field to persist as the list email address? Do you mean you want the From: in delivered messages to be the original poster's From: so that replies to the From: go to the OP. You can accomplish this by setting DMARC mitigation action to No DMARC mitigations, however this will ensure that any mail whose From: domain publishes a DMARC policy of quarantine or reject will most likely be bounced by all large ESPs. We do are best to ensure that a simple reply to a message to which DMARC mitigations are applied will go to the poster unless the Reply goes to list setting says otherwise. But I am confused as to your goal. Previously when the list was anonymous, all replies went to the list. Maybe your goal is to have list replies be addressed to <list-name(a)caltech.edu> rather than Last Name, First Name via list-name <list-name(a)caltech.edu>. If that is the goal, you could try setting Reply goes to list setting to Reply goes to list. That will set a Reply-To: list's short description <list-name(a)caltech.edu>. That may be what you want as long as the responder's MUA honors Reply-To: over From: -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 days, 15 hours

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I read the doc and it says that when the DEBUG var is set to False we should do these commands: django-admin collectstatic --pythonpath example_project --settings settings django-admin compress --pythonpath example_project --settings settings I did the first one and got this: (env2) [mailman@localhost mailman-suite]$ pwd /var/lib/mailman/mailman-suite (env2) [mailman@localhost mailman-suite]$ django-admin collectstatic --pythonpath mailman-suite_project --settings settings You have requested to collect static files at the destination location as specified in your settings: /var/lib/mailman/mailman-suite/mailman-suite_project/static This will overwrite existing files! Are you sure you want to do this? Type 'yes' to continue, or 'no' to cancel: yes 0 static files copied to '/var/lib/mailman/mailman-suite/mailman-suite_project/static', 345 unmodified. why it did not copy the files??? El mar., 1 ago. 2017 a las 23:18, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/01/2017 02:40 PM, Rafael Mora wrote: > > Why isn't it sending emails? > > > > What do you think? > > > What exactly are you doing that you think should result in sent mail? > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 10 months

[MM3-users] Re: All addresses in a bounced list posting seem to be considered as bouncing

by Mark Sapiro

On 7/9/22 9:51 AM, Andy Smith wrote: > > Over in Exim's mainlog I then see that delivered out to list > members. One of them rejects it at SMTP time, which I think causes > this: > > Jul 09 12:46:13 2022 (71509) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) > Jul 09 12:46:13 2022 (71509) Peer: ('127.0.0.1', 35440) > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) handling connection > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) Data: b'LHLO lists0.bitfolk.com' > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) Data: b'MAIL FROM:<>' > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) sender: <> > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) Data: b'RCPT TO:<users-bounces(a)mailman.bitfolk.com>' > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) recip: users-bounces(a)mailman.bitfolk.com > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) Data: b'DATA' > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) Data: b'QUIT' > Jul 09 12:46:13 2022 (71509) ('127.0.0.1', 35440) connection lost > Jul 09 12:46:13 2022 (71509) Connection lost during _handle_client() The SMTP rejection should not cause that. An SMTP recipient reject is processed internally and does not result in anything sent via SMTP to the list-bounces address. > …and I think that bounce message somehow incremented the bounce > score for andy(a)bitfolk.com even though that address was only present > in the original post's Cc: and body. If the original post was the message delivered to users-bounces(a)mailman.bitfolk.com, it is possible that simplematch or another recognizer parsed those addresses from the message body. > Is there a good way to further debug this? Maybe by being able to > see the full content of the DSNs that Mailman generates? As I posted previously, the DSN that Mailman generates is defined at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/outgoi…, but this message is not sent anywhere. It is only saved for possible inclusion in an admin notification or a probe message. If you send me the post as received from the list, I can run it through flufl.bounce and see what that produces. You might also be able to find the fake dsn and/or the message received via SMTP to users-bounces(a)mailman.bitfolk.com in Mailman's var/messages/ directory, although these are pickles and need to be examined with `mailman qfile`. > I think I've seen this before in the last couple of weeks so I'm > sure it'll crop up again soon. I've seen it mention about bounce > score for users-leave before, but I only really paid attention today > when it also listed my own address. users-leave probably is parsed out of the message footer. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: Database read only error on mailman_sync job

by Ugnius

Thank You, Mark for guideline. I accidentally posted here. I wanted to start new thread and just replaced subject of messages. Message was sent to this thread anyway. The reason of this issue was very simple. I creadet symlink in /usr/local/bin/django-admin to /project/home/manage.py, because I was unable to set original django-admin file to work as it should to work. Later I decided to run mailman project under other user and forgot about that symbolic link. So it was normal, that previous user had no privileges on database file. Thank You for helping. > On 12 Sep 2019, at 21:50, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 9/1/19 1:02 AM, Ugnius S wrote: >> >> I guess that issue is hyperkitty database, but I even do not know the name >> and location of that database. > > See the DATABASES definition in your Django settings. The default is a > sqlite3 database named mailmansuite.db in the same directory as the > Django settings. > > -- > 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/

5 years, 9 months

Search results for query "sapiro"