• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue mailist dont work

Status
Not open for further replies.
It seems that the website is not configured correctly in Plesk. The domain itself is not accessible. It has nothing to do with the IP exclusion, it is a simple web server configuration issue. Please check that the path to your web server document root directory is correct and that you are using the Plesk default permissions on files and directories. Then run
# /usr/local/psa/admin/sbin/httpdmng --reconfigure-domain lists.doitauto.de
You can run this, too:
# /usr/local/psa/bin/repair --restore-vhosts-permissions
 
show here attachment, must i creat here separately a DNS for the mailisting?
 

Attachments

  • Bildschirmfoto 2017-08-17 um 20.54.27.png
    Bildschirmfoto 2017-08-17 um 20.54.27.png
    177.3 KB · Views: 4
also i think the problem is here the file etc/mailman apache.conf in my file is following, is that right so?
Code: 
# Sample configuration for Debian mailman with Apache

# We can find mailman here:
ScriptAlias /cgi-bin/mailman/ /usr/lib/cgi-bin/mailman/
# And the public archives:
Alias /pipermail/ /var/lib/mailman/archives/public/
# Logos:
Alias /images/mailman/ /usr/share/images/mailman/

# Use this if you don't want the "cgi-bin" component in your URL:
# In case you want to access mailman through a shorter URL you should enable
# this:
#ScriptAlias /mailman/ /usr/lib/cgi-bin/mailman/
# In this case you need to set the DEFAULT_URL_PATTERN in
# /etc/mailman/mm_cfg.py to http://%s/mailman/ for the cookie
# authentication code to work.  Note that you need to change the base
# URL for all the already-created lists as well.

<Directory /usr/lib/cgi-bin/mailman/>
    AllowOverride None
    Options ExecCGI
    AddHandler cgi-script .cgi
    Order allow,deny
    Allow from all
</Directory>
<Directory /var/lib/mailman/archives/public/>
    Options FollowSymlinks
    AllowOverride None
    Order allow,deny
    Allow from all
</Directory>
<Directory /usr/share/images/mailman/>
    AllowOverride None
    Order allow,deny
    Allow from all
</Directory>


## The following describes how to configure mailman on
## a dedicated virtual host, courtesy Marco d'Itri.

# Add these lines in /etc/mailman/mm_cfg.py:
#DEFAULT_EMAIL_HOST = 'lists.example.net'
#DEFAULT_URL_HOST = 'lists.example.net'
#DEFAULT_URL_PATTERN = 'http://%s/'

#<VirtualHost *>
#ServerName lists.example.net
#DocumentRoot /var/www/lists
#ErrorLog /var/log/apache2/lists-error.log
#CustomLog /var/log/apache2/lists-access.log combined
#
#<Directory /var/lib/mailman/archives/>
#    Options FollowSymLinks
#    AllowOverride None
#</Directory>
#
#Alias /pipermail/ /var/lib/mailman/archives/public/
#Alias /images/mailman/ /usr/share/images/mailman/
#ScriptAlias /admin /usr/lib/cgi-bin/mailman/admin
#ScriptAlias /admindb /usr/lib/cgi-bin/mailman/admindb
#ScriptAlias /confirm /usr/lib/cgi-bin/mailman/confirm
#ScriptAlias /create /usr/lib/cgi-bin/mailman/create
#ScriptAlias /edithtml /usr/lib/cgi-bin/mailman/edithtml
#ScriptAlias /listinfo /usr/lib/cgi-bin/mailman/listinfo
#ScriptAlias /options /usr/lib/cgi-bin/mailman/options
#ScriptAlias /private /usr/lib/cgi-bin/mailman/private
#ScriptAlias /rmlist /usr/lib/cgi-bin/mailman/rmlist
#ScriptAlias /roster /usr/lib/cgi-bin/mailman/roster
#ScriptAlias /subscribe /usr/lib/cgi-bin/mailman/subscribe
#ScriptAlias /mailman/ /usr/lib/cgi-bin/mailman/
#</VirtualHost>
 
Ankebut said:
show here attachment, must i creat here separately a DNS for the mailisting?
Click to expand...
Yes, because you don't have a wildcard entry, so it is unclear where the domain resolves to. For the lists subdomain you need to set an IP address. After doing that, it can take several ours for the setting to propagate through the Internet.
 
You did it with the other subdomains, didn't you? Do the same for the lists subdomain. Simply create an entry for it in your DNS.
 
Oh sorry, I did not notice the CNAME. Actually, while you are at it, why use a CNAME for this and not add the lists with an A-record directly. Is the IP address correct? You have some other IP addresses in the record. Maybe the subdomain is not on the same IP as he main domain that the CNAME is currently pointing to?
 
It does not work here. Instead, the Plesk default page for the case when there is no website configured on the address is displayed. Besides, it seems to forward to https://, but the SSL ccertificate is missing, too.
 
Why do you use a CNAME in the first place? It is pointing to your main domain, that is pointing to the IP address. Why not remove the CNAME and add the A-record for the lists subdomain to point to the IP address? Then add a certificate or better: Remove the SSL redirection, because it can also be the cause of the issue you are experiencing with the Plesk default page.
 
also i have remove the CNAME and have ceatet A Record with lists.doitauto.de after i have create a subdomain with lists.doitauto.de and have set here SSL cert and nothing dont work :(
 
Once again: Can you please also remove the https:// redirect? Before installing all these extra gimmicks, maybe it is a good idea to first get the basic setup of the domain running.
 
Status
Not open for further replies.

Similar threads

C
Issue New Configuration not created
Replies
3
Views
365
Peter Debik
P
M
Issue Can't open Port 25. Please help
Replies
2
Views
367
mhogue
M
Lenny
Resolved Seeking Assistance with API Communication Issues via SSL on Plesk
Replies
4
Views
686
Lenny
Lenny
C
Issue Errors with Plesk scheduled backups
Replies
2
Views
202
cmartinez127
C
A
Question Plesk for Windows (Godaddy Website Hosting) and Microsoft RPC Service
Replies
4
Views
1K
AlmaWalters
A
Back
Top