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

[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, 6 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Hello Abhilash, I have this in my settings.py file: EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_PORT = 25 #EMAIL_HOST_USER = 'mailing(a)labbrands.com' #EMAIL_HOST_PASSWORD = '******' What should I use in user and password?? Does Django use postfix to send the email??? Thanks El mar., 1 ago. 2017 a las 16:20, Abhilash Raj (<raj.abhilash1(a)gmail.com>) escribió: > Hi, > > > > On Tue, Aug 1, 2017, at 02:11 PM, Rafael Mora wrote: > > It's ok now, but still I can't make it send the confirmation email > > > > This is from mailman.log: > > > > > > [mailman@localhost logs]$ tail -f mailman.log > > Aug 01 15:59:18 2017 (2327) lmtp runner started. > > Aug 01 15:59:18 2017 (2333) virgin runner started. > > Aug 01 15:59:18 2017 (2332) retry runner started. > > Aug 01 15:59:18 2017 (2330) pipeline runner started. > > Aug 01 15:59:18 2017 (2325) command runner started. > > Aug 01 15:59:19 2017 (2328) nntp runner started. > > Aug 01 15:59:19 2017 (2326) in runner started. > > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET > > /3.0/lists?count=0&page=1&advertised=true HTTP/1.1" 200 90 > > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET > > /3.0/lists?count=10&page=1&advertised=true HTTP/1.1" 200 90 > > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET /3.0/domains HTTP/1.1" 200 > > 90 > > > > > > > > > > What should I do? > > If you are talking about Account confirmation emails, they usually are > sent out from Django and not Mailman Core itself. > > To configure Django you need to edit the `settings.py` file, wherever > that is one your installation. If you are following the guide mentioned > at http://docs.mailman3.org/en/latest/prodsetup.html, it should be at > `mailman-suite/mailman-suite_project/settings.py`. > > To configure your Django to send emails, have a look at > > http://docs.mailman3.org/en/latest/config-web.html#setting-up-email-required > . > > That documentation page has pretty much everything you need in order to > have a running Web Frontend, please go through it and make sure you have > everything configured. > > Finally, the actual emails from Mailing lists are supposed to be handled > by Core. You need to configure Postorius & Mailman both to communicate. > The settings are mentioned > http://docs.mailman3.org/en/latest/config-core.html#configuring-mta > here. > > > Hope that helps! > > > > > > > > > > > > > > > El mar., 1 ago. 2017 a las 15:36, Mark Sapiro (<mark(a)msapiro.net>) > > escribió: > > > > > On 8/1/17 1:14 PM, Rafael Mora wrote: > > > > > > > > Why does it say Address already in use? > > > > > > > > > Because you are starting lm tp runner and it's already running. > > > > > > Do 'mailman stop'. Then ensure no Mailman processes are running. kill > > > any if necessary. Then do 'mailman start'. > > > > > > -- > > > 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, 2 months

[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, 11 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, 4 months

[MM3-users] Re: Scheduled tasks

by Darren Smith

So I don't know how in the world we missed the qcluster and running that. Pretend I'm a python novice (that would be correct) - can you tell me what the ramifications of not running this? I have attempted to start the queues running, but it caused the entire machine to be consumed processing things. So I'm going to have to do this later at night again when our customers won't be as inconvenienced. This is one of those times that I wish that I had been able to understand everything deeper before we had to switch to the new system. Live and learn I guess. -Darren On Thu, Jun 7, 2018 at 9:57 PM, Darren Smith <silas.crutherton(a)gmail.com> wrote: > I will take up any problems with the installation with the creator. > However, I was able to find and run some of the scripts this afternoon, and > I'm running some of the longer-running ones tonight while the usage is > lower. > > As for bogging down - I mean attempting to click on an email can take a > LONG time to render, and we frequently get 504 gateway timeouts (the calls > to hyperkitty are timing out). I am trying hard to figure out why this is > happening and to try to tune the system. I still suspect that there are > some inefficiencies with how the database is being used, or how the > database is doing things. > > I will take a look at qcluster, that was interesting info and hopefully it > can help me out. > > Thanks for your response, > > -Darren > > On Thu, Jun 7, 2018 at 4:16 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 6/7/18 9:59 AM, Darren Smith wrote: >> > All, >> > >> > I am looking more through the documentation of the Mailman Suite here: >> > >> > https://media.readthedocs.org/pdf/gnu-mailman/latest/gnu-mailman.pdf >> > >> > In section 3.2.5 it talks about the scheduled tasks that need to be run >> to >> > do "specific routine functions" in hyperkitty. >> > >> > I installed through the easy install script found here: >> > >> > https://github.com/iomarmochtar/mailman3_ei/ >> > >> > However, I can't find anything in THAT documentation that talks about >> these >> > cron jobs, and in fact the Mailman Suite isn't installed through that >> > script. >> >> >> That is a third party project. If you have issues with it, you should >> take them up with @iomarmochtar. >> >> >> > Can someone point me to any other documentation about the tasks that >> need >> > to be run on a continual basis? >> >> >> The section 3.2.5 you refer to tells you what needs to be set up in >> cron. For a list of the jobs tat are run, use >> >> django-admin runjobs --list >> >> >> . Our hyperkitty installation seems to be >> > bogging down more and more, and I am hoping that it will be as simple as >> > just running some jobs that haven't been on our radar. >> >> >> what do you mean by 'bogging down'? If you aren't doing so, setting up >> qcluster as in section 3.2.3 may help. >> >> -- >> 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/ >> > >

8 years, 4 months

[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.

4 years

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

[MM3-users] Re: Disable "confirmation emails"

by Jonas Meurer

Am 18.09.2018 um 23:25 schrieb Mark Sapiro: > On 09/18/2018 01:46 PM, Hagen Bauer wrote: >> >> even after a lot of google search I could not find a way to disable the >> Confirmation Mails like >> .... >> The results of your email command are provided below. >> >> - Original message details: >> ....... >> >> Is there a way to do this? I have users who would be irritated and I >> dont want them to recieve this > > > Where are you seeing these? There were changes in this area in Mailman > core v. 3.2.0 and I think these now should only be sent in response to > mail to the -request address that contains a command other than > (un)subscribe or confirm. I can confirm that these mails are sent in response to messages to -subscribe (not only to -request) with Mailman 3.2. I experienced the same as Hagen and I also wonder how to turn them of. Cheers, jonas

8 years

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

by Odhiambo Washington

On Sat, May 15, 2021 at 12:01 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/14/21 1:54 PM, Odhiambo Washington wrote: > > > > /usr/local/include/sass > > > > That is the only thing found that is in the base system. > > And that's the one you want. What is it's mode? > root@gw:/usr/home/wash # ls -al /usr/local/include/sass total 104 drwxr-xr-x 2 root wheel 512 Apr 16 16:49 . drwxr-xr-x 176 root wheel 10240 Apr 19 18:05 .. -rw-r--r-- 1 root wheel 2369 Apr 8 11:08 base.h -rw-r--r-- 1 root wheel 10742 Apr 8 11:08 context.h -rw-r--r-- 1 root wheel 6632 Apr 8 11:08 functions.h -rw-r--r-- 1 root wheel 6489 Apr 8 11:08 values.h -rw-r--r-- 1 root wheel 198 Apr 8 11:08 version.h I imagined I needed an executable. drwxr-xr-x 2 root wheel 512 Apr 16 16:49 sass -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

5 years, 5 months

[MM3-users] Re: 120 gmail users removed from lists !

by Andrew Hodgson

Mark Sapiro <mark(a)msapiro.net> wrote: >On 10/23/23 9:51 PM, Yvan ♞ wrote: >> Hello, >> Thanks for this answer, my problem is I'm on yunohost server and the >> update 3.3.9 is not available now. >> Any "handmaid" solution should be great. >It may be more disruptive than you want, but you can just set DMARC Mitigate unconditionally to Yes to apply DMARC mitigations to all list mail. Another thing which helped me a lot with Gmail bounces was setting VERP options everywhere in Mailman. I'm not sure what has made more of a difference, setting the DMARC to unconditionally apply the mitigations or setting VERP everywhere. Speaking of the new additions in Mailman 3.3.9, does anyone have a list of the domains Google are using which we can add to the list so we can disable the unconditional DMARC mitigations for all list posts? Its probably somewhere obvious on a Gitlab issue or similar, but haven't found it yet. Thanks. Andrew.

2 years, 11 months

Search results for query "sapiro"