Search results for "Postorius" - Mailman-users

Re: Your Dashboard

by Mark Sapiro

On 2/11/20 1:27 PM, Allan Hansen wrote: > > Our site has over 50 lists and several moderators are responsible for multiple lists. In addition to a dashboard like described here I would like to have a ‘comment’ field next to each request, so tha the moderator can keep track of the status of each. Our approval process involves multiple steps. > > Time to visit gitlab? GitLab is the one place for feature requests for Mailman 3/Htperkitty/Postorius. Things requested in list posts get lost and forgotten. That said, the more specific you can be in a request, the better. I.e., if you want a dashboard, what do you want on it for, e.g., the site admin, a user who may or may not be an owner of a couple of lists, a moderator of a couple more and a member of still others. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

Re: Held messages page not rendering the message

by peter＠chubb.wattle.id.au

>>>>> "mike-mailman" == mike-mailman <mike-mailman(a)earth.li> writes: mike-mailman> Hi When the list moderator goes to the held_messages mike-mailman> page, they correctly get a list of the held messages and mike-mailman> can accept/reject/discard them mike-mailman> However, clicking on the individual message to read it mike-mailman> doesn't work - it does nothing visible at all. From mike-mailman> debug I can see it requests mike-mailman> /mailman3/postorius/api/list/<list>/held_message/1/ mike-mailman> which returns correctly (and the body includes the mike-mailman> message as expected) - but it never renders it If you installed from the Debain/Ubuntu packages, this is probably https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033072 The fix is to get your web server to pick the correct location for Jquery,js --- se the bug fix. To confirm, turn on the developer tools in your browser and look in the javascript console. Peter C

3 years, 1 month

Re: Installing mailman 3

by Rafael Mora

I did not run the createsuperuser command, have to do that. What about this: Don’t leave the console email backend configured and running once you get to the point where you want to send real emails, though! How do I change the setting to send the emails instead of printing them on the console???? On Fri, Jul 21, 2017, 21:16 Mark Sapiro <mark(a)msapiro.net> wrote: > On 07/21/2017 06:59 PM, Rafael Mora wrote: > > Is there a ´default´ admin account?? > > > It's the user you create with > > python manage.py createsuperuser > > See > < > http://docs.list.org/en/latest/devsetup.html#run-the-mailman-suite-combined… > >. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 8 months

Re: Emergency moderation and clearing out a lot of held messages

by Caballero, Danny (Dan)

I don't understand. We have a single database configured for everything. I don't recall reading anything in the set-up documentation about using more than 1 database for Mailman3. Let me know if I'm missing something! -- Dan Get Outlook for Android<https://aka.ms/AAb9ysg> ________________________________ From: Stephen J. Turnbull <stephenjturnbull(a)gmail.com> Sent: Friday, November 11, 2022, 7:01 AM To: Caballero, Danny (Dan) <dancab(a)caltech.edu> Cc: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Emergency moderation and clearing out a lot of held messages I don't have a helpful suggestion yet but would like to clarify: Dan Caballero writes: > "2022-11-09T18:37:49.106105Z 19100868 [Note] Aborted connection > 19100868 to db: 'mailman3_prod' user: 'mailman' host: '10.6.5.187' > (Got an error reading communication packets)" db: mailman3_prod is the core database, not the Django (Postorius and Hyperkitty, or mailman-web), is that correct?

3 years, 5 months

Re: pending subscriptions lost?

by IEM Network Operation Center (IOhannes m zmölnig)

On 3/14/22 17:03, Mark Sapiro wrote: > On 3/14/22 06:00, IEM Network Operation Center (IOhannes m zmölnig) wrote: > > This is https://gitlab.com/mailman/mailman/-/issues/729 fixed in Mailman > 3.3.5. thanks for comfirming. > > >> - i (as administrator) do not see any "pending subscriptions" (the >> list is setup with a simple "Confirm" subscription policy > > The count badge only counts subscriptions waiting moderator approval. If > you pull down the Subscription requests tab and click Pending > Confirmation you should see them and be able to discard them. hmm. i'm not sure i can follow. my "Subscription requests" tab seems to not have any "Pending Confirmation" section (see attached screenshot). this is with "Postorius Version 1.2.4" (as installed by the mailman3 Debian package). fdsm< IOhannes ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: Subscription requests.png

