Search results for "sapiro" - lists.mailman3.org

[MM3-users] [SOLVED] Re: Re: multiple sites on a mailman3 server question

by William Oliver

On Wed, 2021-12-29 at 09:21 -0800, Mark Sapiro wrote: > On 12/29/21 8:48 AM, William Oliver wrote: > > > > [snip] > If you are following > https://docs.mailman3.org/en/latest/install/virtualenv.html you have > ``` > location / { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > > } > ``` > in your nginx config and everything goes to uwsgi. What you want is to > put those proxy directives in only the mailman locations as at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > and then configure your document root so other locations are served > from > there. > The problem was more stupid than one might imagine. My browser was caching so no matter what changes I made, it loaded domain/mailman/lists because that was what was cached. When I tinkered with things, I only changed whether or not mailman was loaded after that. I changed machines and used a different browser, and it started working fine. And it worked fine on my regular box once I cleared my browser's cache. It turns out that nginx works like it's supposed to work. Go figure. So, just to make things clear. Here was my goal: www.domain.com <-- go to welcome page lists.domain.com <-- go to mailman later, I'll install roundcube for mail.domain.com This gives me two primary entries in nginx. I'll send www.domain.com to /var/www/html2 and lists.domain.com to /var/www/html (though mailmanweb will kick in before that). Here's the /etc/nginx/sites-enabled file that works. The entry for location/ for the mailman section is different from the one you pointed to, but it is cut and pasted from one of the examples on that site. I can't find it right now, though -- but it works fine, and life is short. Anyway, this works if you clear your browser's cache: **************************************************** ##### paths for www.exampledomain.com ##### #### just goes to /var/www/html2 ##### server { root /var/www/html2; index index.html index.htm index.nginx-debian.html; server_name exampledomain.com, mail.exampledomain.com, www.exampledomain.com; location /{ # try_files $uri $uri/ =404; } ##### added 12/19 listen 443 ssl default_server; listen [::]:443 ssl default_server; ########## ssl_certificate /etc/letsencrypt/live/exampledomain.com/fullchain.pem; # managed by Certbot ssl_certificate_key /etc/letsencrypt/live/exampledomain.com/privkey.pem; # managed by Certbot include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot } ##### this for lists.exampledomain, that turns on mailman server { root /var/www/html; index index.html index.htm index.nginx-debian.html; server_name lists.exampledomain.com; location /{ proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; #proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Server $host; proxy_set_header X-Forwarded-Proto $scheme; proxy_redirect off; } location /static/ { alias /opt/mailman/web/static/; } ##### added 12/19 listen 443 ssl ; listen [::]:443 ssl ; ########## ssl_certificate /etc/letsencrypt/live/exampledomain.com/fullchain.pem; # managed by Certbot ssl_certificate_key /etc/letsencrypt/live/exampledomain.com/privkey.pem; # managed by Certbot include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot } ###### Certbot stuff to force things to 443 server { if ($host = mail.exampledomain.com) { return 301 https://$host$request_uri; } # managed by Certbot if ($host = www.exampledomain.com) { return 301 https://$host$request_uri; } # managed by Certbot if ($host = lists.exampledomain.com) { return 301 https://$host$request_uri; } # managed by Certbot listen 80 ; listen [::]:80 ; server_name www.exampledomain.com lists.exampledomain.com mail.exampledomain.com exampledomain.com; return 404; # managed by Certbot } ********************************************************

4 years, 10 months

[MM3-users] Re: External MTA incoming mail: configuration

by Roland Giesler

