Search results for "Postorius" - Mailman-users

Re: Hyperkitty using wrong email address in archive view

by Mark Sapiro

On 5/16/23 01:42, peter(a)chubb.wattle.id.au wrote: > Hi Folks, > I notice that for people with multiple email addresses, the email > address that appears as the 'FROM' address in the hyperkitty > archive is not the primary address, nor is it the address that the > email actually came from, but the address that was created first. > (Hyperkitty version 1.3.7) Where exactly do you see this address? Normally, if the From: header of the mail contains a display name, it is that name which is displayed as the author of the email. The display is only an address if the From: header of the mail had no display name or if it had a display name which was an email address as in From: user(a)example.com <user(a)example.com> > When I click on that from address in the archive view, I see all > the email addresses for the user -- these do not match up with the > ones in the django admin screen from .../admin/account/emailaddress/ Because they are not the Django user's email addresses, they are the Mailman user's email addresses. > When I see 'User profile for Fred Frog' > it shows obsolete addresses (not subscribed, not in the Django > profile for the user). Again these are the Mailman user's addresses. The Mailman users are listed at the Users tab on the top Postorius nav bar. > How can I as administrator get rid of bogus addresses? Or do I > have to ask each user to do this? The user can do it at https://example.com/accounts/email/ but the admin can't do it from Postorius. A site admin can do it via REST or `mailman shell`. > and how can I ensure that the email address displayed in the > archive is the primary address, not some address that no longer > works? Again, where do you see this? You may want to download that thread and see what that shows as the From: header of the email. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

Acceptable aliases defaults to []

by Henrik Rasmussen

* Docker-mail 0.1.1 * Mailman 3.1 * Postorius 1.1.1 * Hyperkitty 1.1.1 Minor issues: Settings -> Message Acceptance -> Acceptable aliases has a default of [] resulting in "An error occured: [u'[]']" when saving. This fiend should be empty by default or at least accept the default when saving. To me the description right under the Acceptable aliases field is not user friendly. It doesn't explain the purpose of the field, but is meant for the Mailman sysadmin, not the list admin who can't be expected to understand this. A much better description would be the ones used for MM2: * http://www.list.org/mailman-admin/node23.html * https://wiki.list.org/DOC/What%20does%20%22message%20has%20implicit%20desti… On a second note: Where I can change the field and message descriptions in MM3, like the /usr/lib/mailman/messages/[sprog]/LC_MESSAGES/mailman.po in MM2? -- Henrik Rasmussen <her(a)adm.ku.dk<mailto:her@adm.ku.dk>> Copenhagen, Danmark

7 years, 9 months

Re: Importing config and archives only partially succeeded?

by Mark Sapiro

On 12/12/20 3:56 PM, Eric Broens via Mailman-users wrote: > After everything was imported, and I noticed that the mails were not shown in the archives for half of the mailinglists, I ran "manage.py update_index" to index the mails for all mailinglists.This command is still running for hours.Since it builds the search index, I don't expect that this would make the mails available on the webpage. I agree, that won't make the mails available on the webpage. If you're using the default Whoosh search engine, "hours" is not unexpected. Elasticsearch is much faster and Xapian faster still. What do you see in Postorius - Settings -> Archiving for the lists whose messages don't show? -- 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

Re: Django administration - User permissions

by Mark Sapiro

On 5/29/24 11:18 AM, advorkin(a)cs.princeton.edu wrote: > > So, just to be clear, in order for someone to have an ability to create/delete a mailing list, they must be a superuser? The reason I'm asking is for security purposes and making sure that specific user has only minimal access. Currently that's true. It should be possible for a domain owner to create a list in that domain, but currently I don't think it is. > What are those Django permissions for...? Is there a use for them? Those permissions correspond to database tables, and I think they allow actions on those tables through the django admin UI. They do not (currently at least) allow any Postorius or HyperKitty UI actions. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

Re: Member Issue Discovered

by Mark Sapiro

On 10/28/20 1:42 PM, Brian Carpenter wrote: > > This is a bug with Affinity which I have scheduled to be fixed. However > I am confused. Data is completely removed from Mailman 3 core when you > delete the account via Postorius but not when you unsubscribe from a list? Why do you keep bringing this up? The current design of Mailman core does not remove the user when the user unsubscribes from a list, even if it is their only subscription. We know you don't like this behavior, but there are reasons for it. On the other hand, when a user removes their account, the circumstance is different and we do remove the user's information in this case because that's what the user asked for. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

Re: changing the main template for subscriptions and more

by Paul Paulchen

