Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Thats true, I dint build cyrus at the time of installation of postfix. But later I tried upgrading postfix with cyrus. Everything went on fine at the time of upgradation. But now when u told this, I doubt if it is succesful or not. How can I confirm it ?
If not successful, can I upgrade/update existing postfix with cyrus ?
You should just have to rebuild with the flags given in that link, ie:
Code:
% make tidy # if you have left-over files from a previous build
% make makefiles CCARGS="-DUSE_SASL_AUTH -DUSE_CYRUS_SASL \
-I/usr/local/include/sasl" AUXLIBS="-L/usr/local/lib -lsasl2"
(actually, the paths are probably /usr/include and /usr/lib), and check with "postconf -a". I'd be conservatrive and use a "make clean" as well.
Code:
# postconf -a
cyrus
dovecot
Last edited by billymayday; 11-12-2008 at 08:10 PM.
You should just have to rebuild with the flags given in that link, ie:
Code:
% make tidy # if you have left-over files from a previous build
% make makefiles CCARGS="-DUSE_SASL_AUTH -DUSE_CYRUS_SASL \
-I/usr/local/include/sasl" AUXLIBS="-L/usr/local/lib -lsasl2"
(actually, the paths are probably /usr/include and /usr/lib), and check with "postconf -a". I'd be conservatrive and use a "make clean" as well.
Code:
# postconf -a
cyrus
dovecot
Ok buddy. Did all those and my postconf -a is exactly what you mentioned. Now shall I try enabling sasl in main.cf ?
Meanwhile, I didn't understand what the command
make makefiles CCARGS="-DUSE_SASL_AUTH -DUSE_CYRUS_SASL \
-I/usr/local/include/sasl" AUXLIBS="-L/usr/local/lib -lsasl2"
Now I get a msg "Helo command rejected: need fully-qualified hostname"
Maillog
Quote:
# tail -f /var/log/maillog
Nov 13 16:45:00 MYHOST postfix/postfix-script[21317]: starting the Postfix mail system
Nov 13 16:45:00 MYHOST postfix/master[21318]: daemon started -- version 2.5.1, configuration /etc/postfix
Nov 13 16:45:00 MYHOST postfix/nqmgr[21320]: warning: please update the /etc/postfix/master.cf file; the new queue manager
Nov 13 16:45:00 MYHOST postfix/nqmgr[21320]: warning: (old name: nqmgr) has become the standard queue manager (new name: qmgr)
Nov 13 16:45:00 MYHOST postfix/nqmgr[21320]: warning: support for the name old name (nqmgr) will be removed from Postfix
Nov 13 16:45:00 MYHOST postfix/nqmgr[21320]: warning: bounce_queue_lifetime is larger than maximal_queue_lifetime - adjusting bounce_queue_lifetime
The message could not be sent because one of the recipients was rejected by the server. The rejected e-mail address was 'bimal@MYDOMAIN.com'. Subject 'test', Account: 'mail.MYDOMAIN.com', Server: 'mail.MYDOMAIN.com', Protocol: SMTP, Server Response: '554 5.5.2 <simi>: Helo command rejected: need fully-qualified hostname', Port: 25, Secure(SSL): No, Server Error: 554, Error Number: 0x800CCC79
The hostname given is MYHOST.MYDOMAIN.com. Its not blanked.
I was looking at the output of postconf -n on page 3.
Anyway, what's the story with your master.cf? Did you copy it from an older installation - may be worth starting with a fresh copy and replacing what you have. That's the real problem though.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.