Hi Abhilash,

I'm trying to use Mailman 3 on my centos 7 virtual machine.

Those steps I wrote are from websites, the last console instructions are mine.

I don't use ubuntu, I use centos 7.

When I run the start command I get this: (venv3) [root@localhost mailman]# mailman start

Starting Mailman's master runner /root/dev/mailman/venv3/bin/python: can't open file '/sbin/master': [Errno 2] No such file or directory

What can I do?

Thank you

El mar., 11 jul. 2017 a las 12:31, Abhilash Raj (raj.abhilash1@gmail.com) escribió:

Hi Rafael,

On Tue, Jul 11, 2017, at 07:32 AM, Rafael Mora wrote:

...

Hello,

I want to install mailman 3 in a centos 7 virtual machine. I'm following these steps and I cannot make it work:

I am wondering if you are interested to setup a development environment or use Mailman 3? These instructions below are for working on Mailman, if you just need to deploy, instructions here1 would be the best.

...

1. cd ~
2. git clone https://gitlab.com/mailman/mailman.git

https://gitlab.com/mailman/mailman.git

...

3. cd mailman
4. virtualenv -p python3 venv
5. source venv/bin/activate
6. python setup.py develop
7. I am pretty sure this setup command will place a configuration file

into ~/mailman/var/etc/mailman.cfg. Edit this file.

https://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html

...

8. mailman info can confirm which configuration file is in use
9. mailman start will start up Mailman 3 Core. This is what the parent

background process command looks like in ps -ef: /home/ubuntu/mailman/venv/bin/python /home/ubuntu/mailman/venv/bin/master -C /home/ubuntu/mailman/var/etc/mailman.cfg

Looks like you are working as the ubuntu user here and the the virtualenv that you created exists at /home/ubuntu/mailman/venv.

...

I also tried the steps on the website https://wiki.list.org/DEV/SetupDevEnvironment but it doesn't work either

What do you suggest?

This is what I get from console:

[root@localhost ~]# cd dev/

[root@localhost dev]# cd mailman/

[root@localhost mailman]# source venv3/bin/activate

Why do you try to user a different venv as a root user here? If you'd just try:

$ source /home/ubuntu/mailman/venv/bin/activate

and then try

$ mailman start

things would work!

However, this would be a different instance of mailman and would create the new configuration (and the entire var directory) at the directory you run this command from. If you want to inhibit this, you can either use the -C flag, or set MAILMAN_CONFIG_FILE environment variable to point to your one single configuration file.

...

(venv3) [root@localhost mailman]# cd mailman/

(venv3) [root@localhost mailman]# ls conf.py COPYING data README.rst src unittest.cfg contrib coverage.ini MANIFEST.in setup.cfg template.py copybump.py cron port_me setup.py tox.ini

(venv3) [root@localhost mailman]# cd ..

(venv3) [root@localhost mailman]# mailman start Starting Mailman's master runner /root/dev/mailman/venv3/bin/python: can't open file '/sbin/master': [Errno 2] No such file or directory

(venv3) [root@localhost mailman]#

Thank you

Hope that helps!

-- thanks, Abhilash Raj _______________________________________________ Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

Below is how I would recommend to run Mailman for production using a virtualenv

# useradd -r -m -d /var/lib/mailman mailman

# su - mailman

$ python3 -m venv env $ source env/bin/activate $ pip install mailman $ mailman info

Now you should have a working configuration in /var/lib/mailman/var/

to run mailman you don't need to activate the virtualenv, just use the executable /var/lib/mailman/env/bin/mailman

cheers, Simon

Looks like you are using the fhs (filesystem hierarchy standard) layout; is that what you intend? I would suggest changing the layout to "dev" for testing purposes. This will use your mailman.cfg/../.. as the var directory.

Is it possible you also have mailman v2 installed via rpms?

-Kyle

On Tue, Jul 11, 2017 at 3:41 PM, Rafael Mora rafael.mora.guti@gmail.com wrote:

Hello,

Here it's mailman info: [root@localhost bin]# ./mailman info GNU Mailman 3.2.0a1 (La Villa Strangiato) Python 3.6.0 (default, Jul 7 2017, 11:59:56) [GCC 4.8.5 20150623 (Red Hat 4.8.5-11)] config file: /etc/mailman.cfg db url: sqlite:////var/lib/mailman/data/mailman.db devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:restpass

Here it's mailman conf: [root@localhost bin]# ./mailman conf [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.master] class: [archiver.master] clobber_date: maybe [archiver.master] clobber_skew: 1d [archiver.master] configuration: changeme [archiver.master] 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.sqlite.SQLiteDatabase [database] debug: no [database] url: sqlite:///$DATA_DIR/mailman.db [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: iso-8859-1 [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.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: fhs [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: changeme@example.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 # IP where Mailman should listen for emails from MTA [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: 127.0.0.1 # IP Where MTA is listening for emails [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 [shell] banner: Welcome to the GNU Mailman shell [shell] history_file: [shell] prompt: >>> [shell] use_ipython: no [styles] default: legacy-default [styles] paths: mailman.styles [webservice] admin_pass: restpass [webservice] admin_user: restadmin [webservice] api_version: 3.1 [webservice] hostname: localhost [webservice] port: 8001 [webservice] show_tracebacks: yes [webservice] use_https: no

What do you suggest? Thank you

El mar., 11 jul. 2017 a las 14:31, Simon Hanna (<simon.hanna@serve-me.info

...

)

escribió:

...

Below is how I would recommend to run Mailman for production using a virtualenv

# useradd -r -m -d /var/lib/mailman mailman

# su - mailman

$ python3 -m venv env $ source env/bin/activate $ pip install mailman $ mailman info

Now you should have a working configuration in /var/lib/mailman/var/

to run mailman you don't need to activate the virtualenv, just use the executable /var/lib/mailman/env/bin/mailman

cheers, Simon _______________________________________________ Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

--

Atentamente / Best Regards

Ing. Rafael Mora _______________________________________________ Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

Hello Kyle,

What steps do you suggest in order to install mailman v2 via rpm's??

Thank you.

El mar., 11 jul. 2017 a las 15:13, Kyle Richardson (< kylerichardson2@gmail.com>) escribió:

Looks like you are using the fhs (filesystem hierarchy standard) layout; is that what you intend? I would suggest changing the layout to "dev" for testing purposes. This will use your mailman.cfg/../.. as the var directory.

Is it possible you also have mailman v2 installed via rpms?

-Kyle

On Tue, Jul 11, 2017 at 3:41 PM, Rafael Mora rafael.mora.guti@gmail.com wrote:

...

Hello,

Here it's mailman info: [root@localhost bin]# ./mailman info GNU Mailman 3.2.0a1 (La Villa Strangiato) Python 3.6.0 (default, Jul 7 2017, 11:59:56) [GCC 4.8.5 20150623 (Red Hat 4.8.5-11)] config file: /etc/mailman.cfg db url: sqlite:////var/lib/mailman/data/mailman.db devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:restpass

Here it's mailman conf: [root@localhost bin]# ./mailman conf [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.master] class: [archiver.master] clobber_date: maybe [archiver.master] clobber_skew: 1d [archiver.master] configuration: changeme [archiver.master] 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.sqlite.SQLiteDatabase [database] debug: no [database] url: sqlite:///$DATA_DIR/mailman.db [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: iso-8859-1 [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.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: fhs [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: changeme@example.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 # IP where Mailman should listen for emails from MTA [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: 127.0.0.1 # IP Where MTA is listening for emails [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 [shell] banner: Welcome to the GNU Mailman shell [shell] history_file: [shell] prompt: >>> [shell] use_ipython: no [styles] default: legacy-default [styles] paths: mailman.styles [webservice] admin_pass: restpass [webservice] admin_user: restadmin [webservice] api_version: 3.1 [webservice] hostname: localhost [webservice] port: 8001 [webservice] show_tracebacks: yes [webservice] use_https: no

What do you suggest? Thank you

El mar., 11 jul. 2017 a las 14:31, Simon Hanna (< simon.hanna@serve-me.info>) escribió:

...

Below is how I would recommend to run Mailman for production using a virtualenv

# useradd -r -m -d /var/lib/mailman mailman

# su - mailman

$ python3 -m venv env $ source env/bin/activate $ pip install mailman $ mailman info

Now you should have a working configuration in /var/lib/mailman/var/

to run mailman you don't need to activate the virtualenv, just use the executable /var/lib/mailman/env/bin/mailman

cheers, Simon _______________________________________________ Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

--

Atentamente / Best Regards

Ing. Rafael Mora _______________________________________________ Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

--

Atentamente / Best Regards

Ing. Rafael Mora

Dear Kyle,

I did what you suggested and this is what I got: [root@localhost ~]# rpm -qa | grep -i mailman [root@localhost ~]# rm -rf /var/lib/mailman [root@localhost ~]# find / -name mailman /run/lock/mailman /etc/selinux/targeted/active/modules/100/mailman /etc/selinux/targeted/tmp/modules/100/mailman /root/mailman /root/mailman/src/mailman /root/mailman/venv/bin/mailman /root/dev/mailman /root/dev/mailman/venv3/bin/mailman /root/dev/mailman/mailman /root/dev/mailman/mailman/src/mailman /var/log/mailman /var/spool/mailman /usr/local/lib/python3.6/site-packages/mailman-3.2.0a1-py3.6.egg/mailman /mailman /mailman/mailman /mailman/mailman/src/mailman /mailman/mailman/build/lib/mailman

How do I wipe all other mailman directories? using rm -rf???

I don't think I can start with a brand new centos 7 for the moment.

Thank you

El jue., 13 jul. 2017 a las 10:13, Kyle Richardson (< kylerichardson2@gmail.com>) escribió:

Rafael,

Apologies for the delay. I would certainly encourage you to stick with mailman3 :-). Thanks for providing all of the details of your current environment. Let me try and answer each of your questions as best I can.

You can check if mailman2 is already installed via rpms with the following command:

# rpm -qa | grep -i mailman

Based on your find results, it looks as though you have multiple locations where you have cloned or copied mailman3. At this point, it might be easiest to start fresh. You mentioned you're using a CentOS 7 VM. Is it possible to start from a clean build or snapshot?

Once you have a clean build, you should be able to follow Simon's instructions to get a working mailman3 instance (steps reproduced below for clarity).

# useradd -r -m -d /var/lib/mailman mailman # su - mailman $ python3 -m venv env $ source env/bin/activate $ pip install mailman $ mailman info

From there you can adjust the layout in your mailman.cfg file at /var/lib/mailman/var/etc/ (snippet below).

[mailman] layout: dev

If you can't start from a clean CentOS 7 VM, then you should be able to just wipe out your existing /var/lib/mailman directory and still use Simon's instructions.

# rm -rf /var/lib/mailman

Hopefully this will help you get up and going.

-Kyle

On Thu, Jul 13, 2017 at 10:16 AM, Rafael Mora rafael.mora.guti@gmail.com wrote:

...

Hello Kyle,

What steps do you suggest in order to install mailman v2 via rpm's??

Thank you.

El mar., 11 jul. 2017 a las 15:13, Kyle Richardson (< kylerichardson2@gmail.com>) escribió:

...