On 2024/08/05 19:59, Mark Sapiro wrote: > I see this reply is now moot as you have now configured list mail to > go directly to the Mailman server, but ... > > On 8/5/24 03:44, Roland Giesler via Mailman-users wrote: >> >> In the logs of the MTA I see this however: warning: do not list >> domain fast.za.net in BOTH virtual_mailbox_domains and relay_domains >> >> Mailman creates these entries, but postfix doesn't like it. I don't >> see any mail delivered to the mailman yet. Is this the problem? > > Probably not. It is telling you that mail to the fast.za.net domain > cannot both be delivered to local mailboxes (virtual_mailbox_domains) > and relayed to foreign hosts (relay_domains) > Thanks, yes, I have since assumed that to be the case. > >> In the MTA postfix main.cf: >> >> relay_domains = hash:/etc/mailman3/data/postfix_domains > > >> cat /etc/mailman3/data/postfix_domains >> ... >> >> and also >> >> local_recipient_maps=$virtual_mailbox_maps, >> hash:/etc/mailman3/data/postfix_lmtp >> >> cat /etc/mailman3/data/postfix_lmtp >> ... > > How about > > transport_maps = hash:/etc/mailman3/data/postfix_lmtp I can't remove the $virtual_mailbox_maps entry, since Power-mailinbox (PMiaB) uses that. It may make Mailman3 work, but break PMiaB). > > >> >> Then there's: >> virtual_mailbox_domains=sqlite:/etc/postfix/virtual-mailbox-domains.cf >> >> cat /etc/postfix/virtual-mailbox-domains.cf >> dbpath=/home/user-data/mail/users.sqlite >> query = SELECT 1 FROM users WHERE email LIKE '%%@%s' UNION SELECT 1 >> FROM aliases WHERE source LIKE '%%@%s' UNION SELECT 1 FROM >> auto_aliases WHERE source LIKE '%%@%s' >> >> When I run that query in sqlite3, it returns no records, so I'm not >> sure how this is supposed to work. %s to me means that first >> argument, so is this used in python and then %s is the argument sent >> to this query? > > > See https://www.postfix.org/sqlite_table.5.html > > `%%` is replaced with `%` which is a SQL wildcard matching anything > and `%s` is replaced by the key postfix is looking for, i.e. the > domain that it is asking about. > > So, that query becomes > > SELECT 1 FROM users WHERE email LIKE '%(a)fast.za.net' UNION SELECT 1 > FROM aliases WHERE source LIKE '%(a)fast.za.net' UNION SELECT 1 FROM > auto_aliases WHERE source LIKE '%(a)fast.za.net' > > I.e, it returns true if any user or alias or auto_alias has an address > ending in '@fast.za.net' and if that's true the mail to any > '@fast.za.net' address including list mail will be stored locally. Ah, thank you! I created a ticket at MiaB about this, so I'll post your response there. The %s had be stumped at first, but now it's clear. > > If you really have local users on box2.gtahardware.co.za with > addresses '@fast.za.net' and you want to relay list mail to lists > '@fast.za.net', you need to see > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…. Thank you for that! From that it seems it may still be possible to use PMiaB as my MTA after, but I'll work through that reference and test it and report back.

2 years, 2 months

[MM3-users] Re: Bulk changes to delivery mode and moderation action

by David Newman

