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

[MM3-users] Re: CSS Hyperkitty ERROR

by Johan Alsina

Mark Sapiro wrote: > On 3/18/25 3:39 PM, Johan Alsina via Mailman-users wrote: > > Like i said before, i think the problem comes with the css files in /static/CACHE.. because the ones that are in /static/hyperkitty are loading ok.. > > See this thread: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/7... > Some of that may be useful. > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan Hi Mark, i configured the paths to load all the files from /staticfiles/ but for some reason the .css files are loading but not showing again and i dont know why... https://freeimage.host/i/3ovaZgf https://freeimage.host/i/3ovaQ0G

11 months

[MM3-users] Re: Is it possible to use an authenticator with incorrect, missing, or changing email addresses?

by Mark Sapiro

On 05/23/2018 12:56 PM, andrew(a)fsf.org wrote: > Hello Mailman 3 users list, > > I was wondering if it's possible to set up a CAS authenticator with django-allauth ( https://pypi.org/project/django-allauth-cas/ ) even if we cannot guarantee the correctness of email addresses supplied by our CAS instance? Some contacts may also be missing an email address. I read about this here, and it seems like it wouldn't be possible: > > http://docs.mailman3.org/en/latest/config-web.html#configure-social-login > >> To see a list of all the providers, please have a look at the documentation of django-allauth. Make sure that the one you choose provides “email” as part of user data, otherwise it won’t work with Mailman. e.g. Twitter doesn’t give out emails. > > What if a user's email address changes on the CAS server? Will their email address in Mailman 3 be updated the next time they log in? If django-allauth-cas can't provide an email address, that user can't use it for Mailman authentication because authentication is for a registered email address. The way it works is a user registers an email address with Mailman. Once the address is registered, but not before, it can be linked to one or more configured django-allauth providers, and once linked, the user can log in to the Mailman web UI via a linked allauth provider. If the allauth provider doesn't supply the user's email address, I don't think it can be linked, but even if it can, it won't work. If the user's CAS email changes, the user would have to add the new address to her account in Mailman and could then link the new address to the CAS allauth provider. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 9 months

[MM3-users] Re: Odd hold message

by Mark Sapiro

On 7/4/19 6:00 AM, Andrew Bernard wrote: > I received a very simple post today that was held with the following reason: > > The message is being held because: > > Message contains administrivia > > At your convenience, visit your dashboard to approve or deny the > request. > > > What is this all about? What does Mailman consider to be administrivia, of > all things, and why is this a reason to hold a message? The administrivia check is designed to detect messages posted to a list which look like they should have been sent to the list-request address instead. You can turn this check off in Postorius at Settings -> Message Acceptance -> Administrivia. > The only thing in the message I can see is that it mentioned '100 members'. > Is Mailman becoming sentient and developing an attitude? Seriously, I'd > like to know more about this. That's not the reason. The administrivia rule checks the Subject: header and the first N non-blank lines of the first text/plain part of the message for things that look like an email command. I.e., lines that begin with a command word followed by the appropriate number of 'arguments'. Here's the list EMAIL_COMMANDS = { # keyword: (minimum #args, maximum #args) 'confirm': (1, 1), 'help': (0, 0), 'info': (0, 0), 'lists': (0, 0), 'options': (0, 0), 'password': (2, 2), 'remove': (0, 0), 'set': (3, 3), 'subscribe': (0, 3), 'unsubscribe': (0, 1), 'who': (0, 2), } This is actuall not a valid list because it is from Mailman 2.1 and not all the above are valid Mailman 3 email commands, but that's what is checked. The N is the configured value for [mailman] email_commands_max_lines: (default 10) Thus, if the Subject: or one of the first 10 non-blank lines is who are you? the administrivia rule will hit. See the source in mailman/rules/administrivia.py for more detail. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 7 months

[MM3-users] Re: Issues with migrating from Mailman2 to Mailman 3

by Mark Sapiro