Looks like you are using the fhs (filesystem hierarchy standard) layout; is that what you intend? I would suggest changing the layout to "dev" for testing purposes. This will use your mailman.cfg/../.. as the var directory.

Is it possible you also have mailman v2 installed via rpms?

-Kyle

On Tue, Jul 11, 2017 at 3:41 PM, Rafael Mora <rafael.mora.guti@gmail.com

...

wrote:

...

Hello,

Here it's mailman info: [root@localhost bin]# ./mailman info GNU Mailman 3.2.0a1 (La Villa Strangiato) Python 3.6.0 (default, Jul 7 2017, 11:59:56) [GCC 4.8.5 20150623 (Red Hat 4.8.5-11)] config file: /etc/mailman.cfg db url: sqlite:////var/lib/mailman/data/mailman.db devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:restpass

Here it's mailman conf: [root@localhost bin]# ./mailman conf [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.master] class: [archiver.master] clobber_date: maybe [archiver.master] clobber_skew: 1d [archiver.master] configuration: changeme [archiver.master] 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.sqlite.SQLiteDatabase [database] debug: no [database] url: sqlite:///$DATA_DIR/mailman.db [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: iso-8859-1 [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.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: fhs [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: changeme@example.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 # IP where Mailman should listen for emails from MTA [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: 127.0.0.1 # IP Where MTA is listening for emails [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 [shell] banner: Welcome to the GNU Mailman shell [shell] history_file: [shell] prompt: >>> [shell] use_ipython: no [styles] default: legacy-default [styles] paths: mailman.styles [webservice] admin_pass: restpass [webservice] admin_user: restadmin [webservice] api_version: 3.1 [webservice] hostname: localhost [webservice] port: 8001 [webservice] show_tracebacks: yes [webservice] use_https: no

What do you suggest? Thank you

El mar., 11 jul. 2017 a las 14:31, Simon Hanna (< simon.hanna@serve-me.info>) escribió:

...

Below is how I would recommend to run Mailman for production using a virtualenv

# useradd -r -m -d /var/lib/mailman mailman

# su - mailman

$ python3 -m venv env $ source env/bin/activate $ pip install mailman $ mailman info

Now you should have a working configuration in /var/lib/mailman/var/

to run mailman you don't need to activate the virtualenv, just use the executable /var/lib/mailman/env/bin/mailman

cheers, Simon _______________________________________________ Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

--

Atentamente / Best Regards

Ing. Rafael Mora _______________________________________________ Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

--

Atentamente / Best Regards

Ing. Rafael Mora

--

Atentamente / Best Regards

Ing. Rafael Mora

I'm getting this: [root@localhost ~]# ps -elf | grep -i mailman 0 R root 6830 5998 0 80 0 - 28161 - 13:43 pts/0 00:00:00 grep --color=auto -i mailman

What is the pid??

Thank you

[excessive, redundant quoting removed by moderator]

Ok, I'm going to proceed with Simon's steps and will let you know.

Thank you Kyle

El jue., 13 jul. 2017 a las 12:51, Kyle Richardson (< kylerichardson2@gmail.com>) escribió:

Ok, that's normal. You don't have any mailman instances running. You should be able to proceed with Simon's steps.

-Kyle

[excessive quoting removed]

Dear Kyle, sorry ...

El jue., 13 jul. 2017 a las 12:58, Rafael Mora (rafael.mora.guti@gmail.com) escribió:

Dear Simon,

I did Simon's steps and got this: [root@localhost ~]# useradd -r -m -d /var/lib/mailman mailman useradd: user 'mailman' already exists [root@localhost ~]# su - mailman Last login: Wed Jul 12 15:19:42 EDT 2017 on pts/0 su: warning: cannot change directory to /var/lib/mailman: No such file or directory

What should I do?

[excessive quoting removed]

Dear Kyle,

I got this: [root@localhost ~]# userdel -r mailman userdel: mailman mail spool (/var/spool/mail/mailman) not found userdel: mailman home directory (/var/lib/mailman) not found

El jue., 13 jul. 2017 a las 13:25, Kyle Richardson (< kylerichardson2@gmail.com>) escribió:

Try this...

# userdel -r mailman # useradd -r -m -d /var/lib/mailman # su - mailman

Then continue on with the steps outlined.

-Kyle

[excessive quoting removed]

Sorry, you're correct. I mistyped the useradd command.

# useradd -r -m -d /var/lib/mailman mailman

-Kyle

I included the corrected command in my previous message.

For clarity, it is:

# useradd -r -m -d /var/lib/mailman mailman

-Kyle

On Thu, Jul 13, 2017 at 4:56 PM Rafael Mora rafael.mora.guti@gmail.com wrote:

What would be the correct command???

Thank you

El jue., 13 jul. 2017 a las 15:55, Kyle Richardson (< kylerichardson2@gmail.com>) escribió:

...

Sorry, you're correct. I mistyped the useradd command.

# useradd -r -m -d /var/lib/mailman mailman

-Kyle

--

Atentamente / Best Regards

Ing. Rafael Mora

Dear Kyle,

Look at this: (env) [mailman@localhost ~]$ ls -l /var/lock lrwxrwxrwx. 1 root root 11 Jun 23 17:01 /var/lock -> ../run/lock (env) [mailman@localhost ~]$ ls -l /var/lock/mailman ls: cannot access /var/lock/mailman: No such file or directory

El jue., 13 jul. 2017 a las 16:15, Kyle Richardson (< kylerichardson2@gmail.com>) escribió:

I included the corrected command in my previous message.

For clarity, it is:

# useradd -r -m -d /var/lib/mailman mailman

-Kyle

On Thu, Jul 13, 2017 at 4:56 PM Rafael Mora rafael.mora.guti@gmail.com wrote:

...

What would be the correct command???

Thank you

El jue., 13 jul. 2017 a las 15:55, Kyle Richardson (< kylerichardson2@gmail.com>) escribió:

...

Sorry, you're correct. I mistyped the useradd command.

# useradd -r -m -d /var/lib/mailman mailman

-Kyle

--

Atentamente / Best Regards

Ing. Rafael Mora

--

Atentamente / Best Regards

Ing. Rafael Mora

Dear Kyle,

I did what you suggest but there's no cfg file nor /var directory, look: (env) [mailman@localhost ~]$ pwd /var/lib/mailman (env) [mailman@localhost ~]$ ls archives cache data env lists messages templates

El jue., 13 jul. 2017 a las 17:29, Kyle Richardson (< kylerichardson2@gmail.com>) escribió:

The only reason it would try to use that lock file is if you are still trying to use the fhs layout. Edit your mailman.cfg file to use the dev layout. Location of your mailman.cfg should be under /var/lib/mailman/var/etc/.

You should probably also try to specify the full path to your config file with the -C option.

# su - mailman $ cd /var/lib/mailman $ source env/bin/activate (env) $ mailman info -C /var/lib/mailman/var/etc/mailman.cfg

-Kyle

Rafael,

I have validated that these steps [1] work on a clean CentOS 7 x64 build.

[1] https://gist.github.com/kylerichardson/9dcf72082feccf77a7bee4be5c390400

-Kyle

Kyle,

After doing the steps and running mailman info I got:

Permission denied: '/var/lock/mailman'

El sáb., 15 jul. 2017 a las 13:53, Kyle Richardson (< kylerichardson2@gmail.com>) escribió:

Rafael,

I have validated that these steps [1] work on a clean CentOS 7 x64 build.

[1] https://gist.github.com/kylerichardson/9dcf72082feccf77a7bee4be5c390400

-Kyle

--

Atentamente / Best Regards

Ing. Rafael Mora

Look:

[root@localhost mailman]# find / -name mailman.cfg /etc/mailman.cfg /root/var/etc/mailman.cfg /root/mailman/src/mailman/config/mailman.cfg /root/dev/mailman/mailman/src/mailman/config/mailman.cfg /var/lib/mailman/env/lib/python3.6/site-packages/mailman/config/mailman.cfg /usr/local/lib/python3.6/site-packages/mailman-3.2.0a1-py3.6.egg/mailman/config/mailman.cfg /usr/local/lib/python3.6/site-packages/postorius/var/etc/mailman.cfg /mailman/mailman/src/mailman/config/mailman.cfg /mailman/mailman/build/lib/mailman/config/mailman.cfg /mailman/mailman/var/etc/mailman.cfg

El sáb., 15 jul. 2017 a las 19:28, Kyle Richardson (< kylerichardson2@gmail.com>) escribió:

There must be another config file being picked up. Have a look at the mailman.cfg search order explained here [1].

My guess is that /etc/mailman.cfg exists. Do a 'find / -name mailman.cfg' to be sure. You'll want to delete any in the search path and then rerun 'mailman info'.

[1] http://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html

-Kyle

--

Atentamente / Best Regards

Ing. Rafael Mora

Hi Rafael,

On Wed, Jul 19, 2017, at 01:49 PM, Rafael Mora wrote:

Hello,

What are the suggested steps in order to install the web UI ??

I haven't read through this entire thread but I understand that you are having problems with multiple configuration files for Core and setting up the Web UI.

The installation guide at docs.mailman3.org should now have a "Pre-Installation Guide" and another new section called "Configuring Mailman 3". Please make sure than you read both of them along with the "Installation Guide" They have more information about how to setup Mailman 3 after you have installed them so that it becomes function.

Also, your original question's answer can be found there. It has instructions about how to setup your Django project, which is the what the Web frontend for Mailman 3 is based on.

Thanks

El sáb., 15 jul. 2017 a las 19:28, Kyle Richardson (< kylerichardson2@gmail.com>) escribió:

...

There must be another config file being picked up. Have a look at the mailman.cfg search order explained here [1].

My guess is that /etc/mailman.cfg exists. Do a 'find / -name mailman.cfg' to be sure. You'll want to delete any in the search path and then rerun 'mailman info'.

[1] http://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html

-Kyle

--

Atentamente / Best Regards

Ing. Rafael Mora _______________________________________________ Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

Hi Abhilash,

