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

[MM3-users] Re: Sign and encrypt e-mail responses

by Markus Grandpre

Dear Mark, thank you very much for your response. Is there already a way to enable signing in Mailman v3.3.8 / v3.1 or does the signing support still have to be implemented? Best regards, Markus Grandpré Am 6/3/24 um 18:51 schrieb Mark Sapiro: > On 6/2/24 11:51 PM, Markus Grandpré wrote: >> Dear List, >> >> is it possible to sign and encrypt all e-mail responses from the Mailman3 server with a digital certificate? > > > Not without significant code changes. Signing alone should not be difficult. Encryption is more difficult if the > recipients are going to be able to read the encrypted mail without access to the server's private key. This would > require mail to be personalized, which digests currently aren't, and encrypted with the recipient's public key which > requires the server to have all those keys. > -- Markus Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur, Tel: ++49 7531 88 4342

2 years, 2 months

[MM3-users] Re: Feature request, hyperkitty, low volume lists

by Alain D D Williams

On Thu, Jan 09, 2025 at 10:19:17AM -0800, Mark Sapiro wrote: > This is a long standing issue. See > https://gitlab.com/mailman/hyperkitty/-/issues/79 Thanks > > For an example see: > > > > https://fridayfolk.phcomp.co.uk/mailman3/hyperkitty/list/announce@fridayfol… > > The style of this page is not standard. Is this a downstream packaged > HyperKitty? See > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/2025/1/ > for the standard page or > https://mail.python.org/archives/list/mailman-i18n@python.org/2024/12/ for > one with no posts. I installed from the Debian repositories as it seemed more straightforward than following the instructions on the mailman project. But it has left me running code that is ~2 years old. I might try to migrate at some point. -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

1 year, 7 months

[MM3-users] Re: Core, Hyperkitty and Postorius releases

by Odhiambo Washington

On Fri, May 14, 2021 at 7:04 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/14/21 5:02 AM, Odhiambo Washington wrote: > > On Fri, May 14, 2021 at 2:52 PM Jeff Steele <jeff(a)steele.com> wrote: > > > >> > >> > >> On May 14, 2021, at 7:49 AM, Odhiambo Washington <odhiambo(a)gmail.com> > >> wrote: > >> > >> /bin/sh: sass: Permission denied* > >> > >> > >> > >> Did you check the permissions on your sass binary? > >> > > > > My mailman installed in /opt/mailman/mm > > > > find /opt/mailman/ -type f -name sass > > > > yielded nothing! > > > > Try `which sass` > root@gw:/usr/home/wash # su mailman3 (venv) [mailman3@gw /usr/home/wash]$ which sass (venv) [mailman3@gw /usr/home/wash]$ There is no sass. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

5 years, 3 months

[MM3-users] Re: Recommended way to backup a mailman3 instance

by Gilles Filippini

Andrew Hodgson a écrit le 18/04/2020 à 12:26 : > Mark Sapiro wrote: > >> On 4/17/20 4:51 PM, Abhilash Raj wrote: >>> >>> If they are empty, perhaps the digest creation process should just re-create them instead of failing to create/send digests? We don't really need the directory structure to exist. > >> I created <https://gitlab.com/mailman/mailman/-/issues/699> for this. > > In my situation I noticed the directories weren't created very quickly as my Exim config looks for the list directories to identify whether that address exists. I don't know how Postfix does the aliasing but for my case it would make sense to get the directories created as soon as possible, not sure if the digest handler would be soon enough or not. There is no need for these directories on the Exim side actually. You can safely drop the related checks from the Exim configuration [1]. [1] https://github.com/maxking/docker-mailman/pull/371 _g.

6 years, 4 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

