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

[MM3-users] Re: hooking up mailman and sendmail

by John Covici

On Sun, 14 Mar 2021 14:05:33 -0400, OK, thanks a lot. Mark Sapiro wrote: > > On 3/14/21 7:56 AM, John Covici wrote: > > That post does not answer my question, it applies only to mailman2 and > > is a big mess. I was hoping to use lmtp, which sendmail will use and > > mailman seems to have some facilities to use it as well. > > > What that post describes is for Mailman 2.1, how to hijack Mailman's > generated aliases for Postfix and apply them to sendmail. The hope is > that someone who understands how to configure sendmail can take those > ideas and apply them to the Postfix transport and domain mappings > generated in var/data/postfix_lmtp and var/data/postfix_domains to > generate what is needed for sendmail. > > Hopefully, once people figure out how to do this, they will inform us of > the solution and we can update the docs. > > > -- > 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/ > -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una covici(a)ccs.covici.com

5 years, 1 month

[MM3-users] Re: Importing MBOX from custom listserv to MM3?

by Thomas Ward

Thank you kindly, Mark, for pointing me in the right direction on multiple questions so far! I'll dig into the import command and hopefully that resolves most of the chaos if the client decides to agree with the decision to move to Mailman 3 Thomas -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Saturday, June 24, 2023 6:41 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Importing MBOX from custom listserv to MM3? On 6/24/23 3:26 PM, Thomas Ward wrote: > We are looking at moving from a home grown listserv system at a client to potentially MailMan3 for the lists platform instead. > > We have historic thread data from the homegrown systems in mbox form. Is there a way to import that into MM3 for indexing in the archiver there so we dont need to keep the (literally massive) MBOX file? That's what the django admin hyperkitty_import command is for. You can check the mbox for anomalies that might cause issues with the scripts at https://gitlab.com/mailman/hyperkitty/-/tree/master/hyperkitty/contrib. -- 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 teward(a)thomas-ward.net

2 years, 10 months

[MM3-users] Re: Spam sent to list owner causes bounce increment for list owner

by Mark Sapiro

On 12/18/23 9:59 AM, Allan Hansen wrote: > Hi all, > > Someone sent a spam message to the list owner (me) of one of my lists. Then I got booted from the list. > > The scenario in more detail: > The list server forwards the message to me, as I’m the list owner. This message is sent from <list>-bounces+hansen=rc.org(a)list.rc.org to hansen(a)rc.org. > My service provider’s spam filter rejects the spam (correctly) in a message and informs the list server. > The list server sends a message to <list>-bounces+hansen=rc.org(a)list.rc.org (the fake sender) saying that the message to hansen(a)rc.org (the recipient) could not be delivered because it was spam. > The list server also blames hansen(a)rc.org (me) for the bounce and increments my bounce score, which, to me, is unfair. > > So I wonder: > Is the Mailman host at list.rc.org at fault for not catching the spam before it reaches the list server? (One could argue that) Depends on what kind of spam filtering if any you have on incoming mail to list.rc.org. > Is my rc.org service provider at fault for sending the bounce message to the server instead of the to the original sender? Absolutely not. The envelope sender of the mail was set by Mailman to <list>-bounces+hansen=rc.org(a)list.rc.org in order to enable automated bounce processing. rc.org correctly sent the bounce to the envelope sender. > Is Mailman at fault for thinking that the bounce message was caused by a list message FROM me, instead of a bounced message TO the list owner? Arguably, yes, but not based on FROM. FROM has nothing to do with it. The message was sent TO you so if it bounces, it is a message to you that bounced, so you are the one bouncing this message. All Mailman knows is a message was sent to you and it bounced so it's your address that is bouncing. It doesn't matter whether this was a post to the list that bounced or a message to <list>-owner. A bounce is a bounce. Note that this list's bounce processing is very aggressive. If you got removed from the list after one bounce, the list must have Bounce score threshold = 1 and Bounce disable warnings = 0. You might consider adjusting these. There is an easy fix for this. Set `verp_probes: yes` in mailman.cfg. Then when your bounce score reaches threshold, instead of disabling/removing you, Mailman will send a probe message to you. It will only disable/remove you if the probe bounces which it presumably won't. Another avoidance would be to use an address for the owner which is not the address of a member. Then if the owner address bounces, nothing is done because the bouncing address isn't a list member. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: Post installation issues (recipients refused) with Exim4 in a virtual host environment

by Kyriakos Terzopoulos

