Search results for "Postorius" - Mailman-users

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, 5 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, 5 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, 6 months

changing the main template for subscriptions and more

by Jens Günther

Hey there, in Mailman2 there was a simple link in the moderation-emails, with which I was able to open directly the "held-messages". I know how to manually integrate such a link with the variables of mailman (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) But: How can I change the template for all the lists (respectively maildomains/webdomains) so that I don't have to do this manually for all lists? I searched a bit for the corresponding template, but didn't find it. At the end it only says the following: "At your convenience, visit your dashboard to approve or deny the request." -> here I would like to add the following: "At your convenience, visit your dashboard to approve or deny the request: https://$domain/postorius/lists/$short_listname.$domain/held_messages" Or if someone sees another possibility to get us on the right track, it would be more than welcome, thank you! Kind regards, Jens.

4 years, 9 months

unique key violation because of case sensitivity of email address

by Jörg Schulz

After updating to the most recent version of mailman-web, the migrations script issued an error: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount mailman-web | Running migrations: mailman-web | Traceback (most recent call last): mailman-web | File "/usr/lib/python3.12/site-packages/django/db/backends/utils.py", line 89, in _execute mailman-web | return self.cursor.execute(sql, params) mailman-web | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ mailman-web | psycopg2.errors.UniqueViolation: duplicate key value violates unique constraint "account_emailaddress_user_id_email_987c8728_uniq" mailman-web | DETAIL: Key (user_id, email)=(27, John.Doe(a)mynicedomain.de) already exists. mailman-web |(...) Digging into the db, I found the duplicate to result from a duplicate entry using john.doe(a)mynicedomain.de Obviously, the process that originally created the entry, took case sensitivity literally which doesn't seem to be the case any longer for the migration script. I fixed this by removing one of the duplicates hoping no further errors will come up.... What would have been the better approach?

1 year, 9 months

Re: "To:" header field

by Mark Sapiro

On 08/05/2018 06:20 AM, Asaf Ohayon wrote: > > Comparing to Mailman 2.1, which we recently upgrading from, > and didn't got spammed, the "To:" field was set to the actual reciever, > While in Mailman 3.2, the "To:" field is set to the list's address. > > How can this be configured ? This is full personalization. See <http://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/cook-head…>. This setting is not yet exposed in Postorius, so you have to set it via 'mailman shell'. E.g. $ bin/mailman shell -l test(a)msapiro.net Welcome to the GNU Mailman shell The variable 'm' is the test(a)msapiro.net mailing list >>> m.personalize <Personalization.none: 0> >>> from mailman.interfaces.mailinglist import Personalization >>> m.personalize = Personalization.full >>> m.personalize <Personalization.full: 2> >>> commit() -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 7 months

Re: Confirmation emails to Users has wrong domain name (example.com!)

by Mark Sapiro

On 10/3/21 12:47 AM, Odhiambo Washington wrote: > On Sat, Oct 2, 2021 at 8:58 PM Mark Sapiro <mark(a)msapiro.net> wrote: >> The SITE_ID setting affects the domain displayed at the top left of >> HyperKitty pages. Is this the correct domain? >> > > No. Mine is showing example.com OK. If I understand correctly, the subject of this thread notwithstanding, your only issue is the domain example.com displayed on the upper left of Hyperkitty web pages, and when you go to the domains view in Postorius, you see your domain with SITE_ID = 2. You said you edited settings_local.py to set SITE_ID = 2. Did you restart Apache after this? ``` touch /usr/local/mailman/etc/wsgi.py ``` should be sufficient to reload Django without restarting Apache. Have you done one of these things? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

Re: How to store additional information about lists?

by Mark Sapiro

On 5/25/21 12:28 AM, Stephen J. Turnbull wrote: > Andreas Barth writes: > > > private: hand-selected people, think about e.g. board or steering > > committees internal discussions. Of course, the archive (if there is > > any) should be restricted to the actual members. Posting to these > > lists is currently not restricted, so no derivation needed from the > > current set in postorius. > > This is already possible by requiring admin approval, or by setting > the ban list to something that matches everything like "^.". The ban list can't be used in this way. A banned address can't be subscribed by any means including admin action. And even if an admin temporarily removes the ban, subscribes the address and then restores the ban, the now banned member can't post. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

Re: Posterious membership listing for non-owner/moderators?

by Mark Sapiro

On 3/11/21 4:58 AM, Duane Raymond wrote: > Hi, > > I'm configuring my new mailman3 lists and one option I wish to use is a membership listing (which list members can opt-in/out of via their preferences). The only problem is, via the web interface (Posterious / Hyperkitty) I can't find that listing when logged in as an ordinary member. Am I missing something or is this not built in yet? > > I have my test list setting under List Identity -> Members List Visibility set to "Only mailinglist members", but all I can find in terms of members is the side-listing of posters to the list/thread. > > (as usual before asking the question I explored a lot and searched the archives/documentation). Maybe you should also check issues. This is <https://gitlab.com/mailman/postorius/-/issues/369> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

Re: Hyperkitty performance problem

by Odhiambo Washington

On Fri, Nov 22, 2024 at 9:59 AM Tobias Diekershoff <tobiasd(a)fsfe.org> wrote: > Hey all, > > so far we could not find the reason behind the problem. However while > reviewing the installation process one one our team mentioned that he > read the installation instructions for Hyperkitty different then the > rest of the team. > > Are Mailman3/Postorius and Hyperkitty supposed to run in separated > databases, or are they supposed to use the same database? > > Thanks in advance for clarification! > Tobias > The official documentation specifies two DBs - one for Mailman Core and the other for Mailmanweb. As far as I know, there are no conflicts in the tables so you could use the same DB for both. -- 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, 4 months

Mailman-users search results for query "Postorius"