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

[MM3-users] Re: hyperkitty url not found

by Eggert Ehmke

So I have to use the external url via https? I can access the address https://lists.[1]<tld>_/mailman3/archives/api/_ so I set: (<tld> is my existing domain) base_url: https://lists.<tld>/mailman3/archives Now I get this in the mailman.log: Mar 14 19:40:21 2022 (166928) ACCEPT: <12973151.uLZWGnKmhe@wookie> Mar 14 19:40:21 2022 (166932) HyperKitty failure on https://lists.<tld>/mailman3/archives/ api/mailman/urls: <html><title>Forbidden</title><body> <h1>Access is forbidden</h1><p>Please check the IP addresses assigned to MAILMAN_ARCHIVER_FROM in the settings file. </p></body></html> (403) In my settings I have my local IP and 127.0.0.1 and ::1. What should I set there? Am Montag, 14. März 2022, 18:48:51 CET schrieb Mark Sapiro: > On 3/9/22 07:13, Eggert Ehmke wrote: > > I installed mailman3 in a virtualenv following this guide: > > > > https://docs.mailman3.org/en/latest/install/virtualenv.html[1] > > The mailinglists work very good. However, I did not manage to set up > > hyperkitty archiving. Archiving is enabled in mailman.cfg. I can call the > > Archive site from my configuration page, but it is empty. > > > > In my /opt/mailman/mm/var/logs/mailman.log > > file I find error messages like: > > > > HyperKitty failure on > > http://localhost/mailman/hyperkitty/api/mailman/archive: The requested > > URL was not found on this server. > > Your setting in mailman-hyperkitty.cfg for base_url is > > base_url: http://localhost/mailman/hyperkitty/ > > It needs to be the base URL for accessing hyperkitty, possibly > > base_url: http://localhost/mailman3/hyperkitty/ > > or whatever you use to access hyperkitty from a web browser. > > Whatever it is, `<base_url>/api` should return a page of API documentation. -------- [1] https://lists.ftv-spandau.de/mailman3/archives/api/

3 years, 5 months

[MM3-users] Re: Sending a message to a subscription applicant when a subscription request is made

by Allan Hansen

Mark, I tried doing this. I unsubscribed myself from a list, set the policy as you suggest and re-applied. I got no confirmation messages but as moderator I got the moderate message. I then tried a bogus email and saw that a message was sent to that and no moderator message to me. Would the server skip the verification message because I'm a moderator/admin? Yours, Allan On 3/28/23, 08:57, "Mark Sapiro" <mark(a)msapiro.net <mailto:mark@msapiro.net>> wrote: On 3/28/23 01:49, Allan Hansen wrote: > > There is a template, 'list:user:action:subscribe' that almost does this, but it gets sent only if the email address of the applicant is unverified. A good number of our applicants are already on our lists, so they would not get this template if we set the Subscription Policy to 'Confirm, then moderate'. > > Our Subscription Policy is currently: 'Moderate' for all lists. If you set the subscription policy to 'Confirm, then moderate' the user will receive a confirmation request based on the list:user:action:subscribe template whether or not the address is verified. -- Mark Sapiro <mark(a)msapiro.net <mailto:mark@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 <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org <mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org <mailto:mailman-users@mailman3.org>/message/ORDAIBK4JUICZADYPEPWDVV2WP5EXWEB/ This message sent to hansen(a)rc.org <mailto:hansen@rc.org>

2 years, 4 months

[MM3-users] Re: Migrating Mailman 3 lists

by Mark Dadgar