4 years, 1 month

Re: mailman-users archive search

by Abhilash Raj

On Mon, Sep 9, 2019, at 7:38 PM, Abhilash Raj wrote: > > > On Mon, Sep 9, 2019, at 7:19 PM, Mark Dale wrote: > > Is this list's search function kaput, or is it an issue with MM3, or is > > it me? > > > > *** > > https://lists.mailman3.org/archives/search?mlist=mailman-users%40mailman3.o… > > *** > > Mailman-users search results for query "Postorius" > > mailman-users(a)mailman3.org > > > > 0 messages > > > > Sorry no email could be found for this query. > > Elasticsearch server is down for now, I'll fix it. Should be working now. > > > > > > /Mark > > _______________________________________________ > > 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) -- thanks, Abhilash Raj (maxking)

6 years, 7 months

Re: Ann: Mailman Core 3.3.5 is out

by Eggert Ehmke

Should I upgrade my Mailman 3.3.3 installed from Debian Bullseye? I would have to bypass the Debian installer. Or will there be Debian packages available? Same question for Postorius 1.3.6 Am Mittwoch, 29. September 2021, 05:26:47 CEST schrieb Abhilash Raj: > Hey Everyone, > > I just tagged and uploaded Mailman Core 3.3.5 release. > > This release includes both bug fixes and some new features. A full list of > changes is available here: > > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS. > html#news-3-3-5 > > You can install this version using pip: > > $ pip install mailman==3.3.5 > > The release tarball is available on PyPI as well: > > https://pypi.org/project/mailman/3.3.5/#files > > Thanks to everyone who made this release possible! > > Abhilash > > > On Sep 19, 2021, at 11:02 AM, Abhilash Raj <maxking(a)asynchronous.in> > > wrote: > > > > Hey Everyone, > > > > I just tagged and released Mailman Core 3.3.5rc1 release. > > > > This is identical to 3.3.5b1 in code, the only changes that have been made > > are in utility scripts and testing configuration.> > > You can install this version using: > > $ pip install --pre mailman==3.3.5rc1 > > > > If you want to download a release tarball, you can do so from here: > > https://pypi.org/project/mailman/3.3.5rc1/#files > > > > This is the first (and only) planned release candidate for 3.3.5 release. > > The stable release is planned for next week. > > > > thanks, > > Abhilash > > > > On 9/7/21 12:39 AM, Abhilash Raj wrote: > >> Hello Everyone, > >> I am pleased to announce that Mailman Core 3.3.5b1 is now out. It is a > >> pre-release for 3.3.5, which is slated to come out in 3 weeks from now. > >> I am planning for a 2 week beta period, after which I'll release the > >> first RC and then stable a week after. Right now I am not planning to > >> release a second beta version, but if there are several changes in Core > >> in the next week or so, then I might. This release includes a lot of bug > >> fixes and some new features. It also includes a security enhancement > >> that improves the authentication of REST API by adding resistance to > >> some timing channel attacks. A full list of changes in this version can > >> be found here[1]. > >> [1]: > >> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NE > >> WS.html#news-3-3-5 We have also made improvements in the i18n workflow > >> and now the email templates are updated from the translated messages in > >> the .po files that we get from Weblate. Documentation for translators is > >> available here[2] if you want to help translate Mailman into your native > >> language. [2]: https://docs.mailman3.org/en/latest/translation.html > >> > >> This is a pre-release version, if you want to test it with your setup, you can install it using: > >> $ pip install --pre mailman==3.3.5b1 > >> > >> If you want to download a release tarball, you can do so from here: > >> https://pypi.org/project/mailman/3.3.5b1/#files > >> > >> This release received a lot of contributions from community, which I am > >> really happy about! I'd like to thank everyone who made this release > >> possible!> > > -- > > thanks, > > Abhilash Raj (maxking) > > -- > thanks, > Abhilash Raj (maxking)

4 years, 6 months

Re: cannot bind to lmtp host address through lmtp port(OSError: [Errno 99] error while attempting to bind on address: cannot assign requested address)

