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

[MM3-users] Re: Installing mailman 3

by Rafael Mora

What should I do to tell Postfix to use my domain?? for example send emails using the email account mailing(a)labbrands.com Thank you El mar., 25 jul. 2017 a las 15:10, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/25/2017 12:58 PM, Rafael Mora wrote: > > I got this error starting mailman service: > > > > > > [mailman@localhost ~]$ source env2Traceback (most recent call last): > > File "/usr/local/lib/python3.6/asyncio/base_events.py", line 1043, in > > create_server > > sock.bind(sa) > > OSError: [Errno 99] Cannot assign requested address > ... > > What do you think? > > > I think you have configured > > lmtp_host: mail.example.com > > which is wrong. > > -- > 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, 1 month

[MM3-users] Re: mail loops back to myself

by Mark Sapiro

On 6/8/25 16:04, Florian Sukup wrote: > > Postfix on its own is working fine. > > I set up mailman, created a site/domain (lists.yyy.com) My hostname is > host.xxx.com . My IP has a RDNS entry: reverse.rrr.com . Why is the RDNS to reverse.rrr.com and not host.xxx.com. It is important for mail delivery to have full circle DNS. I.e. the sending server should have an A record for its IP and revers DNS for that IP should point back to the sending server's name. I'm guessing that rrr.com is a hosting provider and you don't control the rDNS for that IP, but you should try to get them to change it for you. Without that change, delivery of your outbound mail, at least to large ISPs, will be problematic at best. > When I send an email to my mailing list mylist(a)lists.yyy.com I receive > an error email. The logfile says the following: > > ... > Jun 9 00:23:38 arvak postfix/smtpd[]: connect from host.xxx.com[m.y.i.p] > Jun 9 00:23:38 arvak postfix/relay/smtp[]: warning: host > reverse.rrr.com[178.251.71.190]:25 greeted me with my own hostname > host.xxx.com > Jun 9 00:23:38 arvak postfix/relay/smtp[]: warning: host > reverse.rrr.com[m.y.i.p]:25 replied to HELO/EHLO with my own hostname > host.xxx.com See above. > Jun 9 00:23:38 arvak postfix/relay/smtp[]: 094895FADB: > to=<mylist(a)lists.yyy.com>, relay=reverse.rrr.com[m.y.i.p]:25, > delay=0.06, delays=0.03/0.01/0.02/0, dsn=5.4.6, status=bounced (mail for > lists.yyy.com loops back to myself) What is the output from `postconf -n`? > Jun 9 00:23:38 arvak postfix/smtpd[114119]: disconnect from > host.xxx.com[m.y.i.p] ehlo=1 quit=1 commands=2 > ... > > The MX record of lists.yyy.com points to reverse.rrr.com. Not sure if > this is the best idea? reverse.rrr.com has no A or AAAA record. An MX MUST point to a domain that has an A or AAAA record. The MX should point to host.xxx.com. > Can anyone give me a hint where to search for this error? The output from `postconf -n` would help. Also, have you set up postfix per https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… ? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months

[MM3-users] Re: archives html user interface menu selection retention after refresh

by Mark Sapiro

On 6/28/23 10:38 PM, Ken Alker wrote: > I have just started studying the archives feature and I've noticed that > if I select "Most Active" in the top menu and then I refresh my browser, > the refreshed screen jumps back to Recent after the refresh. In fact, > if ANY of the five menu items across the top are selected and then a > browser refresh is performed, the result is that one is always taken > back to the Recent menu item. It was not apparent to me for a couple of > days that this was happening and I'd convinced myself there was some bug > in the Recent vs. Most Active lists because the Most Active list changed > entirely after I did a refresh, when, in fact, I was then viewing the > Recent list again. Confusing. This is the expected behavior. the various Recent, Most Active, ... tabs use # fragments to switch the view, but these don't change the URL that the browser went to (the one in the browser's address bar) so a refresh goes to that original URL which defaults to the `Recent` view. > Is there some way that whatever menu item was being viewed before a > refresh could be retained so that the same menu item is shown after a > refresh? Probably not without significant redesign of the web UI. > Thinking this through even further, I suppose a side-affect of this > request could be that visiting the same page much later (ie. not > immediately after a refresh) may result in the page NOT defaulting to > the Recent menu item any longer (unless once could clear the "last menu > item" memory when the viewer moves AWAY from or closes the page). I > don't have enough familiarly with the interface to suggest if this would > be a bad side-effect, or good, but would this, indeed become a > side-affect that would have to be thought through? It would depend on how the feature was designed, but this is probably moot as such a feature is unlikely to be implemented as it seems the potential benefit doesn't warrant the additional complexity. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: LookupError: unknown encoding: _iso-2022-jp$esc

