Error when installing mailman (Perfect Server setup Centos 7)

haddaraboy New Member

Hi everyone,

So I am having an issue at step #22 when following THIS tuturial, when doing this:

... and add the line ScriptAlias /cgi-bin/mailman/ /usr/lib/mailman/cgi-bin/. Comment out Alias /pipermail/ /var/lib/mailman/archives/public/ and add the line Alias /pipermail /var/lib/mailman/archives/public/:
Click to expand...

after I start mailman i get this:

# systemctl start mailman.service
Job for mailman.service failed. See 'systemctl status mailman.service' and 'journalctl -xn' for details.
Click to expand...

For Journalct -xn i get:

# journalctl -xn
-- Logs begin at Tue 2014-12-02 03:07:47 UTC, end at Tue 2014-12-02 11:14:23 UTC. --
Dec 02 11:14:19 server1 mailmanctl[18976]: Site list is missing: mailman
Dec 02 11:14:19 server1 systemd[1]: mailman.service: control process exited, code=exited status=1
Dec 02 11:14:19 server1 systemd[1]: Failed to start GNU Mailing List Manager.
-- Subject: Unit mailman.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mailman.service has failed.
--
-- The result is failed.
Dec 02 11:14:19 server1 systemd[1]: Unit mailman.service entered failed state.
Dec 02 11:14:20 server1 sshd[18952]: Failed password for root from 189.2.201.53 port 39265 ssh2
Dec 02 11:14:20 server1 sshd[18952]: Received disconnect from 189.2.201.53: 11: Bye Bye [preauth]
Dec 02 11:14:23 server1 sshd[18979]: Invalid user carlos from 189.2.201.53
Dec 02 11:14:23 server1 sshd[18979]: input_userauth_request: invalid user carlos [preauth]
Dec 02 11:14:23 server1 sshd[18979]: pam_unix(sshd:auth): check pass; user unknown
Dec 02 11:14:23 server1 sshd[18979]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.2.201.53
Click to expand...

And for systemctl status mailman.service:

# systemctl status mailman.service
mailman.service - GNU Mailing List Manager
Loaded: loaded (/usr/lib/systemd/system/mailman.service; enabled)
Active: failed (Result: exit-code) since Tue 2014-12-02 11:20:37 UTC; 7min ago
Process: 19343 ExecStart=/usr/lib/mailman/bin/mailmanctl -s start (code=exited, status=1/FAILURE)
Process: 19341 ExecStartPre=/bin/chmod 660 /var/log/mailman/error (code=exited, status=0/SUCCESS)
Process: 19339 ExecStartPre=/bin/chown mailman:mailman /var/log/mailman/error (code=exited, status=0/SUCCESS)
Process: 19337 ExecStartPre=/bin/touch /var/log/mailman/error (code=exited, status=0/SUCCESS)
Process: 19335 ExecStartPre=/usr/bin/install -m644 -o root -g root /usr/lib/mailman/cron/crontab.in /etc/cron.d/mailman (code=exited, status=0/SUCCESS)
Process: 19333 ExecStartPre=/usr/lib/mailman/bin/mailman-update-cfg (code=exited, status=0/SUCCESS)

Dec 02 11:20:37 server1 mailmanctl[19343]: Site list is missing: mailman
Dec 02 11:20:37 server1 systemd[1]: mailman.service: control process exited, code=exited status=1
Dec 02 11:20:37 server1 systemd[1]: Failed to start GNU Mailing List Manager.
Dec 02 11:20:37 server1 systemd[1]: Unit mailman.service entered failed state.
Click to expand...

haddaraboy, Dec 2, 2014

#1

haddaraboy New Member

Also, for Till...

I think im being attacked from 189.2.201.53

In the journalctl -xn i can see:

