Qmail compliation & Installation

[jamrock]

There is not much we can do until you have all services up and running for more than one second.

Perhaps you could stop qmail, backup the /var/qmail/supervise/qmail-send/run file and copy the contents from your browser into a text editor.

Remember to use a Linux machine for this.

Have you checked the logs?

How do I get rid of the messages in queue?

The messages will be routed to the user when qmail is working. If you manually delete the messages, you will corrupt your queue. You really don't want to do this.

What should the email address of the user be?
syntax
=address:user:uid:gid:directory:dash:extension

Is it tom@machinename.domain or is it
[b]tom@domain[b/]?

The user's address is username@test_company.com. DNS is important in the whole process. When you send a message, qmail will check the MX record in your DNS zone file to see which machine handles mail for test_company.com. DNS will also tell it, the I.P. address of the mail server.

The mail will then be routed to the user's mailbox on the mail server, if it can be found.

I expected a message to be returned, if the user cannot be found on the server.

Until qmail has been set up properly, it cannot deliver mail, including replies stating that the user does not exist on the server.

Your log should show repeated attempts to send the mail and a description of the error that is preventing the mail from being sent.

Please note that you have not yet set up the pop3 programme. This will allow the user to transfer the messages from his mailbox on the mail server to his workstation. Checkpassword is the one that the documentation recommends.

You should have all the services running before attempting to set it up. You will only be making your life harder if you attempt to set up pop3 at this point.

[exdol]

What should directory be?

Give me an example of a user, using the complete syntax.
=address:user:uid:gid:directory:dash:extension

[jamrock]

Give me an example of a user, using the complete syntax.
=address:user:uid:gid:directory:dash:extension

I don't understand. Please clarify.

Where is this information taken from?

[exdol]