by Mark Sapiro

On 09/07/2018 08:30 AM, Thor Atle Rustad wrote: > This happens when I open a page of Held Messages containing an offending > message. I get Server Error (500) in Postorius. Here is the mailman.log: > > > Sep 07 15:25:39 2018 (32) REST request handler error: > Traceback (most recent call last): > File "/usr/local/lib/python3.6/wsgiref/handlers.py", line 137, in run > self.result = application(self.environ, self.start_response) > File > "/usr/local/lib/python3.6/site-packages/mailman/database/transaction.py", > line 50, in wrapper > rtn = function(*args, **kws) > File "/usr/local/lib/python3.6/site-packages/mailman/rest/wsgiapp.py", > line 214, in __call__ > return super().__call__(environ, start_response) > File "/usr/local/lib/python3.6/site-packages/falcon/api.py", line 244, in > __call__ > responder(req, resp, **params) > File > "/usr/local/lib/python3.6/site-packages/mailman/rest/post_moderation.py", > line 160, in on_get > resource = self._make_collection(request) > File "/usr/local/lib/python3.6/site-packages/mailman/rest/helpers.py", > line 159, in _make_collection > for resource in collection] > File "/usr/local/lib/python3.6/site-packages/mailman/rest/helpers.py", > line 159, in <listcomp> > for resource in collection] > File > "/usr/local/lib/python3.6/site-packages/mailman/rest/post_moderation.py", > line 150, in _resource_as_dict > resource = self._make_resource(request.id) > File > "/usr/local/lib/python3.6/site-packages/mailman/rest/post_moderation.py", > line 77, in _make_resource > resource['msg'] = msg.as_string() > File "/usr/local/lib/python3.6/site-packages/mailman/email/message.py", > line 54, in as_string > value = email.message.Message.as_string(self) > File "/usr/local/lib/python3.6/email/message.py", line 158, in as_string > g.flatten(self, unixfrom=unixfrom) > File "/usr/local/lib/python3.6/email/generator.py", line 116, in flatten > self._write(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 181, in _write > self._dispatch(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 214, in _dispatch > meth(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 243, in > _handle_text > msg.set_payload(payload, charset) > File "/usr/local/lib/python3.6/email/message.py", line 315, in set_payload > payload = payload.encode(charset.output_charset) > LookupError: unknown encoding: _iso-2022-jp$esc I think this should be fixed in Mailman core 3.2.0. It is related to Mailman core issues 256, 437 and 470 and merge requests 197, 322, 350 and 375. In particular, it looks like you are missing at least <https://gitlab.com/mailman/mailman/merge_requests/375>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

[MM3-users] Re: Mailman Core 3.3.2 is now out

by Mark Sapiro

On 11/22/20 1:10 AM, Torge Riedel wrote: > > today I did this on my setup and got the following exception after > "systemctl restart mailman": > > # systemctl status mailman.service > mailman.service - GNU Mailing List Manager > Loaded: loaded (/opt/mailman/core/mailman.service; enabled; vendor > preset: enabled) > Active: failed (Result: exit-code) since Sun 2020-11-22 09:59:53 CET; > 46s ago > Process: 30520 ExecStop=/opt/mailman/core/bin/mailman.sh stop > (code=killed, signal=TERM) > Process: 30597 ExecStart=/opt/mailman/core/bin/mailman.sh start > (code=exited, status=1/FAILURE) > Main PID: 1223 (code=exited, status=0/SUCCESS) > > Nov 22 09:59:53 basis2 mailman.sh[30597]: File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/protocol.py", line > 220, in check_error > Nov 22 09:59:53 basis2 mailman.sh[30597]: > err.raise_mysql_exception(self._data) > Nov 22 09:59:53 basis2 mailman.sh[30597]: File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/err.py", > line 109, in raise_mysql_exception > Nov 22 09:59:53 basis2 mailman.sh[30597]: raise errorclass(errno, > errval) > Nov 22 09:59:53 basis2 mailman.sh[30597]: sqlalchemy.exc.InternalError: > (pymysql.err.InternalError) (1060, "Duplicate column name > 'archive_rendering_mode'") > Nov 22 09:59:53 basis2 mailman.sh[30597]: [SQL: ALTER TABLE mailinglist > ADD COLUMN archive_rendering_mode INTEGER] > Nov 22 09:59:53 basis2 mailman.sh[30597]: (Background on this error at: > http://sqlalche.me/e/2j85) > Nov 22 09:59:53 basis2 systemd[1]: mailman.service: Control process > exited, code=exited status=1 > Nov 22 09:59:53 basis2 systemd[1]: mailman.service: Failed with result > 'exit-code'. > Nov 22 09:59:53 basis2 systemd[1]: Failed to start GNU Mailing List > Manager. > > I checked the database and - yes - there is already such a column in the > DB. So I tried it the "hacker" way and just removed the column from the > DB and give "systemctl restart mailman" a second try. Now it worked and > the column is back. > > I don't know if this column was already there from 3.3.1. That column was added in 3.3.2 by <https://gitlab.com/mailman/mailman/-/merge_requests/644> It is the migration to add that column that failed in the above. It appears that somehow that migration was previously run and added the column, but the version_num entry in the alembic_version table was not updated to indicate that that migration had been run. -- 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

[MM3-users] Re: Hyperkitty 1.1.1 to HyperKitty 1.2.1

by Mark Sapiro

On 09/30/2018 11:42 PM, Thomas G wrote: > Hi, > > I would like to migrate my current Mailman3.1/Hyperkitty data to a fresh > install in Mailman3.2. > > I didn't found how migrate the archives. >>From : HyperKitty - Version: 1.1.1 - Python2.7 > To : HyperKitty - Version: 1.2.1 - Python3.5 As Abhilash said, you shouldn't need to migrate anything but the search index. > I exported a mbox from hyperkitty (web interface) and tried to re-import > it, without result. > """""""""""""""""""""""""""""""""""""""" > xxxx @xxxxxx :/opt/mailman# python3.5 manage.py hyperkitty_import -l > listedetests(a)hatlab.fr /home/admin/listedetests(a)hatlab.fr.mbox.gz > > Importing from mbox file /home/admin/listedetests(a)hatlab.fr.mbox.gz to > listedetests(a)hatlab.fr You can't import a gzipped mbox. You have to gunzip it. > Computing thread structure > Synchronizing properties with Mailman > Warming up cache > The full-text search index is not updated for this list. It will not be > updated by the 'minutely' incremental update job. To update the index > for this list, run the 'manage.py update_index_one_list > listedetests(a)hatlab.fr' command. > """""""""""""""""""""""""""""""""""""" > The database stay empty (and web interface): > """""""""""""""""""""""""""""""""""""" > mailmandbnameprod=# select * from hyperkitty_email; > id | message_id | message_id_hash | subject | content | date | timezone > | in_reply_to | archived_date | thread_depth | thread_order | > mailinglist_id | parent_id | sender_id | thread_id | sender_name > ----+------------+-----------------+---------+---------+------+----------+-------------+---------------+--------------+--------------+----------------+-----------+-----------+-----------+------------- > (0 rows) > """""""""""""""""""""""""""""""""""""" > > Any idea to do this importation ? Why is the database empty? It should be as it was with the prior HyperKitty. Also, it doesn't seem to be the issue here, but if you don't specify a --since option to hyperkitty_import, it won't import any messages older than the most recent message in the existing archive. i.e., if there are any messages in the existing archive, the default for --since is the date of the most recent such message. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 11 months

[MM3-users] Re: Moderate mails from owner

by Mark Sapiro

On 4/30/19 1:04 AM, Henrik Rasmussen wrote: > @Mark: I am really sorry for the delayed responses, but this is a very low frequency list. I have subscribed to the list using a non-Microsoft address to see the outcome. > > The mails does indeed contain 'X-Mailman' headers. > > X-Mailman-Rule-Hits:nonmember-moderation > X-Mailman-Rule-Misses:dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation It looks like the message hit the nonmember-moderation rule and was accepted. This can happen in a few ways: First we determine the senders. Assuming the config is default, these are the addresses in From:, the envelope sender, and addresses in Reply-To: and Sender: if any. The only address I can see in the message headers that hasn't been altered by Mailman is the From: and maybe Reply-To: which you have munged to [LISTNAME](a)senderdep.example.com. Anyway that unmunged address and possibly others from the original incoming message will be users of the list with role nonmember. Now each of those (possibly only the one) nonmember(s) is checked for a moderation action. Since the message does not appear to have been held or processed through rules beyond nonmember-moderation, we presumably found a moderation action of accept. This can happen in a few ways., If this list was originally imported from Mailman 2.1 by the 'mailman import21' command, there may be a legacy accept_these_nonmembers attribute for the list. If so, and if a nonmember sender address matches an address or pattern in the list's accept_these_nonmembers, the message will be accepted. Otherwise if the moderation_action for a nonmember sender address is accept the message will be accepted. You need to check the list's accept_these_nonmembers attribute and the non-member address's moderation action. If you have recent Postorius, you can see nonmembers and their options from the 'users' -> Non-members view. In any case, you can do something like mailman shell -l list.example.com Welcome to the GNU Mailman shell The variable 'm' is the list.example.com mailing list >>> m.accept_these_nonmembers returns a possibly empty list Then for the sender addresses >>> memb = m.nonmembers.get_member('sender address') >>> memb.moderation_action This may return <Action.accept: 3> in which case you may want >>> memb.moderation_action = m.default_nonmember_action -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

[MM3-users] Re: Message IDs

by Mark Sapiro

On 10/15/21 3:19 AM, Philip Colmer wrote: > > I'm not sure that the message ID identifies the author, does it? No, but it identifies the message, and while Mailman has made some cosmetic modifications to the headers, it is still the same message. > I've just done a quick test of sending myself an email and then replying to it. > > The original email has a message ID of > CAKTSSThxADLoO=Cy5cNzHoihGb5dYbmB0iw_ThTqe9T9At9efw(a)mail.gmail.com > > In the reply, the following headers are present: > > References: <CAKTSSThxADLoO=Cy5cNzHoihGb5dYbmB0iw_ThTqe9T9At9efw(a)mail.gmail.com> > In-Reply-To: <CAKTSSThxADLoO=Cy5cNzHoihGb5dYbmB0iw_ThTqe9T9At9efw(a)mail.gmail.com> > Message-ID: <CAKTSSTh-Fgy63MbDQtWS=oPCw0kGxTmj5RxRe6r1U0W=Die4mQ(a)mail.gmail.com> > > Would it be reasonable for Mailman 3 to use "References:" to keep the > original Message ID and then add a new Message ID? No, because the message from the list is not a reply to the incoming message. It is the incoming message. > I think that what Mailman 3 is doing is similar to forwarding the > email. If I forward an email, again the headers change: If you want Mailman to 'forward' the message, set DMARC mitigation action to wrap the message. >> The IETF has addressed the issue of non-identical but equivalent >> messages with the Resent-Message-ID field (and in general the whole >> suite of Resent-* fields. > > Mailman doesn't appear to be adding that header. Would that be an > acceptable solution instead of the one I suggested above? Mailman doesn't add the header, but even if it did, I doubt it would solve the problem with Gmail. > I appreciate your view that Google is broken. I'm just trying to find > an acceptable solution to the end-user perception of "I've sent an > email to the list but I haven't received a copy back". That is going > to be a big issue/headache for us. It's a long standing PITA with Google. See <https://wiki.list.org/x/4030680>. Your Gmail users can partially mitigate this by setting their Acknowledge posts option to Yes. Note also that Mailman core communicates with archivers to determine what goes in the Archived-At: header and this value is usually based on the Message-ID:. Changing the Message-ID: could possibly render that value incorrect. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

[MM3-users] Re: django-allauth 0.59.0

by Jered Floyd

This is only required for the new "user sessions" app which doesn't appear to be exposed within Mailman. (I agree it should be added, though.) --Jered ----- On Dec 21, 2023, at 4:12 AM, Mark Sapiro mark(a)msapiro.net wrote: > On 12/20/23 7:27 PM, Jered Floyd wrote: >> >> >> FYI, django-allauth 0.59.0 was released on December 12 and incorporates the >> patches to work properly with Mailman again. > > django-allauth 0.59.0 requires django.contrib.humanize in > INSTALLED_APPS. You may need to add this in your Django settings when > upgrading django-allauth. > > > -- > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to jered(a)convivian.com

1 year, 8 months

[MM3-users] Re: Held for notification - runner exception: 'ascii' codec can't encode character

by Mark Sapiro

On 1/2/22 11:00 AM, Seth Seeger wrote: > > I have a case where a user (set to be moderated), posts a message. She got the appropriate email back saying she was being held for moderation. However, the moderator did not get the email. I found the following block in mailman.log: > > Dec 28 19:37:44 2021 (33) Uncaught runner exception: 'ascii' codec can't encode character '\u2019' in position 5: ordinal not in range(128) > Dec 28 19:37:44 2021 (33) Traceback (most recent call last): > File "/usr/lib/python3.8/site-packages/mailman/core/runner.py", line 173, in _one_iteration > self._process_one_file(msg, msgdata) > File "/usr/lib/python3.8/site-packages/mailman/core/runner.py", line 266, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/lib/python3.8/site-packages/mailman/runners/incoming.py", line 79, in _dispose > process(mlist, msg, msgdata, start_chain) > File "/usr/lib/python3.8/site-packages/mailman/core/chains.py", line 79, in process > link.function(mlist, msg, msgdata) > File "/usr/lib/python3.8/site-packages/mailman/chains/hold.py", line 234, in _process > text = MIMEText(expand(template, mlist, substitutions), > File "/usr/lib/python3.8/email/mime/text.py", line 42, in __init__ > self.set_payload(_text, _charset) > File "/usr/lib/python3.8/email/message.py", line 315, in set_payload > payload = payload.encode(charset.output_charset) > UnicodeEncodeError: 'ascii' codec can't encode character '\u2019' in position 5: ordinal not in range(128) > Dec 28 19:37:44 2021 (33) SHUNTING: 1640720264.0541506+b139f885caa9444586b43093a09991b7c19581e6 > > There are two owners listed, one of them is also listed as the moderator. This is redundant. Having the same user as both owner and moderator only results in possible duplicate notifications. There is no reason to have an owner also be a moderator. > "mailman version" says: GNU Mailman 3.3.4 (Tom Sawyer) We are running from Docker. I can send you the pck file offline if that would help. Please do send me the shunted .pck. what is going on is this is an English language list which has character set `ascii` and the notice for some reason has non-ascii, possbbly the Subject: or the user's display name has non-ascii. But possibly the message itself is defective. In any case, I'd like to get the shunted message to see if there's something we should fix. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

Search results for query "sapiro"