Search results for "Postorius" - Mailman-users

Setting for archiving multi email domains?

by Duane Raymond

Hi again, I have a Debian-postfix-postgres-nginx-Hyperkitty-Postorius setup with a primary domain (e.g. primarydomain.com) and several 'secondary' domains used for email lists (e.g. emaillistA.com and emaillistB.com) When sending emails to a list using the primarydomain.com address, the email is received, sent to subscribers and archived properly. But when it is sent to one of the secondary domains like tes(a)emaillistA.com - the email doesn't seem to be sent and isn't archived - despite it being set to be. What I've tried so far (after searching these archives and looking at the documentation) is to: 1) Adding emaillistA.com and emaillistB.com to the MAILMAN_ARCHIVER_FROM setting in the settings_local.py file (and then restart mailman) 2) Adding emaillistA.com and emaillistB.com to the mydestination setting in the postfix main.cf file (and the restarting postfix). ...I even tried adding to /etc/hosts 127.0.0.1 emaillistA.com and 127.0.0.1 emaillistB.com but removed it as it didn't seem appropriate there. Does anyone have any hits of what else I need to configure to get it working for these 'secondary' email domains? Cheers, Duane

5 years

Re: Post-installation documentation?

by David Newman

On 11/24/21 2:36 PM, Mark Sapiro wrote: > 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. Thanks, will get into this ASAP. Am happy to contribute once I acquire a bit more clue. > > >> 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 Good up to here, but ... hyperkitty_import not found. This wasn't covered in the venv docs: https://docs.mailman3.org/en/latest/install/virtualenv.html or in the web frontend docs [1]: https://docs.mailman3.org/en/latest/config-web.html or in the howto Brian Carpenter (RIP) wrote for Debian 10: https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 Also, I had previously created two other lists under the site admin page. These do not appear in the site's mailing lists page, nor does the list I successfully imported from MM 2.1 appear in the admin page, under mailing lists. > ``` > >> 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/ No. I clicked the archives icon at the top of a Postorious page. This is possibly related to the hyperkitty_import issue above. Thanks again. dn [1] In addition to the web frontend docs, there is also a hyperkitty docs page: https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html I found this page unhelpful. For example it starts with this command: sudo python setup.py install but doesn't say where setup.py resides, or which directory the command should be run from. (And yes, different OSs use different locations. I'd setting for one being named, along with a YMMV disclaimer.) Then this doc goes to database setup, with this example: django-admin migrate --pythonpath example_project --settings settings Again, this is unclear. I don't know what "example_project" is, or in what context it's used here. This doc also describes a different, and less straightforward, import-from-2.1 procedure than Mark described above. It's possible the hyperkitty doc is now outdated. I'd be glad to help bring the various different install guides together and update them -- once I better understand how they work. Thanks.

4 years, 3 months

Re: Problems with New MM3 Installation

by Jeff

Thanks Mark and Abhilash (who responded separately). I have worked out all the issues I was having and now the list is running smoothly. The trick for POSTORIUS_TEMPLATE_BASE_URL with uwsgi was "http://[hostname]/mailman3/ <http://[hostname]/mailman3/>“. I appreciate all the help I’ve received from this mailing list. > On May 11, 2021, at 11:43 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 5/11/21 7:46 PM, Jeff wrote: >> >> I really appreciate your assistance. New messages are now being archived as expected, but I still have a few small remaining issues to work out with my MM3 installation: >> >> 1) some emails that arrived before I got the archive working are still sitting in: >> >> /usr/local/mailman3/mm/var/archives/prototype/[listname]@[domain]/new >> >> Strangely this includes at least one email that was archived. Should this directly be cleared as messages are archived? Is there a way to force it to be cleared? > > /usr/local/mailman3/mm/var/archives/prototype/[listname]@[domain] is a > collection of messages in maildir format. This is how the prototype > archiver stores messages. This has nothing to do with HyperKitty. It is > a separate archiver. If you don't want messages to be stored there, you > can disable the prototype archiver for the list by unchecking prototype > in Postorius -> Settings -> Archiving -> Active archivers or disable it > entirely for the installation by setting > ``` > [archiver.prototype] > enable: no > ``` > in mailman.cfg > >> 2) Some messages that arrived while I was having other problems with the setup have been stored in: >> >> /usr/local/mailman3/mm/var/queue/shunt >> >> What should I do to get these messages processed? > > > Assuming the issues that caused them to be shunted have been fixed, just > run the command > ``` > mailman unshunt > ``` > >> 3) Similar to above, some messages are in: >> >> /usr/local/mailman3/mm/var/queue/bad >> >> How can I get these messages processed? > > > First examine the messages with > ``` > mailman qfile /usr/local/mailman3/mm/var/queue/bad/<file> > ``` > To be sure you want them. Also examine mailman.log for the times they > were stored in the `bad` queue. You are looking for 'Skipping and > preserving unparseable message: <file>' and/or 'SHUNTING FAILED, > preserving original entry: <file> messages and you want to determine > which runner preserved the message. There may be a 'whichq' entry in the > message's metadata in which case, that's the answer. > > Once you have determined the queue, you can just move the .psv file from > the bad queue to the appropriate queue, renaming it from .psv to .pck in > the process. > > >> 4 Modified the template for “list:admin:action:post” through Postorious and emails that arrived after that were put in the “shunt” queue. I traced this problem to POSTORIUS_TEMPLATE_BASE_URL. By default, it is set to "http://localhost:8000 <http://localhost:8000/>” which is where uwsgi is listening. However, uwsigi is listening for uwsgi:/ not http://. Should I change POSTORIUS_TEMPLATE_BASE_URL to “uwsgi://localhost:8000 <uwsgi://localhost:8000>” or keep http but make it something else? > > > I know little about uwsgi. setting it to `uwsgi://localhost:8000` might > work. You could also set it to the base URL that a user would use to > access the web UI, e.g. `https://example.com` and that would presumably > be proxied to uwsgi. For example, on the server for this list we have > ``` > POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.mailman3.org' > ``` > which gets proxied to gunicorn, but the idea is the same. > > -- > 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 > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 10 months