The confirmation email says: Hello from example.com! Where can I change example.com to mydomain.com ???? Thanks El mié., 2 ago. 2017 a las 11:50, Abhilash Raj (<raj.abhilash1(a)gmail.com>) escribió: > When you set DEBUG=False, Django doesn't serve static files because of > which you see only text and no styles. > > > http://docs.mailman3.org/en/latest/pre-installation-guide.html#django-stati… > > If you do set DEBUG=False, you need to serve the static pages somehow. > > Alternatively in you case, you can remove the part of the `settings.py` > which changes the Emailbackend when `DEBUG=False` so that you don't have > to worry about serving static files and still send out emails. > > On Wed, Aug 2, 2017, at 09:46 AM, Rafael Mora wrote: > > For testing purpose I turned back to false the DEBUG var and everything > > started working fine with HyperKitty > > > > I don't understand... this is the trace when I click Login from Postorius > > to HyperKitty > > > > [02/Aug/2017 16:43:42] "GET /postorius/lists/ HTTP/1.1" 200 3645 > > [02/Aug/2017 16:43:48] "GET /accounts/login/?next=/postorius/lists/ > > HTTP/1.1" 200 10950 > > [02/Aug/2017 16:43:49] "GET /static/CACHE/css/hyperkitty.2f591b4e31fe.css > > HTTP/1.1" 200 156657 > > > > > > What should I check? > > > > > > > > > > > > > > > > > > El mié., 2 ago. 2017 a las 10:56, Mark Sapiro (<mark(a)msapiro.net>) > > escribió: > > > > > On 08/02/2017 07:55 AM, Rafael Mora wrote: > > > > HyperKitty is looking for some files in /static/CACHE/... but it > doesn't > > > > find them: > > > > > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/b3547a2ab51b.css > HTTP/1.1" > > > > 404 107 > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/4c17bb8058aa.css > HTTP/1.1" > > > > 404 107 > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/2fa1cba00450.css > HTTP/1.1" > > > > 404 107 > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/js/4ce1260ef558.js > HTTP/1.1" > > > 404 > > > > 105 > > > > [02/Aug/2017 14:53:39] "GET /static/CACHE/js/4ce1260ef558.js > HTTP/1.1" > > > 404 > > > > 105 > > > > > > > > > > > > Should I run any command to activate the CACHE dir? > > > > > > > > > You need to ensure you have a working sass compiler. As I said at > > > < > > > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > >, > > > See the third bullet under > > > <http://docs.list.org/en/latest/prodsetup.html#dependencies>. > > > > > > Then you need to run commands like > > > > > > django-admin collectstatic --clear > > > django-admin compress > > > > > > > > > -- > > > 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 > > _______________________________________________ > > Mailman-users mailing list > > mailman-users(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > -- > thanks, > Abhilash Raj > _______________________________________________ > 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

9 years

[MM3-users] Re: Chinese characters in list name shows question mark (?)

by Franklin Weng

Franklin Weng 於 2019/10/24 上午8:05 寫道: > Hi Mark, > > Thanks for your reply. > > Mark Sapiro 於 2019/10/24 上午6:10 寫道: >>> Is there any other setting I should look at? >> The list's preferred_language setting (Postorius -> Settings -> List >> Identity -> Preferred Language. The list welcome message is encoded in >> Mailman's character set for the list's preferred_language. If this is >> English (USA), the character set is us-ascii. If it is set to Chinese >> (Taiwan), the character set is utf-8, and it should work. > However in my settings -> List Identity page I didn't see Preferred > Language option. > > https://nextcloud.slat.org/index.php/s/45tGaE7ALgAFQFK > > What may be possible wrong that I couldn't see Preferred Language > settings in the web interface? I got it. It is implemented in postorius 1.2.5 but my Debian buster contains 1.2.4-1 for now. Franklin

6 years, 9 months

[MM3-users] Re: Where does sender postorius@ come from?

by Jens Günther

Thanks for the hint. Unfortunately it's not working as expected. I'm using the docker-setup and tried it in 2 different locations, but neither got the expected effect: - I put the variable in the mm-web-container-environment: mm-web: environment: - EMAIL_CONFIRMATION_FROM=myaddress(a)something.org - Then I tried settings_local.py with: EMAIL_CONFIRMATION_FROM = 'myaddress(a)something.org' What am I missing, where do I have to set this value correctly? Thanks for the help! Jens. Am 08.06.23 um 01:57 schrieb Mark Sapiro: > On 6/7/23 14:13, Jens Günther wrote: >> >> The more important question would be, where :-) since I already >> checked if I can set it to something alse, I might need a hint where >> exactly I can find it. In the SERVE_FROM_DOMAIN/admin I did not >> stumble upon it. If you don't know it, no problem, let's just wait for >> somebody who does, thanks. > > > It's the EMAIL_CONFIRMATION_FROM setting in your Django settings. >

3 years, 2 months

[MM3-users] Re: Mail control not given from Mailman 3 to postfix

by Shashikanth Komandoor

