Would you like to...

Print this page

Email this page

Post a comment

User Opinions

No users have voted.

---

How would you rate this answer?

Helpful

Not helpful

Thank you for rating this answer.

Start out by checking the Mailman and MTA logs. (MTA means Message Transfer Agent e.g., Sendmail.) They are your best guide and will, every time; contain the necessary clues as to both the exact definition of the problem and its solution.

The most frequent reasons for this are:

a) You didn't setup the cronjobs needed by Mailman

·        Check the crontab for the mailman user (or whatever user your Mailman installation runs as) and make sure the Mailman entries are there. If necessary restart cron to pick up the changes.

b) You haven't properly setup the aliases for your list.

·        The newlist command prints out the necessary aliases for the list. You will need to copy/add them to the alias file you are using for your list setup (often ~mailman/data/aliases).

c) You haven't run `newaliases` to "compile" the new aliases into a hash table or DBM. (Sendmail and Postfix)

·        Run `newaliases` as root. For postfix you'll also need to do a `postfix reload` for Postfix to pick up the changes.

d) You haven't run the Mailman qrunner daemon (~mailman/scripts/mailman or ~mailman/bin/mailmanctl). (You have to do this regardless of your MTA.)

·        Remember to configure your system to run the daemon when it boots!

e) The message you sent is being held for moderation by the list.

·        Check into the administrative interface for your list and then check the moderation queue.

f)    You haven’t subscribed to the list

·        Depending upon your list configurations, you must be subscribe in order to send mail to the list.

g) Make sure that you have set these variables:

DEFAULT_EMAIL_HOST = 'your.host.name'

DEFAULT_URL_HOST = 'your.url.addess'