On 1/7/22 4:32 PM, Mark Sapiro wrote: > On 1/7/22 3:41 PM, David Newman wrote: >> >> There are 24 messages in the shunt queue, the most recent of which is >> a digest from 0000 hours today. The test messages I sent later today >> are not there. >> >> There are also 13 messages in the out queue. I can't read these as the >> filenames appear to change on every invocation of ls. > > > I suspect an issue trying to connect to the MTA to send the messages. > This can be caused by permission errors. Check permissions on Mailman's > var/templates/* Bingo. This list had regular and digest footer templates with 0644 permissions owned by root:root, and there was an exception and traceback for the most recent message in shunt about the permissions issue. I've changed ownership to mailman:mailman and restarted the mailman3 service. As soon as I fixed this, my inbox filled with test messages... > >>> Are there errors and tracebacks in var/logs/mailman.log? > > > Every message in the shunt queue should have an exception and traceback > logged in mailman.log. > > >> But the Postfix log doesn't show it being distributed to me or anyone >> else. > > > Is there a 'Cannot connect to SMTP server ... on port ...' anywhere in > mailman.log? Yes, lots. This might or might not be a different issue. As I mentioned earlier, the most recent message in shunt was from 0000 hours today. There are many "Cannot connect" messages since then, but none since fixing the issue above. > > >> Oddly, neither of the two list owner emails (me and someone else) show >> this message in the archive via the admin panel. However if I log in >> as the list owner directly to the archives: > > >> https://lists.domain.tld/archives/ >> >> I can see today's test posts if logged in as the list member, but do >> not see the posts if logged directly into the archive as the Django >> superuser. > > > That seems strange, I don't know why the superuser would not be able to > see things in the archive that a list owner or member can. Seems OK now. The superuser sees all posts after the unshunt action. Thanks very much for your help with this. dn > > >> The nondelivery of list mail is more serious than the archive problem, >> though. > > > Archiving is separate from delivery. messages can be archived and still > fail delivery in the out runner which is what's happening here. The > question is why? > > I suspect you have one or more 'Cannot connect to SMTP server ... on > port ...' messages in mailman.log? and I suspect this is a misleading > issue in this case caused by an inability to read some file in Mailman's > var/templates/lists/<list_id>/en directory. > > I also suspect the shunted messages are from some prior condition which > has possibly been fixed, but I can't be sure without exceptions and > tracebacks from mailman.log (should be timestamped the same as the mod > time if the shunted file). You can view them with `mailman qfile` and > unshunt (reprocess) them with `mailman unshunt`. >

4 years, 9 months

[MM3-users] Re: integrating mm3 with postfix / lmtp

by Fabian A. Santiago

On October 25, 2017 9:17:33 PM EDT, "Fabian A. Santiago" <fsantiago(a)garbage-juice.com> wrote: >On October 25, 2017 9:13:20 PM EDT, Mark Sapiro <mark(a)msapiro.net> >wrote: >>On 10/25/2017 05:41 PM, Fabian A. Santiago wrote: >>> >>> No to the domains part and I think virtual alias maps is needed: >>> >>> mail postfix/trivial-rewrite[19445]: warning: do not list domain xxx >>in BOTH virtual_mailbox_domains and relay_domains >>> Oct 25 20:39:19 mail postfix/trivial-rewrite[19445]: warning: do not >>list domain xxx in BOTH virtual_mailbox_domains and relay_domains >>> Oct 25 20:39:19 mail postfix/submission/smtpd[19441]: NOQUEUE: >>reject: RCPT from >>pool-108-53-239-102.nwrknj.fios.verizon.net[108.53.239.102]: 550 5.1.1 >><test123@xxx>: Recipient address rejected: User unknown in virtual >>mailbox table; from=<fsantiago@xxx> to=<test123@xxx> proto=ESMTP >>helo=<[10.0.0.29]> >> >>(above slightly sanitized for return to the list) >> >>The issue here is your list domain cannot be a virtual_mailbox_domain >>or >>a virtual_alias_domain. >> >>I have the same issue on mail.python.org where we have both Mailman 2 >>and Mailman 3 lists @python.org. and python.org is a >>virtual_alias_domain. >> >>I have a group of MRs for a branch that implements "alias_domains" to >>deal with this. >> >>Basically it works by creating another (virtual_alias_maps) >>postfix_vmap >>mapping to map list addresses @python.org to addresses @x.python.org. >>Then the postfix_domains and postfix_lmtp maps have the x.python.org >>domain and there is a patch to mailman/runners/lmtp.py to map the >>x.python.org domain back to python.org. >> >>The various MRs are >><https://gitlab.com/mailman/mailman/merge_requests/202> for the core, >><https://gitlab.com/mailman/mailmanclient/merge_requests/18> for the >>REST bindings used by Postorius and >><https://gitlab.com/mailman/postorius/merge_requests/186> to be able >to >>set an alias_domain via Postorius. >> >>That's not all implemented at mail.python.org. What's there is the >>basic >>Postfix config, a bash script the generate the new mappings from the >>old >>and a simple patch to mailman/runners/lmtp.py. >> >>So, the bottom line is it can be done and it's in process, but it >won't >>really be supported until Mailman 3.2. In the mean time, you just need >>to have a separate domain for your lists that isn't a >virtual_*_domain. > >Ok thanks. At least I have a clear answer now. Any ETA on 3.2 in mind >yet? >-- > >Thanks, > >Fabian S. > >OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC >_______________________________________________ >Mailman-users mailing list >mailman-users(a)mailman3.org >https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Mark, Ok I have it almost perfectly working now having taken your direction and configuring a unique domain not in my email system already. But in my testing, I replied to a subscription confirmation message and received back an undeliverable looping email error message from postfix. Any clues there you can offer? I can post to the list from any email added via the admin console. The test subscriber address was local to my server. From an outside address, same error. Once I registered the new email domain, I reverted my postfix config back to the default suggested by maxking's docker instructions. https://github.com/maxking/docker-mailman Thanks. -- Thanks, Fabian S. OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

9 years

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by David Partain

On Thu, 2021-01-28 at 12:03 -0800, Mark Sapiro wrote: On 1/28/21 5:33 AM, David Partain via Mailman-users wrote: I wrote: I have the same issue, and have changed the configuration in /etc/mailman3/mailman-web.py to: DATABASES = { 'default': { 'ENGINE': 'django.db.backends.mysql', 'NAME': 'mailman3web', 'USER': 'mailman3web', 'PASSWORD': 'xxxxxxxxxxxxxxxxxx', 'HOST': 'localhost', 'PORT': '', 'OPTIONS': { 'init_command': "SET sql_mode='STRICT_TRANS_TABLES'", 'charset': 'utf8mb4', }, } } and restarted stuff, but I cannot tell that it has changed anything. You responded: That should do it. I think the original message should have been saved as a queue entry in Mailman's var/archives/hyperkitty/spool/ directory. That directory has all of the messages sent to that list: # ls /var/lib/mailman3/archives/hyperkitty/spool/ 1611827925.8030825+925c996b9b6020ee18e9a689ce23384855159f77.pck 1611827926.1923075+e728f3c29c1fe6eeeca641314cdba7007cb6e132.pck 1611827925.8917305+d16b7004bdbbef98ce40fb8ee70e492715d1607d.pck 1611827926.2623458+1aac13b50d8e7f32eb14d13e6559656aa8f3bd10.pck 1611827925.9594557+7ad2a910b5ee9142c88f0bf26c60c6df960d4262.pck 1611827926.3488555+04a540651c5f829751518433e1c54168ab63a38b.pck 1611827926.0404096+a5e745f51a9f7d541aeb770a89604be17019f3c5.pck 1611827926.4206145+de861eec6404d0c8f9f8bdb180e29bff2de7c52b.pck 1611827926.1167526+0aa63639a4ec102bf63522827637e75e6a2b092a.pck This is what's expected since the underlying issue isn't yet fixed. Yes, I'm still seeing the errors. When I send mail to a list with a cute emoji, I see the following in /var/log/mailman3/web/mailman-web.log: ERROR 2021-01-28 10:58:45,708 16923 django.request Internal Server Error: /mailman3/hyperkitty/api/mailman/archive (bunch of python errors omitted) DataError: (1366, u"Incorrect string value: '\\xF0\\x9F\\x98\\x8A\\x0A\\x0A...' for column 'content' at row 1") OK. The issue is with your database it doesn't like '\xF0\x9F\x98\x8A' which is a 4-byte utf-8 encoding for a smiley face emoji. The issue is with MySQL and MariaDB which do not accept 4-byte utf-8 encodings by default. The settings you show above should be sufficient to allow 4-byte utf-8 encodings. I'm not that familiar with how the Debian/Ubuntu package sets things up. Are you sure that /etc/mailman3/mailman-web.py is the settings file used by Django, and if so does it have at the end something like ``` try: from settings_local import * except ImportError: pass ``` and if so is there something there that overrides the DATABASES setting? If all that is OK, you may need to do something like ``` ALTER DATABASE mailman3web CHARACTER SET utf8mb4; ALTER TABLE hyperkitty_email CHARACTER SET utf8mb4; ``` on the database itself. Hi Mark (and others), I'm now looking at this again after having to focus on other stuff. I'm befuddled, and I don't really know what to do now. I did the above. If I send mail to my list with those bleeping emojis, I see the same errors. In /var/log/mailman3/web/mailman-web.log I see DataError: (1366, u"Incorrect string value: '\\xF0\\x9F\\x95\\xB5\\xF0\\x9F... new mail to root, /var/lib/mailman3/archives/hyperkitty/spool/ has a new file, etc. The mail gets delivered, of course. If I then look at the database itself, I see: mysql> use mailman3web; mysql> SELECT @@character_set_database, @@collation_database; +--------------------------+----------------------+ | @@character_set_database | @@collation_database | +--------------------------+----------------------+ | utf8mb4 | utf8mb4_general_ci | +--------------------------+----------------------+ 1 row in set (0.00 sec) mysql> SHOW TABLE STATUS where name like 'hyperkitty_email'; +------------------+--------+---------+------------+------+----------------+-------------+-----------------+--------------+-----------+----------------+---------------------+-------------+------------+--------------------+----------+----------------+---------+ | Name | Engine | Version | Row_format | Rows | Avg_row_length | Data_length | Max_data_length | Index_length | Data_free | Auto_increment | Create_time | Update_time | Check_time | Collation | Checksum | Create_options | Comment | +------------------+--------+---------+------------+------+----------------+-------------+-----------------+--------------+-----------+----------------+---------------------+-------------+------------+--------------------+----------+----------------+---------+ | hyperkitty_email | InnoDB | 10 | Dynamic | 133 | 11949 | 1589248 | 0 | 196608 | 4194304 | 150 | 2021-01-29 17:23:13 | NULL | NULL | utf8mb4_general_ci | NULL | | | +------------------+--------+---------+------------+------+----------------+-------------+-----------------+--------------+-----------+----------------+---------------------+-------------+------------+--------------------+----------+----------------+---------+ 1 row in set (0.00 sec) So, I go look elsewhere... In /etc/mailman3/mailman.cfg I see: class: mailman.database.mysql.MySQLDatabase url: mysql+pymysql://mailman3:NopeNotPastingThat@localhost/mailman3?charset=utf8&use_unicode=1 Should I change the latter to be something like: url: mysql+pymysql://mailman3:NopeNotPastingThat@localhost/mailman3?charset=utf8mb4&use_unicode=1 ? Cheers, David

5 years, 8 months

[MM3-users] Re: Join a Mailman 3 list?

by Thomas Ward

On 2025-06-02 20:19, Cathryn McGuire wrote: > We are Administrators of a small neighbourhood group with more than 20 years of archives. You'll have to talk to EMWD to see if your archives will be kept with the migration. They have a completely custom web interface for archival. --- I'm going to re-state what Mark said here. To quote Mark Sapiro: > As far as your EMWD migration from cPanel Mailman 2.1 to Mailman 3 is conerned, I think you'll find little if any change as far as email posting to the list and email from the list is concerned, but EMWD has their own proprietary web UI for list management and archiving, so the web UI at EMWD is quite different from that for this list. THEREFORE... > We love the simple functionality of Mailman 2. > One post goes to the entire membership by email. Any reply arrives by email; either immediately or as part of the 9:00 am Digest. That part isn't going to change. > No websites or browsers or sign-ins. Well, you manage your list SOMEHOW, probably with EMWD's web panel and UI panel. > No threads or topics. There's no "threads" like forums have, but discussions by topic at least in mailman 2 and mailman 3 have still existed and probably still will exist. > Simply emails back and forth. > > Does Mailman 3 have the ability to function this way? (Read my last statements) > Might someone invite us to temporarily join their group so we can see how Mailman 3 operates from the point of view of members?\ EMWD uses their **own custom UI** for management and archiving. This means that we can't give you any real guidance on EMWD and such for how it relates to user management, etc. because the standard Mailman 3 UI (Postorious) for that won't be what you use with EMWD. So we can't really assist you to see how things will be from the view of "members of the list" in that front. For the vast majority of users and use cases though, if all they care about is the email messages being sent to the list and received from the list, nothing will change for users. It's the *management* components and EMWD's custom UIs you'll have to work with though, not the standard Postorious Mailman3 UI. At my dayjob, we use mailing lists here on Mailman3, albeit with the standard Postorious UI, but we have a separate management UI that we use for managers to check who is a member, remove members, etc. that uses the Mailman API and not Postorious, but the core management group (myself and IT staff) use Postorious for our management tasks and to see if Mailman is working and such. Additionally, we have 53 lists and well over a thousand members on some of othe lists and it works well. The vast majority of the members only care that the email functionality works, and it does for them. (None of them use digest format mail notifications, but that's because the lists tend to be more 'realtime' for those members.) (And before you ask, those lists are not open) If you have *more specific* questions beyond "do the same basics of Mailman2 like digests, email handling, etc. still behave more or less the same way" then you should ask those questions *specifically*. If your specific questions revolve around the management interface, you have to talk to EMWD. Same with message archives. Thomas

1 year, 4 months

[MM3-users] Re: Templates

by David Krantz

Hi again, I had the problem with getting two footers, i.e. two expansions of the template. After some digging in the source code I found out that the decorator made one expansion (without personalization) and that the delivery handling made another (with personalization). So I hacked pipelines/builtin.py with a new pipeline that excluded the decorate step, recompiled and changed to that pipeline for my personalized list. That worked. Nothing like a bit of shotgun debugging in production. That solves my immediate problem. Is there a known and recommended way of configuring personalized delivery so that you only get the personalized footer? I have ideas, but I probably should share them with the developer list instead. :-) Of course this very nice functionality is a bit buried. I activated it using the interactive python shell, seems less risky than changing the database directly. Cheers // David On Sat, Sep 23, 2017 at 10:39 PM, David Krantz <gazorg(a)gmail.com> wrote: > On Sat, Sep 23, 2017 at 6:48 PM, Mark Sapiro <mark(a)msapiro.net> wrote: >> >> Have you tried restarting/reloading whatever dbm (MySQL, PostgreSQL, ?) >> you are using? > > No, that would have been strange to me; the table in the database was > up to date. But now I tried that, I got no effect this time but I > probably could set up a better test. > > I also had another problem [solved]: I get the error message "Multiple > rows were found for one_or_none" when I try TemplateManager.get(name, > context) for the list. There is only one matching row in the templates > table so something is fishy with the ORM. This occured when I changed > to the previous uri value. As the database does not have any > duplicates in the templates table I suspect either a broken join or > that the cache retains the old value. > > The traceback looks like this in the mailman shell: >>>> tm.get('list:member:regular:footer', 'test.example.com') > Traceback (most recent call last): > File "<console>", line 1, in <module> > File ".../venv-3.5/lib/python3.5/site-packages/mailman-3.2.0a1-py3.5.egg/mailman/database/transaction.py", > line 85, in wrapper > return function(args[0], config.db.store, *args[1:], **kws) > File ".../venv-3.5/lib/python3.5/site-packages/mailman-3.2.0a1-py3.5.egg/mailman/model/template.py", > line 98, in get > contents = cache_mgr.get(actual_uri) > File ".../venv-3.5/lib/python3.5/site-packages/mailman-3.2.0a1-py3.5.egg/mailman/database/transaction.py", > line 85, in wrapper > return function(args[0], config.db.store, *args[1:], **kws) > File ".../venv-3.5/lib/python3.5/site-packages/mailman-3.2.0a1-py3.5.egg/mailman/model/cache.py", > line 125, in get > CacheEntry.key == key).one_or_none() > File ".../venv-3.5/lib/python3.5/site-packages/SQLAlchemy-1.2.0b2-py3.5-linux-x86_64.egg/sqlalchemy/orm/query.py", > line 2814, in one_or_none > "Multiple rows were found for one_or_none()") > sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for > one_or_none() > > Workaround: Delete cached files in .../var/cache and run delete from > file_cache in postgresql. Then that works again. The culprit was that > the file got cached twice so there is a bug in the cache function. I > used the ITemplateManager-util in the shell to cause the problem. > >>> 2. the $user_delivered_to and $user_email do not expand for some >>> reason. Known problem? >> >> >> These require that the list delivery be personalized. See >> <http://mailman.readthedocs.io/en/latest/src/mailman/runners/docs/outgoing.h…>. >> > > That explains things. Thank you! > > Now I got two footers, first one without personalisation and one > personalised. Interesting. > > best regards > // David

9 years, 1 month

[MM3-users] Re: psycopg2 error?

by Odhiambo Washington

On Fri, Oct 27, 2023 at 8:21 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/27/23 09:16, Odhiambo Washington wrote: > > (venv) mailman@debian12:~$ pip cache remove psycopg2-binary > > WARNING: No matching packages for pattern "psycopg2-binary" > > Files removed: 0 > > This was intended to prevent the following 'Using cached'. > > > > (venv) mailman@debian12:~$ pip install psycopg2-binary > > Collecting psycopg2-binary > > Using cached > > > psycopg2_binary-2.9.9-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl > > (3.0 MB) > > > However, you now have a different issue. > > > > raise DistributionNotFound(req, requirers) > > pkg_resources.DistributionNotFound: The 'flufl.lock>=5.1' distribution > was > > not found and is required by mailman > > See https://gitlab.com/mailman/mailman/-/issues/1085 Thank you. That solves the problem for sure! But this was detected 4 months ago. When is the permanent solution coming? (venv) mailman@debian12:~$ vi venv/lib/python3.11/site-packages/mailman-3.3.9.egg-info/requires.txt # flufl.xxx to flufl-xxx (venv) mailman@debian12:~$ mailman info GNU Mailman 3.3.9 (Tom Sawyer) Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0] config file: /etc/mailman3/mailman.cfg db url: postgresql://mailman:XXXXXXX@localhost/mailman devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:restpass (venv) mailman@debian12:~$ exit logout root@debian12:/home/wash# systemctl start mailman3 root@debian12:/home/wash# systemctl status mailman3 ● mailman3.service - GNU Mailing List Manager Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; preset: enabled) Active: active (running) since Sat 2023-10-28 01:22:56 EAT; 7s ago Process: 15590 ExecStart=/opt/mailman/venv/bin/mailman start (code=exited, status=0/SUCCESS) Main PID: 15592 (python3) Tasks: 17 (limit: 4547) Memory: 980.8M CPU: 27.774s CGroup: /system.slice/mailman3.service ├─15592 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/master -C /etc/mailman3/mailman.cfg ├─15598 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=archive:0:1 ├─15599 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=bounces:0:1 ├─15600 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=command:0:1 ├─15601 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=in:0:1 ├─15602 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=lmtp:0:1 ├─15603 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=nntp:0:1 ├─15604 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=out:0:1 ├─15605 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=pipeline:0:1 ├─15606 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1 ├─15607 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=retry:0:1 ├─15608 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=task:0:1 ├─15609 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=virgin:0:1 ├─15610 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=digest:0:1 ├─15648 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1 └─15649 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1 Oct 28 01:22:54 debian12.wash.lan systemd[1]: Starting mailman3.service - GNU Mailing List Manager... Oct 28 01:22:55 debian12.wash.lan mailman[15590]: Starting Mailman's master runner Oct 28 01:22:55 debian12.wash.lan mailman[15590]: Generating MTA alias maps Oct 28 01:22:56 debian12.wash.lan systemd[1]: mailman3.service: Can't open PID file /opt/mailman/mm/var/master.pid (yet?) after start: No such file or directory Oct 28 01:22:56 debian12.wash.lan systemd[1]: Started mailman3.service - GNU Mailing List Manager. root@debian12:/home/wash# -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

3 years

[MM3-users] Re: Different Mail Domain Cause Key Error

by Brian Carpenter

On 4/21/20 4:04 PM, Mark Sapiro wrote: > This is not the error. The KeyError ... 'file' exception is a Django > logging exception. It is not the underlying error. There should be more > in the log indicating what the real problem is. Ok. The first thing however is did I miss a step? Here is the complete error that is sent to me via email as superuser: Internal Server Error:/mailman3/lists/ KeyError at/mailman3/lists/ 'file' Traceback: File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/handlers/exception.py" in inner 34. response = get_response(request) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/handlers/base.py" in _get_response 115. response = self.process_exception_by_middleware(e, request) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/handlers/base.py" in _get_response 113. response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/postorius/views/list.py" in list_index 755. paginator_class=MailmanPaginator) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django_mailman3/lib/paginator.py" in paginate 71. objects = paginator.page(page_num) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django_mailman3/lib/paginator.py" in page 46. number = self.validate_number(number) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/paginator.py" in validate_number 48. if number > self.num_pages: File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/utils/functional.py" in __get__ 80. res = instance.__dict__[self.name] = self.func(instance) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/paginator.py" in num_pages 97. if self.count == 0 and not self.allow_empty_first_page: File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/utils/functional.py" in __get__ 80. res = instance.__dict__[self.name] = self.func(instance) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django_mailman3/lib/paginator.py" in count 56. return self.function(count=0, page=1).total_size File "/opt/mailman/mm/venv/lib/python3.7/site-packages/postorius/views/list.py" in _get_list_page 751. advertised=advertised, mail_host=mail_host, count=count, page=page) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/client.py" in get_list_page 181. return Page(self._connection, url, MailingList, count, page) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/restbase/page.py" in __init__ 37. self._create_page() File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/restbase/page.py" in _create_page 62. response, content = self._connection.call(self._build_url()) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/restbase/connection.py" in call 112. error_msg, response, None) *During handling of the above exception (HTTP Error 404: {"title": "404 Not Found"}), another exception occurred:* File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/handlers/exception.py" in inner 34. response = get_response(request) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/postorius/middleware.py" in __call__ 42. return self.get_response(request) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/handlers/exception.py" in inner 36. response = response_for_exception(request, exc) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/handlers/exception.py" in response_for_exception 95. exc_info=sys.exc_info(), File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/utils/log.py" in log_response 228. exc_info=exc_info, File "/usr/lib/python3.7/logging/__init__.py" in error 1412. self._log(ERROR, msg, args, **kwargs) File "/usr/lib/python3.7/logging/__init__.py" in _log 1519. self.handle(record) File "/usr/lib/python3.7/logging/__init__.py" in handle 1529. self.callHandlers(record) File "/usr/lib/python3.7/logging/__init__.py" in callHandlers 1591. hdlr.handle(record) File "/usr/lib/python3.7/logging/__init__.py" in handle 905. self.emit(record) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/utils/log.py" in emit 119. reporter = ExceptionReporter(request, is_email=True, *exc_info) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/views/debug.py" in __init__ 254. self.template_info = getattr(self.exc_value, 'template_debug', None) File "/usr/lib/python3.7/tempfile.py" in __getattr__ 614. file = self.__dict__['file'] Exception Type: KeyError at/mailman3/lists/ Exception Value: 'file' Request information: USER: AnonymousUser -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

6 years, 6 months

[MM3-users] [SOLVED] Re: Re: Newbie question 2: Rewriting issue for bounced emails

by William Oliver

On Mon, 2021-12-27 at 14:36 -0800, Mark Sapiro wrote: > > It appears that the MX for billoblog.com is not accepting mail from > your > server. Can you send non-mailman mail from this server to this address? > If not, you need to contact billoblog.com to fin wht they are blocking > your mail. > > > I tried changing the smtp port in mailman.cfg to 587, but that didn't > > change anything. > > because the issue is not in delivery from Mailman to Postfix. It is in > delivery from Postfix to billoblog.com. First, thanks so much for talking me through this. I could never have done it on my own. If you ever decide to go to the Smoky Mountain National Park or Knoxville, TN, send me an email, and I'll buy you a drink (I live in the hills between Knoxville and Gatlinburg, TN). In any case, I did some wandering around the intertubes and it appears this is an uncommon but well-known problem when using dovecot and postfix. It has to do with the setting of smtpd_recipient_restrictions in master.cf. It's not clear *which* "reject" command is triggered, but if I set it to just: -o smtpd_recipient_restrictions=permit_sasl_authenticated then it can get through. Er, to the next error, anyway. Sigh. I have *no* idea why it only shows up with mailman, but not with regular mail. I got some learnin' to do about that line. I don't know what the default reject criteria are. I have this horrible suspicion that I've opened myself up to zillions of evil emails, but I'll investigate that later. So, this took care of the Access Denied issue. That opened up the next error, which was "relay access denied". Again, regular mail worked just fine. Here's the syslog when I sent email to testlist from fp145(a)libertyfp.org: Here's the rejection to billo(a)billoblog.com: Dec 27 18:31:52 libertyfp postfix/submission/smtpd[471207]: connect from mail.libertyfp.org[2.56.57.28] Dec 27 18:31:52 libertyfp postfix/submission/smtpd[471207]: NOQUEUE: reject: RCPT from mail.libertyfp.org[2.56.57.28]: 454 4.7.1 <billo(a)billoblog.com>: Relay access denied; from=<testlist-bounces+billo=billoblog.com(a)libertyfp.org> to=<billo(a)billoblog.com> proto=ESMTP helo=<mail.libertyfp.org> Dec 27 18:31:52 libertyfp postfix/submission/smtpd[471207]: disconnect from mail.libertyfp.org[2.56.57.28] ehlo=1 mail=1 rcpt=0/1 rset=1 quit=1 commands=4/5 But it accepts the email to fp145(a)libertyfp.org Dec 27 18:31:53 libertyfp postfix/submission/smtpd[471207]: connect from mail.libertyfp.org[2.56.57.28] Dec 27 18:31:53 libertyfp postfix/submission/smtpd[471207]: 4FCDD420F5: client=mail.libertyfp.org[2.56.57.28] Dec 27 18:31:53 libertyfp postfix/cleanup[471223]: 4FCDD420F5: message- id=<8d3bf47c5dcd86983e8c01f8baece4e3ac43a1a1.camel(a)libertyfp.org> Dec 27 18:31:53 libertyfp postfix/cleanup[471223]: 4FCDD420F5: warning: header Subject: [Testlist] bbbbb from mail.libertyfp.org[2.56.57.28]; from=<testlist-bounces+fp145=libertyfp.org(a)libertyfp.org> to=<fp145(a)libertyfp.org> proto=ESMTP helo=<mail.libertyfp.org> Dec 27 18:31:53 libertyfp postfix/qmgr[468573]: 4FCDD420F5: from=<testlist-bounces+fp145=libertyfp.org(a)libertyfp.org>, size=1870, nrcpt=1 (queue active) Dec 27 18:31:53 libertyfp postfix/submission/smtpd[471207]: disconnect from mail.libertyfp.org[2.56.57.28] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 Direct mail from fp145(a)libertyfp.org to billo(a)billoblog.com worked fine also. Again, a quick DuckDuckGo search reveals that this has come up a couple of times. It required that I modify /etc/postfix/main.cf to add the non-localhost ip4 address of the box to the mynetworks line: mynetworks = 127.0.0.0/8 10.0.0.0/24 to mynetworks = 127.0.0.0/8 10.0.0.0/24 2.56.57.28 I assume that means that postfix uses localhost for regular mail, but mailman3 uses the 2.56.57.28 address. In any case, it now works fine. I am happily receiving the six million test messages that were queued awaiting delivery to billo(a)billoblog.com. Once again, thanks. I owe you. billo

4 years, 10 months

Search results for query "sapiro"