Re: timezone in hyperkitty

by matthew_saunders＠harvard.edu

Mark Sapiro wrote: > On 6/29/20 12:18 PM, Marco Marinello wrote: > > I'm expirencing the same behaviour in Postorius. Is > > it possible to set a default timezone for new users? Already set it in settings_local.py > > but not having any effect, still seeing "Africa/Abidajin" in new users. > > Do you mean the users time zone as displayed in the user's profile? This > is a Django setting and the default should come from the TIME_ZONE > setting in settings_local.py, at least if USE_TZ is set True I'm seeing the same behavior on my development site, and I was even able to reproduce this when I created my account on this very site moments ago using OAuth. If you check the django_mailman3_profile table in the DB, I expect you'll see that my timezone record is blank (since I haven't touched it from the Accounts page). FWIW, it's empty... not NULL, since there's a not-null constraint on this field. Is it possible to have this set to a default (non-empty) value somehow? TIME_ZONE & USE_TZ isn't doing it.

5 years, 8 months

Mailman Core 3.3.2 is now out

by Abhilash Raj

Hi Everyone, I am pleased to announce that with a week long delay from the planned date, GNU Mailman Core 3.3.2 is now finally out. This release includes both bug fixes and some new features. Some notable changes include: - Support for inviting users to join mailing lists. - New adddmembers, delmembers and syncmembers command to manage membership from CLI. - Addition of new REST API endpoints that return the count of held messages and subscription requests of much faster page loads in Postorius. - Addition of support for filtering in some API endpoints like Members and Subscription requests. - Support for address= option in email join command to subscribe an address other then sending address. - Addition of who email command to lookup memberships. - Expose emergency field for MailingList resource in REST API. - Several bug fixes to support new major version of libraries like dnspython, flufl.* etc. You can install it using: $ pip install --upgrade mailman The tarball for the release is available at PyPI: https://pypi.org/project/mailman/ Finally, many thanks to all the contributors who have helped make this release a success! -- Abhilash Raj (maxking) on behalf of Mailman Core team

5 years, 4 months

No Archives

by Odhiambo Washington

I am working on a migration from MM2 to MM3. My MM2 lists are domiciled at https://lists.kictanet.or.ke/ To work on the web UI for MM3, I created a subdomain - mm3-lists.kictanet.or.ke. I have mostly done everything, including importing the archives. However, when I access https://mm3-lists.kictanet.or.ke/archives/, it's all empty. However, when I visit https://mm3-lists.kictanet.or.ke/mailman3/lists/, I can see my list. In Postorius, the site name is lists.kictanet.or.ke (same with mail domain). I have SITE_ID = 3 in both settings*.py and have restarted both Apache and Gunicorn. Could this be due to the fact that I am accessing the site using a domain name different than what the actual site is? Or there is something minor I am missing? PS: I am wondering also why SITE_ID=3 when I only added one site, besides the default example.com. If need be, I am willing to blow away the whole virtualenv and start afresh. It's a good step towards mastering the installation of MM3 :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 2 months

Re: Moderator e-mails only going out once a day

by Stephen J. Turnbull

Joe, It may help to have more information about what your system is like. Specifically: 1. Did you install Mailman from our source distribution, from PyPI, or from some other source? 2. Did you install Mailman in its own virtual environment? 3. When you run 'mailman info', does the output make sense? Especially, is the configuration file (mailman.cfg) in the directory (usually /etc/mailman3) you expect? 4. How do you control the Mailman processes? Using systemd's systemctl utility, SysV init scripts, or the 'mailman' and 'mailman-web' utilities? If you are not using the systemd or init utilities, what is the current directory when you start or restart Mailman? 5. Is the virgin runner running? (ps aux | grep virgin) Are there messages stuck in queue/virgin or elsewhere in queue/*? Especially queue/shunt and queue/bad. As long as I'm asking, may as well check these as well: 6. What versions of Mailman applications (mailman, Postorius, HyperKitty, mailmanclient, django-mailman3) are installed? 7. What version of Python are you running Mailman under? 8. What is the operating system?

11 months, 2 weeks

Re: Problems with mailman core translation and other details

by Mark Sapiro

On 2/6/24 2:41 PM, celi--- via Mailman-users wrote: > It´s the case below: the pair msgid/msgstr seems to be OK, but this particular sentence is not being translated. > > #: templates/postorius/lists/summary.html:88 > #, python-format > msgid "" > "\n" > " To subscribe you can send an email with 'subscribe' in the" > "subject to\n" > " <a href=\"mailto:%(address)s?subject=Subscribe\">" > "%(address)s</a>\n" > " or use the form below:\n" > "" > msgstr "" > "\n" > " Para se inscrever você pode enviar um e-mail com o assunto" > "'subscribe' para\n" > " <a href=\"mailto:%(address)s?subject=Subscribe\">" > "%(address)s</a>\n" > " ou use o formulário abaixo:\n" > > What am I doing wrong? Or what can I do to make things suitable? Is the rest of that page translated appropriately? -- 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

Re: configuring postfix local recipient table

by Odhiambo Washington

On Wed, Apr 23, 2025 at 5:56 PM Alexander Inzinger-Zrock via Mailman-users < mailman-users(a)mailman3.org> wrote: > **System Key Data** > OS: Debian 12 > mailman: GNU Mailman 3.3.10 (Tom Sawyer) > Python: Python 3.11.2 (main, Nov 30 2024, 21:22:50) [GCC 12.2.0] > Method: Python Virtual Environment Installation > > > Ahoi, > > i am trying to configure a mailman3 instance > to replace a mailman2 installation (both on different hosts). > The mm3 instance is actually not reachable (Incoming) but can send > (Outgoing), > as is the desired state to be (we intend to swap IPs during change of > systems). > > A. Verify Incoming > > To verify that emails send to the MTA (postfix) get properly handled > and handed over to the mm3-instance i tried to substitute incoming email by > > a) swaks utility [1] (fail) > b) telnet utility [2] (fail) > c) command ''mailman inject'' [3] (success) > > With c) i copied a former generate testmail-file to the mm3-host > and injected it directly to my testlist (leaving out the MTA). > > With a) and b) i tried to hand over a testmail via CLI to the MTA (postfix) > what resulted in the error: > > "Recipient address rejected: User unknown in local recipient table" > > > B. /etc/postfix/main.cfg > > A search in mailman-users(a)mailman3.org archives [4] pointed me to the > configuration of postfix as MTA [5], especially settings with the > 'local_recipients_maps' parameter that should be set like [5]: > > local_recipient_maps = proxy:unix:passwd.byname $alias_maps > hash:/path-to-mailman/var/data/postfix_lmtp > > what i did / already had done. > > > C. aliasing, restarting services and test without , > > I then restarted postfix, rebuilt the postfix aliases (command > ''newaliases'') > and rebuilt the mailman aliases (command ''mailman aliases''), > even tried with space-separation instead of coma-separation [6], > testet again with same result. > > > D. empty /opt/mailman/mm/var/data/postfix_lmtp > > and then i just found out that my postfix_lmpt file was empty > (that i believe to be the the place from where the hastables take their > input). > > > Questions: > > 1. could somebody suggest a way, an entry should occur in postfix_lmtp? > 2. What would be the appropriate order to manually generate aliases? > first: postfix-command ''newaliases'' and > second: mailman-command ''mailman aliases'' > or reverse? > 3. finding traces [7] of a file called postfix.cfg > i can't find it (anymore) in the official installation instructions. > Is that file (still?) necessary regarding: > 3.1 parameter for default lookup table type > 3.2 pointing to command ''postmap'' > 4. to what user should the command ''postmap'' be available [8]? > > > Any pointer to manuals or examples i may have missed or ideas > on any of those 4 questions would be greatly appreciated. > There is just one definitive manual: https://docs.mailman3.org/en/latest/install/virtualenv.html If this is NOT what you followed, then my suggestion is you start over afresh and follow the steps without skipping anything. You can test Mailman3+Postfix with a phony domain name. As long as the domain name is local, deliveries to the list should happen. Try and apply the KISS principle. For instance, you could submit a post to Mailman by: echo "This is a test post" | mail -s " Testing ML Delivery" listname@phony-domain-name If submitted from an address you have subscribed to the list, you should see it in the archives of that list. Otherwise, you can see it in Postorius under held messages. The transaction details will be in mailman.log as well as your Postfix logfile. -- 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]