Thank you Mark for your help. Unfortunately, I felt myself dummy after seeing the mailman.log and the shunt queue. I did not find any clue from them. I did not see any log records based on that message id in mailman.log. There is a lot much of shunt queue but I don't see any file with the required message id. The same is the bad queue also. I find below two lines at that particular time stamp by when the log recorded in vette.log *Uncaught runner exception: sequence item 0: expected str instance, Header foundTypeError: sequence item 0: expected str instance, Header found* But I am not sure if the above lines are related to that missing message or not. I am using postgresql as database. FYI, if it brings an idea to you to help me. Could you please help me out how to trace further ? On Tue, Jul 7, 2020 at 9:12 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/6/20 11:07 PM, Shashikanth Komandoor wrote: > > > > Recently I observed a peculiar case. There is a list say > > testlist(a)lists.testdom.com has a non member say testuser(a)testdom.com > whose > > Moderation attribute is set to "Accept immediately (bypass all other > rules). > > > > This testuser(a)testdom.com has sent a mail to > testlist(a)lists.testdom.com > > and postfix of my Maliman 3 received the request and handed over to > Mailman > > at 0.0.0.0:8024 socket running on the same machine and the same is > logged > > in /var/log/maillog. > > > So it was received by Postfix and delivered to Mailman. > > > > Since the user has the moderation attribute set to Accept, the > > /var/lib/mailman/mailman/var/logs/vette.log also displayed "ACCEPT" on > > searching with the same message id. > > > And the post was accepted. (Apparently you override the path for > logging.vette in your mailman.cfg since the default logs these to > mailman.log) > > > > At this point, to my expectations, there should be 2 entries for this > > message id in smtp.log one for smtp and one for post. But I don't find > any > > log records with this message id in smtp.log and of course the mail is > not > > delivered even. > > > You don't find the message-id in the smtp.log for the incoming LMTP > because the message-id is not logged in this entry. It only logs the > actual LMTP commands and the envelope sender and recipient(s). > > You don't find the > > <messageid> post to testlist(a)lists.testdom.com ... > and > <message-id> smtp to testlist(a)lists.testdom.com for nn recips, ... > > entries because the post never got to that point in the processing > (those are logged when the post is delivered to the list members). > > > > Could you please help me out if I have missed any point or improperly > > understood the mail flow while using the mailman 3? > > There was probably some exception in processing causing the message to > be shunted. If so, the message is in the shunt queue and there is an > entry in mailman.log for the exception and shunting with a traceback > from the exception which will help in diagnosing the reason. > > -- > 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

6 years, 1 month

[MM3-users] Re: Upgrading packages

by Eggert Ehmke

Am Donnerstag, 13. Oktober 2022, 19:09:20 CEST schrieb Mark Sapiro: > On 10/13/22 03:49, Eggert Ehmke wrote: > > pip install --upgrade git+https://gitlab.com/mailman/hyperkitty@master > > > > I noticed that mistune-2.0.0rc1 was upgraded to mistune-2.0.4. > > > > All packages were upgraded fine. I applied the patch to > > venv/lib/python3.9/site-packages/hyperkitty/lib/renderer.py > > It shouldn't have been necessary to apply any patch. The head of the > GitLab hyperkitty master branch is already compatible with mistune 2.0.4 strange, I still had the line with the (not working) from mistune.scanner import escape_html, escape_url maybe because the migration step was not working at that time? > I'm guessing at some point you installed something which required you to > manually make this migration and that produced this conflict. Do you > have both 0017_alter_emailtemplate_language.py and > 0017_auto_20220628_1132 in your postorius/migrations/ directory? If so, > probably just removing 0017_auto_20220628_1132 will fix this? That's what I did in the meantime, and it works now! Thank you.

3 years, 10 months

[MM3-users] Re: Hyperkitty no longer archiving

by Stephen J. Turnbull

Mark Sapiro writes: > On 11/21/22 16:33, Hirayama, Pat wrote: > > > > mailmansuite.log is full of: > > > > ERROR 2022-11-22 00:25:40,365 7 hyperkitty.views.mailman Access to the archiving API endpoint was forbidden from IP 172.31.0.1, your MAILMAN_ARCHIVER_FROM setting may be misconfigured > > > Set > ``` > MAILMAN_ARCHIVER_FROM = '172.31.0.1' > ``` > in your Django settings, or to accept any IP set > ``` > MAILMAN_ARCHIVER_FROM = '*' > ``` Hm. Pat wrote: > settings_local.py: > MAILMAN_ARCHIVER_FROM = ('172.18.8.14', '172.31.0.1', '172.31.0.2', '172.31.0.3', '172.31.0.4', '172.31.0.5', '127.0.0.1', '::1') where '172.31.0.1' is the second element. So we need to figure out where HyperKitty is getting its setting for MAILMAN_ARCHIVER_FROM. 1. Are there multiple copies of settings_local.py lying around? 2. Does settings.py have "from settings_local import *" in it? 3. Are there multiple copies of settings.py lying around? 4. What else may have changed in the migration? Any software upgrades in mailman, hyperkitty, mailman-web (or wherever the settings*.py are coming from)? Steve

3 years, 8 months

Search results for query "sapiro"