Search results for query "sapiro"
- 6108 messages
[MM3-users] Re: new list not working
by Christian
When I ran
mailman members -r -n enabled redlatinleg(a)lists.ccalternatives.org
I did receive a list of subscribers for the new list I created, not just the
owner or moderator.
Upon closer examination, another of my longtime working lists is also not
working. Similar behavior as the new list I created in that I see the
message has been archived, but not distributed to the subscribers.
-----Original Message-----
From: Mark Sapiro <mark(a)msapiro.net>
Sent: Thursday, March 9, 2023 1:44 PM
To: mailman-users(a)mailman3.org
Subject: [MM3-users] Re: new list not working
On 3/9/23 13:26, Christian via Mailman-users wrote:
> I am only having issues with the new list.
>
>
>
> Below are logfile entries
>
>
>
> Smtp.log
>
> ++++++
>
> Mar 09 20:57:09 2023 (9401) Available AUTH mechanisms: LOGIN(builtin)
> PLAIN(builtin)
>
> Mar 09 20:57:09 2023 (9401) Peer: ('127.0.0.1', 35982)
>
> Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) handling connection
>
> Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'LHLO
zarathustra.ccalternatives.org'
>
> Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'MAIL
FROM:<christian(a)naturalintelligence.us> SIZE=3653'
>
> Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) sender:
> christian(a)naturalintelligence.us
>
> Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'RCPT
TO:<redlatinleg(a)lists.ccalternatives.org>'
>
> Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) recip:
> redlatinleg(a)lists.ccalternatives.org
>
> Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'DATA'
>
> Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'QUIT'
>
> Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) connection lost
>
> Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) Connection lost
> during _handle_client()
This is the post being delivered to mailman and is expected.
>
>
> Access.log
Irrelevant.
> Mailman.log
>
> ++++++++
>
> Mar 09 20:57:09 2023 (9400) ACCEPT:
> <032101d952c9$caf09990$60d1ccb0$(a)naturalintelligence.us>
>
> Mar 09 13:03:42 2023 (9397) HyperKitty archived message
> <032101d952c9$caf09990$60d1ccb0$(a)naturalintelligence.us> to
> https://lists.ccalternatives.org/archives/list/redlatinleg@lists.ccalt
> ernatives.org/message/PAJ5GDGGK74LWHQINB32BDV22BMR6LRQ/
These are the expected messages (there seems to be a time zone
difference) and in the absence of any other error type messages say the
message should have been delivered to the eligible recipients. Are there
any? See
https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/
CTAF4RDJ2CTNCGI7MXFYL3Q5HTGYMZH6/
or the results from
```
mailman members -r -n enabled redlatinleg(a)lists.ccalternatives.org
```
> mailmansuite.log
not relevant.
--
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/
ZVY3EFBA5WQKYS6E7AS475TNY6C4NJQU/
This message sent to csa(a)web-analysts.net
2 years, 11 months
[MM3-users] Re: SMTPSenderRefused - howto enable STARTTLS for local mail drop
by Stefan Bauer
Unfortunately i need this, as the postfix is listening on all interfaces
and we have the policy to enforce TLS only. Nothing special in the logs:
Dec 07 08:14:14 2021 (12303) Using agent: <mailman.mta.bulk.BulkDelivery
object at 0x7fbc29b1c4a8>
Dec 07 08:14:14 2021 (12303) Connecting to localhost:25
Dec 07 08:14:14 2021 (12303) envsender: v-test-bounces@domain, recipients:
['recipient(a)own.domain'], size(msgtext): 5809
Dec 07 08:14:14 2021 (12303)
<kcEE.aBI3BVc2RCi6kAxA4PJ0hg.ADrcCDrr1wE(a)mailsrv103.my.domain> smtp to
v-test@domain for 1 recips, completed in 0.008081912994384766 seconds
Dec 07 08:14:14 2021 (12303)
<kcEE.aBI3BVc2RCi6kAxA4PJ0hg.ADrcCDrr1wE(a)mailsrv103.my.domain> post to
v-test@domain from v-test@domain, 5336 bytes
Dec 07 08:14:47 2021 (12297) Peer: ('127.0.0.1', 43210)
Dec 07 08:14:47 2021 (12297) ('127.0.0.1', 43210) handling connection
Dec 07 08:14:47 2021 (12297) b'220 ml01.my.domain GNU Mailman LMTP runner
2.0\r\n'
Dec 07 08:14:47 2021 (12297) ('127.0.0.1', 43210) EOF received
Dec 07 08:14:47 2021 (12297) Connection lost during _handle_client()
Dec 07 08:14:47 2021 (12297) ('127.0.0.1', 43210) connection lost
Dec 07 08:15:00 2021 (12297) Peer: ('127.0.0.1', 43516)
Dec 07 08:15:00 2021 (12297) ('127.0.0.1', 43516) handling connection
Is my mailman version maybe too old for this setting?
I'm running GNU Mailman 3.1.1 (Between The Wheels)
Thank you.
Am Mo., 6. Dez. 2021 um 19:04 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>:
> On 12/6/21 2:51 AM, Stefan Bauer wrote:
> > Need to bring this up again. Django now sends with STARTTLS, but mailman
> > itself, does still only drop mails in cleartext.
> > Dec 6 11:47:33 al01 postfix/lmtp[7598]: A6422600510:
> > to=<remote-party@remote>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.01,
> > delays=0.01/0/0/0.01, dsn=2.0.0, status=sent (250 Ok)
> > Dec 6 11:47:33 al01 postfix/qmgr[29156]: A6422600510: removed
> > Dec 6 11:47:35 al01 postfix/smtpd[8092]: disconnect from localhost[::1]
> > ehlo=1 mail=2 rcpt=2 data=2 commands=7
> >
> > No starttls=1 at all :(
> >
> > Does the above settings work for anyone?
> >
> > etc/mailman3/mailman.cfg
> > [mta]
> > incoming: mailman.mta.postfix.LMTP
> > outgoing: mailman.mta.deliver.deliver
> >
> > smtp_host: localhost
> > smtp_port: 25
> > smtp_user:
> > smtp_pass:
> > smtp_verify_hostname: false
> > smtp_verify_cert: false
> > smtp_secure_mode: starttls
>
>
> This should work. What do you see in Mailman's smtp.log if you add
> ```
> [logging.smtp]
> level: debug
> ```
> to mailman.cfg.
>
> However, do you really need this. It will only affect delivery from
> Mailman to Postfix via the loopback interface on the localhost.
>
> --
> 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, 2 months
[MM3-users] Re: Installing mailman 3
by Rafael Mora
New output from command 'postconf -n ':
[root@localhost ~]# postconf -n
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
command_directory = /usr/sbin
config_directory = /etc/postfix
daemon_directory = /usr/libexec/postfix
data_directory = /var/lib/postfix
debug_peer_level = 2
debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin ddd
$daemon_directory/$process_name $process_id & sleep 5
html_directory = no
inet_interfaces = localhost
inet_protocols = all
local_recipient_maps = hash:/var/lib/mailman/var/data/postfix_lmtp
mail_owner = postfix
mailq_path = /usr/bin/mailq.postfix
manpage_directory = /usr/share/man
mydestination = $myhostname, localhost.$mydomain, localhost
newaliases_path = /usr/bin/newaliases.postfix
owner_request_special = no
queue_directory = /var/spool/postfix
readme_directory = /usr/share/doc/postfix-2.10.1/README_FILES
recipient_delimiter = +
relay_domains = hash:/var/lib/mailman/var/data/postfix_domains
sample_directory = /usr/share/doc/postfix-2.10.1/samples
sendmail_path = /usr/sbin/sendmail.postfix
setgid_group = postdrop
transport_maps = hash:/var/lib/mailman/var/data/postfix_lmtp
unknown_local_recipient_reject_code = 550
El dom., 23 jul. 2017 a las 11:19, Mark Sapiro (<mark(a)msapiro.net>)
escribió:
> On 07/23/2017 08:16 AM, Rafael Mora wrote:
> > This is the content of my /var/log:
> >
> >
> > [root@localhost log]# pwd
> > /var/log
> > [root@localhost log]# ls
> > anaconda grubby messages-20170716 spooler-20170710
> > audit grubby_prune_debug messages-20170723 spooler-20170716
> > boot.log httpd mysqld.log spooler-20170723
> > btmp lastlog php-fpm tallylog
> > btmp-20170701 letsencrypt ppp tuned
> > chrony maillog rhsm wtmp
> > cron maillog-20170702 samba xferlog
> > cron-20170702 maillog-20170710 secure xferlog-20170702
> > cron-20170710 maillog-20170716 secure-20170702 xferlog-20170710
> > cron-20170716 maillog-20170723 secure-20170710 xferlog-20170716
> > cron-20170723 mailman secure-20170716 xferlog-20170723
> > dmesg messages secure-20170723 yum.log
> > dmesg.old messages-20170702 spooler
> > firewalld messages-20170710 spooler-20170702
>
>
> Your current postfix log is /var/log/maillog. The files like
> /var/log/maillog-20170702, etc are older versions rotated by logrotate.
>
> On 07/23/2017 08:14 AM, Rafael Mora wrote:
> > content of the file maillog-20170723 (I didn't find mail.log in
> /var/log):
> >
> > [root@localhost log]# cat maillog-20170723
>
> You want to be looking at /var/log/maillog for current messages.
>
>
> ...
> > Jul 21 16:10:47 localhost postfix/qmgr[2116]: error: open database
> > /var/lib/mailman/var/data/postfix_domains.db: No such file or directory
>
>
> Is this where these files are? You should have at least postfix_domains,
> postfix_domains.db, postfix_lmtp and postfix_lmtp.db in the
> /var/lib/mailman/var/data/ directory. It this the case?
>
> > output command 'postconf -n':
> >
> ...
> > transport_maps = hash:/var/libmailman/var/data/postfix_lmtp
>
>
> This is missing a /
>
>
> transport_maps = hash:/var/lib/mailman/var/data/postfix_lmtp
>
>
> --
> 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, 6 months
[MM3-users] Re: templates
by Odhiambo Washington
If you don't have any templates in the file system and none in the DB
table, then you must go to Jerusalem and pray, because you don't have any
and nothing will work the way you want.
It's either or!
On Thu, May 4, 2023, 21:14 Christian via Mailman-users <
mailman-users(a)mailman3.org> wrote:
> In March when I started troubleshooting my lists, you stated:
>
> "Also, one other thing you might check. Do these non-working lists have
> templates defined in postorius, in particular, one for
> list:member:regular:footer, and if not, are there any in Mailman's
> var/templates/lists/redlatinleg(a)lists.ccalternatives.org/ derectory that
> Mailman doesn't have permission to find and read?"
>
> There are no other templates listed in either Postorius nor in Mailman's
> var/templates (as I stated, I do not even lave a 'lists' subdirectory under
> Mailman's var/templates). My subscribers are not receiving message
> distributions from my lists, even while some of them are listed in the
> archives.
>
>
>
>
> -----Original Message-----
> From: Mark Sapiro <mark(a)msapiro.net>
> Sent: Thursday, May 4, 2023 10:58 AM
> To: mailman-users(a)mailman3.org
> Subject: [MM3-users] Re: templates
>
> On 5/4/23 10:33, Christian via Mailman-users wrote:
> > I'm having issues with my lists. For each list I have created a
> > template [ list:user:action:subscribe ]which has a prospective
> > subscriber have to consent to list rules before they are subscribed.
> > This template I created is listed in Postorius for each list. I have
> > noticed that there are no other templates listed in Postorius.
> Furthermore, there is no 'lists'
> > subdirectory under Mailman's var/templates/.
>
>
> When you set a template in Postorius it saves it in the
> postorius_emailtemplate table in the database and tells Mailman core to get
> the template from Postorius via a URI to a Postorius API.
>
> --
> 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/
> QIHCMEBWANR67HV3NKBK5MCQNSNZRF2A/
> <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>
>
> This message sent to csa(a)web-analysts.net
>
> _______________________________________________
> 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 odhiambo(a)gmail.com
>
2 years, 9 months
[MM3-users] Re: mailman3 postorius cannot retrieve template at ... (<no authorization>)
by Mark Sapiro
On 10/29/21 3:41 AM, Wolfgang Bock via Mailman-users wrote:
>
> the question is: postgres - mailman3web-postorius_emailtemplate table vs
> mailman3 - templates table
>
> I installed a brand new mailman3 with mailman Core 3.3.3, Api 3.1, Core
> Python 3.9.2 postgres12 nginx on debian bullseye.
>
> I created a template via postorius -> lists -> (testliste01) -> templates
> -> new template -> [list:member:regular:footer] and
> [list:member:digest:footer]
>
> They are shown in the postgres database mailman3 table templates:
> id name context uri username password
> 14 list:member:digest:footer testliste01.mydomain.de
> http://localhost/postorius/api/templates/list/testliste01.mydomain.de/list:m
> ember:digest:footer
> 15 list:member:regular:footer testliste01.mydomain.de
> http://localhost/postorius/api/templates/list/testliste01.mydomain.de/list:m
> ember:regular:footer
>
> First there where no templates in the /var/lib/mailman3/templates folder,
> which was empty after installation.
This is expected. That is one place where you can put custom templates.
> Later I created in /var/lib/mailman3/templates theses folders and the files
> /list/testliste01.mydomain.de/list:member:digest:footer +
> list:member:regular:footer owned by list:list 644
>
> A testmail went through but instead of the default footer no footer was
> shown.
By default Mailman searches for templates first in the var/templates
directory and then in the templates directory in the Mailman
installation. The details are described at
https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n….
However, the default search is only applied if there is matching entry
for the template name and context in the `templates` table in the
database or if the uri in the entry is a `mailman://` uri.
When you create a template in Postorius, that uri becomes something like
`https://example.com/mailman3/api/templates/list/<list_id>/<template_name>`
which basically says get the template from Postorius, and the template
if any in var/templates is ignored.
> In the sys.log I found the following error message:
> Oct 29 11:28:04 myserver mailman3[33015]: Message: `Cannot retrieve template
> at
> http://localhost/postorius/api/templates/list/testliste01.mydomain.de/list:m
> ember:regular:footer (<no authorization>)`
So Mailman is trying to get the Postorius template. What is in the web
server logs for this retrieval?
> How can I solve this problem? What kind of authorisation is meant? list?
> restadmin?
>
> I read in
> https://docs.mailman3.org/en/latest/config-core.html#configure-templates
> ... list specific templates invar/templates/lists/LIST-ID/LC/ ...
> I guess the LC means Language Code. But in the database table templates no
> LC subdirectory is mentioned (in my case must be de).
If you delete the Postorius template, The entry in the templates table
will be removed and the search will revert to var/templates, etc.
> And I read (dont know where) .... The templates created in Postorius are
> created in the postorius_emailtemplate table in Mailman`s database and
> referenced via URLs like
> `https://example.com/mailman3/api/templates/list/<list-id>/<template-name>`.
> I.e., they are not stored in the file system. ...
>
> That`s true. I found in postgres database mailman3web in the table
> mailman3web postorius_emailtemplate my
>
> id name data language created_at modified_at
> context identifier
> 15 list:member:digest:footer postorius footer digest 1x linefeed
> 2021-10-29 11:17:40.664689+02 2021-10-29 11:26:48.692628+02 list
> testliste01.mydomain.de
> 16 list:member:regular:footer postorius footer non-digest 1x
> linefeed 2021-10-29 11:18:29.166241+02 2021-10-29 11:27:24.519024+02 list
> testliste01.mydomain.de
>
> But my question is how to integrate this into the mailman3-system. The
> language isn`t set either.
It is integrated. The language isn`t set because you are getting the
template from Postorius and Postorius knows the language.
On 10/31/21 4:13 AM, Wolfgang Bock via Mailman-users wrote:
> regarding my mail before, here an additional information.
>
> I can show the templates with following command (anonymized):
>
https://active_domain.de/postorius/api/templates/list/testliste01.active_do…
As it should be.
> The complete syslog
>
(edited and reformatted by me)
```
> --- Logging error ---
> Traceback (most recent call last): Oct 30 11:49:52 active_server
mailman3[107630]: File
"/usr/lib/python3/dist-packages/mailman/model/template.py", line 110, in get
> contents = protocols.get(actual_uri, **auth)
> File
"/usr/lib/python3/dist-packages/mailman/utilities/protocols.py", line
39, in get
> response.raise_for_status()
> File "/usr/lib/python3/dist-packages/requests/models.py", line
943, in raise_for_status
> raise HTTPError(http_error_msg, response=self)
> requests.exceptions.HTTPError: 404 Client Error: Not Found for url:
http://localhost/postorius/api/templates/list/testliste01.active_domain.de/…
> During handling of the above exception, another exception occurred:
> Traceback (most recent call last):
> File "/usr/lib/python3.9/logging/__init__.py", line 430, in format
> return self._format(record)
> File "/usr/lib/python3.9/logging/__init__.py", line 426, in _format
> return self._fmt % record.__dict__
> KeyError: `t`
> During handling of the above exception, another exception occurred:
```
Your template is malformed. You have $ strings that are not defined as
Mailman substitution variables. See
https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…
--
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
4 years, 3 months
[MM3-users] Re: Relaying email from external SMTP server (office365 or Exchange)
by Waqas Ahmed Khan
Hi,
I have successfully configured Office365 to relay emails from Mailman3. I
used the below configuration.
change following lines in mailman.cfg:
smtp_host: your-domain.com.mail.protection.outlook.com
smtp_port: 25
And then configure SMTP Relay Connector in Office365, so it can recognize
your server. SMTP relay doesn't use a specific Office 365 mailbox to send
email.
Option3 of Link:
https://docs.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-s…
Could you Please confirm, what should be hardware configuration (ram,
processor, disk) to run mailman3 server for medium size organization? This
server will have 10-15 lists and some lists having 10k to 20k members. Also
what should be DISK SPACE of the server for Archiving emails?
Regards,
*Waqas Ahmed Khan*
p: +923212608044
Skype: waqas-ahmed00 <waqas.ahmed0(a)gmail.com>
waqas.ahmed0(a)gmail.com
[image: LinkedIn] <http://pk.linkedin.com/pub/waqas-ahmed-khan/15/96a/39a/>
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam…>
Virus-free.
www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam…>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Tue, Jun 23, 2020 at 8:23 AM Mark Sapiro <mark(a)msapiro.net> wrote:
> On 6/22/20 7:58 AM, Waqas Ahmed Khan wrote:
> > Hi,
> >
> > I have installed mailman3 with postfix. The server is working fine. To
> > protect the IPs from blacklisting, I want to relay all emails from
> > postfix/mailman to external SMTP servers like O365, Gmail, or our
> exchange
> > server.
>
>
> I would not recommend using O365 or Gmail as outgoing MTAs. I don't
> really know about )365, but I don't think Gmail likes you to send mail
> via a gmail server if it is not From: (or maybe envelope from or both) a
> gmail or googlemail address.
>
>
> > Could you please confirm is this possible. And how to do its
> configuration.
>
>
> It is possible and there are two ways to do it. You can configure this
> in Postfix to relay all outgoing mail via some other server.
>
>
> You can configure it in Mailman by setting in the [mta] section of
> mailman.cfg
>
> smtp_host:
> smtp_port:
>
> and presumably for authentication
>
> smtp_user:
> smtp_pass:
>
> Also see
>
> https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.…
> and following for other relevant settings.
>
> --
> 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/
>
5 years, 7 months
[MM3-users] Re: Hyperkitty Recommended mySQL Database Setup & Archive Importing
by matthew＠alberti.us
I should clarify a bit. That connection string I mentioned in the previous
post is in the docker-compose.yaml file for the docker-mailman containers.
For web, it seems the settings.py file for the mailman-web container is
configured to parse connection string, but there isn't (I don't think) any
provision to set additional options, such as the encoding. So there doesn't
appear to be a straightforward way, using the container yaml approach, to
pass the 'OPTIONS' for the encoding. It does however look like it is
possible to override the whole database connection settings using
settings_local.py, but unsure. That would I think be the way to do it,
setting the whole database configuration settings per
https://gitlab.com/mailman/mailman-suite/-/blob/master/mailman-suite_project
/settings.py#L156 in the settings_local.py file.
For core, the connection string seems to accept a tailing
"?charset=utf8&use_unicode=1" per
https://mailman.readthedocs.io/en/stable/src/mailman/docs/database.html So
for core, maybe just updating the connection string to include
"?charset=utfmb4&use_unicode=1" will just work? The link lists utf8 as the
recommend encoding... maybe that should be updated?
I realize this may be drifting more towards concerning the docker container
setup vs. non-containerized core and web. But either way, these seem to be
mysql specific caveats that I've certainly missed. Hopefully this helps
someone else.
Seems the takeaway is that, for mysql databases only, the use of utf8mb4 is
recommended, and it needs to be explicitly identified in the database
settings for BOTH core and web, and probably somehow at database creation
time?
Now to see what the best procedure is to put these configuration changes in
place, and also update the database?
- Matt Alberti
-----Original Message-----
From: Mark Sapiro <mark(a)msapiro.net>
Sent: Wednesday, December 9, 2020 9:35 PM
To: mailman-users(a)mailman3.org
Subject: [MM3-users] Re: Hyperkitty Recommended mySQL Database Setup &
Archive Importing
On 12/9/20 6:06 PM, matthew(a)alberti.us wrote:
> Thanks Mark. Also, just to confirm, should the database connection
> string also be updated? In both the core and web configuration, I have
> something
> like:
>
> DATABASE_URL=mysql+pymysql://mailman:password@database/mailmandb
>
> Note the trailing UTF-8 encoding stuff isn't there. Should we be
> specifying
> utf8mb4 there as well?
In the mailman.cfg database section, you probably want
url:
mysql+pymysql://myuser:mypassword@mymysqlhost/mailman?charset=utf8mb4&us
mysql+e_unicode=1
I don't know why you would have a DATABASE_URL setting in the web
configuration. Exactly where is this? I don't think it would be meaningful
in any Django settings.
--
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/
5 years, 2 months
[MM3-users] Re: Installing mailman 3
by Rafael Mora
I got this on maillog:
[root@localhost log]# cat maillog
Jul 24 11:33:13 localhost postfix/postfix-script[2044]: warning: not
set-gid or
not owner+group+world executable:
/usr/sbin/postqueue
Jul 24 11:33:13 localhost postfix/postfix-script[2066]: warning: not
set-gid or
not owner+group+world executable: /usr/sbin/postdrop
Jul 24 11:33:13 localhost postfix/postfix-script[2081]: starting the
Postfix mai
l system
Jul 24 11:33:13 localhost postfix/master[2083]: daemon started -- version
2.10.1
, configuration /etc/postfix
Jul 24 11:35:29 localhost postfix/postfix-script[2115]: warning: not
set-gid or
not owner+group+world executable:
/usr/sbin/postqueue
Jul 24 11:35:29 localhost postfix/postfix-script[2116]: warning: not
set-gid or
not owner+group+world executable: /usr/sbin/postdrop
Jul 24 11:35:29 localhost postfix/postfix-script[2123]: starting the
Postfix mai
l system
Jul 24 11:35:29 localhost postfix/master[2125]: daemon started -- version
2.10.1
, configuration /etc/postfix
Jul 24 13:55:31 localhost postfix/postfix-script[2095]: warning: not
set-gid or
not owner+group+world executable:
/usr/sbin/postqueue
Jul 24 13:55:31 localhost postfix/postfix-script[2096]: warning: not
set-gid or
not owner+group+world executable: /usr/sbin/postdrop
Jul 24 13:55:31 localhost postfix/postfix-script[2105]: starting the
Postfix mai
l system
Jul 24 13:55:32 localhost postfix/master[2110]: daemon started -- version
2.10.1
, configuration /etc/postfix
Jul 24 15:57:26 localhost postfix/postfix-script[2079]: warning: not
set-gid or
not owner+group+world executable:
/usr/sbin/postqueue
Jul 24 15:57:26 localhost postfix/postfix-script[2086]: warning: not
set-gid or
not owner+group+world executable: /usr/sbin/postdrop
Jul 24 15:57:26 localhost postfix/postfix-script[2093]: starting the
Postfix mai
l system
Jul 24 15:57:26 localhost postfix/master[2095]: daemon started -- version
2.10.1
, configuration /etc/postfix
Jul 24 16:33:01 localhost postfix/postfix-script[1993]: warning: not
set-gid or
not owner+group+world executable:
/usr/sbin/postqueue
Jul 24 16:33:01 localhost postfix/postfix-script[1996]: warning: not
set-gid or
not owner+group+world executable: /usr/sbin/postdrop
Jul 24 16:33:01 localhost postfix/postfix-script[2003]: starting the
Postfix mai
l system
Jul 24 16:33:01 localhost postfix/master[2005]: daemon started -- version
2.10.1
, configuration /etc/postfix
Jul 24 17:29:21 localhost postfix/postfix-script[2077]: warning: not
set-gid or
not owner+group+world executable:
/usr/sbin/postqueue
Jul 24 17:29:21 localhost postfix/postfix-script[2079]: warning: not
set-gid or
not owner+group+world executable: /usr/sbin/postdrop
Jul 24 17:29:21 localhost postfix/postfix-script[2092]: starting the
Postfix mai
l system
Jul 24 17:29:21 localhost postfix/master[2096]: daemon started -- version
2.10.1
, configuration /etc/postfix
El lun., 24 jul. 2017 a las 17:23, Mark Sapiro (<mark(a)msapiro.net>)
escribió:
> On 07/24/2017 02:52 PM, Rafael Mora wrote:
> > I did that but I don't have a maillog for today 07.24.2017
>
>
> The current log is just named 'maillog' the ones with dates are older
> logs rotated by logrotate.
>
> --
> 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, 6 months
[MM3-users] Re: Hyperkitty Text/Markdown/HTML
by Mark Sapiro
On 9/8/25 07:22, Sam Darwin via Mailman-users wrote:
> How about a feature to include "HTML" in the current Hyperkitty choices of (Text or Markdown) rendering?
I don't understand what you envision such a rendering to do. First of
all, this setting only affects rendering in HyperKitty thread and
message views of archived messages. It has nothing at all to do with
messages delivered to list members.
Archived messages which contain text/html parts currently render those
parts as attachments that can be downloaded. Are you suggesting that
"HTML" rendering would render those inline or something else?
> A sanitizer must be used to prevent malicious attacks. https://github.com/messense/nh3 . lxml is another package that processes html.
>
> A sanitizer would be helpful for more aspects. Permit a limited set of markdown so that messages still appear professional. Gitlab/Github don't allow arbitrary fonts or font sizes, right? Mostly remove these tags.
>
> A way that code blocks could be presented: determine an established list of known codeblock styles. Configure the sanitizer to permit this range of fonts or styling elements. By allowing them through the filter, a code styling is rendered. (It is permitted/allowed to be rendered.) Even better, when the sanitizer recognizes the fonts, it replaces them with an "official" set of codeblock fonts.
>
> Otherwise, if other font tags are entirely removed, if they are missing, the email client or web ui will decide the font selection, and it will appear "standard".
Your reference to email client suggests you are thinking in terms of
messages delivered to list members. HyperKitty's rendering mode has
nothing to do with that.
> In order for both email clients and Hyperkitty to view the same result, the sanitizer should ideally be applied to outgoing emails as well as rendering in the UI. That means this feature would affect more than just Hyperkitty. (i.e. mailman-core). Although, that could be implemented as a separate step, until which time emails would get a full range of HTML, without sanitizing.
As far as Mailman core is concerned, Things like this are handled in
content filtering. In particular the settings Collapse alternatives and
Convert html to plaintext.
> In this scheme, ensure outgoing emails are multi-part MIME with plain text and html versions.
If the incoming message is multipart/alternative with text/plain and
text/html alternatives and content filtering accepts all those MIME
types and does not Collapse alternatives, the outgoing message will be
the same.
If you're suggesting a text/html part outside of a multipart/alternative
part should cause Mailman to create a text/plain alternative and convert
the text/html part into a multipart/alternative part containing the
text/plain and text/html alternatives, that could be done, but I'm not
interested in doing it. We already have a mechanism for converting HTML
to plain text, but current code replaces the HTML.
As far as converting plain text to HTML, the straight forward way to to
that is just to wrap it in <pre>..</pre> tags, but there seems to be
nothing gained by that. As far as converting urls and email addresses
into clickable links, many MUAs already do that.
> Some of our users are really in favor of more formatting.
>
> Others prefer plain text.
>
> Those who prefer plain text have various arguments that HTML messages will be rendered badly, and won't be legible.
All of the settings mentioned are per list, not user option/
> Questions:
>
> 1. Would "multi-part MIME with plain text and html versions both" solve the problem for users who prefer plain text?
If they set their MUA to render the text/plain alternative.
> 2. What percentage of email clients that support HTML formatting when sending will also include a plain text rendering of the same content in the outgoing message?
Many if not all mainstream ones do or at least have settings to control
it, but some do a horrible job. For example if in Yahoo mail one
composes in "rich text" and drags and drops or copy/pastes or in some
ways even types a link, the generated text/plain alternative doesn't
contain the url in any form - see
<https://www.grizz.org/wiki/PostingURLsToLists>
> 3. Is it usually the responsibility of a receiving mail client to be able to convert HTML to plain text if the user requests it?
If a message part is multipart/alternative and the user wants plain
text, I think most MUAs will just display the text/plain alternative. If
the message is HTML only, I suppose the MUA will convert it somehow.
> 4. When mailman-core receives and then sends out a message, can it receive HTML, generate a plain-text version, and then send both?
Not currently. It can convert the HTML to plain text using a configured
process such as lynx or elinks, but then only the plain text is sent,
not both.
On the other hand, if the incoming message is multipart/alternative and
content filtering is off or appropriately set, the outgoing message will
be multipart/alternative.
--
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
5 months, 2 weeks
[MM3-users] Re: Mailman notify generating emails for request that aren't visible.
by Simon Coggins
The version of postorius is 1.3.4
django-mailman3 1.3.5
mailman 3.3.4
mailman-hyperkitty 1.1.0
mailmanclient 3.3.2
postorius 1.3.4
---
[https://www.cqu.edu.au/]
Mr Simon Coggins
Principal Systems Engineer | Digital Services Directorate
CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000
P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au>
[https://www.cqu.edu.au/social-media]
I respectfully acknowledge the Traditional Owners of the land on which we work and learn,
and pay respect to the First Nations Peoples and their Elders, past, present and future.
This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete.
CRICOS: 00219C | RTO Code 40939
On 1 Nov 2021, at 12:04 pm, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote:
On 10/31/21 6:11 PM, Simon Coggins wrote:
> Hi,
>
> We’re running mailman 3.3.4 (about to upgrade to 3.3.5 this week). I enabled mailman notify cron a few weeks ago to email out any pending requests for admins. I’ve now got multiple lists that keep emailing out the same outstanding holds but they can’t visible in the GUI. The requests are all duplicates as well. This is a redacted example email:
>
> -----Original Message-----
> From: mailman-alerts(a)example.com<mailto:mailman-alerts@example.com><mailto:mailman-alerts@example.com>
> Sent: Monday, 1 November 2021 8:10 AM
> To: somelist-owner(a)lists.example.com<mailto:somelist-owner@lists.example.com><mailto:somelist-owner@lists.example.com>
> Subject: The somelist(a)lists.example.com<mailto:somelist@lists.example.com><mailto:somelist@lists.example.com> list has 4 moderation requests waiting.
>
> The somelist(a)lists.example.com<mailto:somelist@lists.example.com><mailto:somelist@lists.example.com> list has 4 moderation requests waiting.
>
> Held Unsubscriptions:
> User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com><mailto:john.smith@maildomain.com>
> User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com><mailto:john.smith@maildomain.com>
> User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com><mailto:john.smith@maildomain.com>
> User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com><mailto:john.smith@maildomain.com>
>
> Please attend to this at your earliest convenience.
Your lists are configured with Un-Subscription Policy moderate or
confirm, then moderate so unsubs require Moderator approval.
What Postorius version is this? Prior to 1.3.3, unsubsubscription
requests were not visible in Postorius. In 1.3.3_+ they are available in
the Subscription requests dropdown at
https://example.com/mailman3/lists/listname.example.com/unsubscription_requ…<https://example.com/mailman3/lists/listname.example.com/unsubscription_requ…>
although they may not be counted in the Subscription requests count badge.
--
Mark Sapiro <mark(a)msapiro.net<mailto:mark@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<mailto:mailman-users@mailman3.org>
To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org>
https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org>
4 years, 3 months