I set up the mailman3 services and lists, and we can send mail to the list successfully. However in the Archive section I couldn't see anything. My configuration: ubuntu, milman core 3.2.2, postresql, postorius 1.2.4, hyperkitty 1.3.2
This is my mailman conf result:
[antispam] header_checks: [antispam] jump_chain: hold [archiver.mail_archive] class: mailman.archiving.mailarchive.MailArchive [archiver.mail_archive] clobber_date: maybe [archiver.mail_archive] clobber_skew: 1d [archiver.mail_archive] configuration: python:mailman.config.mail_archive [archiver.mail_archive] enable: no [archiver.mhonarc] class: mailman.archiving.mhonarc.MHonArc [archiver.mhonarc] clobber_date: maybe [archiver.mhonarc] clobber_skew: 1d [archiver.mhonarc] configuration: python:mailman.config.mhonarc [archiver.mhonarc] enable: no [archiver.prototype] class: mailman.archiving.prototype.Prototype [archiver.prototype] clobber_date: maybe [archiver.prototype] clobber_skew: 1d [archiver.prototype] configuration: changeme [archiver.prototype] enable: no [bounces] register_bounces_every: 15m [database] class: mailman.database.postgresql.PostgreSQLDatabase [database] debug: no [database] url: postgres://mailman3:--------------@localhost/mailman3 [devmode] enabled: no [devmode] recipient: [devmode] testing: no [devmode] wait: 60s [digests] mime_digest_keep_headers: Date From To Cc Subject Message-ID Keywords In-Reply-To References Content-Type MIME-Version Content-Transfer-Encoding Precedence Reply-To Message List-Post [digests] plain_digest_keep_headers: Message Date From Subject To Cc Message-ID Keywords Content-Type [dmarc] cache_lifetime: 7d [dmarc] org_domain_data_url: https://publicsuffix.org/list/public_suffix_list.dat [dmarc] resolver_lifetime: 5s [dmarc] resolver_timeout: 3s [language.ar] charset: utf-8 [language.ar] description: Arabic [language.ar] enabled: yes [language.ast] charset: iso-8859-1 [language.ast] description: Asturian [language.ast] enabled: yes [language.ca] charset: utf-8 [language.ca] description: Catalan [language.ca] enabled: yes [language.cs] charset: iso-8859-2 [language.cs] description: Czech [language.cs] enabled: yes [language.da] charset: iso-8859-1 [language.da] description: Danish [language.da] enabled: yes [language.de] charset: utf-8 [language.de] description: German [language.de] enabled: yes [language.el] charset: iso-8859-7 [language.el] description: Greek [language.el] enabled: yes [language.es] charset: iso-8859-1 [language.es] description: Spanish [language.es] enabled: yes [language.et] charset: iso-8859-15 [language.et] description: Estonian [language.et] enabled: yes [language.eu] charset: iso-8859-15 [language.eu] description: Euskara [language.eu] enabled: yes [language.fi] charset: iso-8859-1 [language.fi] description: Finnish [language.fi] enabled: yes [language.fr] charset: iso-8859-1 [language.fr] description: French [language.fr] enabled: yes [language.gl] charset: utf-8 [language.gl] description: Galician [language.gl] enabled: yes [language.he] charset: utf-8 [language.he] description: Hebrew [language.he] enabled: yes [language.hr] charset: iso-8859-2 [language.hr] description: Croatian [language.hr] enabled: yes [language.hu] charset: iso-8859-2 [language.hu] description: Hungarian [language.hu] enabled: yes [language.ia] charset: iso-8859-15 [language.ia] description: Interlingua [language.ia] enabled: yes [language.it] charset: iso-8859-1 [language.it] description: Italian [language.it] enabled: yes [language.ja] charset: euc-jp [language.ja] description: Japanese [language.ja] enabled: yes [language.ko] charset: euc-kr [language.ko] description: Korean [language.ko] enabled: yes [language.lt] charset: iso-8859-13 [language.lt] description: Lithuanian [language.lt] enabled: yes [language.nl] charset: iso-8859-1 [language.nl] description: Dutch [language.nl] enabled: yes [language.no] charset: iso-8859-1 [language.no] description: Norwegian [language.no] enabled: yes [language.pl] charset: iso-8859-2 [language.pl] description: Polish [language.pl] enabled: yes [language.pt] charset: iso-8859-1 [language.pt] description: Protuguese [language.pt] enabled: yes [language.pt_BR] charset: iso-8859-1 [language.pt_BR] description: Protuguese (Brazil) [language.pt_BR] enabled: yes [language.ro] charset: iso-8859-2 [language.ro] description: Romanian [language.ro] enabled: yes [language.ru] charset: koi8-r [language.ru] description: Russian [language.ru] enabled: yes [language.sk] charset: utf-8 [language.sk] description: Slovak [language.sk] enabled: yes [language.sl] charset: iso-8859-2 [language.sl] description: Slovenian [language.sl] enabled: yes [language.sr] charset: utf-8 [language.sr] description: Serbian [language.sr] enabled: yes [language.sv] charset: iso-8859-1 [language.sv] description: Swedish [language.sv] enabled: yes [language.tr] charset: iso-8859-9 [language.tr] description: Turkish [language.tr] enabled: yes [language.uk] charset: utf-8 [language.uk] description: Ukrainian [language.uk] enabled: yes [language.vi] charset: utf-8 [language.vi] description: Vietnamese [language.vi] enabled: yes [language.zh_CN] charset: utf-8 [language.zh_CN] description: Chinese [language.zh_CN] enabled: yes [language.zh_TW] charset: utf-8 [language.zh_TW] description: Chinese (Taiwan) [language.zh_TW] enabled: yes [logging.archiver] datefmt: %b %d %H:%M:%S %Y [logging.archiver] format: %(asctime)s (%(process)d) %(message)s [logging.archiver] level: info [logging.archiver] path: mailman.log [logging.archiver] propagate: no [logging.bounce] datefmt: %b %d %H:%M:%S %Y [logging.bounce] format: %(asctime)s (%(process)d) %(message)s [logging.bounce] level: info [logging.bounce] path: bounce.log [logging.bounce] propagate: no [logging.config] datefmt: %b %d %H:%M:%S %Y [logging.config] format: %(asctime)s (%(process)d) %(message)s [logging.config] level: info [logging.config] path: mailman.log [logging.config] propagate: no [logging.database] datefmt: %b %d %H:%M:%S %Y [logging.database] format: %(asctime)s (%(process)d) %(message)s [logging.database] level: warn [logging.database] path: mailman.log [logging.database] propagate: no [logging.debug] datefmt: %b %d %H:%M:%S %Y [logging.debug] format: %(asctime)s (%(process)d) %(message)s [logging.debug] level: info [logging.debug] path: debug.log [logging.debug] propagate: no [logging.error] datefmt: %b %d %H:%M:%S %Y [logging.error] format: %(asctime)s (%(process)d) %(message)s [logging.error] level: info [logging.error] path: mailman.log [logging.error] propagate: no [logging.fromusenet] datefmt: %b %d %H:%M:%S %Y [logging.fromusenet] format: %(asctime)s (%(process)d) %(message)s [logging.fromusenet] level: info [logging.fromusenet] path: mailman.log [logging.fromusenet] propagate: no [logging.http] datefmt: %b %d %H:%M:%S %Y [logging.http] format: %(asctime)s (%(process)d) %(message)s [logging.http] level: info [logging.http] path: mailman.log [logging.http] propagate: no [logging.locks] datefmt: %b %d %H:%M:%S %Y [logging.locks] format: %(asctime)s (%(process)d) %(message)s [logging.locks] level: info [logging.locks] path: mailman.log [logging.locks] propagate: no [logging.mischief] datefmt: %b %d %H:%M:%S %Y [logging.mischief] format: %(asctime)s (%(process)d) %(message)s [logging.mischief] level: info [logging.mischief] path: mailman.log [logging.mischief] propagate: no [logging.plugins] datefmt: %b %d %H:%M:%S %Y [logging.plugins] format: %(asctime)s (%(process)d) %(message)s [logging.plugins] level: info [logging.plugins] path: plugins.log [logging.plugins] propagate: no [logging.root] datefmt: %b %d %H:%M:%S %Y [logging.root] format: %(asctime)s (%(process)d) %(message)s [logging.root] level: info [logging.root] path: mailman.log [logging.root] propagate: no [logging.runner] datefmt: %b %d %H:%M:%S %Y [logging.runner] format: %(asctime)s (%(process)d) %(message)s [logging.runner] level: info [logging.runner] path: mailman.log [logging.runner] propagate: no [logging.smtp] datefmt: %b %d %H:%M:%S %Y [logging.smtp] every: $msgid smtp to $listname for $recip recips, completed in $time seconds [logging.smtp] failure: $msgid delivery to $recip failed with code $smtpcode, $smtpmsg [logging.smtp] format: %(asctime)s (%(process)d) %(message)s [logging.smtp] level: info [logging.smtp] path: smtp.log [logging.smtp] propagate: no [logging.smtp] refused: $msgid post to $listname from $sender, $size bytes, $refused failures [logging.smtp] success: $msgid post to $listname from $sender, $size bytes [logging.subscribe] datefmt: %b %d %H:%M:%S %Y [logging.subscribe] format: %(asctime)s (%(process)d) %(message)s [logging.subscribe] level: info [logging.subscribe] path: mailman.log [logging.subscribe] propagate: no [logging.vette] datefmt: %b %d %H:%M:%S %Y [logging.vette] format: %(asctime)s (%(process)d) %(message)s [logging.vette] level: info [logging.vette] path: mailman.log [logging.vette] propagate: no [mailman] cache_life: 7d [mailman] default_language: en [mailman] email_commands_max_lines: 10 [mailman] filtered_messages_are_preservable: no [mailman] html_to_plain_text_command: /usr/bin/lynx -dump $filename [mailman] layout: debian [mailman] listname_chars: [-_.0-9a-z] [mailman] noreply_address: noreply [mailman] pending_request_life: 3d [mailman] post_hook: [mailman] pre_hook: [mailman] sender_headers: from from_ reply-to sender [mailman] site_owner: max.paragnani@gmail.com [mta] configuration: python:mailman.config.postfix [mta] delivery_retry_period: 5d [mta] incoming: mailman.mta.postfix.LMTP [mta] lmtp_host: 127.0.0.1 [mta] lmtp_port: 8024 [mta] max_autoresponses_per_day: 10 [mta] max_delivery_threads: 0 [mta] max_recipients: 500 [mta] max_sessions_per_connection: 0 [mta] outgoing: mailman.mta.deliver.deliver [mta] remove_dkim_headers: no [mta] smtp_host: localhost [mta] smtp_pass: [mta] smtp_port: 25 [mta] smtp_user: [mta] verp_confirm_format: $address+$cookie [mta] verp_confirm_regexp: ^(.*<)?(?P<addr>[^+]+?)\+(?P<cookie>[^@]+)@.*$ [mta] verp_confirmations: no [mta] verp_delimiter: + [mta] verp_delivery_interval: 0 [mta] verp_format: ${bounces}+${local}=${domain} [mta] verp_personalized_deliveries: no [mta] verp_probe_format: $bounces+$token@$domain [mta] verp_probe_regexp: ^(?P<bounces>[^+]+?)\+(?P<token>[^@]+)@.*$ [mta] verp_probes: no [mta] verp_regexp: ^(?P<bounces>[^+]+?)\+(?P<local>[^=]+)=(?P<domain>[^@]+)@.*$ [nntp] host: [nntp] password: [nntp] port: [nntp] remove_headers: nntp-posting-host nntp-posting-date x-trace x-complaints-to xref date-received posted posting-version relay-version received [nntp] rewrite_duplicate_headers: To X-Original-To CC X-Original-CC Content-Transfer-Encoding X-Original-Content-Transfer-Encoding MIME-Version X-MIME-Version [nntp] user: [passwords] configuration: python:mailman.config.passlib [passwords] password_length: 8 [plugin.master] class: [plugin.master] component_package: [plugin.master] configuration: [plugin.master] enabled: no [shell] banner: Welcome to the GNU Mailman shell [shell] history_file: [shell] prompt: >>> [shell] use_ipython: no [styles] default: legacy-default [webservice] admin_pass: --------------------------------- [webservice] admin_user: restadmin [webservice] api_version: 3.1 [webservice] hostname: localhost [webservice] port: 8001 [webservice] show_tracebacks: yes [webservice] use_https: no
SOLVED! I edited /etc/mailman3/mailman3-web.py adding in MAILMAN_ARCHIVER_FROM = the ip of the server and finally starts to work
Il Ven 27 Gen 2023, 18:52 Massimiliano Paragnani <max.paragnani@gmail.com> ha scritto:
I set up the mailman3 services and lists, and we can send mail to the list successfully. However in the Archive section I couldn't see anything. My configuration: ubuntu, milman core 3.2.2, postresql, postorius 1.2.4, hyperkitty 1.3.2
This is my mailman conf result:
[antispam] header_checks: [antispam] jump_chain: hold [archiver.mail_archive] class: mailman.archiving.mailarchive.MailArchive [archiver.mail_archive] clobber_date: maybe [archiver.mail_archive] clobber_skew: 1d [archiver.mail_archive] configuration: python:mailman.config.mail_archive [archiver.mail_archive] enable: no [archiver.mhonarc] class: mailman.archiving.mhonarc.MHonArc [archiver.mhonarc] clobber_date: maybe [archiver.mhonarc] clobber_skew: 1d [archiver.mhonarc] configuration: python:mailman.config.mhonarc [archiver.mhonarc] enable: no [archiver.prototype] class: mailman.archiving.prototype.Prototype [archiver.prototype] clobber_date: maybe [archiver.prototype] clobber_skew: 1d [archiver.prototype] configuration: changeme [archiver.prototype] enable: no [bounces] register_bounces_every: 15m [database] class: mailman.database.postgresql.PostgreSQLDatabase [database] debug: no [database] url: postgres://mailman3:--------------@localhost/mailman3 [devmode] enabled: no [devmode] recipient: [devmode] testing: no [devmode] wait: 60s [digests] mime_digest_keep_headers: Date From To Cc Subject Message-ID Keywords In-Reply-To References Content-Type MIME-Version Content-Transfer-Encoding Precedence Reply-To Message List-Post [digests] plain_digest_keep_headers: Message Date From Subject To Cc Message-ID Keywords Content-Type [dmarc] cache_lifetime: 7d [dmarc] org_domain_data_url: https://publicsuffix.org/list/public_suffix_list.dat [dmarc] resolver_lifetime: 5s [dmarc] resolver_timeout: 3s [language.ar] charset: utf-8 [language.ar] description: Arabic [language.ar] enabled: yes [language.ast] charset: iso-8859-1 [language.ast] description: Asturian [language.ast] enabled: yes [language.ca] charset: utf-8 [language.ca] description: Catalan [language.ca] enabled: yes [language.cs] charset: iso-8859-2 [language.cs] description: Czech [language.cs] enabled: yes [language.da] charset: iso-8859-1 [language.da] description: Danish [language.da] enabled: yes [language.de] charset: utf-8 [language.de] description: German [language.de] enabled: yes [language.el] charset: iso-8859-7 [language.el] description: Greek [language.el] enabled: yes [language.es] charset: iso-8859-1 [language.es] description: Spanish [language.es] enabled: yes [language.et] charset: iso-8859-15 [language.et] description: Estonian [language.et] enabled: yes [language.eu] charset: iso-8859-15 [language.eu] description: Euskara [language.eu] enabled: yes [language.fi] charset: iso-8859-1 [language.fi] description: Finnish [language.fi] enabled: yes [language.fr] charset: iso-8859-1 [language.fr] description: French [language.fr] enabled: yes [language.gl] charset: utf-8 [language.gl] description: Galician [language.gl] enabled: yes [language.he] charset: utf-8 [language.he] description: Hebrew [language.he] enabled: yes [language.hr] charset: iso-8859-2 [language.hr] description: Croatian [language.hr] enabled: yes [language.hu] charset: iso-8859-2 [language.hu] description: Hungarian [language.hu] enabled: yes [language.ia] charset: iso-8859-15 [language.ia] description: Interlingua [language.ia] enabled: yes [language.it] charset: iso-8859-1 [language.it] description: Italian [language.it] enabled: yes [language.ja] charset: euc-jp [language.ja] description: Japanese [language.ja] enabled: yes [language.ko] charset: euc-kr [language.ko] description: Korean [language.ko] enabled: yes [language.lt] charset: iso-8859-13 [language.lt] description: Lithuanian [language.lt] enabled: yes [language.nl] charset: iso-8859-1 [language.nl] description: Dutch [language.nl] enabled: yes [language.no] charset: iso-8859-1 [language.no] description: Norwegian [language.no] enabled: yes [language.pl] charset: iso-8859-2 [language.pl] description: Polish [language.pl] enabled: yes [language.pt] charset: iso-8859-1 [language.pt] description: Protuguese [language.pt] enabled: yes [language.pt_BR] charset: iso-8859-1 [language.pt_BR] description: Protuguese (Brazil) [language.pt_BR] enabled: yes [language.ro] charset: iso-8859-2 [language.ro] description: Romanian [language.ro] enabled: yes [language.ru] charset: koi8-r [language.ru] description: Russian [language.ru] enabled: yes [language.sk] charset: utf-8 [language.sk] description: Slovak [language.sk] enabled: yes [language.sl] charset: iso-8859-2 [language.sl] description: Slovenian [language.sl] enabled: yes [language.sr] charset: utf-8 [language.sr] description: Serbian [language.sr] enabled: yes [language.sv] charset: iso-8859-1 [language.sv] description: Swedish [language.sv] enabled: yes [language.tr] charset: iso-8859-9 [language.tr] description: Turkish [language.tr] enabled: yes [language.uk] charset: utf-8 [language.uk] description: Ukrainian [language.uk] enabled: yes [language.vi] charset: utf-8 [language.vi] description: Vietnamese [language.vi] enabled: yes [language.zh_CN] charset: utf-8 [language.zh_CN] description: Chinese [language.zh_CN] enabled: yes [language.zh_TW] charset: utf-8 [language.zh_TW] description: Chinese (Taiwan) [language.zh_TW] enabled: yes [logging.archiver] datefmt: %b %d %H:%M:%S %Y [logging.archiver] format: %(asctime)s (%(process)d) %(message)s [logging.archiver] level: info [logging.archiver] path: mailman.log [logging.archiver] propagate: no [logging.bounce] datefmt: %b %d %H:%M:%S %Y [logging.bounce] format: %(asctime)s (%(process)d) %(message)s [logging.bounce] level: info [logging.bounce] path: bounce.log [logging.bounce] propagate: no [logging.config] datefmt: %b %d %H:%M:%S %Y [logging.config] format: %(asctime)s (%(process)d) %(message)s [logging.config] level: info [logging.config] path: mailman.log [logging.config] propagate: no [logging.database] datefmt: %b %d %H:%M:%S %Y [logging.database] format: %(asctime)s (%(process)d) %(message)s [logging.database] level: warn [logging.database] path: mailman.log [logging.database] propagate: no [logging.debug] datefmt: %b %d %H:%M:%S %Y [logging.debug] format: %(asctime)s (%(process)d) %(message)s [logging.debug] level: info [logging.debug] path: debug.log [logging.debug] propagate: no [logging.error] datefmt: %b %d %H:%M:%S %Y [logging.error] format: %(asctime)s (%(process)d) %(message)s [logging.error] level: info [logging.error] path: mailman.log [logging.error] propagate: no [logging.fromusenet] datefmt: %b %d %H:%M:%S %Y [logging.fromusenet] format: %(asctime)s (%(process)d) %(message)s [logging.fromusenet] level: info [logging.fromusenet] path: mailman.log [logging.fromusenet] propagate: no [logging.http] datefmt: %b %d %H:%M:%S %Y [logging.http] format: %(asctime)s (%(process)d) %(message)s [logging.http] level: info [logging.http] path: mailman.log [logging.http] propagate: no [logging.locks] datefmt: %b %d %H:%M:%S %Y [logging.locks] format: %(asctime)s (%(process)d) %(message)s [logging.locks] level: info [logging.locks] path: mailman.log [logging.locks] propagate: no [logging.mischief] datefmt: %b %d %H:%M:%S %Y [logging.mischief] format: %(asctime)s (%(process)d) %(message)s [logging.mischief] level: info [logging.mischief] path: mailman.log [logging.mischief] propagate: no [logging.plugins] datefmt: %b %d %H:%M:%S %Y [logging.plugins] format: %(asctime)s (%(process)d) %(message)s [logging.plugins] level: info [logging.plugins] path: plugins.log [logging.plugins] propagate: no [logging.root] datefmt: %b %d %H:%M:%S %Y [logging.root] format: %(asctime)s (%(process)d) %(message)s [logging.root] level: info [logging.root] path: mailman.log [logging.root] propagate: no [logging.runner] datefmt: %b %d %H:%M:%S %Y [logging.runner] format: %(asctime)s (%(process)d) %(message)s [logging.runner] level: info [logging.runner] path: mailman.log [logging.runner] propagate: no [logging.smtp] datefmt: %b %d %H:%M:%S %Y [logging.smtp] every: $msgid smtp to $listname for $recip recips, completed in $time seconds [logging.smtp] failure: $msgid delivery to $recip failed with code $smtpcode, $smtpmsg [logging.smtp] format: %(asctime)s (%(process)d) %(message)s [logging.smtp] level: info [logging.smtp] path: smtp.log [logging.smtp] propagate: no [logging.smtp] refused: $msgid post to $listname from $sender, $size bytes, $refused failures [logging.smtp] success: $msgid post to $listname from $sender, $size bytes [logging.subscribe] datefmt: %b %d %H:%M:%S %Y [logging.subscribe] format: %(asctime)s (%(process)d) %(message)s [logging.subscribe] level: info [logging.subscribe] path: mailman.log [logging.subscribe] propagate: no [logging.vette] datefmt: %b %d %H:%M:%S %Y [logging.vette] format: %(asctime)s (%(process)d) %(message)s [logging.vette] level: info [logging.vette] path: mailman.log [logging.vette] propagate: no [mailman] cache_life: 7d [mailman] default_language: en [mailman] email_commands_max_lines: 10 [mailman] filtered_messages_are_preservable: no [mailman] html_to_plain_text_command: /usr/bin/lynx -dump $filename [mailman] layout: debian [mailman] listname_chars: [-_.0-9a-z] [mailman] noreply_address: noreply [mailman] pending_request_life: 3d [mailman] post_hook: [mailman] pre_hook: [mailman] sender_headers: from from_ reply-to sender [mailman] site_owner: max.paragnani@gmail.com [mta] configuration: python:mailman.config.postfix [mta] delivery_retry_period: 5d [mta] incoming: mailman.mta.postfix.LMTP [mta] lmtp_host: 127.0.0.1 [mta] lmtp_port: 8024 [mta] max_autoresponses_per_day: 10 [mta] max_delivery_threads: 0 [mta] max_recipients: 500 [mta] max_sessions_per_connection: 0 [mta] outgoing: mailman.mta.deliver.deliver [mta] remove_dkim_headers: no [mta] smtp_host: localhost [mta] smtp_pass: [mta] smtp_port: 25 [mta] smtp_user: [mta] verp_confirm_format: $address+$cookie [mta] verp_confirm_regexp: ^(.*<)?(?P<addr>[^+]+?)\+(?P<cookie>[^@]+)@.*$ [mta] verp_confirmations: no [mta] verp_delimiter: + [mta] verp_delivery_interval: 0 [mta] verp_format: ${bounces}+${local}=${domain} [mta] verp_personalized_deliveries: no [mta] verp_probe_format: $bounces+$token@$domain [mta] verp_probe_regexp: ^(?P<bounces>[^+]+?)\+(?P<token>[^@]+)@.*$ [mta] verp_probes: no [mta] verp_regexp: ^(?P<bounces>[^+]+?)\+(?P<local>[^=]+)=(?P<domain>[^@]+)@.*$ [nntp] host: [nntp] password: [nntp] port: [nntp] remove_headers: nntp-posting-host nntp-posting-date x-trace x-complaints-to xref date-received posted posting-version relay-version received [nntp] rewrite_duplicate_headers: To X-Original-To CC X-Original-CC Content-Transfer-Encoding X-Original-Content-Transfer-Encoding MIME-Version X-MIME-Version [nntp] user: [passwords] configuration: python:mailman.config.passlib [passwords] password_length: 8 [plugin.master] class: [plugin.master] component_package: [plugin.master] configuration: [plugin.master] enabled: no [shell] banner: Welcome to the GNU Mailman shell [shell] history_file: [shell] prompt: >>> [shell] use_ipython: no [styles] default: legacy-default [webservice] admin_pass: --------------------------------- [webservice] admin_user: restadmin [webservice] api_version: 3.1 [webservice] hostname: localhost [webservice] port: 8001 [webservice] show_tracebacks: yes [webservice] use_https: no
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@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 max.paragnani@gmail.com
I am having a similar issue as described below. I don't have /etc/mailman3/mailman3-web.py
I added MAILMAN_ARCHIVER_FROM variable in /etc/mailman3/settings.py instead. It did *not* solve the issue. Hyperkitty is blank. More questions below
On January 27, 2023 7:30:22 PM GMT+01:00, Massimiliano Paragnani <max.paragnani@gmail.com> wrote:
SOLVED! I edited /etc/mailman3/mailman3-web.py adding in MAILMAN_ARCHIVER_FROM = the ip of the server and finally starts to work
Is this a string value or a list? Perhaps I did something wrong here. Any documentation on this?
My instance is not archiving.
On Mon, Jan 30, 2023 at 3:41 PM Onyeibo Oku <onyeibo@schemefusion.com> wrote:
I am having a similar issue as described below. I don't have /etc/mailman3/mailman3-web.py
I added MAILMAN_ARCHIVER_FROM variable in /etc/mailman3/settings.py instead. It did *not* solve the issue. Hyperkitty is blank. More questions below
On January 27, 2023 7:30:22 PM GMT+01:00, Massimiliano Paragnani < max.paragnani@gmail.com> wrote:
SOLVED! I edited /etc/mailman3/mailman3-web.py adding in MAILMAN_ARCHIVER_FROM = the ip of the server and finally starts to work
Is this a string value or a list?
MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1') So an array??
Perhaps I did something wrong here. Any documentation on this?
https://mailman-web.readthedocs.io/en/latest/settings.html
My instance is not archiving.
Things to check:
- Is your MAILMAN_ARCHIVER_KEY value in settings.py (quoted here!) the same as api_key in mailman-hyperkitty.cf (unquoted here!)?
- Your MM3 log files - do they say anything?
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
am having a similar issue as described below. I don't have /etc/mailman3/mailman3-web.py Sorry... The correct file is /etc/mailman3/mailman-web.py. Add the public ip of your server in MAILMAN_ARCHIVER_FROM
Try to check if secret key is the same in: MAILMAN_ARCHIVER_KEY = in /etc/mailman3/mailman-web.py (with quotes), and in api_key in /etc/mailman3/mailman-hyperkitty.cfg (without quotes)
Check the base_url too in /etc/mailman3/mailman-hyperkitty.cfg
On 1/30/23 05:43, Massimiliano Paragnani wrote:
am having a similar issue as described below. I don't have /etc/mailman3/mailman3-web.py Sorry... The correct file is /etc/mailman3/mailman-web.py.
If one is following <https://docs.mailman3.org/en/latest/install/virtualenv.html>, the correct file is /etc/mailman3/settings.py.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 1/30/23 05:01, Odhiambo Washington wrote:
MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1') So an array??
In Python ('127.0.0.1', '::1') is a tuple. MAILMAN_ARCHIVER_FROM is a sequence <https://docs.python.org/3/library/stdtypes.html#sequence-types-list-tuple-ra...>. It can be a tuple as above or a list like ['127.0.0.1', '::1']
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Mon, Jan 30, 2023 at 6:54 PM Mark Sapiro <mark@msapiro.net> wrote:
On 1/30/23 05:01, Odhiambo Washington wrote:
MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1') So an array??
In Python ('127.0.0.1', '::1') is a tuple. MAILMAN_ARCHIVER_FROM is a sequence < https://docs.python.org/3/library/stdtypes.html#sequence-types-list-tuple-ra...>.
It can be a tuple as above or a list like ['127.0.0.1', '::1']
muito obrigado :)
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
On Mon, 30 Jan 2023 16:01:16 +0300 Odhiambo Washington <odhiambo@gmail.com> wrote:
MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1') So an array??
These are defaults. I have also added my IPs. Nothing is happening.
Perhaps I did something wrong here. Any documentation on this?
https://mailman-web.readthedocs.io/en/latest/settings.ht
My instance is not archiving.
Things to check: the same as api_key in mailman-hyperkitty.cf (unquoted here!)?
- Is your MAILMAN_ARCHIVER_KEY value in settings.py (quoted here!)
I have double-checked this. Yes ... I got it right
- Your MM3 log files - do they say anything?
Nothing! No new errors. It is very strange and frustrating
Onyeibo
On Mon, Jan 30, 2023 at 10:58 PM Onyeibo <onyeibo@schemefusion.com> wrote:
On Mon, 30 Jan 2023 16:01:16 +0300 Odhiambo Washington <odhiambo@gmail.com> wrote:
MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1') So an array??
These are defaults. I have also added my IPs. Nothing is happening.
Perhaps I did something wrong here. Any documentation on this?
https://mailman-web.readthedocs.io/en/latest/settings.ht
My instance is not archiving.
Things to check: the same as api_key in mailman-hyperkitty.cf (unquoted here!)?
- Is your MAILMAN_ARCHIVER_KEY value in settings.py (quoted here!)
I have double-checked this. Yes ... I got it right
- Your MM3 log files - do they say anything?
Nothing! No new errors. It is very strange and frustrating
Simply put:
Mailman3 uses the following components for archiving:
Archiver: responsible for storing messages and metadata, such as message header information, in the archive database. Archiver API: provides an interface for accessing the archived messages. Archiver REST API: allows access to the archives through a RESTful interface.
To configure Mailman3 archiving, you can:
Choose an archive backend, such as the built-in HyperKitty backend, or a third-party archive backend. Set up the archive backend, including database connection details and other required configurations. Configure Mailman3 to use the chosen archive backend. This typically involves updating the Mailman3 configuration file and specifying the backend's configuration information. You can find more information about Mailman3 archiving and its configuration in the Mailman3 documentation.
Now you need to go over the archiver configuration/enablement with a toothcomb :)
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
On 1/30/23 11:58, Onyeibo wrote:
- Your MM3 log files - do they say anything?
Nothing! No new errors. It is very strange and frustrating
Are there files in /opt/mailman/mm/var/archives/hyperkitty/spool/?
Do messages received from the list have an Archived-At: header:?
Do messages received from the list have a List-Archive: header:?
If the first answer is yes, the mailman_hyperkitty archive_message method is failing.
If the second answer is no, the mailman_hyperkitty permalink method is failing.
If the second answer is no, the mailman_hyperkitty list_url method is failing.
All of these failures log errors to the mailman.archiver log which by default is written to mailman.log.
If by chance there is an Archived-At: header, what is it?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hi Mark,
On Mon, 30 Jan 2023 12:24:24 -0800 Mark Sapiro <mark@msapiro.net> wrote:
On 1/30/23 11:58, Onyeibo wrote:
- Your MM3 log files - do they say anything?
Nothing! No new errors. It is very strange and frustrating
Are there files in /opt/mailman/mm/var/archives/hyperkitty/spool/?
YES! A lot of them
Do messages received from the list have an Archived-At: header:?
No
Do messages received from the list have a List-Archive: header:?
No
If the first answer is yes, the mailman_hyperkitty archive_message method is failing.
If the second answer is no, the mailman_hyperkitty permalink method is failing.
If the second answer is no, the mailman_hyperkitty list_url method is failing.
That means they are all failing. Wow
All of these failures log errors to the mailman.archiver log which by default is written to mailman.log.
The log doesn't have entries pointing to failures above
If by chance there is an Archived-At: header, what is it?
The mails don't have that header. I suspect I may have to investigate SELinux.
On 1/30/23 13:17, Onyeibo wrote:
The mails don't have that header. I suspect I may have to investigate SELinux.
I think it's unlikely a SELinux issue unless you mean it's an issue writing the log, but if there are any entries at all in mailman.log, that should be OK.
what does mailman conf -s archiver.hyperkitty -k configuration show?
The default is /etc/mailman3/mailman-hyperkitty.cfg. Whatever it is,
what's in that file. It should be something like
[general]
base_url: http://127.0.0.1:8000/archives/
api_key: some_key
some_key needs to match
MAILMAN_ARCHIVER_KEY = 'some_key'
in /etc/mailman3/settings.py and the base_url setting needs to access hyperkitty. It could be as above or it could be the URL that accesses HyperKitty externally as in
base_url: http:://example.com/archives/
Is all of that correct?
To verify base_url, you can do
curl http://127.0.0.1:8000/archives/api/
where the initial part of that is the base_url setting. That should return the html for a page of documentation.
Look at https://gitlab.com/mailman/mailman-hyperkitty/-/blob/master/mailman_hyperkit.... This is Mailman Core's interface to the archiver.
If any of the methods there fail to connect to HyperKitty or get an appropriate response, they all log errors.
In particular, the archive_message() method at line 171 is saving the message in the spool queue. Immediately before that at lines 164 and 167 it is writing log messages. You should be seeing them.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Mon, 30 Jan 2023 14:43:54 -0800 Mark Sapiro <mark@msapiro.net> wrote:
On 1/30/23 13:17, Onyeibo wrote:
The mails don't have that header. I suspect I may have to investigate SELinux.
I think it's unlikely a SELinux issue unless you mean it's an issue writing the log, but if there are any entries at all in mailman.log, that should be OK.
YES. There were entries in the log. They are good entries. There were no alarming entries.
I was right. Selinux was preventing Python {name connect} to a mailman path. After resolving that, all Archives built/updated. Now I see entries in the log about receiving mails and archiving them. I also see the archived messages via Hyperkitty web interface. Super!
However, I no longer receive my own message to the list. That was working before. The post arrives at the List and gets archived but I don't see it via my mail client -- looks like Mailman is now recieving but not posting back to the subscriber. Strange
On 1/30/23 20:38, Onyeibo wrote:
However, I no longer receive my own message to the list. That was working before. The post arrives at the List and gets archived but I don't see it via my mail client -- looks like Mailman is now recieving but not posting back to the subscriber. Strange
Fixing archiving shouldn't affect that.
There is a list member setting to receive your own posts. Is that possibly set to No as a list based, address based or global preference.
Are you posting from a gmail/googlemail address. Probably not if you were receiving your posts before, but if so, see <https://wiki.list.org/x/4030680>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hi Mark S.
having similar issue. Tried to command "mailman conf -s archiver.hyperkitty"
received below result. ]$ mailman conf -s archiver.hyperkitty Usage: mailman conf [OPTIONS] Try 'mailman conf -h' for help.
Error: No such section: archiver.hyperkitty
Can you advise what need to be changed.
On Wed, Sep 20, 2023 at 11:46 AM Mark Labeste <marqueejen13@gmail.com> wrote:
Hi Mark S.
having similar issue. Tried to command "mailman conf -s archiver.hyperkitty"
received below result. ]$ mailman conf -s archiver.hyperkitty Usage: mailman conf [OPTIONS] Try 'mailman conf -h' for help.
Error: No such section: archiver.hyperkitty
This can only mean that mailman core cannot find your mailman configuration file - aptly named mailman.cfg. A plain 'mailman conf' (without specifying the section) should give you so much output, but does it?
Can you advise what need to be changed.
mailman info should tell you the location of your mailman.cfg. Does it
point to where you expect it to be?
-- 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]
Thanks for your reply. I was abled point to the mailman.cfg path appeared in mailman info. Below is the result of mailman conf. But archive is still now showing on web browser.
[archiver.hyperkitty] class: mailman_hyperkitty.Archiver [archiver.hyperkitty] clobber_date: maybe [archiver.hyperkitty] clobber_skew: 1d [archiver.hyperkitty] configuration: /etc/mailman3/mailman-hyperkitty.cfg [archiver.hyperkitty] enable: yes [archiver.mail_archive] class: mailman.archiving.mailarchive.MailArchive [archiver.mail_archive] clobber_date: maybe [archiver.mail_archive] clobber_skew: 1d [archiver.mail_archive] configuration: python:mailman.config.mail_archive [archiver.mail_archive] enable: no [archiver.mhonarc] class: mailman.archiving.mhonarc.MHonArc [archiver.mhonarc] clobber_date: maybe [archiver.mhonarc] clobber_skew: 1d [archiver.mhonarc] configuration: python:mailman.config.mhonarc [archiver.mhonarc] enable: no [archiver.prototype] class: mailman.archiving.prototype.Prototype [archiver.prototype] clobber_date: maybe [archiver.prototype] clobber_skew: 1d [archiver.prototype] configuration: changeme [archiver.prototype] enable: no
also from comment above my /opt/mailman/var/archives/hyperkitty/spool/ contains *.pck files.
Mark Labeste writes:
Thanks for your reply. I was abled point to the mailman.cfg path appeared in mailman info. Below is the result of mailman conf. But archive is still now showing on web browser.
Sorry, can't help you without more information. Is your archive visible from the Internet?
What do you mean by "archive is not showing"? Do you get an error indication (like HTTP 404 error "no such page")? Do you get the archive page but you expect to see email there and there isn't any? If something else, what?
I assume you installed Mailman from a distribution. Which one?
What does "mailman info" report? If that doesn't work, you'll have to find the installed Mailman hierarchy, probably /var/lib/mailman3 or /usr/lib/mailman3, and run "bin/mailman info" from there.
What are the contents of these files: mailman.cfg (probably in /etc/mailman3/mailman.cfg) settings.py (there are a lot of these with different purposes, with luck you'll find the right one in /etc/mailman3/settings.py or possibly in var/etc/settings.py under the Mailman hierarchy) urls.py (may be in /etc/mailman3/urls.py, or next to settings.py)
This list strips most attachments. However it should be possible to attach these files as long as the Content-Type is text/plain. If you're not sure what the Content-Type your email program applies, you can include them in the message body at the end.
The following version information may be useful later, but it's not urgent. What versions of the following packages are installed:
mailman3 (possibly just mailman) postorius hyperkitty gunicorn mailman-web mailmanclient django_mailman (possibly django-mailman) django (or Django) (all of the above may be prefixed with something that indicates that they are Python programs) apache (possibly apache2 or apache24) or possibly nginx uwsgi (may not be in use)
Steve
On 9/20/23 19:24, Mark Labeste wrote:
also from comment above my /opt/mailman/var/archives/hyperkitty/spool/ contains *.pck files.
These are messages that couldn't be archived because of some error. There should be error messages with tracebacks in Mailman's mailman.log to diagnose these. Once the issue is resolved, those messages will bve archived.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark Labeste writes:
]$ mailman conf -s archiver.hyperkitty Usage: mailman conf [OPTIONS] Try 'mailman conf -h' for help.
Error: No such section: archiver.hyperkitty
mailman conf reads the configuration. There is no configuration for
HyperKitty in the default configuration (mailman/config/schema.cfg and
the active mailman.cfg).
You need to have an [archiver.hyperkitty] section in the active mailman.cfg. If you never added one, check the documentation for what needs to go in there and add one.
If you already have a HyperKitty section, run mailman info, which
will tell you what mailman.cfg is being used. If it gives an
unexpected answer, you're probably just running mailman in a "wrong"
place (wrong only because the search algorithm finds the unexpected
configuration file). Try running mailman from a different current
working directory.
There is one tricky point. For reasons I don't understand, mailman
will often create var/etc/mailman.cfg, and it will be empty
except for comments. I've found it very easy to trip over that file,
so I usually do ln -s /etc/mailman3/mailman.cfg var/etc/mailman.cfg
to placate the evil spirits.
participants (7)
-
Mark Labeste -
Mark Sapiro -
Massimiliano Paragnani -
Odhiambo Washington -
Onyeibo -
Onyeibo Oku
-
Stephen J. Turnbull