On 9/22/19 10:29 AM, Uwe Grasshoff wrote: > Hello all, > > I'm currently trying to convert a Debian based mailman2 installation to > a docker based mailman3 installation. > I successfully running the mailman-web and mailman-core containers > together with the database container but I'm struggling with the import > of the old mailing lists. In the core container I'm running this two > commands for every mailing list: > > mailman create mailman(a)example.com > mailman import21 mailman(a)example.com > /oldmailman/lists/mailman/config.pck > > Then I'm switching over to the mailman-web container and running this > two commands: > > python3.6 manage.py hyperkitty_import -l mailman(a)example.com > /oldmailman/archives/private/mailman.mbox/mailman.mbox > python3.6 manage.py update_index_one_list mailman(a)example.com > > I'm getting no errors or something else which could indicate a problem. > After that I'm looking into the web interface > http://example.com/postorius/lists/ > There I can only see the public mailing list and the private ones are > not shown there (as expected). Everything up to this point is expected behavior. > When I then try to login with the List > Manager credentials of the lists (from mailman2) I can't login in. So I > thought maybe I have to "register" myself again to than get access to > the list management. > So I tried that but when I filled out the form and click "Register" I'm > presented with an error page which titles "Serverfehler" (Server error > in german) and the message "An error occurred while processing your > request." I'm not sure about the error, but the import21 process registered you so what you need to do is go to the Login page, click "Forgot Password?" and then request a password reset. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 5 months

[MM3-users] Re: One bounce, 5 bounce counts

by Mark Sapiro

On 1/13/22 6:17 AM, Henrik Rasmussen wrote: > > My problem, though, is that some subscribers may be disabled even they are able to receive mails (confirmed with sendmail -bv), and I have been looking at one subscriber in particular. > > > 1. Can there be (i'm not saying there are, maybe it's my lack of knowledge) somthing regarding Mailman? > 2. And what would the appropeiate per list bounce settings, if not default? Referring to the example below, it seems that your Postfix delivers successfully to the first hop MX of the recipient, but the mail bounces further downstream resulting in an emailed bounce. One thing you can do to help mitigate scoring of bounces of emails due to spam filtering is to set ``` [mta] verp_probes: yes ``` This will cause Mailman to not disable delivery when bounce score reaches threshold, but rather send a probe which hopefully won't be detected as spam and only disable delivery if the probe bounces. > Actual example: > > > * Mailman sent seemly 6 mails to a member on January 6th. > * I see one bouce message D1426CE22A in Postfix log that was delivered back to Mailman > * I see that Mailman is counting the bounce score from 1 to 5, one at the time, but that was day after receiving the bounce, and no other mails have been sent to the user on the 7th nor received as bounce on the 7th. I suspect that it must have been in the Postfix queue until then, but I wonder why that could be - but could be. > * The bounce would be in the Postfix queue until sent to Mailman and thus removed from the Postfix queue. I suspect the issue is something like a connection problem from the recipient MX to a relay MX that is not being reported as a bounce until the retry interval has expired. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

[MM3-users] Re: All addresses in a bounced list posting seem to be considered as bouncing

by Mark Sapiro

On 7/9/22 6:35 AM, Andy Smith wrote: > > I'm concerned that Mailman seems to have scored my address as > bouncing even though it isn't, merely because it appears inside a > message that was rejected. > > Is that expected? Is there any way to avoid it? No, it's not and it should not ever happen. > I see that Mailman has a bunch of heuristics to parse bounce > messages. In this case though, there shouldn't have been a bounce > message received to users-bounces@, as this was an SMTP-time > rejection. Mailman seems to have parsed addresses out of the actual > mail it was sending, rather than only scoring the subscriber address > it was trying to send a list posting to. Yes, flufl.bounce is used to parse messages delivered to the -bounces. There are a lot of hueristic recognizers, but RFC 3464 compliant DSNs should be recognized by the DSN detector which is tried first and which gets the failed address from the report. See https://gitlab.com/warsaw/flufl.bounce/-/blob/master/flufl/bounce/_scan.py#… However, SMTP failures do not result in DSNs to the -bounces address. If recipients are refused at SMTP time, this should result in a message in Mailman's smtp.log of the form ``` <message_id> recipients refused: <mta's message> ``` and we create a fake DSN (see https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/outgoi…) to be processed as a bounce for the failed recipient. In this case, no parsing of the failed message should occur. I can't explain what happened in your case. It seems that somehow the original post was delivered to the -bounces address and parsed by one of the heuristic recognizers (probably simplematch), but how could that happen? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: Help with mailman user and mailman Web users

by Mark Sapiro

