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

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

by Simon HANNA

On August 3, 2017 8:50:41 PM GMT+02:00, Rafael Mora <rafael.mora.guti(a)gmail.com> wrote: >El jue., 3 ago. 2017 a las 13:21, Mark Sapiro (<mark(a)msapiro.net>) >escribió: > >> On 08/03/2017 10:42 AM, Rafael Mora wrote: >> > >> > I've found the MX records on my cpanel but how do I redirect the >emails >> > going to my list to my private server? >> >> >> You have to configure the MTA that is the MX for the domain to relay >the >> mail to the Mailman server. >> > >Our domain is: LABBRANDS.COM We have that domain config in a Hosgator >hosting. The emails sent to labbrands.com go to our hosting, so how do >I >tell cpanel in hostgator hosting that the mails sent to the list ( >mailing(a)labbrands.com) are redirect to the MTA (postfix) in my private >server (we have static public IP address) ?? > You can't redirect one email address using DNS! If you don't want to host an entire domain on your own server, I suggest using a subdomain (lists.example.con) instead. You could probably also redirect one email in cpanel to the subdomain, but I'm not sure how mailman and clients like emails with different domains... In theory postfix can send emails using any domain. You just have to make sure spf, dkim and PTR records are properly set. Otherwise you'll most likely get issues with rejected mail... -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

8 years, 5 months

[MM3-users] Re: What implications do GDPR have on Mailman, and how to requiring members to accept registration

by Henrik Rasmussen

Mark Sapiro wrote: > I'm confused. Confirm sends a confirmation request to the subscribed > address which must be acted upon by the user before she is added to the > list. Moderate just means approval by an owner/moderator Oh sorry, you're right, I mixed up those two. > which, it seems > to me is more susceptible to a 3rd party subscribe succeeding - i.e., > subscription requires membership in some organization. A subscribes B > who is a member of the organization but doesn't want to be on the list. > The moderator verifies that B is an organization member and approves the > subscription. What I meant was, that the list admin may be able to set the list to Open or Moderate, making it possible to subscribe others, and I was told by our GDPR folks that we have to make the subscribers re-confirm, so I was just trying to figure out a way to do it. I don't know very much about GDPR yet. > Granted that this can be abused, but not allowing admins to directly add > members will probably create more problems than it solves. I agree, I wouldn't remove it either, but I just have to be concerned about the possibility that someone may have been subscribed against their will. Is there a way to resend a confirmation request to either those who haven't been requested to confirm or alternately to all subscribers? Henrik Rasmussen

7 years, 8 months

[MM3-users] Re: hyperkitty web site

by Gelpi Andrea

Il 28/04/20 19:10, Mark Sapiro ha scritto: > On 4/28/20 9:40 AM, Gelpi Andrea wrote: >> >> If in django administration I rename that site it works. >> >> But having more than one domain this is not a solution. >> >> what i need is to separate different domains >> >> https:/website1/mailman3/hyperkitty shows some lists >> https:/website2/mailman3/hyperkitty shows other lists > > > There are issues with FILTER_VHOST. See > <https://gitlab.com/mailman/postorius/-/issues/394> for the Postorius > issue. This will be fixed for Postorius in the next release. > > For HyperKitty, the issue is > <https://gitlab.com/mailman/hyperkitty/-/issues/254>. This is not yet fixed. > > Currently, if FILTER_VHOST is True, HyperKitty only shows lists in the > index for which the list's domain matches the domain in the accessing > url with a leading 'www.' stripped. > > E.g. list(a)example.com will only show on the index if the accessing URL's > host is example.com or www.example.com, but not if it is say > lists.example.com. > Thank You I just discovered it. I put a workaround for now in index.py so also list.example.com works. # Domain filtering if settings.FILTER_VHOST: domain = request.get_host().split(":")[0] if domain.startswith("www."): domain = domain[4:] #gg# Added by Gelpi if domain.startswith("list."): domain = domain[5:] domain = "@%s" % domain mlists = mlists.filter(name__iendswith=domain) Regards -- Gelpi ing. Andrea -------------------------------------------------------------- It took the computing power of three C-64s to fly to the Moon. It takes a 486 to run Windows 95. Something is wrong here. --------------------------------------------------------------

5 years, 9 months

[MM3-users]Re: [Mailman-Users] Mailman3 administration

by Barry Warsaw