On May 24, 2020, at 7:24 AM, Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: >> Mark Sapiro wrote: >>> On 5/19/20 7:25 PM, Mark Dadgar wrote: > >>>> For reference my pgloader script looks like: >>>> >>>> load database >>>> from sqlite:///var/lib/dbconfig-common/sqlite3/mailman3-web/mailman3web.db >>>> into postgresql://mailman3:XXREDACTEDXX@localhost/mailman >>>> >>>> with include drop, create tables, create indexes, reset sequences, no truncate > >> Have you tried this without indexes and then run the migrate >> script? It may re-create them as part of the schema upgrade >> check. > > That was my immediate guess. I'm not an SQL expert, but I believe > that sequences and indexes are different entities, they're both > optimizations that you don't need (ie, ignoring performance), and > implementations differ on how they're implemented. Eg, if sqlite > implements them as tables, while PostgreSQL has a special data > structure, you could run into this kind of behavior. I'm pretty sure > that these will be recreated appropriate to the new database when the > schema validator is done. > > But don't trust me, and *do* keep a backup. ;-) 😁 I did try it without indexes and it started showing the same warnings. I will give this another try and let it run to completion. I was hesitant to do that because the core database is 7.5 GB and the web database is 35 GB so there are only so many copies I can keep hanging around on the cloud volume. Since the data is mostly text, I am hoping that postgres will compress the bejeesus out of it. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 2 months

[MM3-users] Re: Gmail emails bouncing - anybody seen this problem?

by worik

On 12/02/19 11:25 AM, worik wrote: > Friends > > On a fresh install (docker) on a fresh VPS I am getting all Mailman > messages to Gmail addresses bouncing telling me I am sending too many > messages. Has anybody else have this problem? > > I am getting the following error in mail.log: "Our system has detected > an unusual rate of 550-5.7.1 unsolicited mail originating from your IP > address. To protect our 550-5.7.1 users from spam, mail sent from your > IP address has been blocked. 550-5.7.1 Please visit 550-5.7.1 > https://support.google.com/mail/?p=UnsolicitedIPError to review our 550 > 5.7.1 Bulk Email Senders Guidelines. l26si395949wme.8 - gsmtp" > > I have been to the URL mentioned and exhausted my options there. > > Worik > Well. Golly. I complained to Google, and heard nothing back. But with no changes on my end they have stopped bouncing my emails. Now they are just marked as spam. I can live with that. Very frustrated with google's levels of service. What a pain! Thank you Brian Carpenter, who may well have been right about "warming up the IP". What ever that might mean. I have not read that RFC, but I have a lot to learn. Thank you Mark Sapiro, for your patience. Thank you every body for the obviously hard work creating this system. I have a long way to go until I know how to use it properly, but I am no longer stopped at the google cliff. Worik -- If not me then who? If not now then when? If not here then where? So, here I stand, I can do no other root(a)worik.org 021-1680650, (03) 4821804 Aotearoa (New Zealand) I have a lot of onion pie, that explains the aroma

6 years, 6 months

[MM3-users] Re: Error -- postorius Un-handled exception

by Odhiambo Washington

On Thu, Apr 11, 2024 at 11:00 PM Ron / BCLUG <admin(a)bclug.ca> wrote: > Mark Sapiro wrote on 2024-04-10 14:09: > > > I suspect you are not starting the services with your venv active. > > What's in your mailman3.service and mailman3-web.service files? > > Thanks for the pointer! > > I had my mailman3-web.service starting `mailman-web` instead of `uwsgi` > somehow. > > > I changed that to match the docs, did the `systemctl daemon-reload`, > etc. but still had similar problems. > > > I went through all my config files carefully, I wiped the static folder > completely and rebuilt it, and I finally have the last piece of the > puzzle in place and my web interface is working! > > I'm not sure which change actually fixed the issue though. > > > (When looking at "Available lists" my header has "example.com" in the > top-left corner?!?) > See also this: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… But read it as "example.com", not example.org :-) I think I need to backup what I have and do a clean re-install so I have > a better grasp of what's going on with all these components. > Way to go! Before I got MM3 working on the sites that I manage, it took me lots of installs and wipes until I could figure out what's going on. I was literally being hand-held by the good developers. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 4 months

[MM3-users] Re: config incoming email in my domain cpanel

by Rafael Mora

