Search results for "Postorius" - Mailman-users

at the finish line of mailman3 docker, but can't sign in.

by bob B

I am trying to setup mailman3 in docker and have some questions, I can see the finish line :) i hope. I start my images and I can access the web,http://Servername.domain.com/postorius/lists/ and no list are there of course, but How do i sign in? I click the forget link and I have to enter in a email address. I put in the email address I added to the docker-compose.yaml but that does not wrok. I have these setup in the .yaml file. MAILMAN_ADMIN_USER: The username for the admin user to be created by default. MAILMAN_ADMIN_EMAIL: The email for the admin user to be created by default. I found this url http://Servername.domain.com/admin/login However I never set a password and here is no forget button, Basically once I have docker installed, and mailman3 up and no lists are available, How do I setup or/and sign in as admin? Also In docker how can I test sending mail? the command "mailman-web sendtestemail youremailid@domain" from the mailman-web container does not work. How can I make sure my containers can send and receive mail?

4 years

404 on fresh install (Debian11)

by thomas＠lydra.fr

Hello, very new to mailman3, I used to manage mailman2 on a Debian 10 server. The server has been upgraded to Debian 11 and mailman2 disappear… I try fresh install of mailman3, prerequisite to data migration, but without success. If some can help, I would be really greatful. Here is my path: - `mailman3-full` install with apt. MySQL config since I have this DBMS - `python3-pymysql` install with apt after seeing errors in logs - Apache2 configuration (other virtual hosts are present) ```apache2 <VirtualHost *:80> ServerName newsletter.mydomain.tld Alias /static /var/lib/mailman3/web/static Alias /favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico DocumentRoot /var/lib/mailman3/web/static <Directory "/var/lib/mailman3/web/static"> Require all granted </Directory> ProxyPassMatch ^/static ! ProxyPass / http://localhost:8001/ ProxyPassReverse / http://localhost:8001/ ErrorLog ${APACHE_LOG_DIR}/newsletter_error.log CustomLog ${APACHE_LOG_DIR}/newsletter_access.log combined </VirtualHost> ``` And now I have a 404 answer when consulting my http page. When trying to access `/static` sub-path, I get `Cannot serve directory /var/lib/mailman3/web/static/admin/: No matching DirectoryIndex found`. I also tried `ProxyPass / unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost` but also fails with `No protocol handler was valid for the URL / (scheme 'uwsgi')` I am a bit lost with that. Thanks for your help

2 years, 4 months

Import old mails into list

by Stephen J. Turnbull

franklin(a)slat.org writes: > Import list data (from 2.1): > https://docs.mailman3.org/projects/mailman/en/release-3.0/src/mailman/comma… You should have a "mailman" command, with "mailman import21 -h" giving brief usage instructions. I gather this succeeded in importing your list configuration(s). > How do I import an archive into a new mailing list: > https://wiki.list.org/DOC/How%20do%20I%20import%20an%20archive%20into%20a%2… > The second is very old, written in 2007, and now I even can't find > bin/arch commands. Mailman 3's initial public release was at the end of April 2015. Any information dated before that is likely dangerously wrong for recent Mailman 3. > And when I tried `django-admin hyperkitty_import` it even told me > "Unknown command: 'hyperkitty_import'". django-admin is somewhat finicky because it is intended to serve multiple Django instances, applications, and projects on the same host. It depends on where you start it and which settings.py you feed it. On Debian, you should install the "mailman3-web" package, which provides the "mailman-web" command which integrates django-admin functions from HyperKitty, Postorius, and django-mailman3. "mailman-web help hyperkitty_import" should tell you how to import your archives. Steve

2 years

list footer questions

by Mohsen Masoudfar

