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

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

1 year, 11 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

[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

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

3 years, 9 months

[MM3-users] Re: How to create user accounts and mail addresses through CURL instead of Site Administration ?

by Shashikanth Komandoor

Thank you Mark for you response in time. On Tue, Aug 11, 2020 at 9:40 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/10/20 11:18 AM, Shashikanth Komandoor wrote: > > I am currently automating a few things using the CURL commands but > only > > postorius related as of now. Now I have a requirement. > > > > I need to create a lot many users and their mapping email ids through > > Site Administration almost daily. But it is becoming to do the same > through > > Graphical Interface. > > > > So, I just want to know the CURL commands that can be used to create > the > > user accounts and email ids mapped to user accounts. > > The accounts you are talking about are Django accounts. You cannot > create these via CURL to the Mailman core REST API. > > You might find > <https://www.django-rest-framework.org/tutorial/quickstart/> of interest. > > -- > 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, 4 months

[MM3-users] Re: SMTPSenderRefused - howto enable STARTTLS for local mail drop

by Stefan Bauer

No matter what i try, mailman still only connects without STARTTLS: /etc/mailman3/mailman.cfg [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver smtp_host: localhost smtp_port: 25 smtp_user: smtp_pass: smtp_verify_hostname: false smtp_verify_cert: false smtp_secure_mode: starttls systemctl restart mailman3 Nov 9 12:14:52 al02 postfix/smtpd[4183267]: connect from localhost[::1] Nov 9 12:14:52 al02 postfix/smtpd[4183276]: connect from localhost[::1] Nov 9 12:14:52 al02 postfix/smtpd[4183276]: disconnect from localhost[::1] ehlo=1 mail=0/1 rset=0/1 quit=1 commands=2/4 Did i miss something? Am Mo., 8. Nov. 2021 um 18:06 Uhr schrieb Stefan Bauer <cubewerk(a)gmail.com>: > awesome! Thank you a lot! > > Am Mo., 8. Nov. 2021 um 17:37 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>: > >> On 11/8/21 1:03 AM, Stefan Bauer wrote: >> > >> > how can we configure mailman3, to use STARTTLS when dropping mails to >> local >> > postfix for final delivery? >> >> >> Set `smtp_secure_mode: starttls` in the `mta` section of mailman.cfg. >> See >> >> https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.… >> >> -- >> 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, 1 month

[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

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

1 month, 1 week

[MM3-users] Re: Template Ignored?

by Stephen Daniel

Thanks for clarifying. All is working now!!! On Thu, Feb 17, 2022 at 1:27 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/17/22 10:10, Stephen Daniel wrote: > > Fixed the POSTORIUS_TEMPLATE_BASE_URL. Doesn't fix the issue. > > I've been playing with wget, and no matter what I put, I keep getting a > 404 > > error. > > > > So: this works: > > > > wget -O wget.out --user restadmin --password restpass ' > > http://localhost:8001/3.1/lists/list.example.com' > > > > but this does not (404 error): > > > > wget -O wget.out --user restadmin --password restpass ' > > > http://localhost:8001/3.1/templates/list/list.example.com/list:user:notice:… > > > You are using Mailman core's REST API which is wrong. You need to get > the template from Postorius. Maybe something like > > > > http://localhost/postorius/api/templates/list/list.example.com/list:user:no… > > Where http://localhost/postorius/ is the URL you use to access > Postorius, maybe mailman3 instead of postorius. > > Once you figure that out, POSTORIUS_TEMPLATE_BASE_URL is just the scheme > and domain part of that. > > -- > 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/ >

3 years, 9 months

Search results for query "sapiro"