I started to setup Postfix (I don't know if that is the suggested and easy to use mail server) doing the steps on the website http://docs.mailman3.org/en/latest/config-core.html which tells:

Postfix http://www.postfix.org/: To setup Postfix, add the following configuration to master.cf:

# Support the default VERP delimiter.recipient_delimiter = +unknown_local_recipient_reject_code = 550owner_request_special = notransport_maps = hash:/path-to-mailman/var/data/postfix_lmtplocal_recipient_maps = hash:/path-to-mailman/var/data/postfix_lmtprelay_domains = hash:/path-to-mailman/var/data/postfix_domains

I added that config at the bottom of the master.cf file and did a 'postfix reload' and I got this error message:

[root@localhost ~]# postfix reload /usr/sbin/postconf: fatal: file /etc/postfix/master.cf: line 129: bad field count postfix/postfix-script: fatal: cannot execute /usr/sbin/postconf!

What do you suggest???

Thank you

El jue., 20 jul. 2017 a las 14:09, Abhilash Raj (raj.abhilash1@gmail.com) escribió:

Hi Rafael,

On Wed, Jul 19, 2017, at 01:49 PM, Rafael Mora wrote:

...

Hello,

What are the suggested steps in order to install the web UI ??

I haven't read through this entire thread but I understand that you are having problems with multiple configuration files for Core and setting up the Web UI.

The installation guide at docs.mailman3.org should now have a "Pre-Installation Guide" and another new section called "Configuring Mailman 3". Please make sure than you read both of them along with the "Installation Guide" They have more information about how to setup Mailman 3 after you have installed them so that it becomes function.

Also, your original question's answer can be found there. It has instructions about how to setup your Django project, which is the what the Web frontend for Mailman 3 is based on.

...

Thanks

El sáb., 15 jul. 2017 a las 19:28, Kyle Richardson (< kylerichardson2@gmail.com>) escribió:

...

There must be another config file being picked up. Have a look at the mailman.cfg search order explained here [1].

My guess is that /etc/mailman.cfg exists. Do a 'find / -name

mailman.cfg'

...

...

to be sure. You'll want to delete any in the search path and then rerun 'mailman info'.

[1]

http://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html

...

...

-Kyle

--

Atentamente / Best Regards

Ing. Rafael Mora _______________________________________________ Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

-- thanks, Abhilash Raj

Can we modify the docs?

Ok, I'm going to add that config to main.cf and test

Thank you

El vie., 21 jul. 2017 a las 12:25, Mark Sapiro (mark@msapiro.net) escribió:

On 07/21/2017 09:36 AM, Rafael Mora wrote:

...

Postfix http://www.postfix.org/: To setup Postfix, add the following configuration to master.cf:

# Support the default VERP delimiter.recipient_delimiter = +unknown_local_recipient_reject_code = 550owner_request_special = notransport_maps = hash:/path-to-mailman/var/data/postfix_lmtplocal_recipient_maps = hash:/path-to-mailman/var/data/postfix_lmtprelay_domains = hash:/path-to-mailman/var/data/postfix_domains

I added that config at the bottom of the master.cf file and did a

'postfix

...

reload' and I got this error message:

[root@localhost ~]# postfix reload /usr/sbin/postconf: fatal: file /etc/postfix/master.cf: line 129: bad

field

...

count postfix/postfix-script: fatal: cannot execute /usr/sbin/postconf!

First of all, in a report such as this, it would really help if you reported what is actually in master.cf in the vicinity of line 129.

However, that said, the doc is wrong. The lines should be added to main.cf, not master.cf. See https://gitlab.com/mailman/mailman-suite-doc/issues/14.

Also, what you post above is quite garbled. It is not clear what you meant, but the lines to add should be

# Support the default VERP delimiter. recipient_delimiter = + unknown_local_recipient_reject_code = 550 owner_request_special = no transport_maps = hash:/path-to-mailman/var/data/postfix_lmtp local_recipient_maps = hash:/path-to-mailman/var/data/postfix_lmtp relay_domains = hash:/path-to-mailman/var/data/postfix_domains

and should not be wrapped as in your post.

-- Mark Sapiro 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

Nice you opened a new issue, ok then...

About this:

Ideally, you want to use paths.fhs which is based on Filesystem Hierarchy Standard . To use this add the following to your configuration:

[mailman] layout: fhs

Should I do it???? is that for production??

Sometimes I wish the install process was easier, sorry for disturbing you guys but believe me I've been more than 2 weeks trying and it's been difficult

El vie., 21 jul. 2017 a las 13:02, Mark Sapiro (mark@msapiro.net) escribió:

On 07/21/2017 10:29 AM, Rafael Mora wrote:

...

Can we modify the docs?

El vie., 21 jul. 2017 a las 12:25, Mark Sapiro (mark@msapiro.net) escribió:

...

However, that said, the doc is wrong. The lines should be added to main.cf, not master.cf. See https://gitlab.com/mailman/mailman-suite-doc/issues/14.

That's what the above issue and associated MR are for.

-- Mark Sapiro 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

I think you have to open a new issue to modify the website for the mailman-suite git clone, it should be: git clone https://gitlab.com/mailman/mailman-suite.git

El vie., 21 jul. 2017 a las 14:07, Rafael Mora (rafael.mora.guti@gmail.com) escribió:

Installing mailman-suite for web ui. I did this:

(env) [mailman@localhost ~]$ git clone https://gitlab.com/mailman/mailman-suite/ Cloning into 'mailman-suite'... error: RPC failed; result=22, HTTP code = 404 fatal: The remote end hung up unexpectedly

but it returned an error, what should I do??

Thanks

El vie., 21 jul. 2017 a las 13:02, Mark Sapiro (mark@msapiro.net) escribió:

...

On 07/21/2017 10:29 AM, Rafael Mora wrote:

...

Can we modify the docs?

El vie., 21 jul. 2017 a las 12:25, Mark Sapiro (mark@msapiro.net) escribió:

...

However, that said, the doc is wrong. The lines should be added to main.cf, not master.cf. See https://gitlab.com/mailman/mailman-suite-doc/issues/14.

That's what the above issue and associated MR are for.

-- Mark Sapiro 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

--

Atentamente / Best Regards

Ing. Rafael Mora

ok, thanks Mark,

I'm getting an error doing:

(env) [mailman@localhost mailman-suite_project]$ python2 manage.py migrate Traceback (most recent call last): File "manage.py", line 8, in <module> from django.core.management import execute_from_command_line ImportError: No module named django.core.management

What do you suggest??

El vie., 21 jul. 2017 a las 14:31, Mark Sapiro (mark@msapiro.net) escribió:

On 07/21/2017 12:07 PM, Rafael Mora wrote:

...

Installing mailman-suite for web ui. I did this:

(env) [mailman@localhost ~]$ git clone https://gitlab.com/mailman/mailman-suite/ Cloning into 'mailman-suite'... error: RPC failed; result=22, HTTP code = 404 fatal: The remote end hung up unexpectedly

but it returned an error, what should I do??

It's another case of incorrect docs. It should be

git clone https://gitlab.com/mailman/mailman-suite.git

See https://gitlab.com/mailman/mailman-suite-doc/issues/15.

-- Mark Sapiro 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

I thought the mailman-suite would do it for me...

it says: If you have absolutely no idea about Django, just clone/download this mailman-suite repo

How do I install Django? in my 'env' virtualenv ???

Thanks Mark

El vie., 21 jul. 2017 a las 14:37, Mark Sapiro (mark@msapiro.net) escribió:

On 07/21/2017 12:33 PM, Rafael Mora wrote:

...

I'm getting an error doing:

(env) [mailman@localhost mailman-suite_project]$ python2 manage.py

migrate

...

Traceback (most recent call last): File "manage.py", line 8, in <module> from django.core.management import execute_from_command_line ImportError: No module named django.core.management

Have you installed Django in your 'env' virtualenv?

-- Mark Sapiro 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

On 07/21/2017 12:44 PM, Rafael Mora wrote:

I did this:

(env) [mailman@localhost mailman-suite_project]$ pip install Django Requirement already satisfied: Django in /var/lib/mailman/env/lib/python3.6/site-packages Requirement already satisfied: pytz in /var/lib/mailman/env/lib/python3.6/site-packages (from Django)

Does Django is already installed?? with python3.6 ???

Your 'env' vitrualenv is a Python 3 virtualenv. You need this for Mailman core, but Django and mailman-suite are Python 2. They need to be installed and run in a Python 2 virtualenv.

Ok,

I could setup env with python3 and env2 with python 2.7

I visited http://192.168.1.42:8000 in my browser and I could not see the web UI.

Should I install WSGI server?? doing: pip3 install uwsgi ???

Thanks

El vie., 21 jul. 2017 a las 15:03, Mark Sapiro (mark@msapiro.net) escribió:

On 07/21/2017 12:44 PM, Rafael Mora wrote:

...

I did this:

(env) [mailman@localhost mailman-suite_project]$ pip install Django Requirement already satisfied: Django in /var/lib/mailman/env/lib/python3.6/site-packages Requirement already satisfied: pytz in /var/lib/mailman/env/lib/python3.6/site-packages (from Django)

Does Django is already installed?? with python3.6 ???

Your 'env' vitrualenv is a Python 3 virtualenv. You need this for Mailman core, but Django and mailman-suite are Python 2. They need to be installed and run in a Python 2 virtualenv.

-- Mark Sapiro 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

Yes I did ran it in the env2 python2 virtualenv, it says: ERR_CONNECTION_REFUSED I stopped the firewalld service and it's still refused

I installed uwsgi, should I put the config inside mailman.cfg??

El vie., 21 jul. 2017 a las 15:53, Mark Sapiro (mark@msapiro.net) escribió:

On 07/21/2017 01:36 PM, Rafael Mora wrote:

...

I visited http://192.168.1.42:8000 in my browser and I could not see the web UI.

What did you see?

Did you run the Django web server? In your Python 2 virtualenv?

python manage.py runserver

-- Mark Sapiro 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

I did not interrupt the running process...

It's running, but I cannot see anything

El vie., 21 jul. 2017 a las 16:08, Mark Sapiro (mark@msapiro.net) escribió:

On 07/21/2017 02:00 PM, Rafael Mora wrote:

...

Yes I did ran it in the env2 python2 virtualenv, it says: ERR_CONNECTION_REFUSED I stopped the firewalld service and it's still refused

After you ran 'manage.py runserver' did you leave that terminal window open with that process running? If you control-C or interrupt it in any way, it stops listening.

...

I installed uwsgi, should I put the config inside mailman.cfg??

Not yet. That's for production. I don't think you're there yet.

-- Mark Sapiro 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

Good, it answered my call but now I get this:

raise MissingDependency("The 'whoosh' backend requires the installation of 'Whoosh'. Please refer to the documentation.") MissingDependency: The 'whoosh' backend requires the installation of 'Whoosh'. Please refer to the documentation. [21/Jul/2017 21:25:23] "GET /favicon.ico HTTP/1.1" 500 59

it says it needs whoosh

How do I install that? on env2 with python2 or env with python3 ???

El vie., 21 jul. 2017 a las 16:23, Kyle Richardson (< kylerichardson2@gmail.com>) escribió:

If your browser is on a remote system, you'll want to run the command:

'python2 manage.py runserver 0.0.0.0:8000'

-Kyle

Ok, I'll install whoosh on env2

Thanks

El vie., 21 jul. 2017 a las 16:32, Mark Sapiro (mark@msapiro.net) escribió:

On 07/21/2017 02:27 PM, Rafael Mora wrote:

...

it says it needs whoosh

How do I install that? on env2 with python2 or env with python3 ???

In env2 do 'pip install whoosh'

-- Mark Sapiro 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

YEEEES! At last!!! I can see the web UI.

Now I´m getting this message in the web UI:

Something went wrong Mailman REST API not available. Please start Mailman core.

Where do I configure the REST API ?????

Thank you

El vie., 21 jul. 2017 a las 16:32, Mark Sapiro (mark@msapiro.net) escribió:

On 07/21/2017 02:27 PM, Rafael Mora wrote:

...

it says it needs whoosh

How do I install that? on env2 with python2 or env with python3 ???

In env2 do 'pip install whoosh'

-- Mark Sapiro 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

Nice! Up and running!

How do I start using mailman? what are the steps??

REALLY thank you all for your patience and help! Really appreciated !

El vie., 21 jul. 2017 a las 18:48, Mark Sapiro (mark@msapiro.net) escribió:

On 07/21/2017 04:43 PM, Rafael Mora wrote:

...

YEEEES! At last!!! I can see the web UI.

Now I´m getting this message in the web UI:

Something went wrong Mailman REST API not available. Please start Mailman core.

Where do I configure the REST API ?????

So I guess you figured out that ALLOWED_HOSTS is a Django setting in settings.py or wherever your Django settings are.

Now you have to start Mailman Core. In your Python 3 'env' where you installed Mailman Core, run 'bin/mailman start'.

-- Mark Sapiro 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

On 07/21/2017 04:57 PM, Rafael Mora wrote:

Should Sign Up ?? Log In??

Yes.

El vie., 21 jul. 2017 a las 18:56, Rafael Mora (rafael.mora.guti@gmail.com) escribió:

...

Nice! Up and running!

How do I start using mailman? what are the steps??

What do you want to do with Mailman? This is the key question.

There is some list subscriber documentation at http://docs.list.org/en/latest/userguide.html.

You can create domains and lists via Postorius or via the core's bin/mailman commands ('bin/mailman --help' for a list).

On 07/21/2017 06:07 PM, Rafael Mora wrote:

I want to use Mailman to send emails to our customers.

So you need to create a list and add your customers as members.

Please note that Mailman is not a substitute for a customer relations management system. It can be used in that way, but a true CRM system has advantages ove Mailman. Mailman is primarily designed to support discussion lists such as this one.

I´m getting this error when I click on sign up and log in:

FilterError at /accounts/login/ /bin/sh: sassc: command not found

See the third bullet under http://docs.list.org/en/latest/prodsetup.html#dependencies.

On 07/21/2017 06:46 PM, Rafael Mora wrote:

Can I use it for mailing lists? like MailChimp?

Yes, if all you want is a simple one way announcement type list, Mailman can do that quite well, with appropriate list configuration[1], but as I tried to say, MailChimp has many more features that are oriented towards that kind of mailing.

[1]There are many horror stories of people setting up a mailing list and subscribing a bunch of people to it without ensuring that members can't post back to the list.

Then with the first post, people start posting back to be removed and then others reply that they didn't send that mail and it snowballs and within an hower, the poor list server is so backlogged that the clueful replies take hours to be delivered. I personally have been added to more that one list to which this happened.

On 22-Jul-17 09:30, Rafael Mora wrote:

What would be the config for a simple one way announcement type list ????

Here is a possible list configuration (this doesn't go in any particular file; it's a dump from the REST API, but you should be able to find the corresponding settings in the GUI): | ||# Phantom list 41|| ||# ---------------|| ||acceptable_aliases = []|| ||admin_immed_notify = true|| ||admin_notify_mchanges = true|| ||administrivia = true|| ||advertised = true|| ||allow_list_posts = false|| ||anonymous_list = false|| ||archive_policy = "public"|| ||autorespond_owner = "none"|| ||autorespond_postings = "respond_and_discard"|| ||autorespond_requests = "none"|| ||autoresponse_grace_period = "45d"|| ||autoresponse_owner_text = ""|| ||autoresponse_postings_text = "This is an announce-only list"|| ||autoresponse_request_text = ""|| ||bounces_address = "phantomtbonesq-list-bounces@example.net"|| ||collapse_alternatives = false|| ||convert_html_to_plaintext = false|| ||created_at = "2017-06-28T00:33:14.031754"|| ||default_member_action = "discard"|| ||default_nonmember_action = "discard"|| ||description = "well, you see it's like this"|| ||digest_last_sent_at = null|| ||digest_send_periodic = true|| ||digest_size_threshold = 5000|| ||digest_volume_frequency = "weekly"|| ||digests_enabled = true|| ||display_name = "Phantom list 41"|| ||dmarc_mitigate_action = "no_mitigation"|| ||dmarc_mitigate_unconditionally = false|| ||dmarc_moderation_notice = ""|| ||dmarc_wrapped_message_text = ""|| ||filter_content = false|| ||first_strip_reply_to = false|| ||fqdn_listname = "phantomtbonesq-list@example.net"|| ||http_etag = '"ad12b8647391aa81563c67a164c57156e10efca0"'|| ||include_rfc2369_headers = true|| ||info = " The wind in the willows|| ||talked in the pillows||||" ||join_address = "phantomtbonesq-list-join@example.net"|| ||last_post_at = null|| ||leave_address = "phantomtbonesq-list-leave@example.net"|| ||list_name = "phantomtbonesq-list"|| ||mail_host = "example.net"|| ||moderator_password = null|| ||next_digest_number = 1|| ||no_reply_address = "noreply@example.net"|| ||owner_address = "phantomtbonesq-list-owner@example.net"|| ||post_id = 1|| ||posting_address = "phantomtbonesq-list@example.net"|| ||posting_pipeline = "default-posting-pipeline"|| ||reply_goes_to_list = "no_munging"|| ||reply_to_address = ""|| ||request_address = "phantomtbonesq-list-request@example.net"|| ||send_welcome_message = false|| ||subject_prefix = ""|| ||subscription_policy = "confirm"|| ||volume = 1|

The key items are:

allow_list_posts = false autorespond_postings = "respond_and_discard" autorespond_requests = "none" autoresponse_postings_text = "This is an announce-only list" default_member_action = "discard" default_nonmember_action = "discard"

You don't need to worry about DMARC, since you're the only poster.

Deciding about VERP (bounce verification) will require some thought - it's a tradeoff of cost vs. accuracy. It's discussed in the documentation.

In addition, you need to define a subscriber with "moderation_action = accept", from which you post to the list.

This is from a Mailman 3 application that's still being developed, so it may not be fully debugged.

FWIW, your difficulties getting MM3 working are not unique. I have had similar problems - and I'm not done yet. I've run Mailman 2.1 lists for many years, but 3.1 is a lot more complex to set up. In fact, pretty much everyone who has tried to use MM3 has had similar problems.

MM3 is in early stages of adoption & development. You should expect the challenges of any early adopter of complex software. There will undoubtedly be bugs - some serious, some not so. But if you continue to provide feedback, there's hope that the developers will improve it.

On the other hand, if you want a more stable platform and are willing to settle for fewer features, you might consider using MM2.1. It's widely deployed and quite stable. Your distribution will have it packaged & easy to set up. You can always migrate when 3.1 is more mature.

Finally, as others have noted, Mailman is fine for distributing moderate volumes of e-mail. For high volume, you need to tune your mailserver and platform - this may not be cost effective in terms of your time and investment in bandwidth and hardware. Also, Mailman doesn't provide the "services" that many people expect from mass mailing services such as MailChimp - e.g. beacons indicating how many people open your mail, correlation with purchases, tests to see how it fares with spam filters, compatibility tests with common e-mail clients, and so on.

If an open loop system meets your needs, Mailman can work well. If you need feedback, it may not meet your needs.

I logged in with the superuser. It said that it sent a confirmation email which I haven't received yet because I guess I have to configure the mail server right?

What do you suggest??

El sáb., 22 jul. 2017 a las 10:23, Rafael Mora (rafael.mora.guti@gmail.com) escribió:

Thanks for the settings and suggestions. I want just to try it, if it doesn't work out I will move to mailchimp.

I really appreciate your willingness to help me.

Do you know another program for mailing mailchimp/mailman like?

Thanks

El sáb., 22 jul. 2017 a las 10:00, tlhackque via Mailman-users (< mailman-users@mailman3.org>) escribió:

...

On 22-Jul-17 09:30, Rafael Mora wrote:

...

What would be the config for a simple one way announcement type list

????

...

Here is a possible list configuration (this doesn't go in any particular file; it's a dump from the REST API, but you should be able to find the corresponding settings in the GUI): | ||# Phantom list 41|| ||# ---------------|| ||acceptable_aliases = []|| ||admin_immed_notify = true|| ||admin_notify_mchanges = true|| ||administrivia = true|| ||advertised = true|| ||allow_list_posts = false|| ||anonymous_list = false|| ||archive_policy = "public"|| ||autorespond_owner = "none"|| ||autorespond_postings = "respond_and_discard"|| ||autorespond_requests = "none"|| ||autoresponse_grace_period = "45d"|| ||autoresponse_owner_text = ""|| ||autoresponse_postings_text = "This is an announce-only list"|| ||autoresponse_request_text = ""|| ||bounces_address = "phantomtbonesq-list-bounces@example.net"|| ||collapse_alternatives = false|| ||convert_html_to_plaintext = false|| ||created_at = "2017-06-28T00:33:14.031754"|| ||default_member_action = "discard"|| ||default_nonmember_action = "discard"|| ||description = "well, you see it's like this"|| ||digest_last_sent_at = null|| ||digest_send_periodic = true|| ||digest_size_threshold = 5000|| ||digest_volume_frequency = "weekly"|| ||digests_enabled = true|| ||display_name = "Phantom list 41"|| ||dmarc_mitigate_action = "no_mitigation"|| ||dmarc_mitigate_unconditionally = false|| ||dmarc_moderation_notice = ""|| ||dmarc_wrapped_message_text = ""|| ||filter_content = false|| ||first_strip_reply_to = false|| ||fqdn_listname = "phantomtbonesq-list@example.net"|| ||http_etag = '"ad12b8647391aa81563c67a164c57156e10efca0"'|| ||include_rfc2369_headers = true|| ||info = " The wind in the willows|| ||talked in the pillows||||" ||join_address = "phantomtbonesq-list-join@example.net"|| ||last_post_at = null|| ||leave_address = "phantomtbonesq-list-leave@example.net"|| ||list_name = "phantomtbonesq-list"|| ||mail_host = "example.net"|| ||moderator_password = null|| ||next_digest_number = 1|| ||no_reply_address = "noreply@example.net"|| ||owner_address = "phantomtbonesq-list-owner@example.net"|| ||post_id = 1|| ||posting_address = "phantomtbonesq-list@example.net"|| ||posting_pipeline = "default-posting-pipeline"|| ||reply_goes_to_list = "no_munging"|| ||reply_to_address = ""|| ||request_address = "phantomtbonesq-list-request@example.net"|| ||send_welcome_message = false|| ||subject_prefix = ""|| ||subscription_policy = "confirm"|| ||volume = 1|

The key items are:

allow_list_posts = false autorespond_postings = "respond_and_discard" autorespond_requests = "none" autoresponse_postings_text = "This is an announce-only list" default_member_action = "discard" default_nonmember_action = "discard"

You don't need to worry about DMARC, since you're the only poster.

Deciding about VERP (bounce verification) will require some thought - it's a tradeoff of cost vs. accuracy. It's discussed in the documentation.

In addition, you need to define a subscriber with "moderation_action = accept", from which you post to the list.

This is from a Mailman 3 application that's still being developed, so it may not be fully debugged.

FWIW, your difficulties getting MM3 working are not unique. I have had similar problems - and I'm not done yet. I've run Mailman 2.1 lists for many years, but 3.1 is a lot more complex to set up. In fact, pretty much everyone who has tried to use MM3 has had similar problems.

MM3 is in early stages of adoption & development. You should expect the challenges of any early adopter of complex software. There will undoubtedly be bugs - some serious, some not so. But if you continue to provide feedback, there's hope that the developers will improve it.

On the other hand, if you want a more stable platform and are willing to settle for fewer features, you might consider using MM2.1. It's widely deployed and quite stable. Your distribution will have it packaged & easy to set up. You can always migrate when 3.1 is more mature.

Finally, as others have noted, Mailman is fine for distributing moderate volumes of e-mail. For high volume, you need to tune your mailserver and platform - this may not be cost effective in terms of your time and investment in bandwidth and hardware. Also, Mailman doesn't provide the "services" that many people expect from mass mailing services such as MailChimp - e.g. beacons indicating how many people open your mail, correlation with purchases, tests to see how it fares with spam filters, compatibility tests with common e-mail clients, and so on.

If an open loop system meets your needs, Mailman can work well. If you need feedback, it may not meet your needs.

---

Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

--

Atentamente / Best Regards

Ing. Rafael Mora

Dear Barry,

I understand your point. I just want to test as we can use mailman just for basic mailing.

If in the future I see that mailman doesn't fullfill our requirements I'll switch to another tool.

How can I config Mailman/Postfix to send the confirmation email for the superuser I created this morning???

Thank you.

El sáb., 22 jul. 2017 a las 10:46, Barry Warsaw (barry@list.org) escribió:

Mailman does not intend to compete with services like Mailchimp. FWIW, my tai chi teacher uses Mailchimp (I’ve helped him with it) and it’s a great service. But Mailman is *software* primarily, not a service, and one primarily geared toward open discussions and collaborations. It provides good one-way (i.e. announce) type lists, but it’s not designed for tracking response rates on high volume commercial-like emails, and has no composition or marketing tools built in.

As a software library and system, it *could* provide a good framework for building such a thing, although I suspect there’s a lot of work that would need to be done. Mailman 3 would provide a much better basis for that work than Mailman 2 due to its modularity. But that was never Mailman’s main purpose in life. It was born of connecting a (now famous) band to its fans, and quickly reached maturity as an open discussion forum, and that I believe is where it’s main strength lies. To the extent that other use cases make Mailman a better platform, we’re certainly open to ideas and suggestions. E.g. improving the pluggability is a major goal (of mine) for the GSoC encryption project, even if encrypted mailing lists don’t become an official feature. I’d love to have a robust add-ons ecosystem where such things can be supported by community members.

Cheers, -Barry

---

Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

content of the file maillog-20170723 (I didn't find mail.log in /var/log):

[root@localhost log]# cat maillog-20170723 Jul 17 10:29:19 localhost postfix/postfix-script[1702]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postqueue Jul 17 10:29:19 localhost postfix/postfix-script[1760]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postdrop Jul 17 10:29:19 localhost postfix/postfix-script[1781]: starting the Postfix mail system Jul 17 10:29:20 localhost postfix/master[1791]: daemon started -- version 2.10.1, configuration /etc/postfix Jul 21 15:19:31 localhost postfix/postfix-script[9273]: refreshing the Postfix mail system Jul 21 15:19:31 localhost postfix/master[1791]: reload -- version 2.10.1, configuration /etc/postfix Jul 21 15:34:54 localhost postfix/postfix-script[9327]: fatal: cannot execute /usr/sbin/postconf! Jul 21 16:30:03 localhost postfix/postfix-script[9471]: refreshing the Postfix mail system Jul 21 16:30:03 localhost postfix/master[1791]: reload -- version 2.10.1, configuration /etc/postfix Jul 21 16:52:46 localhost postfix/postfix-script[9528]: refreshing the Postfix mail system Jul 21 16:52:46 localhost postfix/master[1791]: reload -- version 2.10.1, configuration /etc/postfix Jul 21 16:52:46 localhost postfix/qmgr[9532]: error: open database /var/lib/mailman/var/data/postfix_domains.db: No such file or directory Jul 21 16:10:47 localhost postfix/postfix-script[2099]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postqueue Jul 21 16:10:47 localhost postfix/postfix-script[2105]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postdrop Jul 21 16:10:47 localhost postfix/postfix-script[2112]: starting the Postfix mail system Jul 21 16:10:47 localhost postfix/master[2114]: daemon started -- version 2.10.1, configuration /etc/postfix 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

output command 'postconf -n':

[root@localhost log]# 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/libmailman/var/data/postfix_lmtp unknown_local_recipient_reject_code = 550

What's wrong? Thanks

El sáb., 22 jul. 2017 a las 22:33, Mark Sapiro (mark@msapiro.net) escribió:

On 07/22/2017 05:29 PM, Rafael Mora wrote:

...

How can I config Mailman/Postfix to send the confirmation email for the superuser I created this morning???

What is in Postfix's logs relevant to the attempt to send the mail (probably /var/log/mail.log)?

What is the output from 'postconf -n'

-- Mark Sapiro 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

Hello Simon,

How can I check that mailman can execute postmap/postalias ??

Thanks

El dom., 23 jul. 2017 a las 11:29, Simon HANNA (simon.hanna@serve-me.info) escribió:

On July 23, 2017 5:14:37 PM GMT+02:00, Rafael Mora < rafael.mora.guti@gmail.com> wrote:

...

content of the file maillog-20170723 (I didn't find mail.log in /var/log):

[root@localhost log]# cat maillog-20170723 Jul 17 10:29:19 localhost postfix/postfix-script[1702]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postqueue Jul 17 10:29:19 localhost postfix/postfix-script[1760]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postdrop

Looks like you have some problems with permissions. They are only warnings, so it shouldn't be the cause of the problems, but you never know... ...

...

Jul 21 16:52:46 localhost postfix/master[1791]: reload -- version 2.10.1, configuration /etc/postfix Jul 21 16:52:46 localhost postfix/qmgr[9532]: error: open database /var/lib/mailman/var/data/postfix_domains.db: No such file or directory

Check if the file exists and is readable by postfix If the file is there, it should be permission errors. If it doesn't you need to check mailman's logs for error regarding their creation (can mailman execute postmap/postalias?)

cheers, Simon -- Sent from my Android device with K-9 Mail. Please excuse my brevity. _______________________________________________ Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

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

On 07/23/2017 06:00 PM, Rafael Mora wrote:

Hello guys,

This is what I've got on ../var/data:

[root@localhost data]# pwd /var/lib/mailman/var/data [root@localhost data]# ls -l total 76 -rw-rw---- 1 mailman mailman 74752 Jul 16 16:44 mailman.db

What should I do in order to let mailman install the DB files?

Run

bin/mailman aliases

On 07/24/2017 07:41 AM, Rafael Mora wrote:

Ok, I ran 'mailman aliases', what should I do now?

Assuming mail delivery is not working, look in /var/log/maillog for messages with timestamps around the time that the mail was generated. Then try to figure out what they are saying.

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.

On 07/24/2017 03:31 PM, Rafael Mora wrote:

I got this on maillog:

[root@localhost log]# cat maillog

There's nothing in that log that shows any attempts by anything to connect to Postfix. You have to look at logs from the processes you think are trying to send mail and see what they're doing.

I put this config in mailman.cfg:

To configure Core to use Postfix, add the following configuration to your mailman.cfg configuration, be sure to replace mail.example.com with your email domain:

[mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: mail.example.com lmtp_port: 8024 smtp_host: mail.example.com smtp_port: 25

is this correct??

El lun., 24 jul. 2017 a las 17:47, Mark Sapiro (mark@msapiro.net) escribió:

On 07/24/2017 03:31 PM, Rafael Mora wrote:

...

I got this on maillog:

[root@localhost log]# cat maillog

There's nothing in that log that shows any attempts by anything to connect to Postfix. You have to look at logs from the processes you think are trying to send mail and see what they're doing.

-- Mark Sapiro 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

This is from the file /var/log/maillog:

Jul 24 17:29:21 localhost postfix/postfix-script[2092]: starting the Postfix mail system Jul 24 17:29:21 localhost postfix/master[2096]: daemon started -- version 2.10.1, configuration /etc/postfix Jul 25 03:30:05 localhost postfix/pickup[2785]: 03F4160D143F: uid=0 from=<root> Jul 25 03:30:05 localhost postfix/cleanup[3191]: 03F4160D143F: message-id=20170725073005.03F4160D143F@localhost.localdomain Jul 25 03:30:05 localhost postfix/qmgr[2113]: 03F4160D143F: from=root@localhost.localdomain, size=508, nrcpt=1 (queue active) Jul 25 03:30:05 localhost postfix/local[3195]: 03F4160D143F: to=root@localhost.localdomain, orig_to=<root>, relay=local, delay=0.11, delays=0.07/0.03/0/0.01, dsn=2.0.0, status=sent (delivered to mailbox) Jul 25 03:30:05 localhost postfix/qmgr[2113]: 03F4160D143F: removed

It seems that postfix is working, isn't it?

El lun., 24 jul. 2017 a las 17:47, Mark Sapiro (mark@msapiro.net) escribió:

On 07/24/2017 03:31 PM, Rafael Mora wrote:

...

I got this on maillog:

[root@localhost log]# cat maillog

There's nothing in that log that shows any attempts by anything to connect to Postfix. You have to look at logs from the processes you think are trying to send mail and see what they're doing.

-- Mark Sapiro 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

I got this error starting mailman service:

[mailman@localhost ~]$ source env2Traceback (most recent call last): File "/usr/local/lib/python3.6/asyncio/base_events.py", line 1043, in create_server sock.bind(sa) OSError: [Errno 99] Cannot assign requested address

During handling of the above exception, another exception occurred:

Traceback (most recent call last): File "/var/lib/mailman/env/bin/runner", line 11, in <module> sys.exit(main()) File "/var/lib/mailman/env/lib/python3.6/site-packages/mailman/bin/runner.py", line 198, in main runner.run() File "/var/lib/mailman/env/lib/python3.6/site-packages/mailman/runners/lmtp.py", line 242, in run self.lmtp.start() File "/var/lib/mailman/env/lib/python3.6/site-packages/aiosmtpd/controller.py", line 55, in start raise self._thread_exception File "/var/lib/mailman/env/lib/python3.6/site-packages/aiosmtpd/controller.py", line 35, in _run ssl=self.ssl_context)) File "/usr/local/lib/python3.6/asyncio/base_events.py", line 466, in run_until_complete return future.result() File "/usr/local/lib/python3.6/asyncio/base_events.py", line 1047, in create_server % (sa, err.strerror.lower())) OSError: [Errno 99] error while attempting to bind on address ('192.185.51.89', 8024): cannot assign requested address

What do you think?

El lun., 24 jul. 2017 a las 17:47, Mark Sapiro (mark@msapiro.net) escribió:

On 07/24/2017 03:31 PM, Rafael Mora wrote:

...

I got this on maillog:

[root@localhost log]# cat maillog

There's nothing in that log that shows any attempts by anything to connect to Postfix. You have to look at logs from the processes you think are trying to send mail and see what they're doing.

-- Mark Sapiro 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

I changed them to 127.0.0.1 and localhost as you suggested

El mar., 25 jul. 2017 a las 15:10, Mark Sapiro (mark@msapiro.net) escribió:

On 07/25/2017 12:58 PM, Rafael Mora wrote:

...

I got this error starting mailman service:

[mailman@localhost ~]$ source env2Traceback (most recent call last): File "/usr/local/lib/python3.6/asyncio/base_events.py", line 1043, in create_server sock.bind(sa) OSError: [Errno 99] Cannot assign requested address

...

...

What do you think?

I think you have configured

lmtp_host: mail.example.com

which is wrong.

-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

On 07/25/2017 01:19 PM, Rafael Mora wrote:

What should I do to tell Postfix to use my domain?? for example send emails using the email account mailing@labbrands.com

If what you're asking is how to configure Postfix to relay all outbound mail via some other email server, that is a Postfix configuration question.

If I thought I could give you a simple answer and that would be the end of it, I'd try, but in your case every answer leads to another question, so I suggest you start here to learn about configuring Postfix http://www.postfix.org/documentation.html.

On 07/25/2017 01:43 PM, Rafael Mora wrote:

Ok, should I install the SASL authentication daemon saslauthd and start it?

Probably not.

If you are trying to configure Postfix to send via a remote server, see http://www.postfix.org/SOHO_README.html#client_sasl_enable.

Hello,

I got postfix installed and I can use the command mail to send emails. The thing is that mailman can't send the confimation mail yet, where should I look for the error??

Thanks

El mar., 25 jul. 2017 a las 16:14, Mark Sapiro (mark@msapiro.net) escribió:

On 07/25/2017 01:43 PM, Rafael Mora wrote:

...

Ok, should I install the SASL authentication daemon saslauthd and start

it?

Probably not.

If you are trying to configure Postfix to send via a remote server, see http://www.postfix.org/SOHO_README.html#client_sasl_enable.

-- Mark Sapiro 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

I'm looking in /var/etc/mailman.log but nothing occurs and in the postfix maillog nothing occurs as well

Is it possible to look into another config or log file?

Thanks

El mar., 1 ago. 2017 a las 13:02, Mark Sapiro (mark@msapiro.net) escribió:

On 8/1/17 10:15 AM, Rafael Mora wrote:

...

Hello,

I got postfix installed and I can use the command mail to send emails.

The

...

thing is that mailman can't send the confimation mail yet, where should I look for the error??

Look in Mailman's logs and Postfix's 'maillog'.

-- Mark Sapiro 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

I made a change for test purpose on the mailman.cfg file and I got this:

(env) [mailman@localhost etc]$ mailman restart Restarting the Mailman runners PID unreadable in: /var/lib/mailman/var/etc/var/master.pid [Errno 2] No such file or directory: '/var/lib/mailman/var/etc/var/master.pid' Is the master even running?

How do I solve this?

El mar., 1 ago. 2017 a las 13:02, Mark Sapiro (mark@msapiro.net) escribió:

On 8/1/17 10:15 AM, Rafael Mora wrote:

...

Hello,

I got postfix installed and I can use the command mail to send emails.

The

...

thing is that mailman can't send the confimation mail yet, where should I look for the error??

Look in Mailman's logs and Postfix's 'maillog'.

-- Mark Sapiro 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

I´m getting this:

(env) [mailman@localhost etc]$ mailman stop Shutting down Mailman's master runner (env) [mailman@localhost etc]$ mailman start Starting Mailman's master runner (env) [mailman@localhost etc]$ Traceback (most recent call last): File "/usr/local/lib/python3.6/asyncio/base_events.py", line 1043, in create_s erver sock.bind(sa) OSError: [Errno 98] Address already in use

During handling of the above exception, another exception occurred:

Traceback (most recent call last): File "/var/lib/mailman/env/bin/runner", line 11, in <module> sys.exit(main()) File "/var/lib/mailman/env/lib/python3.6/site-packages/mailman/bin/runner.py",

      line 198, in main
runner.run()

File "/var/lib/mailman/env/lib/python3.6/site-packages/mailman/runners/lmtp.py

     ", line 242, in run
self.lmtp.start()

File "/var/lib/mailman/env/lib/python3.6/site-packages/aiosmtpd/controller.py"

     , line 55, in start
raise self._thread_exception

File "/var/lib/mailman/env/lib/python3.6/site-packages/aiosmtpd/controller.py"

     , line 35, in _run
ssl=self.ssl_context))

