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

[MM3-users] Re: How to store additional information about lists?

by Andreas Barth

* Stephen J. Turnbull (turnbull.stephen.fw(a)u.tsukuba.ac.jp) [210530 09:19]: > Mark Sapiro writes: > > On 5/29/21 7:31 PM, Stephen J. Turnbull wrote: > > > > Membership adapter is a Mailman 2 feature that allowed use of an > > > external membership database (such as a corporate LDAP system). I > > > thought it was ported to Mailman 3 but maybe not. > > > Actually, it's not quite that simple. Mailman 2.1 defines a > > MemberAdaptor class, [...]. > > The Mailman 3 analog of this is the IMember interface defined in > > mailman/interfaces/member.py and implemented in mailman/model/member.py > > OK, but for Andi it is "simple" in the sense that he doesn't have an > existing MemberAdapter, so the plan is "Implement the IMember interface". Not sure if this is the right approach, or if it wouldn't be more appropriate to "just" replace the dependency on allauth in postorius, and do all the magic in the frontend only (because that's where people actually subscribe). Whoever subscribes by mail needs some admin action, or some cron job, or is unsupported - for my case the main interface is the web interface, not the email commands. That of course would imply that e.g. cleaning up mailing lists happens by a cron job with rest, but why not? Andi

4 years, 4 months

[MM3-users] Re: multiple sites on a mailman3 server question

by David Newman

On 12/28/21 6:15 PM, William Oliver wrote: > So, I have successfully installed mailman3 and it's working great. > However, the way it works now, if someone goes to the domain website, > he or she will get the mailman page. I'd prefer that it work something > like: > My > www.example.com goes to a home page > lists.example.com goes to the mailman3 page > mail.example.com goes to a roundcube page > > > I'm using nginx I'd asked about this a few weeks ago for a MM3 host running Ngnix with a few virtual domains, one of which runs Roundcubemail as its default. Mark Sapiro suggested the following, and it seems to be working OK. You'll need these lines in the Nginx config file for each virtual host you define. # begin mailman3 stuff location /static/ { alias /opt/mailman/web/static/; } location /mailman3/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /archives/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /accounts/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /admin/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /mailman/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /user-profile/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } # end mailman3 stuff dn

3 years, 9 months

[MM3-users] Re: Mailman3 doesn't send Mails to users (Debian12 with Plesk)

by Marcus Bautze

Hi, Am 07.06.2024 um 06:22 schrieb Mark Sapiro: > At > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > you say "Thank you, archiver is now starting. Now there's another > problem:". Does this mean messages are being archived in HyperKitty or > are they accumulating in (I think the Debian path is) > /var/lib/mailman/archives/hyperkitty/spool/? They are in /var/lib/mailman3/archives/hyperkitty/spool/, i doesn't find them in the HyperKitty-archives. > At > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > you say "The Keys are in mailman-hyperkitty.cfg and mailman-web.py > and this are the same Keys." To be clear, in mailman-web.py the key is > quoted and in mailman-hyperkitty.cfg it is not. E.g., in > mailman-hyperkitty.cfg > > api_key: Some_key here is the key unquoted: api_key: *** > > and in mailman-web.py > > MAILMAN_ARCHIVER_KEY = 'Some_key' here's the Key quoted: MAILMAN_ARCHIVER_KEY = '***' > > What are your versions for mailman-hyperkitty and HyperKitty? > HyperKitty >= 1.3.5 is incompatible with mailman-hyperkitty < 1.2.0 > and if I recall corectly, at least one Debian package was shipped with > this incompatibility > i found: python3-django-hyperkitty 1.3.7-1 python3-mailman-hyperkitty 1.2.1-1 mailman3-full 3.3.8-2~deb12u1 (no other hyperkitty-related packages) -- Marcus Bautze marcus(a)mbautze.de

1 year, 4 months

[MM3-users] Re: Cron Error: <mailman@gw> /opt/mailman/mm/bin/django-admin runjobs monthly

by Odhiambo Washington