Hi, It seems that what fixed it was to put in Exim4 conf the following: domainlist mm_domains = myproject.eu *Kyriakos Terzopoulos *Web developer / e-learning expert *Tel:*+30 211 213 9858 *Mobile:* +30 694 526 4512 * E-mail: *kyriakos.terzopoulos(a)gmail.com * Skype:* kyriakos.terzopoulos Find me on Facebook <http://www.facebook.com/cirrus3d> Follow me on Twitter <http://twitter.com/#%21/cirrus3d> On Thu, 12 Oct 2023 at 18:34, Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/12/23 00:49, Kyriakos Terzopoulos wrote: > > I get this in mainlog of Exim: > > > > 2023-10-12 10:48:33 H=static.16.91.201.138.clients.your-server.de > > ([127.0.0.1]) [138.201.91.16] sender verify fail for > > <shinylist-bounces+kterzopoulos=myproject.eu(a)myproject.eu>: Unrouteable > > address > > When following > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… > did you replace > ``` > domainlist mm_domains=list.example.net > > ``` > with > ``` > domainlist mm_domains=myproject.eu > ``` > > -- > 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 kyriakos.terzopoulos(a)gmail.com >

2 years, 6 months

[MM3-users] Re: Is it possible to upgrade from Debian 11 to Debian 12 with Mailman3?

by Pierre Malard

Le 20 déc. 2023 à 09:14, Mark Sapiro <mark(a)msapiro.net> a écrit : > > On December 20, 2023 7:20:17 AM GMT, Pierre Malard via Mailman-users <mailman-users(a)mailman3.org> wrote: >> Ok, don’t throw any more away! >> >> If you really don't recommend the Debian packaged solution, I just have one question: >> Why have you included it in the Debian "main" repositories for so long? > > We have no control over what's in Debian repositories. Maintenance and distribution of the Debian packages is done by Debian. > > We would love it if all the downstream distributions included up to date and bug free Mailman packages. The problem is when people encounter difficulty with a downstream package, we are often unable to help because we don't know the details of that package. Ok Mark, Sorry, I thought that the creation of the repository depended directly on you or, at least, on someone from the team. Obviously this is not really the case and I will address the person in charge: Jonas Meurer I presume? Good day > > > -- > Mark Sapiro <mark(a)msapiro.net> > Sent from my Not_an_iThing with standards compliant, open source software. -- Pierre ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

2 years, 4 months

[MM3-users] Re: Internal Server Error: /archives/

by Christian

Thank you Mark! -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, November 29, 2024 10:02 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Internal Server Error: /archives/ On 11/29/24 7:51 AM, Christian via Mailman-users wrote: > What is this error and how can I fix it please? Running Debian > 4.19.316-1 ... > Request Method: GET > Request URL: https://lists.domedoman.ie/archives/?sort=active%22%27! ... > Traceback (most recent call last): > None ... > GET: > sort = 'active"\'!' Some remote user has requested `https://lists.domedoman.ie/archives/?sort=active"'!` The `"'!` appended to the sort=active query fragment caused the error. This sort of thing happens when bots and script kiddies crawl your web site. You can find the request in your web server logs for more information about where it came from, but the bottom line is this will happen from time to time and it's not an indication that anything is broken. It would be possible to harden HyperKitty to defend against malformed URLs like this, but without a traceback it is not clear where to do it. -- 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/ XH5USTRI7JUHJT7UGWCGALENPDSSXWXE/ This message sent to csa(a)web-analysts.net

1 year, 5 months

[MM3-users] Re: Importing config and archives only partially succeeded?

by Eric Broens

The settings - Archiving, are not different from the ones that do show the messages:"Private Archives" selected, and Active archivers "hyperkitty" also selected. I was trying to find out how the hyperkitty page gets the mails from the database, and if I can start from there.Or maybe something is not completely correct in the database tables. Best Regards,Eric On Sunday, December 13, 2020, 01:27:53 AM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 12/12/20 3:56 PM, Eric Broens via Mailman-users wrote: > After everything was imported, and I noticed that the mails were not shown in the archives for half of the mailinglists, I ran "manage.py update_index" to index the mails for all mailinglists.This command is still running for hours.Since it builds the search index, I don't expect that this would make the mails available on the webpage. I agree, that won't make the mails available on the webpage. If you're using the default Whoosh search engine, "hours" is not unexpected. Elasticsearch is much faster and Xapian faster still. What do you see in Postorius - Settings -> Archiving for the lists whose messages don't show? -- 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, 4 months

[MM3-users] Re: templates

by Mark Sapiro

