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

[MM3-users] Re: Subscription request cannot be moderated: 404 Not Found

by Mark Sapiro

On 1/16/21 7:49 AM, Eric Broens via Mailman-users wrote: > Hi Mark, > I can't find any log entry which indicate a problem with this subscription request. > The _request table does not contain a request for the specific mailinglist, but I am not sure if subscription requests are included in this table. It is unclear and confusing, but the requests are not in the _request table. See <https://gitlab.com/mailman/mailman/-/issues/768#note_415536043>. So this is normal. > The token is found in the pended table: > > +-----+------------------------------------------+---------------------+ > | id | token | expiration_date | > +-----+------------------------------------------+---------------------+ > | 115 | 4d6b4b11266c7332684c5a492eb3f92c531f761b | 2031-01-04 16:17:38 | > +-----+------------------------------------------+---------------------+ > > These are the relevant entries in the pendedkeyvalue table: > +------+--------------+-------------------------------------+-----------+ > | id | key | value | pended_id | > +------+--------------+-------------------------------------+-----------+ > | 1130 | type | subscription | 115 | > | 1131 | list_id | "********************" | 115 | > | 1132 | email | "***********************@*********" | 115 | > | 1133 | display_name | "" | 115 | > | 1134 | when | "2021-01-06T16:17:38" | 115 | > | 1135 | token_owner | "moderator" | 115 | > +------+--------------+-------------------------------------+-----------+ > > Can I workaround this problem for this specific subscriber by adding entries in the _request table, and if so what do I need to add? Adding to the _request table won't help. Try confirming by emailing listname-confirm+4d6b4b11266c7332684c5a492eb3f92c531f761b(a)list.domain You could also try confirming via mailman shell 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 >>> ISubscriptionManager(m).confirm('4d6b4b11266c7332684c5a492eb3f92c531f761b') Traceback (most recent call last): File "<console>", line 1, in <module> File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.3b1-py3.7.egg/mailman/app/subscriptions.py", line 570, in confirm raise LookupError LookupError In my case, I get the LookupError because the token doesn't exist, but I think it should work for you. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: FILTER_VHOST not working

by Mark Sapiro