Dec 02 11:31:11 server1 sshd[19910]: Invalid user build from 189.2.201.53
Dec 02 11:31:11 server1 sshd[19910]: input_userauth_request: invalid user build [preauth]
Dec 02 11:31:11 server1 sshd[19910]: pam_unix(sshd:auth): check pass; user unknown
Dec 02 11:31:11 server1 sshd[19910]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.2.201.53
Dec 02 11:31:13 server1 sshd[19910]: Failed password for invalid user build from 189.2.201.53 port 35521 ssh2
Dec 02 11:31:14 server1 sshd[19910]: Received disconnect from 189.2.201.53: 11: Bye Bye [preauth]
Dec 02 11:31:16 server1 sshd[19912]: Invalid user klog from 189.2.201.53
Dec 02 11:31:16 server1 sshd[19912]: input_userauth_request: invalid user klog [preauth]
Dec 02 11:31:16 server1 sshd[19912]: pam_unix(sshd:auth): check pass; user unknown
Dec 02 11:31:16 server1 sshd[19912]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.2.201.53
Click to expand...

Till please help me let me know what I can do,
Thanks in advance.

haddaraboy, Dec 2, 2014

#2

till Super Moderator Staff Member ISPConfig Developer

Please run:

/usr/lib/mailman/bin/newlist mailman

to create the mailman default list. seem as if the command slipped out of the command field and is shown in the output part of the tutorial only. I will fix that.

Regarding the attack, as soon as the install is finished, fail2ban will take care of blocking this IP.

till, Dec 2, 2014

#3

haddaraboy New Member

Thanks Till, when i try to make the list, i get:

Create a new, unpopulated mailing list.

Usage: /usr/lib/mailman/bin/newlist [options] [listname [listadmin-addr [admin-password]]]

Options:

-l language
--language=language
Make the list's preferred language `language', which must be a two
letter language code.

-u urlhost
--urlhost=urlhost
Gives the list's web interface host name.

-e emailhost
--emailhost=emailhost
Gives the list's email domain name.

-q/--quiet
Normally the administrator is notified by email (after a prompt) that
their list has been created. This option suppresses the prompt and
notification.

-h/--help
Print this help text and exit.

You can specify as many of the arguments as you want on the command line:
you will be prompted for the missing ones.

Every Mailman list has two parameters which define the default host name for
outgoing email, and the default URL for all web interfaces. When you
configured Mailman, certain defaults were calculated, but if you are running
multiple virtual Mailman sites, then the defaults may not be appropriate for
the list you are creating.

You also specify the domain to create your new list in by typing the command
like so:

newlist --urlhost=www.mydom.ain mylist

where `www.mydom.ain' should be the base hostname for the URL to this virtual
hosts's lists. E.g. with this setting people will view the general list
overviews at http://www.mydom.ain/mailman/listinfo. Also, www.mydom.ain
should be a key in the VIRTUAL_HOSTS mapping in mm_cfg.py/Defaults.py if
the email hostname to be automatically determined.

If you want the email hostname to be different from the one looked up by the
VIRTUAL_HOSTS or if urlhost is not registered in VIRTUAL_HOSTS, you can specify
`emailhost' like so:

newlist --urlhost=www.mydom.ain --emailhost=mydom.ain mylist

where `mydom.ain' is the mail domain name. If you don't specify emailhost but
urlhost is not in the virtual host list, then mm_cfg.DEFAULT_EMAIL_HOST will
be used for the email interface.

For backward compatibility, you can also specify the domain to create your
new list in by spelling the listname like so:

[email protected]

where www.mydom.ain is used for `urlhost' but it will also be used for
`emailhost' if it is not found in the virtual host table. Note that
'--urlhost' and '--emailhost' have precedence to this notation.

If you spell the list name as just `mylist', then the email hostname will be
taken from DEFAULT_EMAIL_HOST and the url will be taken from DEFAULT_URL (as
defined in your Defaults.py file or overridden by settings in mm_cfg.py).

Note that listnames are forced to lowercase.

Illegal list name: mailman@server1
Click to expand...

Last edited: Dec 2, 2014

haddaraboy, Dec 2, 2014

#4

till Super Moderator Staff Member ISPConfig Developer

please run this exact command:
Code:
/usr/lib/mailman/bin/newlist mailman

till, Dec 2, 2014

#5

haddaraboy New Member

I did exactly that and got:

# /usr/lib/mailman/bin/newlist mailman
Enter the email of the person running the list: [email protected]
Initial mailman password:
Create a new, unpopulated mailing list.