On Wed, Mar 1, 2023 at 6:13 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/28/23 21:33, Odhiambo Washington wrote: > > > > Now that I have the error message - mail was generated at 0600hrs - what > > should I grep for in mailmanweb.log to ascertain when the cron job > started? > > > You could look in /etc/crontab to see what time the cron.monthly jobs > are run or you could look in syslog for 'cron\.monthly'. > In FreeBSD we have the /var/log/cron. Mar 1 00:00:00 gw /usr/sbin/cron[66206]: (mailman) CMD (/opt/mailman/mm/bin/django-admin runjobs monthly) So the job was started at 00:00, and the email was generated at 06:00: 2023-03-01 06:00:52 1pXCi4-000N2h-2D <= mailman(a)gw.kictanet.or.ke U=mailman P=local S=1466 T="Cron <mailman@gw> /opt/mailman/mm/bin/django-admin runjobs monthly" from <mailman(a)gw.kictanet.or.ke> for mailman That is 6hrs and the lock was still there. Given that my search engine is whoosh and my archive is heading to 3GB, I should probably try setting the value to 10hrs for a start? PS: Is there any documentation (for laymen) on how to set up an alternative search engine for MM3? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 7 months

[MM3-users] Re: How to strip DKIM headers on a domain level or a list level

by Joel Lord

On 11/23/2020 10:48 PM, Mark Sapiro wrote: > On 11/23/20 7:22 PM, Mark Dadgar wrote: >> >> I also believe that it’s common for unsophisticated users to just start marking list emails as spam stop seeing them instead of figuring out how to unsubscribe. Which really sucks for everyone else. > > > Several servers I'm involved with managing are subscribed to Yahoo's > feedback loop (go to https://help.yahoo.com/kb/postmaster and select > "Complaint Feedback Loop"). Reporting list mail as spam is one way to > get quickly removed from a list. However, this is a bit complicated > because the "report spam" button in Yahoo's web mail UI is right next to > the "delete" button, so some reports are accidents. > I've done the same thing, but Yahoo is pretty good at sanitizing their report to make it difficult to impossible to tell who actually needs to get ejected. I added "Sent to %(user_name)s at %(user_address)s" to the footer and while they'd generally get the user_address wiped out, the user_name would generally survive. And because Yahoo's UI is flawed as Mark pointed out, with the delete and spam buttons adjacent, I'd usually give people a couple chances before I'd airlock them. -- Joel Lord

4 years, 10 months

[MM3-users] Re: Problems with shunted Mails

by Stephan Krinetzki

Mark Sapiro wrote: > > One of the list's regular members has no associated address record. I > don't know how this can happen. That doesn't sound good. When something is unknown, that's never good. > You could find the member with mailman shell, e.g. > mailman shell -l list.example.com > Welcome to the GNU Mailman shell > Use commit() to commit changes. > Use abort() to discard changes since the last commit. > Exit with ctrl+D does an implicit commit() but exit() does not. > The variable 'm' is the list.example.com mailing list > >>> for mbr in m.regular_members.members: > ... if mbr.address is None: > ... mbr.subscriber > ... mbr.user > ... mbr.user.addresses > ... mbr.user.preferred_address > ... Yupp, this returns two entries (or better: User Objects?) > You might be able to fix this with something like > >>> for mbr in m.regular_members.members: > ... if mbr.address is None: > ... mbr.address = mbr.user.preferred_address or > member.user.addresses[0] > ... > >>> commit() This fix didn't worked. It returned a "Index out of bounds" exception. Instead, we have deleted the corresponding entry in the database. It should be possible to find it this way: select * from member where list_id = 'list.lists.example.com' AND address_id IS NULL; After deleting the row, the list works again.

3 years, 6 months

[MM3-users] Re: REST API authorization failed

by Axel Rau

Hi Mark, thanks for your answer. > Am 08.01.2022 um 23:07 schrieb Mark Sapiro <mark(a)msapiro.net>: > > Is the password unquoted in mailman.cfg as > > admin_pass: ??? yes. > > and quoted in settings.py as > > MAILMAN_REST_API_PASS = '???‘ yes. > > Does the `mailman info` command report what you think for REST credentials? yes. > > To you get an appropriate JSON response from > > > wget -O- --user restadmin --password ??? http://localhost:8001/3.1/lists <http://localhost:8001/3.1/lists> I used curl: - - - (mailman_33) [root@lists5 /usr/local/mailman3]# curl -v -u restadmin:??? http://localhost:8001/3.1/lists * Trying 127.0.0.1:8001... * Connected to localhost (91.216.35.42) port 8001 (#0) * Server auth using Basic with user 'restadmin' > GET /3.1/lists HTTP/1.1 > Host: localhost:8001 > Authorization: Basic cmVzdGFkbWluOnc2cmtuQXpJZmVRc1o4WnlkMFpBcmNjcm55OA== > User-Agent: curl/7.80.0 > Accept: */* > * Mark bundle as not supporting multiuse < HTTP/1.1 401 Unauthorized < Server: gunicorn < Date: Sun, 09 Jan 2022 13:51:43 GMT < Connection: close * Authentication problem. Ignoring this. < www-authenticate: Basic realm="mailman3-rest",charset="utf-8" < content-type: application/json < vary: Accept < content-length: 77 < * Closing connection 0 {"title": "401 Unauthorized", "description": "REST API authorization failed“} - - - I see "Server: gunicorn“, does this mean, I must install gunicorn? Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

3 years, 9 months

[MM3-users] Re: Installing mailman 3

by Abhilash Raj

On Tue, Aug 1, 2017, at 02:29 PM, Rafael Mora wrote: > 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 = '******' This looks good to me. > > What should I use in user and password?? Does Django use postfix to send the email??? I think you don't need a password and username as long as your postfix is configured to relay local emails without authentication (which it is by default if you installed from distro packages and if you haven't changed the settings). > > 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 -- thanks, Abhilash Raj

