Problem with Postfix (process smtpd exit status 1)
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.
Problem with Postfix (process smtpd exit status 1)
Hi there,
I'm going crazy trying to run a mail server on my slicehost server.
I have followed this how to [link]
but I have problems accessing with squirrel and I thought something was wrong.
Looking at /var/log/mail* I have these errors every action I do with postfixadmin or squirrel:
Code:
Mar 21 11:03:37 rory postfix/smtpd[29308]: fatal: need service transport:endpoint instead of "inet"
==> /var/log/mail.info <==
Mar 21 11:03:37 rory postfix/smtpd[29308]: fatal: need service transport:endpoint instead of "inet"
==> /var/log/mail.log <==
Mar 21 11:03:37 rory postfix/smtpd[29308]: fatal: need service transport:endpoint instead of "inet"
==> /var/log/mail.warn <==
Mar 21 11:03:37 rory postfix/smtpd[29308]: fatal: need service transport:endpoint instead of "inet"
==> /var/log/mail.info <==
Mar 21 11:03:38 rory postfix/master[29286]: warning: process /usr/lib/postfix/smtpd pid 29308 exit status 1
Mar 21 11:03:38 rory postfix/master[29286]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
==> /var/log/mail.log <==
Mar 21 11:03:38 rory postfix/master[29286]: warning: process /usr/lib/postfix/smtpd pid 29308 exit status 1
Mar 21 11:03:38 rory postfix/master[29286]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
==> /var/log/mail.warn <==
Mar 21 11:03:38 rory postfix/master[29286]: warning: process /usr/lib/postfix/smtpd pid 29308 exit status 1
Mar 21 11:03:38 rory postfix/master[29286]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
I can't figure out what is wrong.. All my config files seems ok but I maybe did some mistake somewhere..
I'll have a more detailed look a bit later, but most importantly, are you trying to ruin Postfix chrooted? If not, you need to put "n"s in the relevant column in master (take a backup first please).
Eg change
Code:
# ==========================================================================
# service type private unpriv chroot wakeup maxproc command + args
# (yes) (yes) (yes) (never) (100)
# ==========================================================================
smtp inet n - - - - smtpd
to
Code:
# ==========================================================================
# service type private unpriv chroot wakeup maxproc command + args
# (yes) (yes) (yes) (never) (100)
# ==========================================================================
smtp inet n - n - - smtpd
Also, myorigin should be a domain such as example.com.
As I said, I'll have a better look later. Don't forget to restart Postfix after changing master.cf.
Also, myorigin should be a domain such as example.com.
I found something here, myhostname was localhost instead of mail.domain.com .
I have done this but still the same results:
Code:
==> /var/log/mail.err <==
Mar 21 22:44:57 rory postfix/smtpd[32331]: fatal: need service transport:endpoint instead of "inet"
==> /var/log/mail.info <==
Mar 21 22:44:57 rory postfix/smtpd[32331]: fatal: need service transport:endpoint instead of "inet"
==> /var/log/mail.log <==
Mar 21 22:44:57 rory postfix/smtpd[32331]: fatal: need service transport:endpoint instead of "inet"
==> /var/log/mail.warn <==
Mar 21 22:44:57 rory postfix/smtpd[32331]: fatal: need service transport:endpoint instead of "inet"
==> /var/log/mail.info <==
Mar 21 22:44:58 rory postfix/master[32312]: warning: process /usr/lib/postfix/smtpd pid 32331 exit status 1
Mar 21 22:44:58 rory postfix/master[32312]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
==> /var/log/mail.log <==
Mar 21 22:44:58 rory postfix/master[32312]: warning: process /usr/lib/postfix/smtpd pid 32331 exit status 1
Mar 21 22:44:58 rory postfix/master[32312]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
==> /var/log/mail.warn <==
Mar 21 22:44:58 rory postfix/master[32312]: warning: process /usr/lib/postfix/smtpd pid 32331 exit status 1
Mar 21 22:44:58 rory postfix/master[32312]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
I still think it's a chroot issue. Looking at the chroot troubleshooting at www.postfix.org, they suggest taking of copy master.cf and de-chrooting the working copy. I'd certainly give that a go first - if it works great, if not, at least you've ruled out a possible cause.
Stupid question, but you did populate all the mysql tables referred to by postfix didn't you?
Yes, the tables are been populated by postfixadmin.
Quote:
Originally Posted by billymayday
And when you run postfix check, it shows no errors in your config ? sometimes that will point you to a simple error in your config..
Postfix check doesn't show any errors.
So, I tried to rewrite all the config files after installing postfix again. This seems to fix some problems but after I created a domain and a mailbox I can't connect with squirrelmail to the mailbox.
What I can't do is configure squirrelmail to access the mysql db where postfixadmin saved mailbox data.
Error connecting to IMAP server: localhost.
111 : Connection refused
When you set up postfix, get a basic setup working, then add components one at a time if possible. Squirrelmail shouldn't be an issue intul everything else works.
That said, did you run the config program for squirrelmail (conf.pl)
When you set up postfix, get a basic setup working, then add components one at a time if possible. Squirrelmail shouldn't be an issue intul everything else works.
That said, did you run the config program for squirrelmail (conf.pl)
You are absolutely right. Actually I don't see anymore the exit status 1 error but I'm not sure that all the things works.
So, if all is right I should be able to connect throw telnet and send an email (I suppose) but I can't.
Code:
breiko@starlight:~> telnet mail.MYDOMAIN.com 25
Trying 67.207.139.163...
Connected to mail.MYDOMAIN.com.
Escape character is '^]'.
220 mail.domain.com ESMTP Postfix (Ubuntu)
mail from: info@MYDOMAIN.com
250 2.1.0 Ok
rcpt to: carlo.etc@gmail.com
554 5.7.1 <carlo.etc@gmail.com>: Relay access denied
Try fixing that one up - you could leave it blank and rely on mynetworks_style if you don't have an external IP connected - but I suspect you do. Be careful you don't create an open relay here.
Try fixing that one up - you could leave it blank and rely on mynetworks_style if you don't have an external IP connected - but I suspect you do. Be careful you don't create an open relay here.
What do you mean with don't create an open relay? I tried to fix as you suggested but I got always the same error. Relay access denied.
What do you mean with don't create an open relay? I tried to fix as you suggested but I got always the same error. Relay access denied.
Ok. I think I did something stupid. I received this notification:
This is an automatic notification to let you know the IP Address 67... has been placed on one or more block-lists (see below): http://cbl.abuseat.org/faq.html
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.