File "/usr/local/lib/python3.6/asyncio/base_events.py", line 466, in run_until _complete return future.result() File "/usr/local/lib/python3.6/asyncio/base_events.py", line 1047, in create_s erver % (sa, err.strerror.lower())) OSError: [Errno 98] error while attempting to bind on address ('127.0.0.1', 8024 ): address already in use Traceback (most recent call last): File "/var/lib/mailman/env/bin/runner", line 11, in <module> sys.exit(main()) File "/var/lib/mailman/env/lib/python3.6/site-packages/mailman/bin/runner.py",

      line 194, in main
runner = make_runner(*args.runner, once=args.once)

File "/var/lib/mailman/env/lib/python3.6/site-packages/mailman/bin/runner.py",

      line 94, in make_runner
return runner_class(name, slice)

File "/var/lib/mailman/env/lib/python3.6/site-packages/mailman/runners/rest.py

     ", line 53, in __init__
self._server = make_server()

File "/var/lib/mailman/env/lib/python3.6/site-packages/mailman/rest/wsgiapp.py

     ", line 234, in make_server
handler_class=AdminWebServiceWSGIRequestHandler)

File "/usr/local/lib/python3.6/wsgiref/simple_server.py", line 153, in make_se rver server = server_class((host, port), handler_class) File "/usr/local/lib/python3.6/socketserver.py", line 453, in __init__ self.server_bind() File "/usr/local/lib/python3.6/wsgiref/simple_server.py", line 50, in server_b ind HTTPServer.server_bind(self) File "/usr/local/lib/python3.6/http/server.py", line 136, in server_bind socketserver.TCPServer.server_bind(self) File "/usr/local/lib/python3.6/socketserver.py", line 467, in server_bind self.socket.bind(self.server_address) OSError: [Errno 98] Address already in use