[quote author=jamrock link=board=8;threadid=1526;start=15#msg18676 date=1064445744]
I don't understand. Please clarify.

Where is this information taken from?
[/quote]

This is take from page 31 of the Life with qmail document under the section qmail-users

Should the directory be just the user's home directory or should it be the Maildir in the home directory?

[jamrock]

I see...

I have never used that. I am not too sure what it does.
On my system, we use the Maildir format. User jbrown's mailbox structure is as follows.

/home/jbrown/Maildir/
/home/jbrown/Maildir/new
/home/jbrown/Maildir/cur
/home/jbrown/Maildir/tmp

I have set up the /etc/skel directory so that each new user gets this format. The /etc/skel directory is a useful way to set up the directories that you want created for each user.

Just create the directory structure in the /etc/skel folder and it will be added below the home directory of each new user created.

/etc/skel/Maildir/
/etc/skel/Maildir/new
/etc/skel/Maildir/cur
/etc/skel/Maildir/tmp

My /var/qmail/control/defaultdelivery file has one line

./Maildir/


I will not be able to help you until you have all the services running for more than 1 second.

[jamrock]

Note the contents of the /var/qmail/supervise/qmail-send/run file

#!/bin/sh
exec /var/qmail/rc

It calls the /var/qmail/rc file. You may want to review the section on creating the /var/qmail/rc file. Check for typos, dos formats, etc.

Note that the qmail-send service processes the queue so if it isn't running, no mail will be delivered. See section D.

[exdol]

[quote author=jamrock link=board=8;threadid=1526;start=15#msg18697 date=1064470235]
I see...

I have never used that. I am not too sure what it does.
On my system, we use the Maildir format. User jbrown's mailbox structure is as follows.

/home/jbrown/Maildir/
/home/jbrown/Maildir/new
/home/jbrown/Maildir/cur
/home/jbrown/Maildir/tmp

I have set up the /etc/skel directory so that each new user gets this format. The /etc/skel directory is a useful way to set up the directories that you want created for each user.

Just create the directory structure in the /etc/skel folder and it will be added below the home directory of each new user created.

/etc/skel/Maildir/
/etc/skel/Maildir/new
/etc/skel/Maildir/cur
/etc/skel/Maildir/tmp
[/quote]
I have make the adjustments accordingly.

My /var/qmail/control/defaultdelivery file has one line

./Maildir/

This entry was ./Mailbox. I have subsequently changed it.

I will not be able to help you until you have all the services running for more than 1 second.

Here is my statistics:
[root@quota root]# qmailctl stat
/service/qmail-send: up (pid 833) 62618 seconds
/service/qmail-send/log: up (pid 31307) 0 seconds
/service/qmail-smtpd: up (pid 9464) 60035 seconds
/service/qmail-smtpd/log: up (pid 9466) 60035 seconds
messages in queue: 10
messages in queue but not yet preprocessed: 4
/service/qmail-pop3d: up (pid 9908) 59963 seconds
/service/qmail-pop3d/log: up (pid 31306) 0 seconds
[root@quota root]#

[exdol]

I have gotten Qmail basic installation to work, as usual typos, the inst_check is now giving me the expected message:

Congratulations, your LWQ installation looks good!

readproctitle is showing
# ps -ef| grep "service errors" | grep -v grep
root 821 774 0 Sep25 ? 00:00:28 readproctitle service errors: ..
#

see page 25 of Life with Qmail.

The problem I am now having is that my Qmail -pop3d does not respond after a while. See the
# qmailctl stat
/service/qmail-send: up (pid 828) 57103 seconds
/service/qmail-send/log: up (pid 15961) 0 seconds
/service/qmail-smtpd: up (pid 830) 57103 seconds
/service/qmail-smtpd/log: up (pid 833) 57103 seconds
messages in queue: 1
messages in queue but not yet preprocessed: 0
/service/qmail-pop3d: up (pid 831) 57103 seconds
/service/qmail-pop3d/log: up (pid 15960) 0 seconds

I figure it maybe a typo, so I will check it.

Question:
Below is the /var/qmail/supervise/qmail-pop3d/log/run file

exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t \
/var/log/qmail/pop3d

What is the \ for?

Secondly, the indent before /var/log/qmail/pop3d should the file be typed that way or is it for formatting? One of the things I did with the other files I had typo problems with is to remove this indent. The documentation also mentioned executing trouble files line-by-line at the command line interface to see which line has a problem.

[jamrock]

# qmailctl stat
/service/qmail-send: up (pid 828) 57103 seconds
/service/qmail-send/log: up (pid 15961) 0 seconds
/service/qmail-smtpd: up (pid 830) 57103 seconds
/service/qmail-smtpd/log: up (pid 833) 57103 seconds
messages in queue: 1
messages in queue but not yet preprocessed: 0
/service/qmail-pop3d: up (pid 831) 57103 seconds
/service/qmail-pop3d/log: up (pid 15960) 0 seconds

I see no evidence that your qmail-send service is running. I cannot go forward until that has been corrected.

[exdol]

# netstat -a|grep pop
tcp 0 0 *op3 *:* LISTEN
tcp 1 0 quota.domain.comop3 172.17.25.124:1807 CLOSE_WAIT
tcp 1 0 quota.domain.comop3 172.17.25.124:1599 CLOSE_WAIT
tcp 1 0 quota.domain.comop3 172.17.25.124:1711 CLOSE_WAIT
tcp 1 0 quota.domain.comop3 172.17.25.124:1933 CLOSE_WAIT
tcp 1 0 quota.domain.comop3 172.17.25.124:1659 CLOSE_WAIT
tcp 1 0 quota.domain.comop3 172.17.25.124:1705 CLOSE_WAIT
tcp 1 0 quota.domain.comop3 172.17.25.124:1753 CLOSE_WAIT
tcp 1 0 quota.domain.comop3 172.17.25.124:1798 CLOSE_WAIT
tcp 1 0 quota.domain.comop3 172.17.25.124:1606 CLOSE_WAIT
tcp 1 0 quota.domain.comop3 172.17.25.124:1607 CLOSE_WAIT
tcp 1 0 quota.domain.comop3 172.17.25.124:1924 CLOSE_WAIT
tcp 1 0 quota.domain.comop3 172.17.25.124:1716 CLOSE_WAIT
tcp 1 0 quota.domain.comop3 172.17.25.124:1602 CLOSE_WAIT
tcp 1 0 quota.domain.comop3 172.17.25.124:1714 CLOSE_WAIT
tcp 0 0 quota.domain.comop3 172.17.25.124:1603 ESTABLISHED
tcp 1 0 quota.domain.comop3 172.17.25.124:1715 CLOSE_WAIT
tcp 1 0 quota.domain.comop3 172.17.25.124:1747 CLOSE_WAIT
tcp 1 0 quota.domain.comop3 172.17.25.124:1808 CLOSE_WAIT
tcp 1 0 quota.domain.comop3 172.17.25.124:1792 CLOSE_WAIT
tcp 1 0 quota.domain.comop3 172.17.25.124:1600 CLOSE_WAIT
tcp 1 0 quota.domain.comop3 172.17.25.124:1712 CLOSE_WAIT
tcp 1 0 quota.domain.comop3 172.17.25.124:1601 CLOSE_WAIT
#

Should the IPOP3 service that comes with RedHat be started by default?