Hi, This seems to me like basic simple questions, I have tried FAQ and other resources, with not much success. I have two questions: 1. When I send an email to a list, in gmail and yahoo I see the following text with the links at the end of the email body: _______________________________________________ Testlist_dmark1 mailing list - listname(a)domain.tlb<mailto:testlist_dmark1@newlistserv.aaas.org> To unsubscribe send an email to listname-leave(a)domain.tlb In<mailto:listname-leave@domain.tlb%0b%0bIn> outlook this is added as an attachment in the form of a TEXT file, when you open it, you see the same text. Question: Is there a way to change this, that it looks in outlook the same way as it appears in gmail/yahoo? I know MS does it own stuff sometime and we have no impact on that, but I was thinking maybe we might change the footer in a way that outlooks sees that as part of email body. 2. How may I change the format and the text in footer? I was expecting it under list > setting, in postorius, but I could not find it. Best regards Mohsen Masoudfar Lead System Analyst, IT Operation American Association for the Advancement of Science 1200 New York Ave, NW, Washington, DC 20005 202-326-7087

5 years, 2 months

Re: What's the difference between (purpose of) reject and ignore

by Denis Bitouzé

Le 26/06/22 à 10h58, Stephen J. Turnbull a écrit : > denis.bitouze(a)univ-littoral.fr writes: > > > IMHO, even in English, “Reject” and “Discard” are not self-explanatory. > > I agree, but those are the traditional terms to distinguish "return to > sender without distributing" and "silently delete without > distributing" in the email community, and specifically in Mailman. > I don't have better one-word options ("Discard" is pretty close to > optimal, for one thing). If you ask, any experienced admin or > moderator can tell you what that means, and more important the > implications for third parties. I doubt you will forget the meaning > now that it has been explained. Indeed. > So I don't think changing the button labels is a good idea. OK. > Perhaps some additional help text should be added, although I'm not > sure if we have that capability already or if we would have to revise > templates and CSS or even add code. I understand. Anyway, another solution would be a small question mark being a link to: ┌──── │ .../postorius/lists/.../settings/message_acceptance └──── :) -- Denis

3 years, 1 month

Re: Implicit destination

by Mark Sapiro

On 08/26/2018 12:54 PM, David Krantz wrote: > > I have a spam-problem like anyone else. Most of the spam my listserver > receives has some kind of impilict destination so the implicit rule > catches most of the spam that way. This is fine. What is not so fine, > however, is that this results in a moderation message to the sender. > I'd like to stop that so that the spammer has no confirmation that the > mail was received. That is not the issue. Sending the held message notice to a spammer, if it reaches the spammer, is probably inconsequential. The issue is that virtually always in spam the sender address is either undeliverable or is the address of an innocent 3rd party. Sending these notices to innocent 3rd parties is called backscatter and is a bad thing. To avoid this backscatter, you can set the list's respond_to_post_requests attribute to False. There are two problems here. One is this setting is not currently exposed in Postorius, and the other is this will also stop desired held message notices such as those from list members. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 11 months

Re: Advice

by Jerry Koutavas

Apologizes if there is a better list to post this request to - thank you From: jkoutavas(a)ascii.com [mailto:jkoutavas@ascii.com] Sent: Tuesday, November 19, 2019 8:33 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Advice We are seeking a consultant to help migrate us from Mailman 2.1.9 to 3 > Mailing list (Core + Postorius) + web-forum (Hyperkitty). Any recommendations is appreciated - Jerry _______________________________________________ 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/ ________________________________ Total Control Panel Login<https://asp.reflexion.net/login?domain=ascii.com> To: jk(a)ascii.com<https://asp.reflexion.net/address-properties?aID=10188568&domain=ascii.com> From: mailman-users-bounces+jk=ascii.com(a)mailman3.org<mailto:mailman-users-bounces+jk=ascii.com@mailman3.org> Message Score: 50 High (60): Pass My Spam Blocking Level: Medium Medium (75): Pass Low (90): Pass Block<https://asp.reflexion.net/FooterAction?ver=3&bl-sender-address=1&hID=395558…> this sender / Block<https://asp.reflexion.net/FooterAction?ver=3&ent=1&bl-sender-address=1&hID=…> this sender enterprise-wide Block<https://asp.reflexion.net/FooterAction?ver=3&bl-sender-domain=1&hID=3955588…> mailman3.org / Block<https://asp.reflexion.net/FooterAction?ver=3&ent=1&bl-sender-domain=1&hID=3…> mailman3.org enterprise-wide This message was delivered because the content filter score did not exceed your filter level.

