Mark Labeste writes:
Thanks for your reply. I was abled point to the mailman.cfg path appeared in mailman info. Below is the result of mailman conf. But archive is still now showing on web browser.
Sorry, can't help you without more information. Is your archive visible from the Internet?
What do you mean by "archive is not showing"? Do you get an error indication (like HTTP 404 error "no such page")? Do you get the archive page but you expect to see email there and there isn't any? If something else, what?
I assume you installed Mailman from a distribution. Which one?
What does "mailman info" report? If that doesn't work, you'll have to find the installed Mailman hierarchy, probably /var/lib/mailman3 or /usr/lib/mailman3, and run "bin/mailman info" from there.
What are the contents of these files: mailman.cfg (probably in /etc/mailman3/mailman.cfg) settings.py (there are a lot of these with different purposes, with luck you'll find the right one in /etc/mailman3/settings.py or possibly in var/etc/settings.py under the Mailman hierarchy) urls.py (may be in /etc/mailman3/urls.py, or next to settings.py)
This list strips most attachments. However it should be possible to attach these files as long as the Content-Type is text/plain. If you're not sure what the Content-Type your email program applies, you can include them in the message body at the end.
The following version information may be useful later, but it's not urgent. What versions of the following packages are installed:
mailman3 (possibly just mailman) postorius hyperkitty gunicorn mailman-web mailmanclient django_mailman (possibly django-mailman) django (or Django) (all of the above may be prefixed with something that indicates that they are Python programs) apache (possibly apache2 or apache24) or possibly nginx uwsgi (may not be in use)
Steve