El jue., 3 ago. 2017 a las 16:25, tlhackque via Mailman-users (< mailman-users(a)mailman3.org>) escribió: > On 03-Aug-17 17:14, Rafael Mora wrote: > > > > > > El jue., 3 ago. 2017 a las 16:07, tlhackque via Mailman-users > > (<mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org>>) > > escribió: > > > > You've said you're working with labbrands.com <http://labbrands.com > >. > > > > labbrands.com <http://labbrands.com> has address > 192.185.51.89 > > mail.labbrands.com <http://mail.labbrands.com> has address > > 192.185.51.89 > > www.labbrands.com <http://www.labbrands.com> is an alias for > > labbrands.com <http://labbrands.com>. > > > > telnet proves that Exim is running on that IP address. Either you're > > running it, or hostgator is redirecting the SMTP ports. > > > > You added: > > lists.labbrands.com <http://lists.labbrands.com> has address > > 190.145.27.66 > > > > Presumably that's a different machine. > > > > So that now needs an MX record, and a firewall routing. > > > > > > I added the MX record on our hostgator hosting like this: > > image.png > > > > Is it correct??? > > > No. And sending images to the mailing list doesn't get you help. > > You set up lists.labbrands.com as a secondary server, not an independent > mail domain. This will cause you serious grief. > Ok I will remove that MX record on my hostgator hosting. Thank for your help. > > You need to get some help from a more suitable list. Setting this up is > not mailman-specific, and getting it right is more than a quick note. > > Try the Postfix documentation & mailing lists. > > > > > > > And the SPF > > records ... and spam and virus filters, and all the other stuff > > you need > > to setup an independent, public-facing smtp server. > > > > But at least you won't have to relay. > > > > Good luck. > > > > On 03-Aug-17 16:55, Rafael Mora wrote: > > > El jue., 3 ago. 2017 a las 15:49, tlhackque via Mailman-users (< > > > mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org>>) > > escribió: > > > > > >> I think you're confused. > > >> > > >> You already have mail.labbrands.com <http://mail.labbrands.com> > > set up as the MX record for > > >> labbrands.com <http://labbrands.com>. And it has an A record > > with the same address as your > > >> webserver. > > >> > > > I'm working with the hostgator mailserver, we are not running a > > local > > > mailserver. > > > > > > As suggested I added an A record like this: > > > [image: image.png] > > > > > > Is it correct? is it redirecting to my Ip so I can redirect it to > my > > > postfix/mm3 server? > > > > > > > > >> So if you're getting e-mail on that domain, there's another e-mail > > >> server running on that IP address. You can't have 2 servers > > on port > > >> 25. In that case, as has been noted before, you'll need to setup > a > > >> relay in that server, not a firewall redirect. Depending on > > your MTA, > > >> you would need to relay to your internal server. And make sure > > your > > >> firewall setup allows your MTA to do this. > > >> > > >> We can see it's EXIM: > > >> > > >> telnet mail.labbrands.com <http://mail.labbrands.com> 25 > > >> Trying 192.185.51.89... > > >> Connected to mail.labbrands.com <http://mail.labbrands.com> > > (192.185.51.89). > > >> Escape character is '^]'. > > >> help > > >> 220-gator4137.hostgator.com > > <http://220-gator4137.hostgator.com> ESMTP Exim 4.87 #1 Thu, 03 > > Aug 2017 15:47:48 > > >> -0500 > > >> 220-We do not authorize the use of this system to transport > > unsolicited, > > >> 220 and/or bulk e-mail. > > >> 214-Commands supported: > > >> 214 AUTH STARTTLS HELO EHLO MAIL RCPT DATA NOOP QUIT RSET HELP > > >> quit > > >> 221 gator4137.hostgator.com <http://gator4137.hostgator.com> > > closing connection > > >> Connection closed by foreign host. > > >> > > >> Or, consolidate all your e-mail to one server - which is a lot > > easier to > > >> manage unless you have a really big operation. Postfix is > > probably the > > >> right choice, but requires more setup. > > >> > > >> Although Mailman3 configuration is not well documented (as you've > > >> discovered), you may want to get help from someone with more > > general > > >> network and mail experience. You're now into territory that is, > as > > >> Simon indicated, not Mailman-specific. > > >> > > >> On 03-Aug-17 16:28, Rafael Mora wrote: > > >>> El jue., 3 ago. 2017 a las 15:26, Mark Sapiro > > (<mark(a)msapiro.net <mailto:mark@msapiro.net>>) > > >> escribió: > > >>>> On 08/03/2017 01:22 PM, Rafael Mora wrote: > > >>>>> El jue., 3 ago. 2017 a las 15:18, Mark Sapiro > > (<mark(a)msapiro.net <mailto:mark@msapiro.net>>) > > >>>> escribió: > > >>>>>> You need to forward port 25 for SMTP mail delivery and if > > you want the > > >>>>>> web UI (Postorius and HyperKitty) accessible from the > > outside, port 80 > > >>>>>> for http and/or port 443 for https > > >>>>>> < > > >>>>>> > > >> > > > https://www.iana.org/assignments/service-names-port-numbers/service-names-p… > > >>>>>>> . > > >>>>> I mean for incoming mail redirected from my hostgator > > hosting, because > > >>>> when > > >>>>> I suscribe an email address MM3 sends a confirmation email, > > so I have > > >> to > > >>>>> reply to be suscribed to the list. > > >>>> As I said, for mail delivery you need to forward port 25 to > > the Mailman > > >>>> server. > > >>>> > > >>> Ok so I'll redirect in my zentyal firewall the port 25 to my > local > > >> centos7 > > >>> with postfix and MM3 with IP 192.168.1.42. Thanks Mark. > > >>> > > >>> > > >>>> -- > > >>>> Mark Sapiro <mark(a)msapiro.net <mailto:mark@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 <mailto:mailman-users@mailman3.org> > > >>>> > > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > >>>> > > >> -- > > >> This communication may not represent my employer's views, > > >> if any, on the matters discussed. > > >> > > >> _______________________________________________ > > >> Mailman-users mailing list > > >> mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> > > >> > > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > >> > > > > -- > > This communication may not represent my employer's views, > > if any, on the matters discussed. > > > > _______________________________________________ > > Mailman-users mailing list > > mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> > > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > > -- > > > > Atentamente / Best Regards > > > > Ing. Rafael Mora > > > > -- > This communication may not represent my employer's views, > if any, on the matters discussed. > > _______________________________________________ > 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

