October 2023 - Mailman-users - lists.mailman3.org

mailman-web compress - Invalid template socialaccount/login_cancelled.html
by Odhiambo Washington 24 Jan '24

24 Jan '24

Running an install on Debian12 VM. Getting a new error message that I haven't seen previously: (venv) mailman@debian12:~$ mailman-web compress Compressing... Invalid template socialaccount/login_cancelled.html: Invalid block tag on line 7: 'element', expected 'endblock'. Did you forget to register or load this tag? Invalid template account/verified_email_required.html: Invalid block tag on line 7: 'element', expected 'endblock'. Did you forget to register or load this tag? Error parsing template socialaccount/signup.html: socialaccount/base.html done Compressed 2 block(s) from 78 template(s) for 1 context(s). -- 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]

7 13

Splitting hosts: mta&core vs postorius
by Ruth Ivimey-Cook 18 Jan '24

18 Jan '24

I'm trying to set up mailman3 on two hosts, one of which runs core + exim, the other runs postorius (&possibly hyperkitty). I have I think got core set up correctly, and postorius is sort of usable, but anything in the web ui that talks to core ends up with a white screen. I think what is happening is a postorius URL ends up with the core (or perhaps no) hostname, and as there's nothing there to answer it fails. I've checked the settings and I don't think I have misconfigured postorius. Is it possible that the bad url is being passed from core to postorius in some way and reused without changing the host? In the config at present, both hosts are visible to the browser, and each host can communicate with the other. Any ideas on how to pin down the problem better? Ruth

6 31

how to migrate mailing lists to a new domain using mailman 3
by C. Souza 18 Jan '24

18 Jan '24

In a few days my current domain will be disabled (it is out of my control) and I would like to know how to migrate the mailing lists to the new domain name. As a solution I added a new domain in mailman 3 and created a script that replicates the lists in this new domain. To forward the emails received by the old lists, the script removes the members and adds the email of the new list. Is there a fashionable way to do that? Also, one problem that I don't have a solution is the archive of the old lists. How to bring them to the new ones? Thanks for your help. My mailing list server is running on a CenOS-7x with postgreSQL and the following mailman packages: Package Version ------------------- ---------- 1 aiosmtpd 1.2.4 2 alembic 1.5.3 3 arrow 0.17.0 4 asgiref 3.3.1 5 atpublic 2.1.2 6 authheaders 0.13.0 7 authres 1.2.0 8 bleach 3.3.0 9 blessed 1.17.12 10 certifi 2020.12.5 11 cffi 1.14.4 12 chardet 4.0.0 13 click 7.1.2 14 cmarkgfm 0.5.2 15 cryptography 3.3.1 16 decorator 4.4.2 17 defusedxml 0.6.0 18 Django 3.0.12 19 django-allauth 0.44.0 20 django-appconf 1.0.4 21 django-compressor 2.4 22 django-extensions 3.1.0 23 django-gravatar2 1.4.4 24 django-haystack 3.0 25 django-mailman3 1.3.5 26 django-picklefield 3.0.1 27 django-q 1.3.4 28 djangorestframework 3.12.2 29 dkimpy 1.0.5 30 dnspython 2.1.0 31 docutils 0.16 32 falcon 2.0.0 33 flufl.bounce 3.0.1 34 flufl.i18n 2.0.2 35 flufl.lock 3.2 36 gunicorn 20.0.4 37 HyperKitty 1.3.3 38 idna 2.10 39 importlib-resources 5.1.0 40 lazr.config 2.2.3 41 lazr.delegates 2.0.4 42 mailman 3.3.2 43 mailman-hyperkitty 1.1.0 44 mailman-web 0.0.3 45 mailmanclient 3.3.2 46 Mako 1.1.4 47 MarkupSafe 1.1.1 48 networkx 2.5 49 nose 1.3.7 50 oauthlib 3.1.0 51 packaging 20.9 52 passlib 1.7.4 53 pip 21.0.1 54 postorius 1.3.3 55 psycopg2-binary 2.8.6 56 publicsuffix2 2.20191221 57 pycparser 2.20 58 Pygments 2.7.4 59 PyJWT 2.0.1 60 pyparsing 2.4.7 61 python-dateutil 2.8.1 62 python-editor 1.0.4 63 python3-openid 3.2.0 64 pytz 2021.1 65 rcssmin 1.0.6 66 readme-renderer 28.0 67 requests 2.25.1 68 requests-oauthlib 1.3.0 69 rjsmin 1.1.0 70 robot-detection 0.4 71 setuptools 39.2.0 72 six 1.15.0 73 SQLAlchemy 1.3.23 74 sqlparse 0.4.1 75 typing-extensions 3.7.4.3 76 urllib3 1.26.3 77 uWSGI 2.0.19.1 78 wcwidth 0.2.5 79 webencodings 0.5.1 80 wheel 0.36.2 81 Whoosh 2.7.4 82 zipp 3.4.0 83 zope.component 4.6.2 84 zope.configuration 4.4.0 85 zope.deferredimport 4.3.1 86 zope.deprecation 4.4.0 87 zope.event 4.5.0 88 zope.hookable 5.0.1 89 zope.i18nmessageid 5.0.1 90 zope.interface 5.2.0 91 zope.proxy 4.3.5 92 zope.schema 6.0.1 -- Carlos Souza