On 3/22/21 1:03 PM, Johannes Rohr wrote: > In /etc/mailman3/mailman-web.py I have added > FILTER_VHOST = True > so that only the list for the current domain are shown. > > But this has no effect. The current situation with Postorius >=1.3.3 and Hyperkitty >=1.3.3 is for HyperKitty, FILTER_VHOST = True works. For Postorius, it works only if in the domains view, each mail host has a unique web host. It doesn't work. See this post <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> and others in that thread for more info. Prior to Postorius 1.3.3 and Hyperkitty 1.3.3 it would only work if the mail host and web host values were identical for the domain. > > What's more, in hyperkitty I see at the top left the lable for the > default domain, even though I am visiting from another domain. That has nothing to do with FILTER_VHOST. The displayed there is the site referenced in the SITE_ID setting. > The web domains are exactly the same as the mail domans > (lists.[domain].[tld]) In that case, I'm not sure what's going on. > In the Nginx config I have added > > location / { > proxy_set_header X-Forwarded-Proto $scheme; > proxy_set_header X-Forwarded-Host $host; > proxy_pass http://localhost:8000/; > [....] > > } > > to make sure that mailman3 knows from which URL it is visited. > > Am I overlooking something? > > I am using the distribution packages on Ubuntu 20.04: > mailman3 3.2.2-1 > mailman3-web 0+20180916-10 > > I see, the mailman3-web package is quite dated. Is it recommended to > install via virtualenv instead? Yes, the issue is at least partially that that mailman3-web package doesn't have any of the FILTER_VHOST fixes. And yes, if you don't want to be stuck with dated packages tha don't include recent fixes, we recommend installation as documented at <https://docs.mailman3.org/en/latest/install/virtualenv.html> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: Mm3 - new adventure

by Mark Sapiro

On 03/14/2017 09:14 AM, SP2L wrote: > > Lately started adventurous journey with Mailman3 > which is way, way different already from the beginning. > > Used Mailman bundler to install GNU Mailman, Postorius and HyperKitty > testing instance in virtual environment, mainly relaying on belows recipe: > > https://gitlab.com/mailman/mailman-bundler/ mailman-bundler is out of date and deprecated. You might find <https://wiki.list.org/x/17891998> of interest. > Present status. > > Above trio and MySQLServer are "talking" to each other > but because there isproper database on MySQLServer > I am facing strange and unexpected issues, Hi! > > Executing last two commands: > > (venv)$ ./bin/mailman start > (venv)$ ./bin/mailman-web-django-admin runserver 0.0.0.0:8000 & > > I see Postorius and HyperKitty up & runningbut... > > Belowvery condensed messages from the console: > > > /HyperKitty/ > > DEBUG = False > > [12/Mar/2017 18:59:43] "GET /archives/ HTTP/1.1" 200 8002 > WARNING Not Found: > /static/hyperkitty/libs/jquery/smoothness/jquery-ui-1.10.3.custom.min.css ... Have you run the script that bundler installs as bin/mailman-post-update? > /mailman3/ > > DEBUG = False > > Server Error (500) > > > DEBUG = True > > HTTP Error 500: A server error occurred. Please contact the administrator. > > Exception Location: > /var/lib/mailman3/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanclient/_client.py > in call, line 109 > > Then VERY, verylong list... Without knowing what the exception was and at least the start of the traceback, it's hard to say what this might be. > By means of PhpMyAdmin I created manually mailman3 database > and few tables (looking at 0001_initial.py) , but it is not working O.K. > This handmade table is not doing it's job. You shouldn't need to do this. If you have the proper settings and credentials in the DATABASES setting in mailman-web/settings_local.py and the [database] section in deployment/mailman.cfg, the tables should be created for you. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 7 months

[MM3-users] Re: Template's encoding setup

by Mark Sapiro

On 9/14/19 4:06 AM, Ugnius S wrote: > Yes, I have made several tests. I have set charset: iso-8859-13 > and default_language: lt in mailman.cfg. If you created the list before you set default_language: lt in mailman.cfg, the list's preferred_language is possibly 'en;' with character set us-ascii. > (Also I have set LANGUAGE_CODE = 'lt' in the settings_local.py, but I think > it is not related to this case.) Yes, LANGUAGE_CODE in settings_local.py is not relevant to this. > I have tried to set utf-8 as well in mailman.cfg as well. And I can > confirm - in all tested cases > text characters are correct (in footer as well) if sender sends text only. OK > If sender sends message in HTML (mostly all users send) then no > matter what the encoding is set in my mailman's > configuration or iso-8859-13, or utf-8 message body looks correct, but in > footer all national characters are replaced with > question marks " ? ". The addition of the footer is done by mailman/handlers/decorate.py. In the plain text case the message body is converted to unicode, the unicode footer is appended to the body and the new body is encoded for transmission. The encoding is the first of the list's character set, the incoming message's character set or utf-8 which produces no error. In the case where the incoming message is not a single plain text message part, the footer is added as a separate MIME part with the unicode footer encoded in the list's character set with errors='replace'. This is what produces the '?' characters. I suspect this happens because the list's preferred_language is 'en' with character set us-ascii. try running Mailman's bin/mailman shell -l your_list@domain at the prompt enter m.preferred_language if the response is not <Language [lt] Lithuanian> do m.preferred_language = 'lt' and then control-D to exit. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 1 month

[MM3-users] Re: restrict sending to owner/moderator

by Mark Sapiro

On 09/18/2017 02:28 AM, m.dohmen(a)xconnect.de wrote: > > I'd like to restrict message acceptance on a per-list basis to the owner or moderator, so that simple subscribers cannot send messages to the list. But I don't want the owner/moderator having to moderate own messages, so the member setting "hold for moderation" in Postorius isn't applicable. And on 09/19/2017 10:52 AM, David Krantz wrote: > > I have just tested a variant of this as I got curious: You find the > member you want to be able to send emails without moderation, then set > Administrative Options to "Accept Immediately (bypass other rules)". > That works. I have found no other ways, though. Or you may wish to set the owners/moderators subscriptions to "Default processing" which will still apply subsequent rule checks. I.e., set Default action to take when a member posts to the list to Reject (with notification) and set an appropriate notice (currently can't be set in Postorius - set it via 'mailman shell') and set Default action to take when a non-member posts to thelist to Discard or perhaps Reject but this creates backscatter. Then ordinary members have Moderation set to List default and owners/moderators have it set to Accept or Default. The problems with this are sall the owners/moderators need to be subscribers and there are maintenance issues with adding/removing owners/moderators. A better way to do this by sharing a "moderator password" for the list among the authorized posters. See <http://mailman.readthedocs.io/en/latest/src/mailman/rules/docs/approved.html> for how this is done to pre-approve posts. Then set the list to Discard/Reject all posts, and people who know the "moderator password" can still post. There is still an issue in that the password needs to be changed and redistributed when people become unauthorized, but this is more secure as regular moderation can be fooled by spoofing the sender. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 1 month