Usage: /usr/lib/mailman/bin/newlist [options] [listname [listadmin-addr [admin-password]]]

Options:

-l language
--language=language
Make the list's preferred language `language', which must be a two
letter language code.

-u urlhost
--urlhost=urlhost
Gives the list's web interface host name.

-e emailhost
--emailhost=emailhost
Gives the list's email domain name.

-q/--quiet
Normally the administrator is notified by email (after a prompt) that
their list has been created. This option suppresses the prompt and
notification.

-h/--help
Print this help text and exit.

You can specify as many of the arguments as you want on the command line:
you will be prompted for the missing ones.

Every Mailman list has two parameters which define the default host name for
outgoing email, and the default URL for all web interfaces. When you
configured Mailman, certain defaults were calculated, but if you are running
multiple virtual Mailman sites, then the defaults may not be appropriate for
the list you are creating.

You also specify the domain to create your new list in by typing the command
like so:

newlist --urlhost=www.mydom.ain mylist

where `www.mydom.ain' should be the base hostname for the URL to this virtual
hosts's lists. E.g. with this setting people will view the general list
overviews at http://www.mydom.ain/mailman/listinfo. Also, www.mydom.ain
should be a key in the VIRTUAL_HOSTS mapping in mm_cfg.py/Defaults.py if
the email hostname to be automatically determined.

If you want the email hostname to be different from the one looked up by the
VIRTUAL_HOSTS or if urlhost is not registered in VIRTUAL_HOSTS, you can specify
`emailhost' like so:

newlist --urlhost=www.mydom.ain --emailhost=mydom.ain mylist

where `mydom.ain' is the mail domain name. If you don't specify emailhost but
urlhost is not in the virtual host list, then mm_cfg.DEFAULT_EMAIL_HOST will
be used for the email interface.

For backward compatibility, you can also specify the domain to create your
new list in by spelling the listname like so:

[email protected]

where www.mydom.ain is used for `urlhost' but it will also be used for
`emailhost' if it is not found in the virtual host table. Note that
'--urlhost' and '--emailhost' have precedence to this notation.

If you spell the list name as just `mylist', then the email hostname will be
taken from DEFAULT_EMAIL_HOST and the url will be taken from DEFAULT_URL (as
defined in your Defaults.py file or overridden by settings in mm_cfg.py).

Note that listnames are forced to lowercase.

Illegal list name: mailman@server1
[root@server1 ~]# systemctl restart httpd.service
[root@server1 ~]# systemctl enable mailman.service
[root@server1 ~]# systemctl start mailman.service
Job for mailman.service failed. See 'systemctl status mailman.service' and 'journalctl -xn' for details.
Click to expand...

haddaraboy, Dec 2, 2014

#6

haddaraboy New Member

Can anyone please direct me in the right way, I have done what was suggested, and even looked around the net but haven't had luck so far.

I am going to install CentOS again and start from scratch.

haddaraboy, Dec 3, 2014

#7

till Super Moderator Staff Member ISPConfig Developer

There might be a problem with your hostname. The error says:

Illegal list name: mailman@server1

but a internet server should have a fully qualified domain name as hostname, so it should be like this:

[email protected]

What is the output of:

hostname

and

hostname -f

till, Dec 3, 2014

#8

Log in or Sign up

Error when installing mailman (Perfect Server setup Centos 7)

haddaraboy New Member

haddaraboy New Member

till Super Moderator Staff Member ISPConfig Developer

haddaraboy New Member

till Super Moderator Staff Member ISPConfig Developer

haddaraboy New Member

haddaraboy New Member

till Super Moderator Staff Member ISPConfig Developer

Share This Page

Log in or Sign up

Error when installing mailman (Perfect Server setup Centos 7)

haddaraboy New Member

haddaraboy New Member

till Super Moderator Staff Member ISPConfig Developer

haddaraboy New Member

till Super Moderator Staff Member ISPConfig Developer

haddaraboy New Member

haddaraboy New Member

till Super Moderator Staff Member ISPConfig Developer

Share This Page

Useful Searches