[MM3-users] Re: "Approved:" header from mailman2 times

by Abhilash Raj

On Mon, Apr 9, 2018, at 8:59 PM, Mark Sapiro wrote: > On 04/09/2018 03:59 PM, Abhilash Raj wrote: > > On Mon, Apr 9, 2018, at 3:00 PM, Dmitry Makovey wrote: > >> Hi, > >> > >> is there any equivalent to "Approved" header that was present in MM2 in > >> MM3 land? Google is not very helpful in that. > > > > It does exist in Mailman 3 as a carry-over from Mailman 2, but AFAIK it is broken. > > > I don't think it is broken, but it requires setting the > moderator_password attribute for the list which can be set visa REST but > I think not by mailmanclient. > Thanks Mark for clarification. > > > Also, I have been thinking of not having this as a feature in Mailman 3, mostly because of the issue of having shared passwords. No one should be sending out passwords anyway through plain emails anyway. > > > > > Agreed. This is a shared password. and would be sent in plain text as a > header or body line. > > It would be nice though to have some feature to enable, for example, > spoof proof posting to a one-way (announce only) list. > > One thought on how to do this would be to have a list attribute that > says posts from 'authenticated' owners and moderators can be auto > approved and authentication could be by PGP signing the post. This would > require Mailman to have the ability to verify a PGP signature from an > owner or moderator which is not currently the case. +1 on using PGP signatures for doing this and that is exactly what I was thinking :) -- Abhilash Raj maxking(a)asynchronous.in

7 years, 4 months

[MM3-users] Re: spanish localization

by Guillermo Hernandez (Oldno7)