2 1

Loops back to myself
by David Krantz 12 Jan '24

12 Jan '24

Hi, I have a problem with my Mailman 3-setup. The symptom is that postfix rejects non-existing addresses for my list domains with <adr(a)example.com>: mail for example.com loops back to myself What I guess happens happens is that postfix for some reason accepts the mail as it is for a relay domain and finds that it is not deliverable locally as the address does not exist locally and then tries to relay it on to the appropriate MX server, which is itself and then fails and generates a bounce message. This is a bit annoying as I have set up postfix to only accept valid addresses. I have set the transport_maps, local_recipient_maps and relay_domains to the files generated by MM3. I run an older version of MM3 (3.0) but prefer to fix this without upgrading as upgrading is a relatively big undertaking. This is mostly a backscatter problem for spam I guess. Any ideas of very simple and easy to forget things that I've probably missed? Cheers // David

5 6

Archive import fails: "IndexError: list index out of range"
by Johannes Rohr 06 Jan '24

06 Jan '24

I am now importing the archives of my old mailman2 installation. Unfortunately, with some of the larger and older lists, import fails halfway through, with an exception, the last message of which is IndexError: list index out of range Below is an example. This means that the last few years are missing from the archive in several lists. Are there any suggestions what I could do to still get them importet? Thanks! Johannes File "/usr/lib/python3.8/email/_header_value_parser.py", line 2069, in get_msg_id token, value = get_dot_atom_text(value) File "/usr/lib/python3.8/email/_header_value_parser.py", line 1334, in get_dot_atom_text raise errors.HeaderParseError("expected atom at a start of " email.errors.HeaderParseError: expected atom at a start of dot-atom-text but found '@localhost>' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailman/venv/bin/mailman-web", line 8, in <module> sys.exit(main()) File "/opt/mailman/venv/lib/python3.8/site-packages/mailman_web/manage.py", line 37, in main execute_from_command_line(sys.argv) File "/opt/mailman/venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line utility.execute() File "/opt/mailman/venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 440, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/opt/mailman/venv/lib/python3.8/site-packages/django/core/management/base.py", line 402, in run_from_argv self.execute(*args, **cmd_options) File "/opt/mailman/venv/lib/python3.8/site-packages/django/core/management/base.py", line 448, in execute output = self.handle(*args, **options) File "/opt/mailman/venv/lib/python3.8/site-packages/hyperkitty/management/commands/hyperkitty_import.py", line 387, in handle importer.from_mbox(mbfile, report_name) File "/opt/mailman/venv/lib/python3.8/site-packages/hyperkitty/management/commands/hyperkitty_import.py", line 212, in from_mbox progress_marker.tick(unquote(message.get("message-id", 'n/a'))) File "/usr/lib/python3.8/email/message.py", line 471, in get return self.policy.header_fetch_parse(k, v) File "/usr/lib/python3.8/email/policy.py", line 163, in header_fetch_parse return self.header_factory(name, value) File "/usr/lib/python3.8/email/headerregistry.py", line 607, in __call__ return self[name](name, value) File "/usr/lib/python3.8/email/headerregistry.py", line 202, in __new__ cls.parse(value, kwds) File "/usr/lib/python3.8/email/headerregistry.py", line 535, in parse kwds['parse_tree'] = parse_tree = cls.value_parser(value) File "/usr/lib/python3.8/email/_header_value_parser.py", line 2126, in parse_message_id token, value = get_msg_id(value) File "/usr/lib/python3.8/email/_header_value_parser.py", line 2073, in get_msg_id token, value = get_obs_local_part(value) File "/usr/lib/python3.8/email/_header_value_parser.py", line 1516, in get_obs_local_part if (obs_local_part[0].token_type == 'dot' or IndexError: list index out of range

6 10

Re: [Mailman-Developers] Re: SSL error while connecting to hyperkitty
by Abhilash Raj 29 Nov '23

29 Nov '23

On Sat, Aug 31, 2019, at 10:20 AM, sandeep kumar wrote: > Hi Abhilash > > Thanks for the reply. > > Just two more answers please -:) > > Can I use the sample apache.conf in example_project in my webserver virtual host...?? See this thread for the apache configuration: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… You'd need to adjust the paths and SSL configuration. > > And what should be the configuration details to be given in uwsgi server...?? http://docs.mailman3.org/en/latest/prodsetup.html#setting-up-a-wsgi-server > > Regards > Sandeep > > > On Sat, Aug 31, 2019 at 10:25 PM Abhilash Raj <maxking(a)asynchronous.in> wrote: >> __ >> On Sat, Aug 31, 2019, at 8:49 AM, sandeep kumar wrote: >>> Hi Abhilash >>> >>> Thanks for your reply. -:) >>> >>> We are using apache httpd as webserver to redirect. >>> >>> the proxy pass in webserver is >>> >>> ProxyPass / http://localhost:8000 >>> ReverseProxyPass / http://localhost:8000 >> >> >> Can you put `base_url: http://localhost:8000/hyperkitty` in your mailman-hyperkitty.cfg and see that it works? :) >> >> This should not try any funny SSL redirection. >> >>> I don't have idea of deploying this in production, so I just went on searching and I found wsgi (say uwsgi) is required to send the requests from webserver to mailman. Correct me if I am wrong. >>> >>> I have few queries listed below. Please reply to them. >>> >>> Should I use the wsgi.py present in the directory of mailman-suite ...?? >> >> Yes, that is the one which is supposed to be used. >> >>> >>> What should be the ProxyPass ..?? Where should the first hit go from webserver ---> uwsgi ---> ?? >> >> uwsgi is web server running Mailman's web componenet. It doesn't need to hit anything. You can restart it directly when you want to restart Mailman's web component, you don't need to do anything to your web server (httpd) for this. >> >> >> >>> >>> Can we run "python manage.py runserver" every time to start mailman suite..?? Can we make mailman-suite start/stop just by restarting the HTTPD..?? >> >> >> No, use a wsgi server, like uwsgi or gunicorn to run mailman-suote. `python manage.runserver` is a command used during development shouldn't be used at all in prod. >> >>> >>> What should be the entry in Hyperkitty.cfg file after all the above steps..?? I mean at the end >>> >>> Please reply to the above queries. Thanks for your help >>> Regards >>> Sandeep >>> >>> >>> >>> >>> >>> On Sat, Aug 31, 2019 at 8:45 PM Abhilash Raj <maxking(a)asynchronous.in> wrote: >>>> On Sat, Aug 31, 2019, at 1:36 AM, sandeep kumar wrote: >>>> > Hi Team >>>> > >>>> > Iam seeing following errors while mailman is trying to archive in >>>> > mailman.log >>>> > >>>> > >>>> > This is my base URL in mailman-hyperkitty.cfg >>>> > >>>> > base_url: http://localhost/hyperkitty >>>> >>>> Are you sure this is the URL? this is http and Mailman shouldn't try to connect to this using HTTPS. >>>> >>>> Is your web server configured to redirect all HTTP traffic to HTTPS? If that is the case, then it is going to fail. >>>> >>>> Which wsgi server are you using? uwsgi? >>>> >>>> Can you also show your ProxyPass configuration? >>>> >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > *During handling of the above exception, another exception >>>> > occurred:Traceback (most recent call last): File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-py3.6.egg/requests/adapters.py", >>>> > line 449, in send timeout=timeout File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/urllib3-1.24.1-py3.6.egg/urllib3/connectionpool.py", >>>> > line 638, in urlopen _stacktrace=sys.exc_info()[2]) File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/urllib3-1.24.1-py3.6.egg/urllib3/util/retry.py", >>>> > line 398, in increment raise MaxRetryError(_pool, url, error or >>>> > ResponseError(cause))urllib3.exceptions.MaxRetryError: >>>> > HTTPSConnectionPool(host='domain.com <http://domain.com>', port=443): >>>> > Max >>>> > retries exceeded with url: >>>> > /hyperkitty/api/mailman/archive?key=SecretArchiverAPIKey (Caused by >>>> > SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate >>>> > verify >>>> > failed (_ssl.c:841)'),))During handling of the above exception, another >>>> > exception occurred:Traceback (most recent call last): File >>>> > "/var/lib/mailman/mailman-hyperkitty/mailman_hyperkitty/__init__.py", >>>> > line >>>> > 154, in _archive_message url = self._send_message(mlist, msg) File >>>> > "/var/lib/mailman/mailman-hyperkitty/mailman_hyperkitty/__init__.py", >>>> > line >>>> > 201, in _send_message files={"message": ("message.txt", >>>> > message_text)}) >>>> > File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-py3.6.egg/requests/api.py", >>>> > line 116, in post return request('post', url, data=data, json=json, >>>> > **kwargs) File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-py3.6.egg/requests/api.py", >>>> > line 60, in request return session.request(method=method, url=url, >>>> > **kwargs) File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-py3.6.egg/requests/sessions.py", >>>> > line 533, in request resp = self.send(prep, **send_kwargs) File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-py3.6.egg/requests/sessions.py", >>>> > line 668, in send history = [resp for resp in gen] if allow_redirects >>>> > else [] File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-py3.6.egg/requests/sessions.py", >>>> > line 668, in <listcomp> history = [resp for resp in gen] if >>>> > allow_redirects else [] File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-py3.6.egg/requests/sessions.py", >>>> > line 247, in resolve_redirects **adapter_kwargs File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-py3.6.egg/requests/sessions.py", >>>> > line 646, in send r = adapter.send(request, **kwargs) File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-py3.6.egg/requests/adapters.py", >>>> > line 514, in send raise SSLError(e, >>>> > request=request)requests.exceptions.SSLError: >>>> > HTTPSConnectionPool(host=domain.com <http://domain.com>', port=443): Max >>>> > retries exceeded with url: >>>> > /hyperkitty/api/mailman/archive?key=SecretArchiverAPIKey (Caused by >>>> > SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate >>>> > verify >>>> > failed (_ssl.c:841)'),))* >>>> > >>>> > >>>> > Rgrds >>>> > Sandeep >>>> > >>>> > On Sat, Aug 31, 2019 at 10:20 AM sandeep kumar <sandeep7790(a)gmail.com> >>>> > wrote: >>>> > >>>> > > Team any help >>>> > > >>>> > > Sent from my iPhone >>>> > > >>>> > > > On 30-Aug-2019, at 11:18 PM, sandeep kumar <sandeep7790(a)gmail.com> >>>> > > wrote: >>>> > > > >>>> > > > Hi Team >>>> > > > >>>> > > > Iam using httpd to work with ssl on mailman 3 using proxy pass. >>>> > > > >>>> > > > After this configuration Iam not able to connect to hyperkitty. It is >>>> > > throwing ssl certificate error in mailman.log file. >>>> > > > >>>> > > > What should be the configuration of hyperkitty while using https in >>>> > > mailman..? >>>> > > > >>>> > > > Please help me with this Iam struck here from past 4 days >>>> > > > >>>> > > > Rgrds >>>> > > > Sandeep >>>> > > > >>>> > > > Sent from my iPhone >>>> > > >>>> > >>>> > >>>> > -- >>>> > Regards >>>> > Sandeep Kumar >>>> > +91-9642669192 >>>> > _______________________________________________ >>>> > Mailman-Developers mailing list -- mailman-developers(a)python.org >>>> > To unsubscribe send an email to mailman-developers-leave(a)python.org >>>> > https://mail.python.org/mailman3/lists/mailman-developers.python.org/ >>>> > Mailman FAQ: https://wiki.list.org/x/AgA3 >>>> > >>>> > Security Policy: https://wiki.list.org/x/QIA9 >>>> > >>>> >>>> -- >>>> thanks, >>>> Abhilash Raj (maxking) >>> >>> >>> -- >>> Regards >>> Sandeep Kumar >>> +91-9642669192 >>> >> >> -- >> thanks, >> Abhilash Raj (maxking) >> >> > > > -- > Regards > Sandeep Kumar > +91-9642669192 > -- thanks, Abhilash Raj (maxking)

