Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
Jun 21 09:00:51 Cyberia postfix/qmgr[11507]: warning: connect to transport amavis: Connection refused
Jun 21 09:00:51 Cyberia postfix/qmgr[11507]: 5F8147CE7: from=<root@moodle.localdomain>, size=1823, nrcpt=1 (queue active)
/0/0.01, dsn=4.3.0, status=deferred (mail transport unavailable)
Jun 21 09:00:51 Cyberia postfix/error[11511]: 5BB797CE3: to=<andrew@bitco.co.za>, relay=none, delay=41804, delays=41804/0/0/0.01, dsn=4.3.0, status=deferred (mail transport unavailable)
The error message(s) indicate that Postfix is attempting to filter the mail through Amavis, which is a fairly normal practice. One of the problems appears to be that Amavis is either not running, or is not bound to the correct ports as configured through your Postfix master.cf, main.cf and Amavis configuration.
The other problem I see is that it looks like you have a problem with the domains being handled and what Postfix thinks is the host name and what domains it thinks it is supposed to receive for. You have: to=<andrew@bitco.co.za> and to=<andrew@nutxase.co.za>. Postfix will attempt to deliver for those domains specified in mydestinations. All others it will attempt to do a domain lookup and send to that domain. Depending on how you have the sender restrictions set, e.g. permit my_networks, permit SASL authenticated, etc, and where the message is originating it may try to send or it may bounce on authentication. In this case, <andrew@nutxase.co.za>, bounced, which means that Postfix thinks that it is supposed to deliver for nutxase.co.za, but there is no andrew user.
In order to use virtual users, you will need to have the proper SQL configuration files and reference them in your main.cf. These will contain the lookup strings to verify the user for Postfix. The SQL tables must be in the proper format to match this and so forth. Typically I use the tool Postfixadmin (php based web app) to handle creating the user accounts as it puts them in the correct format for me.
I would recommend that you turn on debugging, including password debugging in Postfix and your POP/IMAP program, which is what Postfix will use to handle SASL authentication. Your log files should then give you a lot more information regarding the problem. Be sure to restart your services, check to see if the applications are running and listening on the proper ports and then test. You might even want to start with a telnet test for SMTP rather than trying to connect through a mail client to eliminate some variables.
This sounds like a mis-match between the user + password in your SQL database vs what is being transmitted and received by Dovecot. Sometimes this can be fixed with an adjustment to the Dovecot SQL configuration. To find out what is happening, there are three lines in dovecot that you can enable to show you what it is doing. This should show you what the problem is and hopefully, in turn, how to solve it.
when i add those i get Jun 21 14:49:14 tornado dovecot: child 5887 (auth) returned error 89
Jun 21 14:49:14 tornado dovecot: Auth process died too early - shutting down
here is my dovecot-mysql.conf
driver = mysql
connect = host=localhost dbname=postfix user=postfix password=XXXX
default_pass_scheme = PLAIN
password_query = SELECT password FROM mailbox WHERE username = '%u'
user_query = SELECT maildir, 89 AS uid, 89 AS gid FROM mailbox WHERE username = '%u'
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.