On 13/2/21 11:55, Victoriano Giralt wrote: > On Fri, 2021-02-12 at 12:24 -0800, Mark Sapiro wrote: >> If the manage.py in the directory in which you ran this is the >> correct one for your Mailman Django project, I don't know why it >> didn't work. > Me neither :-( That's why I asked, and probably Guillermo, as well. > >> Is your Mailman installed in a virtualenv? If so, was the virtualenv >> activated? > No virtualenv. Mine is deployed using system python on a CentOS 7 > system, toghether with another in house developed low requirements > Django project, both served by uWSGI vassals. And mine, as well, in a FreeBSD 12.2-RELEASE, no virtualenv and uWSGI approach with apache24 server. > > And then, all of a sudden, while I was writting this, it dawned on me! > > Postorius, Hyperkitty and django-mailman are installed with pip, so, > the end up in the site-packages directory (usually > /usr/local/lib/python3.x/site-packages), That is my case, too. > but, normally, django projects > are deployed somewhere in the web server hierarchy (/var/ww/django in > my case, due to old personal tastes), and applications properly defined > in the settings.py for the project. > > So, the message files are out of reach for manage.py. > > Changing to /usr/local/lib/python3.x/site-packages/X > (with X being postorius, hyperkitty and django_mailman3) and using > django-admin compilemessages all works! And for me as well. Thanks a lot Victoriano, I owe you a beer > > Thanks for pushing my thoughts in the right direction! > > > _______________________________________________ > 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, 6 months

[MM3-users] Re: Automatic migration from Mailman 2.1 (Debian buster) to Mailman 3 (Debian bookworm)

by Marc SCHAEFER

Hello, On Sat, May 25, 2024 at 11:38:40AM -0400, Mark Sapiro wrote: > The host name displayed in the web UI is based on the SITE_ID setting in > Django's settings. This is a system configuration not associated with any > lists. it references an entry in the django_sites table in the database. Thank you, will look into this. > As far as the comment/display name in From: is concerned, what specific > emails are you talking about? This. Sorry, I mixed From: with Subject: and the content: Date: Sat, 25 May 2024 13:37:29 -0000 From: postorius(a)lists2.alphanet.ch To: schaefer@XXX Subject: [example.com] Please Confirm Your E-mail Address Hello from example.com! You're receiving this e-mail because user Schaefer-XXX has given your e-mail +address to register an account on example.com. To confirm this is correct, go to [ ... ] Thank you for using example.com! example.com I guess it's the same SITE_ID setting in Django's DB: $ grep SITE_ID /usr/share/mailman3-web/settings.py SITE_ID = 1 However, I guess it's the default creation, by the Debian package, of the SQLite local database which presumably was done with example.com. I will anyway switch to a remote PostgreSQL database, and thus create a new one with the correct names. That should fix it. > for ADMINS in your Django settings. ADMINS = ( ('Mailman Suite Admin', 'schaefer(a)alphanet.ch'), ) That looks correct. > The `mailman import21` command will properly import the Mailman 2.1 > from_is_list and Sender filters -> dmarc_* DMARC mitigation settings. Thank you. Aka mailman-wrapper import21 on Debian so to switch to the correct user. > If you have some customization in this area, that probably won't be handled. Obviously.

1 year, 2 months

[MM3-users] Re: Caching problem with templates

by Mark

On Thu, 2025-06-26 at 18:36 -0700, Mark Sapiro wrote: > > You can delete the cached entry from the database via `mailman shell > as in > >>> cm = getUtility(ICacheManager) > >>> uri = 'the_uri_from_the_template_table' > >>> cm.get(uri, expunge=True) > >>> commit() > ``` > > You can also delete the entry from the file_cache table, but if you > do > that, the actual file containing the cached data will remain. To > remove > it, > > Rather than doing any of the above, if you want to manipulate the > database, just set the expires_on column in the file_cache table > entry > to a date in the past. > Hi Mark, Thank you for this information. I've given the options a good workout over the last couple of days and found that: 1. Deleting the cache via the mailman shell does the job, but is beyond me to script. There are numerous lists and list owners updating their templates. 2. Changing the expires_on date (to a date in the past) in the file_cache table didn't prevent the cached entry from being used; 3. What did work was removing the records in the file_cache table PLUS removing the corresponding files in var/cache/*/*/* -- for example: /opt/mailman/mm/var/cache/3a/2f/* This I was able to script in bash and cron to run every minute. A hack I know, but it's working for now. I've attached the script in case it's of use to anyone else. (mailman_clear_template_cache.txt) Note: change <USER> in the script to what suits. Does Mailman really need to cache the templates? It seems to be an unnecessary complication. Anyways it happy days again. Thank you again, very much. Your guidance was appreciated immensely as always. Best, Mark

1 month, 3 weeks

Search results for query "sapiro"