Why does it say Address already in use?

El mar., 1 ago. 2017 a las 15:10, Mark Sapiro (mark@msapiro.net) escribió:

On 8/1/17 12:52 PM, Rafael Mora wrote:

...

I made a change for test purpose on the mailman.cfg file and I got this:

(env) [mailman@localhost etc]$ mailman restart Restarting the Mailman runners PID unreadable in: /var/lib/mailman/var/etc/var/master.pid [Errno 2] No such file or directory: '/var/lib/mailman/var/etc/var/master.pid' Is the master even running?

How do I solve this?

Try

mailman stop mailman start

-- Mark Sapiro 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

It's ok now, but still I can't make it send the confirmation email

This is from mailman.log:

[mailman@localhost logs]$ tail -f mailman.log Aug 01 15:59:18 2017 (2327) lmtp runner started. Aug 01 15:59:18 2017 (2333) virgin runner started. Aug 01 15:59:18 2017 (2332) retry runner started. Aug 01 15:59:18 2017 (2330) pipeline runner started. Aug 01 15:59:18 2017 (2325) command runner started. Aug 01 15:59:19 2017 (2328) nntp runner started. Aug 01 15:59:19 2017 (2326) in runner started. Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET /3.0/lists?count=0&page=1&advertised=true HTTP/1.1" 200 90 Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET /3.0/lists?count=10&page=1&advertised=true HTTP/1.1" 200 90 Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET /3.0/domains HTTP/1.1" 200 90