On Jun 18, 2016, at 12:10 PM, Mark Sapiro wrote: >because I want to run all the Mailman pieces from >the heads of their branches rather than what's in PyPI, but even without >that, installation is significantly more work than installing a distro's >package. My hope is that the upcoming 3.1 release will be much more solid and usable than 3.0 so that you won't have to run from the git heads. I think of it very much like Python 3.0 and 3.1 - the 3.0 release was really a stake in the ground and a major milestone so that people will start using it in anger and helping us understand the priorities for fixing and improving it. In that we've succeeded I believe (witness in addition to Mark's work on python.org, that the Fedora mailing lists have all been converted to use MM3). There are a number of interesting options for improving the turnkey installation of MM3. There are Debian folks who are waiting for 3.1 to complete the packaging work there, and there are docker/juju/etc. containerization work happening too. >I will say that once you have Mailman 3 installed and running, updating >(which I do frequently, but which doesn't need to be done unless you >want specific updates/fixes) is pretty easy. Yes, we're trying to be very serious about upgrades and backward compatibility, so that even if you bravely install 3.0 today, it should always be easy to upgrade to the next point release. Similarly, I try to keep core's git head always working so you could track that if you want. Cheers, -Barry

9 years, 7 months

[MM3-users] Re: FYI: Django security releases issued: 4.0.6 and 3.2.14

by David Newman

On 7/8/22 6:34 AM, Stephen J. Turnbull wrote: > David Newman writes: > > > Interesting -- that does produce two directories with names starting > > with a tilde: > > > > /opt/mailman/venv/lib/python3.9/site-packages/~jango: > > /opt/mailman/venv/lib/python3.9/site-packages/~jango-3.0.14.dist-info: > > I would guess that those are the previous versions before the upgrade, > moved out of the way in case a revert-to-previous was needed. Again, > guessing, they should have been removed by the upgrade process once > the new package was fully installed. Was there an interrupted or > partially successful upgrade in the past? Yes > > So I would guess you can remove them. Probably you have the relevant > Ubuntu packages cached somewhere, and they're probably available from > Ubuntu if you really wanted them. This system runs Debian 11, with everything installed in a venv. I'm unclear on the relationship between the usual apt* tools and pip, and just do everything Mailman-related using pip. On 7/8/22 7:47 AM, Mark Sapiro wrote: > When pip is doing an upgrade of the xyz package, it renames the existing > package as ~yz and then ultimately deletes the old ~yz package after > successfully installing the new xyz. In this case, the upgrade was > aborted because of the Django<3.1 constraint in mailman-web and > apparently pip then installed Django<3.1 and left the ~jango* > directories behind. Ahhh, that explains it. Thanks for your replies. I've deleted the ~ directories and so far have not noticed any adverse effects. dn

3 years, 6 months

[MM3-users] Re: Aborted connection message in log in every 5 minutes

by Danil Smirnov

Hi Mark, On Wed, Jan 31, 2024 at 3:12 AM Mark Sapiro <mark(a)msapiro.net> wrote: > The only thing that runs every 5 minutes is `mailman gatenews`. The > issue may be with that. You could try running it manually via > ``` > _MAILMAN_GATENEWS_NNTP=yes;sudo -u list mailman gatenews > ``` > I observe occasional error messages in MariaDB log even with NNTP runner disabled via ``` [runner.nntp] start: no ``` They look like this: ``` 2024-01-31 0:23:03 231666 [Warning] Aborted connection 231666 to db: 'mailman_core' user: 'root' host: '192.168.32.7' (Got timeout reading communication packets) 2024-01-31 6:00:09 232888 [Warning] Aborted connection 232888 to db: 'mailman_core' user: 'root' host: '192.168.32.7' (Got timeout reading communication packets) 2024-01-31 9:19:34 231643 [Warning] Aborted connection 231643 to db: 'mailman_core' user: 'root' host: '192.168.32.7' (Got timeout reading communication packets) 2024-01-31 9:19:35 232847 [Warning] Aborted connection 232847 to db: 'mailman_core' user: 'root' host: '192.168.32.7' (Got timeout reading communication packets) 2024-01-31 9:19:35 233069 [Warning] Aborted connection 233069 to db: 'mailman_web' user: 'root' host: '192.168.32.4' (Got timeout reading communication packets) 2024-01-31 9:19:35 233068 [Warning] Aborted connection 233068 to db: 'mailman_web' user: 'root' host: '192.168.32.4' (Got timeout reading communication packets) 2024-01-31 9:19:35 233070 [Warning] Aborted connection 233070 to db: 'mailman_web' user: 'root' host: '192.168.32.4' (Got timeout reading communication packets) 2024-01-31 9:19:35 233071 [Warning] Aborted connection 233071 to db: 'mailman_web' user: 'root' host: '192.168.32.4' (Got timeout reading communication packets) ``` However, no harm caused by them was detected. BR, Danil Smirnov Sincerely, Danil Smirnov

2 years

[MM3-users] Re: Can't subscribe on new site/domain

by Flo

