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

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

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

8 years, 6 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

7 years, 5 months

[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 "^$|^.*#" :-)

4 years, 9 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/ >> > >

7 years, 8 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, 3 months

[MM3-users] Re: hyperkitty.views.mailman Could not archive the email with message-id '<snip>': A string literal cannot contain NUL (0x00) characters

by Gilles Filippini

Mark Sapiro a écrit le 11/03/2021 à 22:15 : > On 3/11/21 12:59 PM, Gilles Filippini wrote: >> Hi, >> >> I have this error message repeating endlessly into the mailman-web logs. >> The related list is an open one on which we receive spam sometimes. I >> understand these emails can me malformed and cause this error. How to >> deal with them? They can't stay forever at the hyperkitty door. > > > The message is queued at `var/archives/hyperkitty/spool/`. The files in > that directory are Python pickles. You can examine them with the > `mailman qfile` command and delete the spam ones. Looking at the offending message with 'mailman qfile', it appears it is a legitimate one actually, sent from an Android phone. Couldn't hyperkitty be a bit less strict? _g.

4 years, 11 months

[MM3-users] Re: Not able to start mailman server

by Stephen J. Turnbull

Mark Sapiro writes: >>>>> Kartheek wrote: > > I am trying to setup postorius using this website - I've used up all my bandwidth for now with the "can't send mail in Docker" thread, but FWIW Kartheek appears to be using Homebrew to manage third party packages on Mac, and in particular to install Python. I don't recall specifically with respect to Python, but I suspect that there's a "Homebrew system 'python'" (I know Homebrew does that with certain important programs that the Homebrew system depends on). That might very well confuse pip and other setup programs, since Homebrew likes to put stuff in places where you normally wouldn't find them to avoid conflicts (eg, multiple versions of Python). I can't be more specific about problems, and you'd hope that such stuff would "just work", but that might at least explain Mailman looking for stuff in "wrong places" (which might actually be right for Homebrew). Steve

4 years, 6 months

[MM3-users] Re: PSA: Avoiding spam-scanning outgoing mailman3 mail

by Mark Dadgar

On May 8, 2020, at 3:20 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > We tend to do this differently. For example, on mail.python.org which > currently has 261 Mailman 2.1 lists and 134 Mailman 3 lists and sends > about 135,000 individual messages per day from the two Mailman > instances, we define in /etc/postfix/master.cf > > 127.0.0.1:8026 > inet n - - - - smtpd > -o smtpd_authorized_xforward_hosts=127.0.0.0/8 > -o mynetworks=127.0.0.0/8 > -o smtpd_recipient_restrictions=permit_mynetworks,reject > -o smtpd_client_restrictions= > -o smtpd_helo_restrictions= > -o smtpd_sender_restrictions= > -o smtpd_data_restrictions= > -o receive_override_options=no_unknown_recipient_checks > -o smtpd_milters=inet:127.0.0.1:8891 > > Then port 8026 only accepts locally generated mail and only does dkim > signing (milter on port 8891) and essentially no other checks. > > Then in the [mta] section in mailman.cfg we only need > > smtp_port: 8026 Yep - I used to do something similar back when I was running dspam with mm2.1. This is a slightly more complicated to set up, but cleaner. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 9 months

Search results for query "sapiro"