Your email server cannot accept email
opened this issue · comments
Hi @t3chguy,
I cannot send email to your mailbox (postmaster@). i have no other way to notice you, so forgive me if this issue makes you feel annoying.
Delivery to the following recipient has been delayed:
postmaster@[your_domain]
Message will be retried for 2 more day(s)
Technical details of temporary failure:
read error: generic::failed_precondition: read error (0): error
Oh wow, thanks for notifying me, my mail server permissions are screwed up and I've no idea how to fix them xD
Right, somehow my /etc/postfix had gotten the group of www-data, weirdly no idea how, all I've done is set GID Bit on my /var/www/, maybe that's somehow delegated onto it, idk. Hoping its up now
Is it iRedMail?
Yeah its iRedMail
I compared it against my backup/testing server and found the permissions discrepancy
Just saw your email successfully arrive at my box, only to get rejected by Greylisting xD I'll see that e-mail when it gets re-delivered
great. let's close this issue now.
Alright, well my e-mail is yet more broken
What's the problem? Maybe i can help (via ssh) if you want.
Mar 2 05:52:30 raven postfix/smtpd[13845]: NOQUEUE: reject: RCPT from unknown[209.85.220.48]: 450 4.1.8 zhb@iredmail.org: Sender address rejected: Domain not found; from=zhb@iredmail.org to=postmaster@webdevguru.co.uk proto=ESMTP helo=<mail-pa0-f48.google.com>
Mar 2 05:52:30 raven postfix/smtpd[13845]: disconnect from unknown[209.85.220.48]
Check /var/spool/postfix/etc/resolv.conf. make sure you have correct DNS server.
Mar 2 05:50:45 raven postfix/smtpd[13628]: dict_proxy_lookup: table=mysql:/etc/postfix/mysql/virtual_alias_maps.cf flags=lock|fold_fix key=postmaster@webdevguru.co.uk -> status=0 result=postmaster@webdevguru.co.uk
Mar 2 05:50:45 raven postfix/smtpd[13628]: maps_find: virtual_alias_maps: proxy:mysql:/etc/postfix/mysql/virtual_alias_maps.cf(0,lock|fold_fix): postmaster@webdevguru.co.uk = postmaster@webdevguru.co.uk
the lookup seems successful though
give me a second to add your SSH Key
resolv.conf is set to Google DNS 8.8.8.8 and 8.8.4.4
my ssh public key:
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDWD2oZef2kq2CPq/TYuuAeualfL/AH6EW2n2Tzf5DsC8V5OmZAr4S7pdBH4D33T0gFrLq/woin6KXIdoiLF/dwQcPYYUA5wToRxz9cGG5U8TezkSDogjYyhqVQuDnSiiT/RF0uIytuX5e8XkfZS2TLQJTgt0Af23rPEm0TY/zd6XCNx/osdRAP25Sw3lztWkXH9wNs58ncRQjirBx853dI5qycMzBhcWBpUQAc9Yul1dyKG6SpLPbgz2wyufbDOdZOr9lZPa0MdbuTGZ8Ge3c90BQQlRNzZSBmbfeTbFHQacV+kDOvEX10PpRJE9PXnQnwk6HNs2lxsbbPzqaLnNs7 zhb@laptop
cannot login. i get error Permission denied (publickey).
Could you please try once more, no idea why it'd not let you in as I've added your public key
Probably due to the same error, I'm also unable to send mail
You added my public key in ~/.ssh/authorized_keys, right? detailed debug message:
$ ls -l ~/.ssh/
-rw------- 1 zhb staff 1679 Sep 10 2012 id_rsa
-rw-r--r-- 1 zhb staff 398 Oct 11 09:05 id_rsa.pub
$ ssh -vvv root@...
...
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /Users/zhb/.ssh/id_rsa
debug3: send_pubkey_test
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey
debug1: Trying private key: /Users/zhb/.ssh/id_dsa
debug3: no such identity: /Users/zhb/.ssh/id_dsa: No such file or directory
debug2: we did not send a packet, disable method
debug1: No more authentication methods to try.
Permission denied (publickey).
root@raven:~# cat ~/.ssh/authorized_keys
ssh-rsa ...
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDWD2oZef2kq2CPq/TYuuAeualfL/AH6EW2n2Tzf5DsC8V5OmZAr4S7pdBH4D33T0gFrLq/woin6KXIdoiLF/dwQcPYYUA5wToRxz9cGG5U8TezkSDogjYyhqVQuDnSiiT/RF0uIytuX5e8XkfZS2TLQJTgt0Af23rPEm0TY/zd6XCNx/osdRAP25Sw3lztWkXH9wNs58ncRQjirBx853dI5qycMzBhcWBpUQAc9Yul1dyKG6SpLPbgz2wyufbDOdZOr9lZPa0MdbuTGZ8Ge3c90BQQlRNzZSBmbfeTbFHQacV+kDOvEX10PpRJE9PXnQnwk6HNs2lxsbbPzqaLnNs7 zhb@laptop
Any error in /var/log/secure (or other log file which contains ssh log)?
My /var/log/auth.log is completely empty, which looks like an issue in itself for which I cannot find a fix
Logging is enabled though, weirdly
Try to restart syslog service syslog (or rsyslog), then restart ssh servivce and notify me to try again.
Found the logging issue to be syslog-ng and rsyslog being installed at the same time, broken image from my vendor. I have many logging issues now, but at least auth.log is working. Could you try again
Mar 2 06:37:14 raven sshd[589]: debug1: Forked child 2358.
Mar 2 06:37:14 raven sshd[2358]: Set /proc/self/oom_score_adj to -800
Mar 2 06:37:14 raven sshd[2358]: debug1: rexec start in 5 out 5 newsock 5 pipe 7 sock 8
Mar 2 06:37:14 raven sshd[2358]: debug1: inetd sockets after dupping: 3, 3
Mar 2 06:37:14 raven sshd[2358]: Connection from 211.91.225.180 port 52162 on 31.187.70.196 port 22
Mar 2 06:37:14 raven sshd[2358]: debug1: Client protocol version 2.0; client software version OpenSSH_6.2
Mar 2 06:37:14 raven sshd[2358]: debug1: match: OpenSSH_6.2 pat OpenSSH* compat 0x04000000
Mar 2 06:37:14 raven sshd[2358]: debug1: Enabling compatibility mode for protocol 2.0
Mar 2 06:37:14 raven sshd[2358]: debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2
Mar 2 06:37:14 raven sshd[2358]: debug1: permanently_set_uid: 109/65534 [preauth]
Mar 2 06:37:14 raven sshd[2358]: debug1: list_hostkey_types: ssh-rsa,ssh-dss,ecdsa-sha2-nistp256,ssh-ed25519 [preauth]
Mar 2 06:37:14 raven sshd[2358]: debug1: SSH2_MSG_KEXINIT sent [preauth]
Mar 2 06:37:14 raven sshd[676]: debug1: server_input_channel_req: channel 0 request winadj@putty.projects.tartarus.org reply 1
Mar 2 06:37:14 raven sshd[676]: debug1: session_by_channel: session 0 channel 0
Mar 2 06:37:14 raven sshd[676]: debug1: session_input_channel_req: session 0 req winadj@putty.projects.tartarus.org
Mar 2 06:37:15 raven sshd[2358]: debug1: SSH2_MSG_KEXINIT received [preauth]
Mar 2 06:37:15 raven sshd[2358]: debug1: kex: client->server aes128-ctr hmac-md5-etm@openssh.com none [preauth]
Mar 2 06:37:15 raven sshd[2358]: debug1: kex: server->client aes128-ctr hmac-md5-etm@openssh.com none [preauth]
Mar 2 06:37:15 raven sshd[2358]: debug1: SSH2_MSG_KEX_DH_GEX_REQUEST received [preauth]
Mar 2 06:37:15 raven sshd[2358]: debug1: SSH2_MSG_KEX_DH_GEX_GROUP sent [preauth]
Mar 2 06:37:15 raven sshd[2358]: debug1: expecting SSH2_MSG_KEX_DH_GEX_INIT [preauth]
Mar 2 06:37:16 raven sshd[2358]: debug1: SSH2_MSG_KEX_DH_GEX_REPLY sent [preauth]
Mar 2 06:37:16 raven sshd[2358]: debug1: SSH2_MSG_NEWKEYS sent [preauth]
Mar 2 06:37:16 raven sshd[2358]: debug1: expecting SSH2_MSG_NEWKEYS [preauth]
Mar 2 06:37:16 raven sshd[2358]: debug1: SSH2_MSG_NEWKEYS received [preauth]
Mar 2 06:37:16 raven sshd[2358]: debug1: KEX done [preauth]
Mar 2 06:37:17 raven sshd[2358]: debug1: userauth-request for user root@root service ssh-connection method none [preauth]
Mar 2 06:37:17 raven sshd[2358]: debug1: attempt 0 failures 0 [preauth]
Mar 2 06:37:26 raven sshd[2358]: debug1: Can't match group at line 92 because user root@root does not exist
Mar 2 06:37:26 raven sshd[2358]: Invalid user root@root from 211.91.225.180
Mar 2 06:37:26 raven sshd[2358]: input_userauth_request: invalid user root@root [preauth]
Mar 2 06:37:26 raven sshd[2358]: debug1: PAM: initializing for "root@root"
Mar 2 06:37:26 raven sshd[2358]: debug1: PAM: setting PAM_RHOST to "211.91.225.180"
Mar 2 06:37:26 raven sshd[2358]: debug1: PAM: setting PAM_TTY to "ssh"
Mar 2 06:37:26 raven sshd[2358]: debug1: userauth-request for user root@root service ssh-connection method publickey [preauth]
Mar 2 06:37:26 raven sshd[2358]: debug1: attempt 1 failures 0 [preauth]
Mar 2 06:37:27 raven sshd[2358]: Connection closed by 211.91.225.180 [preauth]
Mar 2 06:37:27 raven sshd[2358]: debug1: do_cleanup [preauth]
Mar 2 06:37:27 raven sshd[2358]: debug1: do_cleanup
Mar 2 06:37:27 raven sshd[2358]: debug1: PAM: cleanup
Mar 2 06:37:27 raven sshd[2358]: debug1: Killing privsep child 2359
er, my mistake, duplicate root@ in ssh command. I can login now.
Alright, for sending the issue looks like:
Mar 2 06:41:08 raven postfix/qmgr[2051]: 7DA787080EE2: from=<postmaster@webdevguru.co.uk>, size=2932, nrcpt=1 (queue active)
2015 Mar 2 06:41:08 raven fatal: unknown service: smtp/tcp
Mar 2 06:41:08 raven postfix/smtp[2503]: fatal: unknown service: smtp/tcp
Mar 2 06:41:09 raven postfix/qmgr[2051]: warning: private/smtp socket: malformed response
Mar 2 06:41:09 raven postfix/master[2037]: warning: process /usr/lib/postfix/smtp pid 2503 exit status 1
Mar 2 06:41:09 raven postfix/master[2037]: warning: /usr/lib/postfix/smtp: bad command startup -- throttling
Mar 2 06:41:09 raven postfix/qmgr[2051]: warning: transport smtp failure -- see a previous warning/fatal/panic logfile record for the problem description
Mar 2 06:41:09 raven postfix/error[2506]: 7DA787080EE2: to=<Helen@greensenvironmental.com>, relay=none, delay=4165, delays=4164/1/0/0.01, dsn=4.3.0, status=deferred (unknown mail transport error)
Have you found anything?
No yet. Copy /etc/resolv.conf, /etc/services to /var/spool/postfix/etc/ doesn't fix this issue. Stilling trying.
Thank you very much for doing this
I just got a fatal error a bunch of times:
root@raven:~# 2015 Mar 2 07:18:23 raven fatal: unknown service: smtp/tcp
2015 Mar 2 07:18:23 raven fatal: unknown service: smtp/tcp
2015 Mar 2 07:18:23 raven fatal: unknown service: smtp/tcp
2015 Mar 2 07:18:23 raven fatal: unknown service: smtp/tcp
2015 Mar 2 07:18:23 raven fatal: unknown service: smtp/tcp
2015 Mar 2 07:18:33 raven fatal: unknown service: smtp/tcp
All my pending e-mails to be received just came through [from one sender]
Did you try to restart server?
Sending still isn't working, what did you do to fix the receiving if you don't mind me asking?
I restarted it 3 times while fixing the Logging issue
I made Postfix run under unchroot.
is that necessary? If all else fails I'll just rebuild the server tonight
What makes me confused is, everyone fixed this issue by copying /etc/services to /var/spool/postfix/etc/, but it doesn't work on your server.
I have no idea yet. Still digging.
As per e-mail, I've created a new release, v3 is the initial version to be supported for PgSQL as well as MySQL
OK. will promote this stable release soon.
By the way, still cannot figure out what the problem is on your server. Clueless...
Alright, I'll spin up a new VPS and migrate everything over tonight, thanks for your help anyway, also thanks for promoting this project!
I fixed the sending issue by unchrooting the other SMTP call