10 months, 3 weeks

Out there plugin idea for tech cost sponsorship

by Stephen J. Turnbull

Steven Clift EDem writes: > Figuring out how to raise money to cover server costs without selling out > our members with targeted social media advertising, was a continuous > challenge. I understand why you object to the kinds of advertising you might see via Google, Amazon, or Facebook, but targeted advertising is the way to go if you want to minimize annoyance and still get revenue. You just want to target something different (don't ask me for specifics, you know your business, but basically you want advertisements your customers / clients / members find informative and useful rather than targeting revenue from advertising). > So here is the question - do you think a Mailman > add-on/plugin/module/whatever you'd call it that allowed list admins to > reward their new subscribers to email lists with custom themed "for good" > discounts would be of interest to many??? Mailman 3 allows you to provide custom templates for both Postorius (how new subscribers sign up by web) and for various emails. It would be easy to provide custom templates for each list for your purpose, for example if all users get the same "coupon code", or get a random code. There isn't really an opportunity for a "plug in" here, though, because presumably you really want carefully designed templates for *your* business (or NPO), and probably with some attention paid to the group your business is affiliated with. Once you have the template, and maybe a little custom code, you're done, nothing left for the "plug in" to do. If you're thinking of something more dynamic, eg, checking profiles of existing Mailman users who sign up for new subscriptions, again, I don't see an opportunity for plugins, because Mailman's current profiles are not going to support personalized rewards. So you'll need to design your own database for that, and unless there's a standard database for that (ie, with the kinds of market share that PostgreSQL and MySQL have with Mailman systems), that's all going to be custom code that nobody else uses. > Normally, we (GoodCarts) reward people post-checkout with discounts in > reciprocity powered circles of online stores. As I understand that, you (GoodCarts) are providing the user database services at least to the extent of ordering and billing records. So you'll be eating your own dogfood here, but probably similar services do their own thing, so your code would be unlikely to be of use to them, right? > The way I could see working with email list providers is basically adding > an affiliate marketing style commission where purchases with > post-subscription rewards would go to the partner based on results. I think Mailman provides a good platform for that kind of thing, but it's going to require a ton of additional APIs to do well. > Our view is that exclusive discounts as rewards post transaction (purchase, > email list subscription, volunteer sign-up, event registration, online > petition signature, etc.) is far better than plastering ads > everywhere. If there's a dominant database application for keeping track of these things, a plug-in architecture might work. But if not, every such business is going to need to make its own extensive customizations, and it's really going to be more of a direct-mail application than a mailing list manager, which is fundamentally for mass mailings, maybe with a bit of personalization of mailings. Stock Mailman only does direct mail for the email verification dance and subscription welcome messages. You could easily use the latter for this one event of subscription. But Mailman doesn't know anything about "volunteer signups" or "event registration", etc, and teaching it to do that part is likely to be painful and make maintenance of the software difficult. My recommendation would be to use a separate application to manage the rewards system, and add only a couple of additional rules or handlers to trigger rewards (by messaging the rewards manager) on specific events that Mailman tracks anyway. Steve

3 years, 2 months

Mailman-users search results for query "Postorius"