[MM3-users] Re: Post-installation documentation?

by Mark Sapiro

On 11/24/21 9:40 AM, David Newman wrote: > > IMO post-installation docs for list admins would be a big help in > Mailman3 adoption. I'm willing to help with this. Thank you for being willing to contribute. I think the place for list admin docs would be in the https://gitlab.com/mailman/mailman-suite-doc project which is the source for https://docs.mailman3.org/en/latest/. There is currently a userguide there at source/userguide.rst and referenced from source/index.rst. the addition of an adminguide.rst would be welcom if you want to work on that. > When I say "working": I'm looking to migrate Mailman2 mailing lists to > Mailman3, but am struggling with even basic setup tasks before we > attempt list migtration. > > For example, on admin page I've set up two lists, one public and one > private (each with unique list IDs), but neither appear in the site's > list index. Here are the steps to migrate a 2.1 list named `alist(a)example.com` and its archives. run Mailman's `bin/mailman create alist(a)example.com` follow that with ``` bin/mailman import21 alist(a)example.com /path/to/mailman2.1/lists/alist/config.pck ``` That will create the list and import its members and settings. To import archives run the Django admin command with arguments ``` hyperkitty_import -l alist(a)example.com /path/to/mailman2.1/archives/private/alist.mbox/alist.mbox ``` > And I don't know where to add list members. For imported lists, they are already added, but for new lists, you can add them in Postorius under Mass operations -> Mass subscribe or via the bin/mailman commands `addmembers` or `syncmembers`. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… > And clicking the site archives link throws this error: > > django.urls.exceptions.NoReverseMatch: Reverse for 'hk_list_overview' > with keyword arguments '{'mlist_fqdn': 'wheee'}' not found. 1 pattern(s) > tried: ['archives/list/(?P<mlist_fqdn>[^/@]+@[^/@]+)/$'] Did you specify the list's fqdn as in https://www.example.com/archives/list/list@example.com/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: users leaking across virtual hosts

by Mark Sapiro

On 3/25/22 12:49, Stanisław Findeisen via Mailman-users wrote: > Hi > > We are hosting several virtual hosts (mail host : web host is a 1:1 mapping with identical names), works fine, but it looks user accounts are somehow global, i.e. registering a new user in a new virtual host doesn't work if the user name or e-mail address are already in use in another virtual host. This happens on the Hyperkitty sign-up page: /accounts/signup/ , with the errors being "A user is already registered with this e-mail address." and "A user with that username already exists.". I am assuming this is a well-known limitation, which would require a serious internal redesign to fix; correct? These user registrations and logins are Django things so yes, they are global within the Django instance. > I was able to successfully login in the browser to a vhost using my user credentials from the original vhost (the one where the account was created) (the password was not auto-filled, of course, because of a different domain name). But how safe is this? How about subscribing to lists, posting etc.? Is this going to mess things up somehow? I don't think it's a problem. The user is a Django user for the web UI. The fact that there is or isn't a Django user with a particular email address has nothing to do with whether that address can post to a list. The user can subscribe to lists or not. The user can manage her subscriptions for lists to which she is subscribed and can subscribe to lists or not as controlled by list settings. Basically, registering as a user allows you to authenticate as that user for the web UI only. If you wanted to separate these user registrations by vhost, you'd need to run separate Django instances for each vhost, but I don't see a need to do that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: Errors while importing mm2 list archives - SOLVED

by Mark Sapiro