What should I do?

El mar., 1 ago. 2017 a las 15:36, Mark Sapiro (mark@msapiro.net) escribió:

On 8/1/17 1:14 PM, Rafael Mora wrote:

...

Why does it say Address already in use?

Because you are starting lm tp runner and it's already running.

Do 'mailman stop'. Then ensure no Mailman processes are running. kill any if necessary. Then do 'mailman start'.

-- Mark Sapiro 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

Hello Abhilash,

I have this in my settings.py file:

EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_PORT = 25 #EMAIL_HOST_USER = 'mailing@labbrands.com' #EMAIL_HOST_PASSWORD = '******'

What should I use in user and password?? Does Django use postfix to send the email???

Thanks

El mar., 1 ago. 2017 a las 16:20, Abhilash Raj (raj.abhilash1@gmail.com) escribió:

Hi,

On Tue, Aug 1, 2017, at 02:11 PM, Rafael Mora wrote:

...

It's ok now, but still I can't make it send the confirmation email

This is from mailman.log:

[mailman@localhost logs]$ tail -f mailman.log Aug 01 15:59:18 2017 (2327) lmtp runner started. Aug 01 15:59:18 2017 (2333) virgin runner started. Aug 01 15:59:18 2017 (2332) retry runner started. Aug 01 15:59:18 2017 (2330) pipeline runner started. Aug 01 15:59:18 2017 (2325) command runner started. Aug 01 15:59:19 2017 (2328) nntp runner started. Aug 01 15:59:19 2017 (2326) in runner started. Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET /3.0/lists?count=0&page=1&advertised=true HTTP/1.1" 200 90 Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET /3.0/lists?count=10&page=1&advertised=true HTTP/1.1" 200 90 Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET /3.0/domains HTTP/1.1" 200 90

What should I do?

If you are talking about Account confirmation emails, they usually are sent out from Django and not Mailman Core itself.

To configure Django you need to edit the settings.py file, wherever that is one your installation. If you are following the guide mentioned at http://docs.mailman3.org/en/latest/prodsetup.html, it should be at mailman-suite/mailman-suite_project/settings.py.

To configure your Django to send emails, have a look at

http://docs.mailman3.org/en/latest/config-web.html#setting-up-email-required .

That documentation page has pretty much everything you need in order to have a running Web Frontend, please go through it and make sure you have everything configured.

Finally, the actual emails from Mailing lists are supposed to be handled by Core. You need to configure Postorius & Mailman both to communicate. The settings are mentioned http://docs.mailman3.org/en/latest/config-core.html#configuring-mta here.

Hope that helps!

...

El mar., 1 ago. 2017 a las 15:36, Mark Sapiro (mark@msapiro.net) escribió:

...

On 8/1/17 1:14 PM, Rafael Mora wrote:

...

Why does it say Address already in use?

Because you are starting lm tp runner and it's already running.

Do 'mailman stop'. Then ensure no Mailman processes are running. kill any if necessary. Then do 'mailman start'.

-- Mark Sapiro 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

--

Atentamente / Best Regards

Ing. Rafael Mora _______________________________________________ Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

-- thanks, Abhilash Raj _______________________________________________ Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

Why isn't it sending emails?

What do you think?

El mar., 1 ago. 2017 a las 16:34, Abhilash Raj (raj.abhilash1@gmail.com) escribió:

On Tue, Aug 1, 2017, at 02:29 PM, Rafael Mora wrote:

Hello Abhilash,

I have this in my settings.py file:

EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_PORT = 25 #EMAIL_HOST_USER = 'mailing@labbrands.com' #EMAIL_HOST_PASSWORD = '******'

This looks good to me.

What should I use in user and password?? Does Django use postfix to send the email???

I think you don't need a password and username as long as your postfix is configured to relay local emails without authentication (which it is by default if you installed from distro packages and if you haven't changed the settings).

Thanks

El mar., 1 ago. 2017 a las 16:20, Abhilash Raj (raj.abhilash1@gmail.com) escribió:

Hi,

On Tue, Aug 1, 2017, at 02:11 PM, Rafael Mora wrote:

...

It's ok now, but still I can't make it send the confirmation email

This is from mailman.log:

[mailman@localhost logs]$ tail -f mailman.log Aug 01 15:59:18 2017 (2327) lmtp runner started. Aug 01 15:59:18 2017 (2333) virgin runner started. Aug 01 15:59:18 2017 (2332) retry runner started. Aug 01 15:59:18 2017 (2330) pipeline runner started. Aug 01 15:59:18 2017 (2325) command runner started. Aug 01 15:59:19 2017 (2328) nntp runner started. Aug 01 15:59:19 2017 (2326) in runner started. Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET /3.0/lists?count=0&page=1&advertised=true HTTP/1.1" 200 90 Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET /3.0/lists?count=10&page=1&advertised=true HTTP/1.1" 200 90 Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET /3.0/domains HTTP/1.1" 200 90

What should I do?

If you are talking about Account confirmation emails, they usually are sent out from Django and not Mailman Core itself.

To configure Django you need to edit the settings.py file, wherever that is one your installation. If you are following the guide mentioned at http://docs.mailman3.org/en/latest/prodsetup.html, it should be at mailman-suite/mailman-suite_project/settings.py.

To configure your Django to send emails, have a look at

http://docs.mailman3.org/en/latest/config-web.html#setting-up-email-required .

That documentation page has pretty much everything you need in order to have a running Web Frontend, please go through it and make sure you have everything configured.

Finally, the actual emails from Mailing lists are supposed to be handled by Core. You need to configure Postorius & Mailman both to communicate. The settings are mentioned http://docs.mailman3.org/en/latest/config-core.html#configuring-mta here.

Hope that helps!

...

El mar., 1 ago. 2017 a las 15:36, Mark Sapiro (mark@msapiro.net) escribió:

...

On 8/1/17 1:14 PM, Rafael Mora wrote:

...

Why does it say Address already in use?

Because you are starting lm tp runner and it's already running.

Do 'mailman stop'. Then ensure no Mailman processes are running. kill any if necessary. Then do 'mailman start'.

-- Mark Sapiro 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

--

Atentamente / Best Regards

Ing. Rafael Mora _______________________________________________ Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

-- thanks, Abhilash Raj _______________________________________________ Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

--

Atentamente / Best Regards

Ing. Rafael Mora

-- thanks, Abhilash Raj

--

Atentamente / Best Regards

Ing. Rafael Mora

As Abhilash said I checked the django configuration for email but nothing happens when the program sends the confirmation email.

Is there any other configuration file for django emails?

On Tue, Aug 1, 2017, 23:18 Mark Sapiro mark@msapiro.net wrote:

On 08/01/2017 02:40 PM, Rafael Mora wrote:

...

Why isn't it sending emails?

What do you think?

What exactly are you doing that you think should result in sent mail?

-- Mark Sapiro 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

Does this have anything to do with the problem?:

(env) [mailman@localhost logs]$ pwd /var/lib/mailman/mailman-suite/mailman-suite_project/logs (env) [mailman@localhost logs]$ tail -f mailmansuite.log File "/var/lib/mailman/env2/lib/python2.7/site-packages/compressor/base.py", line 204, in hunks precompiled, value = self.precompile(value, **options) File "/var/lib/mailman/env2/lib/python2.7/site-packages/compressor/base.py", line 265, in precompile return True, filter.input(**kwargs) File "/var/lib/mailman/env2/lib/python2.7/site-packages/compressor/filters/base.py", line 229, in input return super(CachedCompilerFilter, self).input(**kwargs) File "/var/lib/mailman/env2/lib/python2.7/site-packages/compressor/filters/base.py", line 196, in input raise FilterError(err) FilterError: /bin/sh: sassc: command not found

Thanks

El mar., 1 ago. 2017 a las 23:18, Mark Sapiro (mark@msapiro.net) escribió:

On 08/01/2017 02:40 PM, Rafael Mora wrote:

...

Why isn't it sending emails?

What do you think?

What exactly are you doing that you think should result in sent mail?

-- Mark Sapiro 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

Is this the problem?????:

# When DEBUG is True, don't actually send emails to the SMTP server, just store # them in a directory. This way you won't accidentally spam your mailing-lists # while you're fiddling with the code. if DEBUG == True: EMAIL_BACKEND = 'django.core.mail.backends.filebased.EmailBackend' EMAIL_FILE_PATH = os.path.join(BASE_DIR, 'emails')

Shouldn't DEBUG be FALSE??

El mar., 1 ago. 2017 a las 23:18, Mark Sapiro (mark@msapiro.net) escribió:

On 08/01/2017 02:40 PM, Rafael Mora wrote:

...

Why isn't it sending emails?

What do you think?

What exactly are you doing that you think should result in sent mail?

-- Mark Sapiro 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

HyperKitty is looking for some files in /static/CACHE/... but it doesn't find them:

[02/Aug/2017 14:53:38] "GET /static/CACHE/css/b3547a2ab51b.css HTTP/1.1" 404 107 [02/Aug/2017 14:53:38] "GET /static/CACHE/css/4c17bb8058aa.css HTTP/1.1" 404 107 [02/Aug/2017 14:53:38] "GET /static/CACHE/css/2fa1cba00450.css HTTP/1.1" 404 107 [02/Aug/2017 14:53:38] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" 404 105 [02/Aug/2017 14:53:39] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" 404 105

Should I run any command to activate the CACHE dir?

El mar., 1 ago. 2017 a las 23:18, Mark Sapiro (mark@msapiro.net) escribió:

On 08/01/2017 02:40 PM, Rafael Mora wrote:

...

Why isn't it sending emails?

What do you think?

What exactly are you doing that you think should result in sent mail?

-- Mark Sapiro 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

I have installed rubygem-sass and added the config to settings.py previously and even executed this command:

# Copy all the static files to one single location. $ python2 manage.py collectstatic

I tested the commands you suggested and this is what I got:

(env2) [mailman@localhost mailman-suite_project]$ pwd /var/lib/mailman/mailman-suite/mailman-suite_project (env2) [mailman@localhost mailman-suite_project]$ django-admin collectstatic --clear No Django settings specified. Unknown command: 'collectstatic' Type 'django-admin help' for usage.

El mié., 2 ago. 2017 a las 10:56, Mark Sapiro (mark@msapiro.net) escribió:

On 08/02/2017 07:55 AM, Rafael Mora wrote:

...

HyperKitty is looking for some files in /static/CACHE/... but it doesn't find them:

[02/Aug/2017 14:53:38] "GET /static/CACHE/css/b3547a2ab51b.css HTTP/1.1" 404 107 [02/Aug/2017 14:53:38] "GET /static/CACHE/css/4c17bb8058aa.css HTTP/1.1" 404 107 [02/Aug/2017 14:53:38] "GET /static/CACHE/css/2fa1cba00450.css HTTP/1.1" 404 107 [02/Aug/2017 14:53:38] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1"

404

...

105 [02/Aug/2017 14:53:39] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1"

404

...

105

Should I run any command to activate the CACHE dir?

You need to ensure you have a working sass compiler. As I said at < https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...

...

,

See the third bullet under http://docs.list.org/en/latest/prodsetup.html#dependencies.

Then you need to run commands like

django-admin collectstatic --clear django-admin compress

-- Mark Sapiro 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

For testing purpose I turned back to false the DEBUG var and everything started working fine with HyperKitty

I don't understand... this is the trace when I click Login from Postorius to HyperKitty

[02/Aug/2017 16:43:42] "GET /postorius/lists/ HTTP/1.1" 200 3645 [02/Aug/2017 16:43:48] "GET /accounts/login/?next=/postorius/lists/ HTTP/1.1" 200 10950 [02/Aug/2017 16:43:49] "GET /static/CACHE/css/hyperkitty.2f591b4e31fe.css HTTP/1.1" 200 156657

What should I check?

El mié., 2 ago. 2017 a las 10:56, Mark Sapiro (mark@msapiro.net) escribió:

On 08/02/2017 07:55 AM, Rafael Mora wrote:

...

HyperKitty is looking for some files in /static/CACHE/... but it doesn't find them:

[02/Aug/2017 14:53:38] "GET /static/CACHE/css/b3547a2ab51b.css HTTP/1.1" 404 107 [02/Aug/2017 14:53:38] "GET /static/CACHE/css/4c17bb8058aa.css HTTP/1.1" 404 107 [02/Aug/2017 14:53:38] "GET /static/CACHE/css/2fa1cba00450.css HTTP/1.1" 404 107 [02/Aug/2017 14:53:38] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1"

404

...

105 [02/Aug/2017 14:53:39] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1"

404

...

105

Should I run any command to activate the CACHE dir?

You need to ensure you have a working sass compiler. As I said at < https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...

...

,

See the third bullet under http://docs.list.org/en/latest/prodsetup.html#dependencies.

Then you need to run commands like

django-admin collectstatic --clear django-admin compress

-- Mark Sapiro 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

Clever idea Abhilash! Thanks

El mié., 2 ago. 2017 a las 11:50, Abhilash Raj (raj.abhilash1@gmail.com) escribió:

When you set DEBUG=False, Django doesn't serve static files because of which you see only text and no styles.

http://docs.mailman3.org/en/latest/pre-installation-guide.html#django-static...

If you do set DEBUG=False, you need to serve the static pages somehow.

Alternatively in you case, you can remove the part of the settings.py which changes the Emailbackend when DEBUG=False so that you don't have to worry about serving static files and still send out emails.

On Wed, Aug 2, 2017, at 09:46 AM, Rafael Mora wrote:

...

For testing purpose I turned back to false the DEBUG var and everything started working fine with HyperKitty

I don't understand... this is the trace when I click Login from Postorius to HyperKitty

[02/Aug/2017 16:43:42] "GET /postorius/lists/ HTTP/1.1" 200 3645 [02/Aug/2017 16:43:48] "GET /accounts/login/?next=/postorius/lists/ HTTP/1.1" 200 10950 [02/Aug/2017 16:43:49] "GET /static/CACHE/css/hyperkitty.2f591b4e31fe.css HTTP/1.1" 200 156657

What should I check?

El mié., 2 ago. 2017 a las 10:56, Mark Sapiro (mark@msapiro.net) escribió:

...

On 08/02/2017 07:55 AM, Rafael Mora wrote:

...

HyperKitty is looking for some files in /static/CACHE/... but it

doesn't

...

...

...

find them:

[02/Aug/2017 14:53:38] "GET /static/CACHE/css/b3547a2ab51b.css

HTTP/1.1"

...

...

...

404 107 [02/Aug/2017 14:53:38] "GET /static/CACHE/css/4c17bb8058aa.css

HTTP/1.1"

...

...

...

404 107 [02/Aug/2017 14:53:38] "GET /static/CACHE/css/2fa1cba00450.css

HTTP/1.1"

...

...

...

404 107 [02/Aug/2017 14:53:38] "GET /static/CACHE/js/4ce1260ef558.js

HTTP/1.1"

...

...

404

...

105 [02/Aug/2017 14:53:39] "GET /static/CACHE/js/4ce1260ef558.js

HTTP/1.1"

...

...

404

...

105

Should I run any command to activate the CACHE dir?

You need to ensure you have a working sass compiler. As I said at <

https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...

...

...

...

,

See the third bullet under http://docs.list.org/en/latest/prodsetup.html#dependencies.

Then you need to run commands like

django-admin collectstatic --clear django-admin compress