Hi Mark, thanks for your advice. Unfortunately we need some more clues. First of all, we are using mailman docker by maxking - https://github.com/maxking/docker-mailman Our version: Mailman Core Version - GNU Mailman 3.3.5 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.8.10 (default, May 6 2021, 06:30:44) [GCC 9.3.0] We put an example footer.txt into the templates folder as you mentioned: mailman3_core => var/templates/sites/de/list:member:regular:footer.txt Mailman user can read them Created a new list, restarted the docker-container, but it always showed the default footer.txt and not our example footer.txt from the templates folder. Any guesses or clues? Where is this default footer.txt hiding anyway? Changing languages in postorius works fine and it alters between english, german etc... just won't use our custom footer.txt Much appreciate your effort helping people!

3 years, 4 months

Re: Where does sender postorius@ come from?

by Jens Günther

Thank you for your reply. Am 07.06.23 um 23:03 schrieb Odhiambo Washington: > The addresses are defined in Django settings if I'm not mistaken. The more important question would be, where :-) since I already checked if I can set it to something alse, I might need a hint where exactly I can find it. In the SERVE_FROM_DOMAIN/admin I did not stumble upon it. If you don't know it, no problem, let's just wait for somebody who does, thanks. > And > callout isn't evil. Well, I wasn't talking about evil but bad practise - especially if they bounce the mail only because of this. Why would almost all other mail providers accept those mails!? Good questions with probably a complex answer :-D so let's just stick to the problem and a possible solution. Thanks again. Kind regards, Jens.

2 years

Re: How to set up mailman 3

by Mark Sapiro

On 03/25/2017 04:23 PM, David Krantz wrote: > > I did get things working with the bundler at last. Quite tricky and I have > deactivated archival. But I suspect that I should retrace a bit of that > work and upgrade to the latest versions. I miss a few functions from > mailman2, especially setting a limit for message size to discourage sending > larger files to the list. I also notice that there are no modbits per user > that I can reach from the web as admin. See <https://wiki.list.org/x/17891998> for help in upgrading your bundler install. The lack of the ability to set a member's moderation option from the web UI is fixed in versions later than installed by bundler. Also see <https://gitlab.com/mailman/postorius/issues/127> A list's message_size can't currently be set in Postorius. File an issue at <https://gitlab.com/mailman/postorius/issues/new>. >> Where did you find out about the bundler? I'd like to make sure we steer >> people to the current best recommendations: > > The documentation can be found on several places. The one that is best > formatted is this one. I used a worse formatted version of the same text > but right now I cannot find the link. > > https://mailman-bundler.readthedocs.io/en/latest/ > > I notice that you changed the text on the githlab project. Better. > > Now I have no idea of how upgrading the different components. I might start > from scratch although it probably should be possible to upgrade the parts. > The best option is probably to switch to mailman2, but that has > disadvantages when handling lists for multiple domains if I am correctly > informed and I already have a few domains... See <https://wiki.list.org/x/17891998>. > I also found that sending mails manually (telnet to port 25) with no > headers other than "Subject:" causes the "Held messages" tab to crash with > a 500-error. Log below my signature. This is fixed: <https://gitlab.com/mailman/mailmanclient/merge_requests/16>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 2 months

Re: Separating Lists by Domain

by Abhilash Raj

On Thu, Jan 3, 2019, at 8:19 PM, Stephen J. Turnbull wrote: > Abhilash Raj writes: > > > > Is there a way we can get [Postorius updated] where we can > > > separate lists by domain the way Hyperkitty does? Mark Sapiro > > > refers to this in the following post: > > > > > > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > > You can file an issue at > > https://gitlab.com/mailman/postorius/issues > > Is this feature GSoC-able, or too small? It could be a good first issue for a GSoC applicant, too small to be the project itself. > > Steve > _______________________________________________ > 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/ > -- thanks, Abhilash Raj (maxking)

6 years, 5 months

Re: User settings triggers error

by Mark Sapiro

On 6/18/20 2:23 PM, Mark Dadgar wrote: > > There is definitely something sketchy going on here. As an admin, I am not getting accurate subscription status about people on a list. For example, I search for a list member, find their listing, check the box and click Unsubscribe Selected, and get an error because it turns out that they had already unsubscribed themselves previously. But Postorius thought they were still subscribed. > ... > Could this somehow be related to my recent migration from sqlite3 to postgres? I think it's quite likely that that migration is involved and your database is now corrupted in some way. Exactly how or in what way, I don't know, but it seems likely to me that that's the issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

Mailman-users search results for query "Postorius"