On 5/6/23 14:26, Christian via Mailman-users wrote: > It seems like something about my SPF or DKIM records are upsetting to gmail, > hence the bounces I'm guessing. That aside, this is what mail.log says: Could be, but If the issue is SPF or DKIM, Google is usually specific about that in the reject message. > ... > May 5 08:04:06 zarathustra postfix/smtp[25955]: AF07B1004A4: > to=<eappiah(a)dons.usfca.edu>, > relay=mxb-00277301.gslb.pphosted.com[148.163.158.109]:25, delay=76, > delays=0.01/0/61/15, dsn=2.0.0, status=sent (250 2.0.0 3qcf1p3wf4-1 Message > accepted for delivery) > ... > May 5 08:05:04 zarathustra postfix/smtp[25955]: C263A1004A4: > to=<adga(a)ucdavis.edu>, > relay=ucdavis-edu.mail.protection.outlook.com[104.47.66.10]:25, delay=2.5, > delays=0.01/0/0.15/2.3, dsn=2.6.0, status=sent (250 2.6.0 > <046f01d97f5c$27c4ada0$774e08e0$(a)degrowthcalifornia.org> > [InternalId=117626269340390, > Hostname=BN8PR08MB6290.namprd08.prod.outlook.com] 16054 bytes in 0.131, > 119.439 KB/sec Queued mail for delivery) > ... > May 5 08:07:13 zarathustra postfix/smtp[27926]: D3CCE1004A4: > to=<chris.hebdon(a)yale.edu>, > relay=yale-edu.mail.protection.outlook.com[104.47.59.138]:25, delay=0.77, > delays=0.01/0.02/0.07/0.67, dsn=2.6.0, status=sent (250 2.6.0 > <046f01d97f5c$27c4ada0$774e08e0$(a)degrowthcalifornia.org> > [InternalId=16887811415117, > Hostname=PH0PR08MB6757.namprd08.prod.outlook.com] 16093 bytes in 0.121, > 129.491 KB/sec Queued mail for delivery) The above 3 are successful deliveries. If those users did not receive the mail, it may have been delivered to a spam/bulk/junk/... folder or silently discarded, but it's not a Mailman issue. > ... > May 5 08:09:24 zarathustra postfix/smtp[28575]: E394C1005BA: > to=<vortexanthony(a)hotmail.com>, > relay=hotmail-com.olc.protection.outlook.com[104.47.17.161]:25, delay=0.58, > delays=0.01/0.02/0.41/0.14, dsn=5.7.1, status=bounced (host > hotmail-com.olc.protection.outlook.com[104.47.17.161] said: 550 5.7.1 > Unfortunately, messages from [192.46.218.224] weren't sent. Please contact > your Internet service provider since part of their network is on our block > list (S3140). You can also refer your provider to > http://mail.live.com/mail/troubleshooting.aspx#errors. > [VI1EUR05FT042.eop-eur05.prod.protection.outlook.com > 2023-05-05T15:09:24.433Z 08DB4D70FA71385D] (in reply to MAIL FROM command)) > ... > May 5 08:09:24 zarathustra postfix/lmtp[28581]: 7C9B31005EB: > to=<degrowcali-bounces+vortexanthony=hotmail.com(a)lists.ccalternatives.org>, > relay=127.0.0.1[127.0.0.1]:8024, delay=0.04, delays=0/0.01/0/0.02, > dsn=2.0.0, status=sent (250 Ok) These are a bounced mail (Hotmail/outlook is blocking your IP) and the subsequent successful delivery of the bounce DSN back to Mailman. > ... > May 5 08:11:35 zarathustra postfix/smtp[29219]: 016931005BA: > to=<alaitz.aritza(a)gmail.com>, > relay=gmail-smtp-in.l.google.com[142.251.116.26]:25, delay=0.43, > delays=0.01/0.02/0.03/0.37, dsn=5.7.1, status=bounced (host > gmail-smtp-in.l.google.com[142.251.116.26] said: 550-5.7.1 [192.46.218.224 > 12] Our system has detected that this message is 550-5.7.1 likely > unsolicited mail. To reduce the amount of spam sent to Gmail, 550-5.7.1 this > message has been blocked. Please visit 550-5.7.1 > https://support.google.com/mail/?p=UnsolicitedMessageError 550 5.7.1 for > more information. m12-20020a0568080f0c00b00389455db611si4492291oiw.127 - > gsmtp (in reply to end of DATA command)) > ... > May 5 08:11:35 zarathustra postfix/lmtp[29224]: 6ACFD1005EB: > to=<degrowcali-bounces+alaitz.aritza=gmail.com(a)lists.ccalternatives.org>, > relay=127.0.0.1[127.0.0.1]:8024, delay=0.03, delays=0/0.01/0/0.01, > dsn=2.0.0, status=sent (250 Ok) And similarly for this one, Google thinks it's spam. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

[MM3-users] Re: Template Ignored?

by Stephen Daniel

That pulls a 404 error. Thanks for the hint. I will investigate. On Thu, Feb 17, 2022 at 11:49 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/17/22 08:04, Stephen Daniel wrote: > > Mailman3 people -- > > > > I created a new list, and used postorius to create a template for " > > list:user:notice:welcome". I then used the mass subscription feature to > > add myself to the list, having checked "pre-confirmed", "pre-approved", > and > > "pre-verified". > > > > I received a welcome message that appears to be the default welcome > > message. It certainly wasn't what I put into my template. > > > > Any suggestions on how I get mailman to use my template? Things I might > be > > doing wrong? > > > What is your setting for POSTORIUS_TEMPLATE_BASE_URL? If you create a > full URL by appending > `/api/templates/list/list.example.com/list:user:notice:welcome` > <http://list.example.com/list:user:notice:welcome> to that > where `list.example.com` is the actual list_id of your list, and go to > that URL, what do you get? > > -- > 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: mailman-web Cleaning Up a Few Issues

by Mark Sapiro

On 11/5/25 11:17, dap1--- via Mailman-users wrote: > Sorry Mark: > > These hundreds of emails are distracting and I have too many irons in the fire between you and Stephen. That is not a criticism as I greatly appreciate the help from both of you. Just that I'm having difficulty keeping up with you both. ``` > sudo grep -r '/usr/share/mailman3-web/manage.py' /etc/cron* /var/spool/cron > > /etc/cron.d/mailman3-web:* * * * * www-data [ -f /usr/bin/django-admin ] && flock -n /v > ar/run/mailman3-web/cron.minutely /usr/share/mailman3-web/manage.py runjobs minutely > /etc/cron.d/mailman3-web:2,17,32,47 * * * * www-data [ -f /usr/bin/django-admin ] && flock -n /v > ar/run/mailman3-web/cron.quarter_hourly /usr/share/mailman3-web/manage.py runjobs quarter_hourly > /etc/cron.d/mailman3-web:@hourly www-data [ -f /usr/bin/django-admin ] && flock -n /v > ar/run/mailman3-web/cron.hourly /usr/share/mailman3-web/manage.py runjobs hourly > /etc/cron.d/mailman3-web:@daily www-data [ -f /usr/bin/django-admin ] && flock -n /v > ar/run/mailman3-web/cron.daily /usr/share/mailman3-web/manage.py runjobs daily > /etc/cron.d/mailman3-web:@weekly www-data [ -f /usr/bin/django-admin ] && flock -n /v > ar/run/mailman3-web/cron.weekly /usr/share/mailman3-web/manage.py runjobs weekly > /etc/cron.d/mailman3-web:@monthly www-data [ -f /usr/bin/django-admin ] && flock -n /v > ar/run/mailman3-web/cron.monthly /usr/share/mailman3-web/manage.py runjobs monthly > /etc/cron.d/mailman3-web:@yearly www-data [ -f /usr/bin/django-admin ] && flock -n /v > ar/run/mailman3-web/cron.yearly /usr/share/mailman3-web/manage.py runjobs yearly ``` This is not the crontab you reported at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… That one is probably /var/spool/cron/crontabs/mailman and wouldn't show here because it doesn't contain '/usr/share/mailman3-web/manage.py'. So the system crontab at /etc/cron.d/mailman3-web is your issue and should be removed. That will get rid of the cron failure emails. > This was a fresh install of Ubuntu server so the only packages installed so far are dump/restore, Ubuntu-desktop, MySQL, Postfix, fetchmail and mailman3. Apache2 comes preinstalled with Ubuntu but there may be others of which I am currently unaware. As far as I know the only other crontab is for root where I have the backup jobs scheduled. > > 0 3 * * 0 /usr/local/sbin/sysbackup Then the remaining question is how did that crontab get there in the system crontabs. The only way I know it could have gotten there if you didn't manually create it is via installation of Ubuntu Mailman packages. I think you probably also have a django-admin and perhaps other things in /usr/bin/ and also a /usr/share/mailman-web/ directory which you don't want or need. I suggest you do sudo apt list mailman3 mailman3-web mailman3-full mailman3-doc and see which of those unwanted packages are installed, and if any, `sudo apt remove` them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months

Search results for query "sapiro"