5 years, 8 months

Re: Remove ALL Members button - was: Re: Setting base_url for the domain to use it in the templates.

by Odhiambo Washington

On Thu, Jul 11, 2024 at 6:28 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/10/24 10:46 PM, Odhiambo Washington via Mailman-users wrote: > > > > I find the unsubscribe_all button quite scary! I have never used it > though, > > so I am not quite sure about its behavior. What scares me > > is the possibility of clicking it and then in one fell swoop you've > removed > > ALL the members without a "confirmation". > > See the thread at > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > and the issue at https://gitlab.com/mailman/postorius/-/issues/545. > > Bottom line - there is a confirmation. Try it, perhaps on a test list if > you're really scared. > Will do that test :) -- 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

Re: Mailman installation results in KeyError: 'env_py'

by Abhilash Raj

On Sun, Oct 22, 2017, at 01:28 PM, Marvin Gülker wrote: > Hi, > > Am 22. October 2017 um 11:47 Uhr -0700 schrieb Abhilash Raj > <maxking(a)asynchronous.in>: > > As Simon mentioned, try using DEBUG=False, if you don't already have > > that. With DEBUG=True, you should see emails printed in a `emails` > > directory under `mailman-suite_project` directory. > > Bingo! Man, I was not seeing the forest for the trees. I should have > peeked inside that emails folder. And yes, changing the DEBUG flag > resolves the problem and emails now go out as they should. My bad! > Thank you! > > > > That being said, the enormous number of configuration files to consider > > > and dozens of cross-references to other pages in the docs make the > > > installation guide hard to follow; it also lacks logical structure in my > > > opinion, when it refers to parts of the configuration which are later > > > explained. For someone like me who never programmed a Django application > > > (Ruby dev) this is all pretty cryptic. Especially, that some parts of > > > information are on <http://docs.list.org/en/latest/index.html> whereas > > > other parts are scattered over readthedocs.io makes it very > > > complicated. > > > > There are only two primary configuration files (there are a few more for > > finer configurations ;-): > > Mh, mailman.cfg, settings.py, and hyperkitty.py are three. But I agree, > I exaggerated. > > > All the settings mentioned in the documentation go to either of these > > files, except, when configuring web server and mail server. Please open > > an issue[2] if it is not clear where a particular configuration snippet > > goes and we will fix it. > > I'll open an issue later; for now off the top of my head so I won't > forget I came over these problems with the docs: > > * The linked installation guide for Sass > (<http://sass-lang.com/install>) does not include any C/C++ > implementation you speak of. Fixed, http://sass-lang.com/libsass is the correct URL, not sure why is it not mentioned under `/install`. > * The mailman-suite's settings.py includes a handler for Less, which is > not mentioned in any documentation. I don't think we use `less` anymore, I will confirm this and remove it if needed. It hasn't caused a problem yet, so I am assuming it is never used. https://gitlab.com/mailman/mailman-suite/issues/7 > * It's officially suggested to use the "fhs" filesystem path > layout. It's not documented that you need to create the exact > directories and change permissions accordingly; even worse, if one > uses this layout, Mailman tries to write into /sbin, which only the > package manager is allowed to do. Thus, don't recommend that layout in > <http://docs.list.org/en/latest/config-core.html>. I have been thinking which layout is best and should be used. FHS makes most sense, but it is true that `pip` can't write to `/sbin` and hence it doesn't work if you aren't using a package manager. I have changed the docs to recommend `master` layout which uses the whichever directory the `mailman` command is stored in as `bin_dir`. > * This page: <http://docs.list.org/en/latest/config-core.html> does not > mention that the "postfix_lmtp" and "postfix_domains" files are > *generated* by Mailman. I spend quite some time looking for these > files before I found in the Mailman Core docs that they're generated > and it was not an error in my installation. Added a note about it in the docs under "Configuring MTA" section. > * This page: <http://docs.list.org/en/latest/config-core.html> configures > the LMTP server and the REST API server for the same TCP port > (8024). This clashes. Fixed, thanks! > * This page: <http://docs.list.org/en/latest/config-web.html> should > mention the thing with the DEBUG variable we've successfully worked > through in > this thread. Added a note about it. > * There's no mention of how to create the initial superuser on > <http://docs.list.org/en/latest/>, it is hidden down in > <https://postorius.readthedocs.io/en/latest/setup.html>, where however > there's no mention of the mailman-suite, but some kind of > "example_project". It was unclear to me whether this now applied to me > or not. Added a section about it under http://docs.mailman3.org/en/latest/config-web.html > * <http://docs.list.org/en/latest> contains quite some pip install > commands (duplicated from the postorius/hyperkitty/core docs), but > it's missing "$ pip3 install mailman-hyperkitty", which is only > mentioned in <http://hyperkitty.readthedocs.io/en/latest/install.html> > in the text body (but not as a command block). Added to the installation guide. > * This page: > <http://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html> > uses "configuration: python:mailman.config.postfix" in the > introductory text without explanation, but down in the > Postfix-specific block the directive is missing with no explanation. I > opted to include it, but I don't know whether that's now correct or > not. You only need to specify settings that you want to override from default. "configuration" for Postfix used to be completely blank until recently, when we added support for regex maps along with hash maps in Postfix. The default is set to hash maps and you don't need to specify the configuration if you using it, if you need to use regex maps, you create a new configuration file and point to it under "configuration". I will see how to make that more clear in there. > The overall problem I had with the docs is that they can't be followed > top-down. One has to refer to the subproject docs if something is > unclear, then searching in them until one finds what one was looking for > (even if one doesn't know what one is looking for, as with the superuser > creation command). I totally appreciate the detailed subproject-docs > approach, but you should follow it consequently then. That is, do not > duplicate some information from the subproject docs in the mailman-suite > docs. It creates the impression as if the mailman-suite docs are > complete, which they aren't. Instead, the mailman-suite docs should use > explicit references, for example: > > 1. Do this... > 2. Now follow the procedure outlined in [Postorius Installation link] > 3. Do something else... > 4. Follow the procudedure in [Hyperkitty installation link] > > That way, the Mailman installation guide would be less of a puzzle. > It however might just be me. I apologise if I sound silly. It wasn't silly at all, in-fact you comments were very helpful to improve the documentation. We would like to not make assumptions about pre-requisite knowledge to use Mailman's documentation and it is hard for us developers to do that without feedback. Thanks a lot to you! -- Abhilash Raj maxking(a)asynchronous.in

7 years, 9 months

Mailman issues after re-boot

by Stephen J. Turnbull

Paul Rubin writes: > 'list_unsubscription_requests' not found. > ungettextImportError: cannot import name 'ungettext' from > 'django.utils.translation' > self._stream:Sep 12 10:06:31 mail mailman[31159]: AttributeError: > 'ReopenableFileHandler' object has no attribute '_stream'Sep 12 > Please tell me where to start looking or adjusting. At this point it's not a matter of "adjusting". There are too many errors in too many unrelated places: Mailman, Postorius, and Django. It appears your Mailman installation has been quite corrupted. My guess is in the process of recovering the host you applied OS upgrades to Python and/or reinstalled Mailman components, and the versions are now very much out of sync. Another possibility is that files were corrupted by the crash. As Odhiambo Washington suggests in a parallel post, your best bet is to preserve your configuration files, Postgresql databases, and queue files (if any), wipe your Mailman installation and reinstall from scratch. I'd back up the Postgres database, of course, but Mailman should just "reattach" to it, applying any migrations automatically. I forget whether you need to run "mailman-web migrate" for Django but I'm pretty sure it's idempotent (you did back up Postgres, right?) Steve

1 year, 10 months

Mailman-users search results for query "Postorius"