-- Mark Sapiro 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

--

Atentamente / Best Regards

Ing. Rafael Mora _______________________________________________ Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

-- thanks, Abhilash Raj _______________________________________________ Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

DEBUG var True:

[02/Aug/2017 16:43:42] "GET /postorius/lists/ HTTP/1.1" 200 3645 [02/Aug/2017 16:43:48] "GET /accounts/login/?next=/postorius/lists/ HTTP/1.1" 200 10950 [02/Aug/2017 16:43:49] "GET /static/CACHE/css/hyperkitty.2f591b4e31fe.css HTTP/1.1" 200 156657

DEBUG var False:

[02/Aug/2017 16:46:46] "GET /accounts/login/?next=/postorius/lists/ HTTP/1.1" 200 10001 [02/Aug/2017 16:46:46] "GET /static/CACHE/css/b3547a2ab51b.css HTTP/1.1" 404 107 [02/Aug/2017 16:46:46] "GET /static/CACHE/css/4c17bb8058aa.css HTTP/1.1" 404 107 [02/Aug/2017 16:46:46] "GET /static/CACHE/css/d6cbfc945441.css HTTP/1.1" 404 107 [02/Aug/2017 16:46:46] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" 404 105 [02/Aug/2017 16:46:46] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" 404 105

El mié., 2 ago. 2017 a las 10:56, Mark Sapiro (mark@msapiro.net) escribió:

On 08/02/2017 07:55 AM, Rafael Mora wrote:

...

HyperKitty is looking for some files in /static/CACHE/... but it doesn't find them:

[02/Aug/2017 14:53:38] "GET /static/CACHE/css/b3547a2ab51b.css HTTP/1.1" 404 107 [02/Aug/2017 14:53:38] "GET /static/CACHE/css/4c17bb8058aa.css HTTP/1.1" 404 107 [02/Aug/2017 14:53:38] "GET /static/CACHE/css/2fa1cba00450.css HTTP/1.1" 404 107 [02/Aug/2017 14:53:38] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1"

404

...

105 [02/Aug/2017 14:53:39] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1"

404

...

105

Should I run any command to activate the CACHE dir?

You need to ensure you have a working sass compiler. As I said at < https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...

...

,

See the third bullet under http://docs.list.org/en/latest/prodsetup.html#dependencies.

Then you need to run commands like

django-admin collectstatic --clear django-admin compress

-- Mark Sapiro 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

Postfix is listening on 127.0.0.1:25 is it ok? or should listen on 0.0.0.0:25??

El mar., 1 ago. 2017 a las 16:34, Abhilash Raj (raj.abhilash1@gmail.com) escribió:

On Tue, Aug 1, 2017, at 02:29 PM, Rafael Mora wrote:

Hello Abhilash,

I have this in my settings.py file:

EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_PORT = 25 #EMAIL_HOST_USER = 'mailing@labbrands.com' #EMAIL_HOST_PASSWORD = '******'

This looks good to me.

What should I use in user and password?? Does Django use postfix to send the email???

I think you don't need a password and username as long as your postfix is configured to relay local emails without authentication (which it is by default if you installed from distro packages and if you haven't changed the settings).

Thanks

El mar., 1 ago. 2017 a las 16:20, Abhilash Raj (raj.abhilash1@gmail.com) escribió:

Hi,

On Tue, Aug 1, 2017, at 02:11 PM, Rafael Mora wrote:

...

It's ok now, but still I can't make it send the confirmation email

This is from mailman.log:

[mailman@localhost logs]$ tail -f mailman.log Aug 01 15:59:18 2017 (2327) lmtp runner started. Aug 01 15:59:18 2017 (2333) virgin runner started. Aug 01 15:59:18 2017 (2332) retry runner started. Aug 01 15:59:18 2017 (2330) pipeline runner started. Aug 01 15:59:18 2017 (2325) command runner started. Aug 01 15:59:19 2017 (2328) nntp runner started. Aug 01 15:59:19 2017 (2326) in runner started. Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET /3.0/lists?count=0&page=1&advertised=true HTTP/1.1" 200 90 Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET /3.0/lists?count=10&page=1&advertised=true HTTP/1.1" 200 90 Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET /3.0/domains HTTP/1.1" 200 90

What should I do?

If you are talking about Account confirmation emails, they usually are sent out from Django and not Mailman Core itself.

To configure Django you need to edit the settings.py file, wherever that is one your installation. If you are following the guide mentioned at http://docs.mailman3.org/en/latest/prodsetup.html, it should be at mailman-suite/mailman-suite_project/settings.py.

To configure your Django to send emails, have a look at

http://docs.mailman3.org/en/latest/config-web.html#setting-up-email-required .

That documentation page has pretty much everything you need in order to have a running Web Frontend, please go through it and make sure you have everything configured.

Finally, the actual emails from Mailing lists are supposed to be handled by Core. You need to configure Postorius & Mailman both to communicate. The settings are mentioned http://docs.mailman3.org/en/latest/config-core.html#configuring-mta here.

Hope that helps!

...

El mar., 1 ago. 2017 a las 15:36, Mark Sapiro (mark@msapiro.net) escribió:

...

On 8/1/17 1:14 PM, Rafael Mora wrote:

...

Why does it say Address already in use?

Because you are starting lm tp runner and it's already running.

Do 'mailman stop'. Then ensure no Mailman processes are running. kill any if necessary. Then do 'mailman start'.

-- Mark Sapiro 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

--

Atentamente / Best Regards

Ing. Rafael Mora _______________________________________________ Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

-- thanks, Abhilash Raj _______________________________________________ Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

--

Atentamente / Best Regards

Ing. Rafael Mora

-- thanks, Abhilash Raj

--

Atentamente / Best Regards

Ing. Rafael Mora

my mailman.cfg file is:

# AUTOMATICALLY GENERATED BY MAILMAN ON 2017-07-16 20:44:24 UTC # # This is your GNU Mailman 3 configuration file. You can edit this file to # configure Mailman to your needs, and Mailman will never overwrite it. # Additional configuration information is available here: # # http://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html # # For example, uncomment the following lines to run Mailman in developer mode. # # [devmode] # enabled: yes # recipient: your.address@your.domain #[mailman] #layout: fhs [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 127.0.0.1 lmtp_port: 8024 smtp_host: localhost smtp_port: 25 configuration: python:mailman.config.postfix

my mailman.config.postfix file is:

[postfix] transport_file_type: regex

are they ok?

El mar., 1 ago. 2017 a las 15:10, Mark Sapiro (mark@msapiro.net) escribió:

On 8/1/17 12:52 PM, Rafael Mora wrote:

...

I made a change for test purpose on the mailman.cfg file and I got this:

(env) [mailman@localhost etc]$ mailman restart Restarting the Mailman runners PID unreadable in: /var/lib/mailman/var/etc/var/master.pid [Errno 2] No such file or directory: '/var/lib/mailman/var/etc/var/master.pid' Is the master even running?

How do I solve this?

Try

mailman stop mailman start

-- Mark Sapiro 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

On 07/25/2017 01:21 PM, Rafael Mora wrote:

Regarding this:

# To be added to Django's settings.py

EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_PORT = 25 EMAIL_HOST_USER = <username> EMAIL_HOST_PASSWORD = <password>

What should I use for username and password? Should I keep the localhost on the host param?

If you want Django (i.e. Postorius, Hyperkitty and Django admin/auth/etc.) to deliver via localhost, you don't need EMAIL_HOST_USER and EMAIL_HOST_PASSWORD. Those are only for authentication to some other host.

Hello,

This is what I've got in /var/lib/mailman/var/data:

[root@localhost data]# pwd /var/lib/mailman/var/data [root@localhost data]# ls -l total 100 -rw-rw---- 1 mailman mailman 74752 Jul 16 16:44 mailman.db -rw-rw---- 1 mailman mailman 315 Jul 24 10:41 postfix_domains -rw-r----- 1 mailman mailman 12288 Jul 24 10:41 postfix_domains.db -rw-rw---- 1 mailman mailman 318 Jul 24 10:41 postfix_lmtp -rw-r----- 1 mailman mailman 12288 Jul 24 10:41 postfix_lmtp.db

What should be the next step?

El dom., 23 jul. 2017 a las 20:22, Mark Sapiro (mark@msapiro.net) escribió:

On 07/23/2017 06:00 PM, Rafael Mora wrote:

...

Hello guys,

This is what I've got on ../var/data:

[root@localhost data]# pwd /var/lib/mailman/var/data [root@localhost data]# ls -l total 76 -rw-rw---- 1 mailman mailman 74752 Jul 16 16:44 mailman.db

What should I do in order to let mailman install the DB files?

Run

bin/mailman aliases

-- Mark Sapiro 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

On 07/22/2017 03:46 AM, Rafael Mora wrote:

Can I use it for mailing lists? like MailChimp?

El vie., 21 jul. 2017 a las 20:34, Mark Sapiro (mark@msapiro.net) escribió:

...

On 07/21/2017 06:07 PM, Rafael Mora wrote:

...

I want to use Mailman to send emails to our customers.

I would highly recommend using a service like MailChimp. MailChimp has a decent free tier and if you are above that, I'm not sure if you can handle configuring Postfix the right way. It's not my intention to be demeaning or anything, but it sounds like that would be a little too complicated for you... (I wouldn't want to manage a Mailserver in charge of tens of thousands of emails per month)

Is there a ´default´ admin account??

El vie., 21 jul. 2017 a las 20:34, Mark Sapiro (mark@msapiro.net) escribió:

On 07/21/2017 06:07 PM, Rafael Mora wrote:

...

I want to use Mailman to send emails to our customers.

So you need to create a list and add your customers as members.

Please note that Mailman is not a substitute for a customer relations management system. It can be used in that way, but a true CRM system has advantages ove Mailman. Mailman is primarily designed to support discussion lists such as this one.

...

I´m getting this error when I click on sign up and log in:

FilterError at /accounts/login/ /bin/sh: sassc: command not found

See the third bullet under http://docs.list.org/en/latest/prodsetup.html#dependencies.

-- Mark Sapiro 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

I did not run the createsuperuser command, have to do that.

What about this:

Don’t leave the console email backend configured and running once you get to the point where you want to send real emails, though!

How do I change the setting to send the emails instead of printing them on the console????

On Fri, Jul 21, 2017, 21:16 Mark Sapiro mark@msapiro.net wrote:

On 07/21/2017 06:59 PM, Rafael Mora wrote:

...

Is there a ´default´ admin account??

It's the user you create with

python manage.py createsuperuser

See < http://docs.list.org/en/latest/devsetup.html#run-the-mailman-suite-combined-...

...

.

-- Mark Sapiro 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

On 07/21/2017 02:05 PM, Rafael Mora wrote:

(env2) [mailman@localhost mailman-suite_project]$ python2 manage.py runserver Performing system checks...

System check identified no issues (0 silenced). July 21, 2017 - 20:50:29 Django version 1.11.3, using settings 'settings' Starting development server at http://127.0.0.1:8000/ Quit the server with CONTROL-C.

And did you try to go to http://127.0.0.1:8000/ or http://localhost:8000/ from a browser on that machine? If you're truing to access it from another machine, you need to do something like

python2 manage.py runserver 192.168.1.42:8000