4 3

Mailman3 stopped sending out mail
by Abhijith PA 22 Nov '23

22 Nov '23

Hello. Recently my mailman3 instance stopped distributing mail. But mailman's own mail (notification, digest etc) and archiving are working OK. I couldn't figure what is going wrong From mail.log --- Dec 31 10:03:20 lists postfix/smtpd[10900]: Anonymous TLS connection established from mail.xxxx.xx[5.79.72.163]: TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) Dec 31 10:03:20 lists postfix/smtpd[10900]: Anonymous TLS connection established from mail.xxxx.xx[5.79.72.163]: TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) Dec 31 10:03:20 lists policyd-spf[10907]: prepend Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=5.79.72.163; helo=mail.xxxx.xx; envelope-from=abhijith(a)xxxx.xx; receiver=<UNKNOWN> Dec 31 10:03:20 lists policyd-spf[10907]: prepend Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=5.79.72.163; helo=mail.xxxx.xx; envelope-from=abhijith(a)xxxx.xx; receiver=<UNKNOWN> Dec 31 10:03:21 lists postfix/smtpd[10900]: 04C2412038F: client=mail.xxxx.xx[5.79.72.163] Dec 31 10:03:21 lists postfix/smtpd[10900]: 04C2412038F: client=mail.xxxx.xx[5.79.72.163] Dec 31 10:03:21 lists postfix/cleanup[10912]: 04C2412038F: message-id=<f875c144-a23c-baa2-7de2-1b102d3e7494(a)xxxx.xx> Dec 31 10:03:21 lists postfix/cleanup[10912]: 04C2412038F: message-id=<f875c144-a23c-baa2-7de2-1b102d3e7494(a)xxxx.xx> Dec 31 10:03:21 lists opendkim[450]: 04C2412038F: s=_teknikKey d=xxxx.xx SSL Dec 31 10:03:21 lists opendkim[450]: 04C2412038F: s=_teknikKey d=xxxx.xx SSL Dec 31 10:03:21 lists postfix/smtpd[10900]: disconnect from mail.xxxx.xx[5.79.72.163] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 Dec 31 10:03:21 lists postfix/smtpd[10900]: disconnect from mail.xxxx.xx[5.79.72.163] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 Dec 31 10:03:21 lists postfix/qmgr[13211]: 04C2412038F: from=<abhijith(a)xxxx.xx>, size=1699, nrcpt=1 (queue active) Dec 31 10:03:21 lists postfix/qmgr[13211]: 04C2412038F: from=<abhijith(a)xxxx.xx>, size=1699, nrcpt=1 (queue active) Dec 31 10:03:21 lists postfix/lmtp[10915]: 04C2412038F: to=<test3(a)lists.yyyy.yy>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.87, delays=0.62/0.02/0.04/0.2, dsn=2.0.0, status=sent (250 Ok) Dec 31 10:03:21 lists postfix/lmtp[10915]: 04C2412038F: to=<test3(a)lists.yyyy.yy>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.87, delays=0.62/0.02/0.04/0.2, dsn=2.0.0, status=sent (250 Ok) Dec 31 10:03:21 lists postfix/qmgr[13211]: 04C2412038F: removed Dec 31 10:03:21 lists postfix/qmgr[13211]: 04C2412038F: removed I am not sure why 'postfix/qmgr[13211]: 04C2412038F: removed' is happening. from /var/log/mailman3/smtp.log: Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) handling connection Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) Data: b'LHLO lists.xxxx.xx' Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) Data: b'MAIL FROM:<abhijith(a)xxxx.xx>' Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) sender: abhijith(a)xxxx.xx Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) Data: b'RCPT TO:<test3(a)xxxx.xx>' Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) recip: test3(a)xxxx.xx Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) Data: b'DATA' Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) Data: b'QUIT' Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) connection lost Dec 31 10:03:21 2018 (6323) Connection lost during _handle_client() Here again I am doubtful about 'Connection lost during _handle_client()'. Please help. Abhijith PA