On 2/15/22 05:57, Sherin wrote: > > I have installed mailman3 server and configured MailmanWeb ( > hyperkity + Postorious ) . The service and everything works fine, but I > am little bit confuses with the user management in mailman3, > > 1) I created an owner user for a mailing list using the mailmanclient > api tools, # from mailmanclient.client import Client > 2) I can't login to the Mailmanweb with this user There are Mailman users and Django users. These are distinct. Creating a Mailman user does not automatically create a Django user and vice versa. In order to log in to the web UI, one must be a Django user, so this user has to go to the web UI and Sign Up. > For further investigation shows the mailman have its own database and > the web frontend have its own database too. > So my question is how to configure the webfrontend ( hyperkit+ > postorious ) to use the accounts logins created from the mailmanclient > api from the mailman core database. You can't. Well, I suppose you could modify the HyperKitty sync_mailman job or create another Django job to create Django users for Mailman users who aren't currently Django users, but short of that, there's no config for it. > Or is there a way to use only one user management system ? No. Mailman core and the web UI are separate applications by design in order to enable Mailman core to operate with any appropriate web UI. We provide Postorius and HyperKitty as web UIs for management and archiving and they are based on Django which has its own user management. It was our hope that other, perhaps more light weight, web UIs would be developed and available, but aside from EMWD's proprietary Harmony/Empathy PHP applications, we are not aware of any. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

[MM3-users] Re: Attachement processings questions

by Lars Schimmer

On 2020-02-04 19:15, Mark Sapiro wrote: > On 2/4/20 9:02 AM, Mark Sapiro wrote: >> >> You can fix it by patching the Python library email/generator.py as at >> <https://github.com/python/cpython/pull/18056/files#diff-220640ea02a24dfdbb0…>. > > > > And once you have patched email/generator.py and restarted Mailman core, > you can deliver the messages by running the `mailman unshunt` command, > but first look in var/queue/shunt/ to ensure you won't be unshunting any > unwanted messages. You can examine those files with `mailman qfile`. Great This did helped. Thank you. MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723

6 years

[MM3-users] Re: mailman 2.1 or 3.0 (or another MLM)

by Mark Sapiro

On 1/26/22 11:05, nate wrote: > > Can I suggest the messaging to new users be improved to communicate > this situation as it is not clear. > > The automated message I got said this was the reason my message was > held: The message comes from a moderated member. > > Which makes sense if I REALLY think about it(I was a moderated member > at first), but then the next question is why was I moderated. Your > explanation makes sense. > > It would be nice if it had more info along the lines of what you > said, or even better adjust the messaging for the "Welcome" email > to indicate your first message(s) will be held for moderation(I checked > both emails I got back from the list just now to verify this info is > not there). I was confused for a while(again 21 year veteran of mailman) > thinking I sent my message using the wrong email address, after confirming > I sent with the right one I just decided to wait to see what would > happen. The situation is no different in Mailman 2.1. The issue is that what may be appropriate in the held message to the user or the list welcome message depends on list configuration and the policies of the particular list. Thus, we can't really modify the default message templates in this way. It requires making list specific templates or possibly domain or site specific templates where all the lists in a domain or site have the same policies. This can be done by list, domain or site admins, but doing or suggesting this on a site like, e.g., mail.python.org which has 232 Mailman 2.1 lists with a total of 243 unique owners and 182 Mailman 3 lists with a total of 212 unique owners is a daunting prospect. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

[MM3-users] Re: Digests not working correctly

by Mark Sapiro

On 6/4/23 18:35, Joel Lord wrote: > > The periodic digests do seem to be coming out. I also now have > confirmation that the one message in this morning's digest that was from > May 4th was also included in the last digest back on May 4th, so it > seems that the one message was left behind in the digest queue when the > periodic digest was sent. I don't see how that can happen. The process that sends a digest renames the var/lists/<list-id>/digest.mmdf mailbox file in which the messages are accumulated to var/lists/<list-id>/digest.<volume>.<issue>.mmdf, where <volume> and <issue> are the volume and issue numbers of that digest, and then queues a message in the `digest` queue to tell the digest runner to create the digest from the messages in that mbox and send it. Thus, it leaves no var/lists/<list-id>/digest.mmdf mailbox file behind and that is created anew when the next post arrives. Further, if there is a non-empty digest.mmdf file, its messages should be sent no later than the next 11 PM `cron digests`. > There was one earlier message to the list > back on May 4th, before the one that got duplicated, but I can't tell if > that triggered a size-based digest to be sent: the logs aren't clear > enough on that detail for me to tell. OK > Just to inform things: > > (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep mailman > django-mailman3==1.3.9 > mailman==3.3.8 > mailman-hyperkitty==1.2.1 > mailman-web==0.0.6 > mailmanclient==3.3.5 > (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep hyper > mailman-hyperkitty==1.2.1 Actually, it's HyperKitty, not hyperkitty, but I assume HyperKitty is up to date as are the others. > (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep post > postorius==1.3.8 > > -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

Search results for query "sapiro"