8 years, 2 months

[MM3-users] Re: mailman2 import not working

by Abhijith PA

On 29/07/20 10:38 pm, Mark Sapiro wrote: > On 7/29/20 9:33 AM, Abhijith PA via Mailman-users wrote: >> >> ------------------------------------------- >> mailman create -o <foo(a)example.com> foo-bar(a)lists.example.com >> mailman import 21 foo-bar(a)lists.example.com path/to/config.pck >> ------------------------------------------- > > > You don't need to specify an owner for `mailman create`. The owners will > be imported. Ok, noted. >> After everything done tried a test mail, but didn't reach any of the >> inbox though mail is archived. mailman.log says message is accepted >> >> ACCEPT: <FEE2E515-C054-41E6-9853-744D3312A137(a)xxxxxx.org> >> Nothing after this. > > It is surprising that no exception/traceback/SHUNTING message(s) are > logged. That would seem to say that Mailman's `out` runner is not running. When I restarted mailman. I got, Jul 29 16:58:21 2020 (14473) SHUNTING: 1596041901.2833998+efbeb949a9c248bae23ea6bcc644450f497a4d8d > I think Mailman's var/ directory in the Debian package is > /var/lib/mailman3/, so what does `ls -aR /var/lib/mailman3/queue` show? > Is there a .pck file either in shunt/ or in out/? There is many .pck files in /var/lib/mailman3/queue/shunt and /var/lib/mailman3/queue/out. And a lot of .psv files in /var/lib/mailman3/queue/bad > what does `ps -fwwu list` show? There should be a lot of runner > processes. Is there one with argument --runner=out:0:1? > Yes. I can confirm. --a

5 years, 2 months

[MM3-users] Re: MM3 gateway errors and frequent reboot needs

by Brian Carpenter

On 4/19/20 4:38 PM, Mark Sapiro wrote: > On 4/19/20 1:21 PM, hansen(a)rc.org wrote: >> We have had to reboot the list server almost every week and wonder if there is something leaking and eating up resources. I does not appear to be memory, though. The server is slow to respond (could be because it's overseas) and then after some time we get intermittent gateway errors and finally we cannot access the lists online because of the gateway errors. It appears to me that the issue is with Postorius, but I could be wrong. Do files get closed after opening? Are we alone having such issues? > > We are not seeing an issue like this on either lists.mailman3.org (this > list) or mail.python.org (at the moment 118 @python.org Mailman 3 lists) > > What are you seeing in web server logs? > I concur with Mark. I am not seeing any such behavior on none of my MM3 servers. One server we were having similar problems and that was due to a bunch of bad behaving indexing bots (semrush, ahrefbot) hammering the server. So definitely check your web server log. -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

5 years, 6 months

Search results for query "sapiro"