3 5

ModuleNotFoundError: No module named 'mailman_web'
by gordon＠dickens.com 10 Nov '23

10 Nov '23

I have had mailman3 working great on Debian 11, however, I just upgraded to Debian 12 and, following the upgrade, mailman3 is not working and I am getting the following error message: ModuleNotFoundError: No module named 'mailman_web' Does anybody have any recommendations? Thanks! Gordon

5 24

Immediate notification to the administrator
by pau.baiges＠csuc.cat 02 Nov '23

02 Nov '23

Hello In Mailman, I have all the lists marked with the "Immediate notification to the administrator" option. Should list moderators receive immediate notification of new requests as well as daily reminders about the pending ones? List moderators (and list administrators) receive daily reminders of pending requests for approval, such as subscriptions to a moderated list or submissions that are held for some reason. Enabling this option results in immediate notifications being sent upon the arrival of new requests. When there's a message being held because it needs approval, it automatically sends an email to the list owners. However, it also states that it sends a daily reminder if the email remains unapproved, but it's not doing that. I'll show you how I have /etc/postfix/transport configured. I receive the first "owner" email, but not the daily one. list-owner(a)llistes.csuc.cat relay:[ip]:25 list(a)llistes.csuc.cat .. list-admin(a)llistes.csuc.cat ... list-bounces(a)llistes.csuc.cat ... list-confirm(a)llistes.csuc.cat ... list-join(a)llistes.csuc.cat ... list-leave(a)llistes.csuc.cat ... list-request(a)llistes.csuc.cat ... list-subscribe(a)llistes.csuc.cat ...

5 9

Reduction of spam - FROM_LOCAL_HEX
by Kyriakos Terzopoulos 31 Oct '23

31 Oct '23

Hi, After fixing all issues with mailman I want to reduce the chance for email being marked as spam, especially from Gmail. I have added SPF and DKIM records and I am now using dkimvalidator to debug the emails being sent. Here is what I'm getting from spam evaluation: *0.3 FROM_LOCAL_HEX From: localpart has long hexadecimal sequence* My guess is that the From address is very large, for example: mylist-confirm+3eafa5bd24e52738c900e2e3fd05e366b7ea7580(a)myproject.eu Is there any way to mitigate this problem? Thank you, *Kyriakos Terzopoulos* Web developer / e-learning expert *Tel:*+30 211 213 9858 *Mobile:* +30 694 526 4512 * E-mail: *kyriakos.terzopoulos(a)gmail.com * Skype:* kyriakos.terzopoulos Find me on Facebook <http://www.facebook.com/cirrus3d> Follow me on Twitter <http://twitter.com/#%21/cirrus3d>

4 3