by Mark Sapiro

On 10/18/22 11:28, Paul Ssekamatte via Mailman-users wrote: > i have successfully set up mailman3 instance by following the guide at https://gitlab.com/mailman/mailman-suite-doc/blob/master/source/install/vir… and from this mailing list. > my setup uses an alias domain i.e the mail server is different from the lists server. That is not what alias domains are for. You do not want an alias domain. > I have successfully created an alias domain and mailing list through Postorius but I keep getting this error in syslog. > OSError: [Errno 99] error while attempting to bind on address ('xxx.xx.xx.xx', 8024): cannot assign requested address. > Even when I change the port number, I still get the same error > Kindly assist. First, remove the Alias Domain from your domains. > here is my mailman.cfg config > [paths.here] > var_dir: /opt/mailman/mm/var > > [mailman] > layout: here > site_owner: postmaster(a)mail.example.com > > [database] > class: mailman.database.postgresql.PostgreSQLDatabase > url: postgres://mailman:#passwd@localhost/mailman > > [archiver.prototype] > enable: yes > > # For the HyperKitty archiver. > [archiver.hyperkitty] > class: mailman_hyperkitty.Archiver > enable: yes > configuration: /opt/mailman/mm/mailman-hyperkitty.cfg > > [shell] > history_file: $var_dir/history.py > > [mta] > verp_confirmations: yes > verp_personalized_deliveries: yes > verp_delivery_interval: 1 > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > lmtp_host: mail.example.com The above is wrong. You want the default lmtp_host: 127.0.0.1 > lmtp_port: 8024 > smtp_host: mail.example.com smtp_host should be the mail server, not the list host. Is it? > smtp_port: 25 > configuration: python:mailman.config.postfix These next 3 do not belong in mailman.cfg. They are Postfix main.cf settings: > recipient_delimiter = + > unknown_local_recipient_reject_code = 550 > owner_request_special = no and this next one is a Mailman 2.1 mm_cfg.py directive and is not for Mailman 3. > POSTFIX_STYLE_VIRTUAL_DOMAINS= ['example.com'] > > /etc/mailman3/settings.py file is as follows not relevant for this issue. > /etc/postfix/main.cf is as follows > smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu) > biff = no > append_dot_mydomain = no > readme_directory = no > compatibility_level = 2 > smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination > alias_maps = hash:/etc/aliases > alias_database = hash:/etc/aliases > mydomain = example.com > myhostname = lists.example.com > mydestination = $myhostname, localhost.$mydomain, localhost > relayhost = mail.example.com > myorigin = $mydomain > mynetworks = 127.0.0.0/8, 10.0.0.0, 192.0.0.1, [::ffff:127.0.0.0]/104 [::1]/128 > mynetworks_style = subnet > mailbox_size_limit = 4096000000 > #message_size_limit = 2048000000 > recipient_delimiter = + > inet_interfaces = all > #inet_protocols = all > inet_protocols = ipv4 > unknown_local_recipient_reject_code = 550 > owner_request_special = no > virtual_mailbox_domains = example.com You probably don't want this, at least not if the mailman server is example.com > virtual_mailbox_base = /var/vmail > virtual_uid_maps = static:20000 > virtual_gid_maps = static:20000 > transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp > local_recipient_maps = proxy:unix:passwd.byname $alias_maps > hash:/opt/mailman/mm/var/data/postfix_lmtp > relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains > virtual_alias_maps = hash:/opt/mailman/mm/var/data/postfix_vmap and you don't want this virtual_alias_maps. > postfix domains as follows: > lists.example.com example.com > > postfix lmtp as follows: > testlist(a)lists.example.com lmtp:[mail.example.com]:8024 > testlist-bounces(a)lists.example.com lmtp:[mail.example.com]:8024 > testlist-confirm(a)lists.example.com lmtp:[mail.example.com]:8024 The host in lmtp: is the Mailman server. > postfix vmap as follows: > testlist(a)example.com nmutest(a)lists.example.com > testlist-bounces(a)example.com nmutest-bounces(a)lists.example.com > testlist-confirm(a)example.com nmutest-confirm(a)lists.example.com You don't want that at all. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