On 10/9/25 19:19, Mark Sapiro wrote: > On 10/9/25 5:02 AM, Flo via Mailman-users wrote: >> Hi, >> >> I added a new site in Django: lists.example.com >> >> Usually I click on 'view site' and I can add a Domain in Postorios. In >> this case I get an error message and I need to add a Domain in Django. >> Then I can go to 'view site'. >> >> I can create a mailing list there. However when I send an email to be >> subscribed, I get the following in mailman.log (and nothing else >> happens): >> >> >> Oct 09 13:46:24 2025 (110452) deque: do_confirm_verify >> Traceback (most recent call last): > ... >> File "/usr/lib/python3/dist-packages/mailman/model/domain.py", line >> 177, in __getitem__ >> raise KeyError(mail_host) >> KeyError: 'lists.example.com' > > It appears you don't have a domain in Mailman core with mail_host = > 'lists.example.com'. > > Do you see one in Postorius' domains view? If not, perhaps you need to > add it. > I can see it in Postorius. I have created the a simialar site before and deleted the site and then again created this one. Maybe the database is messed up? I have deleted site - group - list now. And created the site again. If I go to 'view site' I see all mailing lists on the server and not only from this site/domain. This is the first thing where it shows irregularities. Flo

3 months, 3 weeks

[MM3-users] Re: Can't post to my own list from HyperKitty

by MegaBrutal

Mark Sapiro <mark(a)msapiro.net> ezt írta (időpont: 2025. ápr. 8., K, 4:06): > On 4/7/25 17:45, MegaBrutal via Mailman-users wrote: > > > > So it's even weirder – however, I'm really not sure if this is the > address > > HyperKitty is checking for, as I have 3 attached to my account! > > How may I know which one it's trying to use? > > If you go to https://example.com/user-profile/ what Primary email and > Other emails do you see? Do you see all three? And if you go to > https://example.com/mailman3/users and click Manage for your address, do > you see all 3 under Addresses? Now I see a difference here! User-profile shows my GMail address as primary and my own-domain address as secondary. The third address is not present, because I actually wanted to get rid of it, and it seems I succeeded in that. Mailman3/users shows me with the address I wanted to get rid of. If I click Manage, I see all 3 addresses, with (for some reason) only the GMail one being verified (strange because I'm sure I verified the other as well). And here's something interesting: it shows me as a member with my GMail address under subscriptions, but shows me with my megabrutal.com domain under ownerships. This might be the cause? Maybe HyperKitty wants to use my owner identity, which is not subscribed? Btw, is the owner not automatically considered as someone who can post to the list, they also need to be subscribed?

9 months, 3 weeks

[MM3-users] Re: mail stuck in "out" queue

by pdw＠mythic-beasts.com

Mark Sapiro wrote: > On 12/10/24 07:44, pdw(a)mythic-beasts.com wrote: > > First check to ensure there are no files in Mailman's var/templates/ > directory that are not readable by the Mailman user. That can cause this > issue. Checked, and I've also tried removing all templates for the affected list. > > After multiple restarts trying to get some debug information, the hard loop seems to have stopped recurring, and the messages are sat in the "shunt" queue. They've not been delivered to recipients, but they are in the hyperkitty archive. > > The shunted messages should have a SHUNTING entry with an exception and > traceback in mailman.log. If there were files unreadable by Mailman in > Mailman's var/templates/ directory and you have corrected that, you can > move the shunted messages back to their original queue with mailman unshunt. I've now found the SHUNT entries and the exceptions seem related to restarting mailman (see below) so that much makes sense. unshunting does indeed restore them, but unfortunately they're now back in the looping state. Paul Shunting exception: File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 179, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 278, in _process_one_file self.switchboard.enqueue(msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/core/switchboard.py", line 122, in enqueue filebase = now + '+' + hashlib.sha1(hashfood).hexdigest() ^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 117, in signal_handler raise RunnerInterrupt mailman.interfaces.runner.RunnerInterrupt Dec 17 21:25:51 2024 (1039773) SHUNTING: 1734470750.961038+b6946081a6c85ed7c03d221af87b87463eaf68e1 Dec 17 21:25:51 2024 (1039773) out runner exiting.

1 year, 1 month

[MM3-users] Re: How to delete non-users

by Stephen J. Turnbull

Mark Sapiro writes: > My original point is the presence of a nonmember role should not prevent > the user from subscribing. If there is an issue with subscribing it is > probably because of the outstanding subscription request waiting > moderator approval. I don't think it is likely, but is it possible that the moderator is not just refusing the subscription, but banning the address from subscribing? > I understand that you would like the nonmember role to disappear, but > that isn't going to happen in the distribution, and I can't undertake > the extensive effort required to figure out how you can do it for your site. It seems to me that explicitly displaying the nonmember role is an internal and/or administrative need, and most ordinary users are only interested in whether they are subscribed or not. If the list appears in "their" list of list, they're going to assume they're subscribed. (We've even had that confusion about moderators and owners in the past.) I haven't done any deep thinking about this, but perhaps we could provide a more streamlined view tuned to this specific need? That is, the role won't go away, but at least in some contexts you'll have to ask explicitly for that user-list relationship to be displayed. Also, IIRC Allan's community contains a substantial group of folks with visual impairments, presumably including admins and moderators. Especially to serve that circumstance I think it makes sense for us to provide streamlined views that are more easily grasped as a whole where we can.

3 years, 4 months

Search results for query "sapiro"