On Mon, Oct 18, 2010 at 22:34, Steve Clark sclark@netwolves.com wrote:
Hmm... I am not having any problem connecting from the U.S.
ping 178.63.65.136 PING 178.63.65.136 (178.63.65.136) 56(84) bytes of data. 64 bytes from 178.63.65.136: icmp_seq=1 ttl=49 time=140 ms 64 bytes from 178.63.65.136: icmp_seq=2 ttl=49 time=142 ms 64 bytes from 178.63.65.136: icmp_seq=3 ttl=49 time=138 ms
telnet 178.63.65.136 25 Trying 178.63.65.136... Connected to 178.63.65.136. Escape character is '^]'. ^] telnet> close Connection closed.
Exactly the problem! It pings fine (so I know that connections can be established over the physical wires) and on the IP address telnet answers. However, telnet to port 25 (smtp) with the domain name fails. Why could that be?
Dotan Cohen wrote:
On Mon, Oct 18, 2010 at 22:34, Steve Clark sclark@netwolves.com wrote:
Hmm... I am not having any problem connecting from the U.S.
<snip>>
telnet 178.63.65.136 25 Trying 178.63.65.136... Connected to 178.63.65.136. Escape character is '^]'. ^] telnet> close Connection closed.
Exactly the problem! It pings fine (so I know that connections can be established over the physical wires) and on the IP address telnet answers. However, telnet to port 25 (smtp) with the domain name fails. Why could that be?
Bingo! DNS.
mark
On Mon, Oct 18, 2010 at 22:47, m.roth@5-cent.us wrote:
Bingo! DNS.
No, even on the IP address telnet won't answer on port 25:
✈dcl:~$ telnet 178.63.65.188 25 Trying 178.63.65.188... telnet: Unable to connect to remote host: Connection timed out ✈dcl:~$
Dotan Cohen wrote, On 10/18/2010 04:51 PM:
On Mon, Oct 18, 2010 at 22:47, m.roth@5-cent.us wrote:
Bingo! DNS.
No, even on the IP address telnet won't answer on port 25:
✈dcl:~$ telnet 178.63.65.188 25 Trying 178.63.65.188... telnet: Unable to connect to remote host: Connection timed out ✈dcl:~$
are you coming to it from a 178.63.65.* or from a private IP (even if through a NAT)?
i.e. could there be one of those router things that does not pass private IP traffic on through between you and it? :)
Grasping at a straw that look like a thought.
On Mon, Oct 18, 2010 at 22:55, Todd Denniston Todd.Denniston@tsb.cranrdte.navy.mil wrote:
are you coming to it from a 178.63.65.* or from a private IP (even if through a NAT)?
No, I'm pinging and telnetting in from another country!
On Mon, 2010-10-18 at 22:38 +0200, Dotan Cohen wrote:
Exactly the problem! It pings fine (so I know that connections can be established over the physical wires) and on the IP address telnet answers. However, telnet to port 25 (smtp) with the domain name fails. Why could that be?
--- Why not post your config file so peeps can have a look at it?
John
On Mon, 2010-10-18 at 16:55 -0400, JohnS wrote:
On Mon, 2010-10-18 at 22:38 +0200, Dotan Cohen wrote:
Exactly the problem! It pings fine (so I know that connections can be established over the physical wires) and on the IP address telnet answers. However, telnet to port 25 (smtp) with the domain name fails. Why could that be?
Why not post your config file so peeps can have a look at it?
John
Well I have now a feeling it's more involved the his config file....
John
On 10/18/2010 3:38 PM, Dotan Cohen wrote:
On Mon, Oct 18, 2010 at 22:34, Steve Clarksclark@netwolves.com wrote:
Hmm... I am not having any problem connecting from the U.S.
ping 178.63.65.136 PING 178.63.65.136 (178.63.65.136) 56(84) bytes of data. 64 bytes from 178.63.65.136: icmp_seq=1 ttl=49 time=140 ms 64 bytes from 178.63.65.136: icmp_seq=2 ttl=49 time=142 ms 64 bytes from 178.63.65.136: icmp_seq=3 ttl=49 time=138 ms
telnet 178.63.65.136 25 Trying 178.63.65.136... Connected to 178.63.65.136. Escape character is '^]'. ^] telnet> close Connection closed.
Exactly the problem! It pings fine (so I know that connections can be established over the physical wires) and on the IP address telnet answers. However, telnet to port 25 (smtp) with the domain name fails. Why could that be?
No the example above shows a telnet to port 25 connecting - which I can reproduce too - but there is no 220 response as there should be from a mailserver. Either the process is hung or configured to black/graylist unknown connections, or something other than mailserver is listening on port 25.
Telnet is going to go to an A record, so you have to look up the MX record first, then telnet to the target.
No the example above shows a telnet to port 25 connecting - which I can reproduce too - but there is no 220 response as there should be from a
I am late to the thread (and I haven't a clue what we are talking about in fact), but I get a 220 when I telnet into that IP address...
Escape character is '^]'. 220 mercury.localdomain ESMTP Postfix
Ian Murray wrote:
No the example above shows a telnet to port 25 connecting - which I can reproduce too - but there is no 220 response as there should be from a
I am late to the thread (and I haven't a clue what we are talking about in fact), but I get a 220 when I telnet into that IP address...
Escape character is '^]'. 220 mercury.localdomain ESMTP Postfix
Odd. Why would it say localdomain?
mark
On 20/10/10 5:42 AM, m.roth@5-cent.us wrote:
Ian Murray wrote:
No the example above shows a telnet to port 25 connecting - which I can reproduce too - but there is no 220 response as there should be from a
I am late to the thread (and I haven't a clue what we are talking about in fact), but I get a 220 when I telnet into that IP address...
Escape character is '^]'. 220 mercury.localdomain ESMTP Postfix
Odd. Why would it say localdomain?
He probably has an incorrect myhostname or mydomain value in main.cf. From the look of the postconf -n he posted, he hasn't specified either of these.
From the relevant section in Dotan's postconf -n:
mydestination = $myhostname, localhost.$mydomain, localhost newaliases_path = /usr/bin/newaliases.postfix
The equivalent section in mine (sanitised because copying & pasting is not the solution):
mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain mydomain = example.com myhostname = mail.example.com mynetworks = 127.0.0.0/8, 192.168.1.0/24 myorigin = $mydomain newaliases_path = /usr/bin/newaliases.postfix
Regards, Ben
Got it! I had to set these three last values: postconf -e 'mydomain = sharingcenter.eu' postconf -e 'myhostname - mail.sharingcenter.eu' postconf -e 'myhostname = mail.sharingcenter.eu' postconf -e 'mynetworks = 178.63.65.136' postconf -e 'mydestination = $myhostname, localhost.$mydomain, localhost, sharingcenter.eu, mail.sharingcenter.eu'
I thank you guys for your patience and help. I just spent a good few hours googling today and working my way around blogs, documentation, howto articles, forum posts, mailing list archives, and the like. I wouldn't have even known what to google for without the patient and helpful assistance I've received here. When it is said that CentOS is a "Community ENTerprise Operating System" be there no mistake!
Cold beer for anyone visiting Israel soon!
On 21/10/10 6:17 AM, Dotan Cohen wrote:
I thank you guys for your patience and help.
No problem.
I just spent a good few hours googling today and working my way around blogs, documentation, howto articles, forum posts, mailing list archives, and the like. I wouldn't have even known what to google for without the patient and helpful assistance I've received here. When it is said that CentOS is a "Community ENTerprise Operating System" be there no mistake!
Heh. It probably helps that I'm also subscribed to the postfix-users mailing list, which frequently addresses issues like this. I highly recommend it for anyone running postfix, even just as a lurker. Also, Wietse posts regularly to that list.
Cold beer for anyone visiting Israel soon!
If I could afford to visit, I'd take you up on that! :)
Regards, Ben
Am 18.10.2010 22:38, schrieb Dotan Cohen:
On Mon, Oct 18, 2010 at 22:34, Steve Clark sclark@netwolves.com wrote:
Hmm... I am not having any problem connecting from the U.S.
ping 178.63.65.136 PING 178.63.65.136 (178.63.65.136) 56(84) bytes of data. 64 bytes from 178.63.65.136: icmp_seq=1 ttl=49 time=140 ms 64 bytes from 178.63.65.136: icmp_seq=2 ttl=49 time=142 ms 64 bytes from 178.63.65.136: icmp_seq=3 ttl=49 time=138 ms
telnet 178.63.65.136 25 Trying 178.63.65.136... Connected to 178.63.65.136. Escape character is '^]'. ^] telnet> close Connection closed.
Exactly the problem! It pings fine (so I know that connections can be established over the physical wires) and on the IP address telnet answers. However, telnet to port 25 (smtp) with the domain name fails. Why could that be?
Sorry, your problem is not DNS. The MX resolves.
But if you talk to an MTA on port 25 you must get a greeting - that does not happen. Instead the connection hangs.
While your www server works:
~ $ telnet 178.63.65.136 80 Trying 178.63.65.136... Connected to static.136.65.63.178.clients.your-server.de (178.63.65.136). Escape character is '^]'. GET / HTTP/1.0
HTTP/1.1 200 OK Date: Mon, 18 Oct 2010 20:54:23 GMT Server: Apache/2.2.3 (CentOS) Last-Modified: Fri, 08 Oct 2010 21:00:56 GMT ETag: "c7a1c2-28-4e88b200" Accept-Ranges: bytes Content-Length: 40 Connection: close Content-Type: text/html; charset=UTF-8
<html><body>Hello, world!</body></html> Connection closed by foreign host.
~ $ telnet sharingcenter.eu 80 Trying 178.63.65.136... Connected to sharingcenter.eu (178.63.65.136). Escape character is '^]'. GET / HTTP/1.0
HTTP/1.1 200 OK Date: Mon, 18 Oct 2010 20:55:16 GMT Server: Apache/2.2.3 (CentOS) Last-Modified: Fri, 08 Oct 2010 21:00:56 GMT ETag: "c7a1c2-28-4e88b200" Accept-Ranges: bytes Content-Length: 40 Connection: close Content-Type: text/html; charset=UTF-8
<html><body>Hello, world!</body></html> Connection closed by foreign host.
I expect that even being local on the server(s) and running "telnet localhost 25" results in a hung connection.
You misconfigured your Postfix. Check your /var/log/maillog/ for startup errors.
By any chance, did you bring down loopback or destroyed the localhost mapping in /etc/hosts? Or you have something broken in your main.cf. Post the output of "postconf -n".
Alexander
I see now, since the last postfix restart the log is filling up with these:
Oct 18 22:59:42 mercury postfix/smtpd[11318]: fatal: open database /etc/aliases.db: No such file or directory Oct 18 22:59:43 mercury postfix/master[7816]: warning: process /usr/libexec/postfix/smtpd pid 11318 exit status 1 Oct 18 22:59:43 mercury postfix/master[7816]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling
The problem will probably reveal itself here, but I will need to do a bit of googling to decipher it all. I admit that much of the configuration was done with tutorials that I googled, with limited understanding. That's how we learn!
[root@mercury ~]# postconf -n alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix debug_peer_level = 2 home_mailbox = Maildir/ html_directory = no inet_interfaces = all mail_owner = postfix mailbox_command = mailq_path = /usr/bin/mailq.postfix manpage_directory = /usr/share/man mydestination = $myhostname, localhost.$mydomain, localhost newaliases_path = /usr/bin/newaliases.postfix queue_directory = /var/spool/postfix readme_directory = /usr/share/doc/postfix-2.3.3/README_FILES sample_directory = /usr/share/doc/postfix-2.3.3/samples sendmail_path = /usr/sbin/sendmail.postfix setgid_group = postdrop smtp_tls_note_starttls_offer = yes smtp_use_tls = yes smtpd_tls_CAfile = /etc/postfix/ssl/cacert.pem smtpd_tls_auth_only = no smtpd_tls_cert_file = /etc/postfix/ssl/smtpd.crt smtpd_tls_key_file = /etc/postfix/ssl/smtpd.key smtpd_tls_loglevel = 1 smtpd_tls_received_header = yes smtpd_tls_session_cache_timeout = 3600s smtpd_use_tls = yes tls_random_source = dev:/dev/urandom unknown_local_recipient_reject_code = 550 [root@mercury ~]#
To what must I change /etc/aliases.db? Which fine manual should I be reading?
On 10/18/10 2:08 PM, Dotan Cohen wrote:
I see now, since the last postfix restart the log is filling up with these:
Oct 18 22:59:42 mercury postfix/smtpd[11318]: fatal: open database /etc/aliases.db: No such file or directory Oct 18 22:59:43 mercury postfix/master[7816]: warning: process /usr/libexec/postfix/smtpd pid 11318 exit status 1 ....
To what must I change /etc/aliases.db? Which fine manual should I be reading?
in sendmail at least, the command `newaliases` parses /etc/mail/aliases and creates /etc/mail/aliases.db
On Mon, Oct 18, 2010 at 11:08:37PM +0200, Dotan Cohen wrote:
I see now, since the last postfix restart the log is filling up with these:
Oct 18 22:59:42 mercury postfix/smtpd[11318]: fatal: open database /etc/aliases.db: No such file or directory
Well, see if you have an /etc/aliases, which you should, even if it's a defaut. Then just run newaliases which will create an /etc/aliases.db
The issues may be elsewhere, but get rid of that one.
On Mon, Oct 18, 2010 at 05:15:52PM -0400, Scott Robbins wrote:
On Mon, Oct 18, 2010 at 11:08:37PM +0200, Dotan Cohen wrote:
I see now, since the last postfix restart the log is filling up with these:
Oct 18 22:59:42 mercury postfix/smtpd[11318]: fatal: open database /etc/aliases.db: No such file or directory
Well, see if you have an /etc/aliases, which you should, even if it's a defaut. Then just run newaliases which will create an /etc/aliases.db
The issues may be elsewhere, but get rid of that one.
I should add that I think the actual postfix command is postalias and a ls -l /usr/bin/newaliases points to /etc/alternatives/mta-newaliases
The newaliases command, as somone else commented, is the sendmail command and depending upon the system, e.g., in FreeBSD it's done in /etc/mail/mailer.conf, RH uses alternatives, and so on.
On Mon, Oct 18, 2010 at 23:15, Scott Robbins scottro@nyc.rr.com wrote:
Well, see if you have an /etc/aliases, which you should, even if it's a defaut. Then just run newaliases which will create an /etc/aliases.db
The issues may be elsewhere, but get rid of that one.
Well, I tried:
[root@mercury ~]# ls -l /etc/aliases -rw-r--r-- 1 root root 1512 Apr 25 2005 /etc/aliases [root@mercury ~]# newaliases [root@mercury ~]# service postfix restart Shutting down postfix: [ OK ] Starting postfix: [ OK ] [root@mercury ~]# service postfix status master (pid 12412) is running... [root@mercury ~]# tail /var/log/maillog Oct 18 23:15:59 mercury postfix/master[7816]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling Oct 18 23:16:18 mercury dovecot: imap-login: Login: user=<sami37>, method=PLAIN, rip=::ffff:127.0.0.1, lip=::ffff:127.0.0.1, secured Oct 18 23:16:18 mercury dovecot: IMAP(sami37): Disconnected: Logged out Oct 18 23:16:59 mercury postfix/smtpd[12298]: fatal: open database /etc/aliases.db: No such file or directory Oct 18 23:17:00 mercury postfix/master[7816]: warning: process /usr/libexec/postfix/smtpd pid 12298 exit status 1 Oct 18 23:17:00 mercury postfix/master[7816]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling Oct 18 23:17:49 mercury postfix/postfix-script: stopping the Postfix mail system Oct 18 23:17:49 mercury postfix/master[7816]: terminating on signal 15 Oct 18 23:17:49 mercury postfix/postfix-script: starting the Postfix mail system Oct 18 23:17:49 mercury postfix/master[12412]: daemon started -- version 2.3.3, configuration /etc/postfix [root@mercury ~]#
But it still won't connect:
✈dcl:~$ telnet mail.sharingcenter.eu 25 Trying 178.63.65.136... telnet: Unable to connect to remote host: Connection timed out ✈dcl:~$ telnet sharingcenter.eu 25 Trying 178.63.65.188... Trying 178.63.65.136... telnet: Unable to connect to remote host: Connection timed out ✈dcl:~$
Am 18.10.2010 23:22, schrieb Dotan Cohen:
Well, I tried:
[root@mercury ~]# ls -l /etc/aliases -rw-r--r-- 1 root root 1512 Apr 25 2005 /etc/aliases [root@mercury ~]# newaliases [root@mercury ~]# service postfix restart Shutting down postfix: [ OK ] Starting postfix: [ OK ] [root@mercury ~]# service postfix status master (pid 12412) is running... [root@mercury ~]# tail /var/log/maillog Oct 18 23:15:59 mercury postfix/master[7816]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling Oct 18 23:16:18 mercury dovecot: imap-login: Login: user=<sami37>, method=PLAIN, rip=::ffff:127.0.0.1, lip=::ffff:127.0.0.1, secured Oct 18 23:16:18 mercury dovecot: IMAP(sami37): Disconnected: Logged out Oct 18 23:16:59 mercury postfix/smtpd[12298]: fatal: open database /etc/aliases.db: No such file or directory
Sendmail is still the default on CentOS. So to switch to Postfix you will have to use the mechanism to relink - using alternatives.
What prints out: alternatives --display mta If that tells you that Sendmail is still the primary MTA, then run:
alternatives --config mta
and select Postfix. Then rerun "newaliases" or "postalias /etc/aliases".
Alexander
On Mon, Oct 18, 2010 at 23:31, Alexander Dalloz ad+lists@uni-x.org wrote:
Sendmail is still the default on CentOS. So to switch to Postfix you will have to use the mechanism to relink - using alternatives.
What prints out: alternatives --display mta
You found it!
[root@mercury ~]# alternatives --display mta mta - status is manual. link currently points to /usr/sbin/sendmail.exim /usr/sbin/sendmail.exim - priority 10 slave mta-pam: /etc/pam.d/exim slave mta-mailq: /usr/bin/mailq.exim slave mta-newaliases: /usr/bin/newaliases.exim slave mta-rmail: /usr/bin/rmail.exim slave mta-rsmtp: /usr/bin/rsmtp.exim slave mta-runq: /usr/bin/runq.exim slave mta-sendmail: /usr/lib/sendmail.exim slave mta-mailqman: /usr/share/man/man8/exim.8.gz slave mta-newaliasesman: (null) slave mta-aliasesman: (null) slave mta-sendmailman: (null) /usr/sbin/sendmail.postfix - priority 30 slave mta-pam: /etc/pam.d/smtp.postfix slave mta-mailq: /usr/bin/mailq.postfix slave mta-newaliases: /usr/bin/newaliases.postfix slave mta-rmail: /usr/bin/rmail.postfix slave mta-rsmtp: (null) slave mta-runq: (null) slave mta-sendmail: /usr/lib/sendmail.postfix slave mta-mailqman: /usr/share/man/man1/mailq.postfix.1.gz slave mta-newaliasesman: /usr/share/man/man1/newaliases.postfix.1.gz slave mta-aliasesman: /usr/share/man/man5/aliases.postfix.5.gz slave mta-sendmailman: /usr/share/man/man1/sendmail.postfix.1.gz Current `best' version is /usr/sbin/sendmail.postfix.
If that tells you that Sendmail is still the primary MTA, then run:
alternatives --config mta
and select Postfix. Then rerun "newaliases" or "postalias /etc/aliases".
Done! I then restarted postfix and there seem to be no new errors in the logs. However, I still cannot telnet into port 25:
✈dcl:~$ telnet sharingcenter.eu 25 Trying 178.63.65.188... Trying 178.63.65.136... telnet: Unable to connect to remote host: No route to host ✈dcl:~$ telnet mail.sharingcenter.eu 25 Trying 178.63.65.136... telnet: Unable to connect to remote host: Connection timed out ✈dcl:~$
On Mon, 18 Oct 2010, Dotan Cohen wrote:
Done! I then restarted postfix and there seem to be no new errors in the logs. However, I still cannot telnet into port 25:
✈dcl:~$ telnet mail.sharingcenter.eu 25 Trying 178.63.65.136... telnet: Unable to connect to remote host: Connection timed out ✈dcl:~$
It works here (where here is on another continent)
[herrold@stones herrold]$ telnet 178.63.65.136 25 Trying 178.63.65.136... Connected to 178.63.65.136. Escape character is '^]'. 220 mercury.localdomain ESMTP Postfix quit 221 2.0.0 Bye Connection closed by foreign host. [herrold@stones herrold]$
Something between your local setup and 178.63.65.136 is blocking you --
Solve that -- it is NOT a centos issue at this point
-- Russ herrold
[herrold@stones herrold]$ telnet 178.63.65.136 25 Trying 178.63.65.136... Connected to 178.63.65.136. Escape character is '^]'. 220 mercury.localdomain ESMTP Postfix quit 221 2.0.0 Bye Connection closed by foreign host. [herrold@stones herrold]$
Something between your local setup and 178.63.65.136 is blocking you --
Solve that -- it is NOT a centos issue at this point
-- Russ herrold _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
In fact Russ was here before me.... as he says, it is likely a connectivity issue... not a mail issue.
On 10/18/10 2:22 PM, Dotan Cohen wrote:
On Mon, Oct 18, 2010 at 23:15, Scott Robbinsscottro@nyc.rr.com wrote:
Well, see if you have an /etc/aliases, which you should, even if it's a defaut. Then just run newaliases which will create an /etc/aliases.db
The issues may be elsewhere, but get rid of that one.
Well, I tried:
[root@mercury ~]# ls -l /etc/aliases -rw-r--r-- 1 root root 1512 Apr 25 2005 /etc/aliases [root@mercury ~]# newaliases [root@mercury ~]# service postfix restart Shutting down postfix: [ OK ] Starting postfix: [ OK ] [root@mercury ~]# service postfix status master (pid 12412) is running... [root@mercury ~]# tail /var/log/maillog Oct 18 23:15:59 mercury postfix/master[7816]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling Oct 18 23:16:18 mercury dovecot: imap-login: Login: user=<sami37>, method=PLAIN, rip=::ffff:127.0.0.1, lip=::ffff:127.0.0.1, secured Oct 18 23:16:18 mercury dovecot: IMAP(sami37): Disconnected: Logged out Oct 18 23:16:59 mercury postfix/smtpd[12298]: fatal: open database /etc/aliases.db: No such file or directory Oct 18 23:17:00 mercury postfix/master[7816]: warning: process /usr/libexec/postfix/smtpd pid 12298 exit status 1 Oct 18 23:17:00 mercury postfix/master[7816]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling Oct 18 23:17:49 mercury postfix/postfix-script: stopping the Postfix mail system Oct 18 23:17:49 mercury postfix/master[7816]: terminating on signal 15 Oct 18 23:17:49 mercury postfix/postfix-script: starting the Postfix mail system Oct 18 23:17:49 mercury postfix/master[12412]: daemon started -- version 2.3.3, configuration /etc/postfix [root@mercury ~]#
But it still won't connect:
no kidding. look at that log, it didn't start. (last 3 lines notwithstanding, every else there looks like 'error' to me)
On Mon, Oct 18, 2010 at 23:46, John R Pierce pierce@hogranch.com wrote:
no kidding. look at that log, it didn't start. (last 3 lines notwithstanding, every else there looks like 'error' to me)
Yes, those error were before I removed sendmail from the default config.
Even though it seems to be answering on post 25 now, mail sent to an account there from Gmail are not being received. No errors in the logs.
Yes, those error were before I removed sendmail from the default config.
Even though it seems to be answering on post 25 now, mail sent to an account there from Gmail are not being received. No errors in the logs.
-- Dotan Cohen
stupid's question: what happens if you disable selinux?
Seeing how postfix could not access /etc/aliases I tried loosening the permissions, but still no luck:
[root@mercury ~]# chmod +rx /etc/aliases [root@mercury ~]# newaliases [root@mercury ~]# ls -l /etc/aliases -rwxr-xr-x 1 root root 1512 Apr 25 2005 /etc/aliases [root@mercury ~]# service postfix status master (pid 12412) is running... [root@mercury ~]# service postfix restart Shutting down postfix: [ OK ] Starting postfix: [ OK ] [root@mercury ~]# tail /var/log/maillog Oct 18 23:29:02 mercury postfix/master[12412]: warning: process /usr/libexec/postfix/smtpd pid 12987 exit status 1 Oct 18 23:29:02 mercury postfix/master[12412]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling Oct 18 23:29:17 mercury postfix/postalias[13000]: fatal: usage: postalias [-Nfinoprsvw] [-c config_dir] [-d key] [-q key] [map_type:]file... Oct 18 23:29:52 mercury postfix/postfix-script: stopping the Postfix mail system Oct 18 23:29:52 mercury postfix/master[12412]: terminating on signal 15 Oct 18 23:29:52 mercury postfix/postfix-script: starting the Postfix mail system Oct 18 23:29:52 mercury postfix/master[13090]: daemon started -- version 2.3.3, configuration /etc/postfix Oct 18 23:30:00 mercury postfix/smtpd[13106]: fatal: open database /etc/aliases.db: No such file or directory Oct 18 23:30:01 mercury postfix/master[13090]: warning: process /usr/libexec/postfix/smtpd pid 13106 exit status 1 Oct 18 23:30:01 mercury postfix/master[13090]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling [root@mercury ~]# date Mon Oct 18 23:30:08 CEST 2010 [root@mercury ~]#
Am 18.10.2010 23:31, schrieb Dotan Cohen:
Seeing how postfix could not access /etc/aliases I tried loosening the permissions, but still no luck:
[root@mercury ~]# chmod +rx /etc/aliases
It is *NOT* the /etc/aliases plain text file Postfix tries to read in at startup. It is the hashed map /etc/aliases.db!
And it is sufficient if root can read/write both files.
Alexander
On Mon, Oct 18, 2010 at 22:59, Alexander Dalloz ad+lists@uni-x.org wrote:
By any chance, did you bring down loopback or destroyed the localhost mapping in /etc/hosts? Or you have something broken in your main.cf. Post the output of "postconf -n".
No, loopback works and there's nothing unusual about /etc/hosts.
-
Alexander Dalloz -
Ben McGinnes -
cornel panceac -
Dotan Cohen -
Ian Murray -
John R Pierce -
JohnS -
Les Mikesell -
m.roth＠5-cent.us -
R P Herrold -
Scott Robbins -
Todd Denniston