On 12/20/22 22:25, Odhiambo Washington wrote: > > In my case, running `mailman` without any arguments just makes it grok :) > > (venv) [mailman@gw ~/mm]$ mailman info ... > *config file: /opt/mailman/mm/mailman.cfg* That's because it first looks in the current directory for `mailman.cfg` and only if it doesn't find it there does it look in /etc/mailman3. >> Ultimately, when I did the import, there was only one email from the >>> archives that failed to be imported - which I honestly don't mind, but >>> maybe there is a solution for this >>> "'utf-8' codec can't encode character '\udcae' in position 331: >> surrogates >>> not allowed" ?? >> >> >> If you provide a copy of that message from the mbox, either on the list >> or to me directly, I'll investigate. >> > > A mbox file containing that email and the associated thread can be > downloaded from here: > https://webmail.kictanet.or.ke/~wash/chunk_7.txt.gz The offending message is multipart with an attached message/rfc822 part and that part has a preamble which in bytes is b'This document is a Single File Web Page, also known as a Web Archive file. If you are seeing this message, your browser or editor doesn't support Web Archive files. Please download a browser that supports Web Archive, such as Windows\xae Internet Explorer\xae.' The '\xae' is an iso-8859-1 encoding for '®', but no charset is specified for this preamble so email message parsing ends up decoding those as surrogates '\udcae' which throws the exception when hyperkitty.lib.incoming.add_to_list() in trying to save the attachment does `att.set_content(content)`. Normally, when messages to be archived arrive from core via mailman_hyperkitty, the surrogates are replaced by email.utils._sanitize(), but this doesn't happen with messages from hyperkitty_import. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: integrating mm3 with postfix / lmtp

by Mark Sapiro

On 10/25/2017 05:41 PM, Fabian A. Santiago wrote: > > No to the domains part and I think virtual alias maps is needed: > > mail postfix/trivial-rewrite[19445]: warning: do not list domain xxx in BOTH virtual_mailbox_domains and relay_domains > Oct 25 20:39:19 mail postfix/trivial-rewrite[19445]: warning: do not list domain xxx in BOTH virtual_mailbox_domains and relay_domains > Oct 25 20:39:19 mail postfix/submission/smtpd[19441]: NOQUEUE: reject: RCPT from pool-108-53-239-102.nwrknj.fios.verizon.net[108.53.239.102]: 550 5.1.1 <test123@xxx>: Recipient address rejected: User unknown in virtual mailbox table; from=<fsantiago@xxx> to=<test123@xxx> proto=ESMTP helo=<[10.0.0.29]> (above slightly sanitized for return to the list) The issue here is your list domain cannot be a virtual_mailbox_domain or a virtual_alias_domain. I have the same issue on mail.python.org where we have both Mailman 2 and Mailman 3 lists @python.org. and python.org is a virtual_alias_domain. I have a group of MRs for a branch that implements "alias_domains" to deal with this. Basically it works by creating another (virtual_alias_maps) postfix_vmap mapping to map list addresses @python.org to addresses @x.python.org. Then the postfix_domains and postfix_lmtp maps have the x.python.org domain and there is a patch to mailman/runners/lmtp.py to map the x.python.org domain back to python.org. The various MRs are <https://gitlab.com/mailman/mailman/merge_requests/202> for the core, <https://gitlab.com/mailman/mailmanclient/merge_requests/18> for the REST bindings used by Postorius and <https://gitlab.com/mailman/postorius/merge_requests/186> to be able to set an alias_domain via Postorius. That's not all implemented at mail.python.org. What's there is the basic Postfix config, a bash script the generate the new mappings from the old and a simple patch to mailman/runners/lmtp.py. So, the bottom line is it can be done and it's in process, but it won't really be supported until Mailman 3.2. In the mean time, you just need to have a separate domain for your lists that isn't a virtual_*_domain. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 11 months

[MM3-users] Re: Removing a mail addresses and users

by Mark Sapiro

On 6/10/20 10:23 AM, Abhijith PA via Mailman-users wrote: > Hello. > > I tried to remove random email address signing ups (which I signed up > while testing) via admin panel. After removing I tried to sign up again, > but I am getting, > > 'A user is already registered with this e-mail address' You removed the user's subscription from the list, but you didn't remove the user from the system. Mailman3 has a concept of `user` which didn't exist in Mailman 2.1. User's have addresses and a user or one of the user's addresses can belong to a list with one or more roles (non-member, member, moderator or owner) > Combing through the database, I found auth_user table in mailman3web db > still contain those mail address. How to wipe email address entirely > from the db so I can signup again without the 'forget password' method There are a couple of things. If you log in to the web UI as a django superuser, you can go to the django admin UI -> Users section and delete the User, but I think that will only delete the web user and not delete the user from Mailman core. You can also log in to the web UI as the user and go to <https://lists.mailman3.org/user-profile/delete>, but that again only deletes the web user, and if you could do that, you could just subscribe once you're logged in, so I assume that's what you want to avoid. I don't think there is a way for a user as opposed to a site admin to delete her user record from Mailman core and even for a site admin, there's no way in Postorius to delete a user from core. It has to be done via REST <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> or `mailman shell`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

Search results for query "sapiro"