Re: Verification emails 'helo' rejected

by Odhiambo Washington

On Wed, Oct 16, 2024 at 8:15 AM Greg Newby via Mailman-users < mailman-users(a)mailman3.org> wrote: > Thanks for this, Odhiambo. Unfortunately it doesn't address my situation. > See below: > > > > On Tue, Oct 15, 2024 at 3:21 AM Odhiambo Washington <odhiambo(a)gmail.com> > wrote: > > > > > > > On Mon, Oct 14, 2024 at 10:43 PM Greg Newby via Mailman-users < > > mailman-users(a)mailman3.org> wrote: > > > >> Hi friends. > >> > >> I'm now getting a 500 server error upon signing up a new username on the > >> web-based front end. The username is created in the back end, but the > >> verification email does not get sent. > >> > >> This is GNU Mailman 3.3.9 (Tom Sawyer), venv, Ubuntu 24.04LTS, > PostgreSQL, > >> Postfix > >> > >> Here are the corresponding logfile entries from mailmanweb.log: > >> smtplib.SMTPRecipientsRefused: {'redacted(a)gmail.com': (504, b'5.5.2 > >> <mail>: > >> Helo command rejected: need fully-qualified hostname')} > >> > >> and from mail.log: > >> Oct 14 12:06:26 domain postfix/smtpd[722764]: NOQUEUE: reject: RCPT from > >> localhost[127.0.0.1]: 504 5.5.2 <mail>: Helo command rejected: need > >> fully-qualified hostname; from=<root(a)lists.domain.tld> > to=<root@localhost > >> > > >> proto=ESMTP helo=<mail> > >> > > > > ^^^^ Note the problem isn't the "From:" address. That is being correctly > configured from mailman-web.py and settings.py via the variables below. > > The problem is it's going "To:" root@localhost. I don't know why this is > happening - shouldn't it be going to redacted(a)gmail.com? > > Also, based on settings below shouldn't this be From: > postorius(a)lists.domain.tld > not From: root(a)lists.domain.tld? > > More: > > > > > > >> lists.domain.tld is the domain for Mailman3. I don't know why it's > trying > >> to send email from root@. > >> > >> I've seen places where 'localhost' appears in the Mailman settings > >> (settings.py, mailman.cfg, mailman-web.py), and tried changing them to > the > >> host's FQDN and restarting mailman3 and mailman3-web, but the problem > >> persists. > >> > > > > Find and fix these values to what they should be as explained. > > > > # The sender of emails from Django such as address confirmation requests. > > # Set this to a valid email address. > > DEFAULT_FROM_EMAIL = 'johndoe(a)domain.name' > > > > # The sender of error messages from Django. Set this to a valid email > > # address. > > SERVER_EMAIL = 'johndoe(a)domain.name' > > > > I use listmaster(a)lists.domain.name in my servers. > > > > In the default files via the venv installation, these were already set > properly: > > EMAILNAME='lists.domain.tld' <-- I set this myself > > These were default in settings.py and mailman-web.py: > DEFAULT_FROM_EMAIL = 'postorius@{}'.format(EMAILNAME) > SERVER_EMAIL = 'root@{}'.format(EMAILNAME) > For the venv installation, I rarely hear a mention of mailman-web.py. I only know about settings.py, mailman,cfg and mailman-hyperkitty.cfg files in /etc/mailman3/ Are you really using the venv install? -- 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, 6 months

upgraded Django & flufl.lock now do not receive own postings

by Stephen J. Turnbull

Christian via Mailman-users writes: > Now for some reason I'm not receiving my own postings to the list whereas > before I was. 'Receive own postings' is still set to yes. Is anybody receiving posts? Are you looking at your settings as a list subscriber, or for the address, or for your User? The first one in that list will decide what setting is applied. Most likely all of your settings are set in the User (called "global" in Postorius), but you should check to make sure. How about "receive list copies"? If you're Cc'd on the post as well as being a member of the list, setting that to "no" would prevent you from receiving the message via the list. The three levels of setting applies here too. Otherwise, we need to see logs, please. Also check your spam folder and local filters. Steve

3 years, 7 months