ispCP - Board - Support
Problems recieving emails - Printable Version

+- ispCP - Board - Support (http://www.isp-control.net/forum)
+-- Forum: ispCP Omega Support Area (/forum-30.html)
+--- Forum: Usage (/forum-34.html)
+--- Thread: Problems recieving emails (/thread-7536.html)

Pages: 1 2


Problems recieving emails - Krisxxx - 08-18-2009 07:04 AM

Hi
I just migrated my Debian Lenny system with ispCP 1.0.0 OMEGA
build: 20090225 this weekend and everything seemed to work fine at first, but now i cant recieve emails. System mails seems to get ok out, but not when im sending to the system from ex. hotmail.
What could be the problem?

Greets
Kris


RE: Problems recieving emails - rbtux - 08-18-2009 07:08 AM

reverse dns?, dns?, servername?

my crystal ball does not work that well ;-))


RE: Problems recieving emails - theprincy - 08-18-2009 07:15 AM

(08-18-2009 07:08 AM)rbtux Wrote:  my crystal ball does not work that well ;-))

Big GrinBig GrinBig GrinBig Grin

I see that is a phrase we use in many


RE: Problems recieving emails - Krisxxx - 08-18-2009 01:40 PM

(08-18-2009 07:08 AM)rbtux Wrote:  reverse dns?, dns?, servername?

my crystal ball does not work that well ;-))

Smile Sorry

dns and servername should be ok, im not sure about the reverse dns...

This is the error i get in my mail error log:

Aug 17 23:12:55 smedeweb postgrey[2442]: FATAL: ERROR: can't create database /var/lib/postgrey/postgrey.db: No such file or directory#012

And this is a bit from the mail log:

Aug 18 05:35:30 smedeweb postfix/policyd-weight[3133]: decided action=PREPEND X-policyd-weight: using cached result; rate: -8.5; <client=94.145.140.169> <helo=remote.esby-it.dk> <from=kd@esby-it.dk> <to=kd@esby.eu>; delay: 0s
Aug 18 05:35:30 smedeweb postfix/smtpd[19100]: warning: connect to 127.0.0.1:60000: Connection refused
Aug 18 05:35:30 smedeweb postfix/smtpd[19100]: warning: problem talking to server 127.0.0.1:60000: Connection refused
Aug 18 05:35:31 smedeweb postfix/smtpd[19100]: warning: connect to 127.0.0.1:60000: Connection refused
Aug 18 05:35:31 smedeweb postfix/smtpd[19100]: warning: problem talking to server 127.0.0.1:60000: Connection refused
Aug 18 05:35:31 smedeweb postfix/smtpd[19100]: NOQUEUE: reject: RCPT from unknown[94.145.140.169]: 451 4.3.5 Server configuration problem; from=<kd@esby-it.dk> to=<kd@esby.eu> proto=ESMTP helo=<remote.esby-it.dk>
Aug 18 05:35:31 smedeweb postfix/smtpd[19100]: disconnect from unknown[94.145.140.169]
Aug 18 05:36:36 smedeweb postfix/smtpd[19100]: connect from unknown[94.145.140.169]
Aug 18 05:36:36 smedeweb postfix/policyd-weight[3133]: decided action=PREPEND X-policyd-weight: using cached result; rate: -8.5; <client=94.145.140.169> <helo=remote.esby-it.dk> <from=kd@esby-it.dk> <to=kd@esby.eu>; delay: 0s
Aug 18 05:36:36 smedeweb postfix/smtpd[19100]: warning: connect to 127.0.0.1:60000: Connection refused
Aug 18 05:36:36 smedeweb postfix/smtpd[19100]: warning: problem talking to server 127.0.0.1:60000: Connection refused
Aug 18 05:36:37 smedeweb postfix/smtpd[19100]: warning: connect to 127.0.0.1:60000: Connection refused
Aug 18 05:36:37 smedeweb postfix/smtpd[19100]: warning: problem talking to server 127.0.0.1:60000: Connection refused
Aug 18 05:36:37 smedeweb postfix/smtpd[19100]: NOQUEUE: reject: RCPT from unknown[94.145.140.169]: 451 4.3.5 Server configuration problem; from=<kd@esby-it.dk> to=<kd@esby.eu> proto=ESMTP helo=<remote.esby-it.dk>
Aug 18 05:36:37 smedeweb postfix/smtpd[19100]: disconnect from unknown[94.145.140.169]
Aug 18 05:36:40 smedeweb pop3d: Connection, ip=[::ffff:87.56.243.98]
Aug 18 05:36:40 smedeweb pop3d: LOGIN, user=tusse@helgenaes.com, ip=[::ffff:87.56.243.98], port=[64835]
Aug 18 05:36:40 smedeweb pop3d: LOGOUT, user=tusse@helgenaes.com, ip=[::ffff:87.56.243.98], port=[64835], top=0, retr=0, rcvd=12, sent=39, time=0
Aug 18 05:37:26 smedeweb postfix/smtpd[19100]: connect from unknown[195.215.1.153]
Aug 18 05:37:29 smedeweb postfix/policyd-weight[3133]: weighted check: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 NOT_IN_SPAMCOP=-1.5 NOT_IN_BL_NJABL=-1.5 HELO_IP_IN_CL_SUBNET=-1.2 (check from: .bilbasen. - helo: .bilbweb01.bilbasen. - helo-domain: .bilbasen.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; <client=195.215.1.153> <helo=bilbweb01.bilbasen.local> <from=info@bilbasen.dk> <to=tusse@helgenaes.com>; rate: -7.7
Aug 18 05:37:29 smedeweb postfix/policyd-weight[3133]: decided action=PREPEND X-policyd-weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 NOT_IN_SPAMCOP=-1.5 NOT_IN_BL_NJABL=-1.5 HELO_IP_IN_CL_SUBNET=-1.2 (check from: .bilbasen. - helo: .bilbweb01.bilbasen. - helo-domain: .bilbasen.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -7.7; <client=195.215.1.153> <helo=bilbweb01.bilbasen.local> <from=info@bilbasen.dk> <to=tusse@helgenaes.com>; delay: 3s
Aug 18 05:37:29 smedeweb postfix/smtpd[19100]: warning: connect to 127.0.0.1:60000: Connection refused
Aug 18 05:37:29 smedeweb postfix/smtpd[19100]: warning: problem talking to server 127.0.0.1:60000: Connection refused
Aug 18 05:37:30 smedeweb postfix/smtpd[19100]: warning: connect to 127.0.0.1:60000: Connection refused
Aug 18 05:37:30 smedeweb postfix/smtpd[19100]: warning: problem talking to server 127.0.0.1:60000: Connection refused
Aug 18 05:37:30 smedeweb postfix/smtpd[19100]: NOQUEUE: reject: RCPT from unknown[195.215.1.153]: 451 4.3.5 Server configuration problem; from=<info@bilbasen.dk> to=<tusse@helgenaes.com> proto=ESMTP helo=<bilbweb01.bilbasen.local>
Aug 18 05:37:30 smedeweb postfix/smtpd[19100]: lost connection after RSET from unknown[195.215.1.153]
Aug 18 05:37:30 smedeweb postfix/smtpd[19100]: disconnect from unknown[195.215.1.153]
Aug 18 05:37:30 smedeweb postfix/smtpd[19100]: connect from unknown[212.242.40.53]
Aug 18 05:37:31 smedeweb postfix/policyd-weight[3133]: weighted check: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 NOT_IN_SPAMCOP=-1.5 NOT_IN_BL_NJABL=-1.5 CL_IP_NE_HELO=1.5 RESOLVED_IP_IS_NOT_HELO=1.5 (check from: .bilbasen. - helo: .cicero2.cybercity. - helo-domain: .cybercity.) FROM_NOT_FAILED_HELO(DOMAIN)=3; <client=212.242.40.53> <helo=cicero2.cybercity.dk> <from=info@bilbasen.dk> <to=tusse@helgenaes.com>; rate: 1.5
Aug 18 05:37:31 smedeweb postfix/policyd-weight[3133]: decided action=550 Mail appeared to be SPAM or forged. Ask your Mail/DNS-Administrator to correct HELO and DNS MX settings or to get removed from DNSBLs; MTA helo: cicero2.cybercity.dk, MTA hostname: unknown[212.242.40.53] (helo/hostname mismatch); <client=212.242.40.53> <helo=cicero2.cybercity.dk> <from=info@bilbasen.dk> <to=tusse@helgenaes.com>; delay: 1s
Aug 18 05:37:31 smedeweb postfix/smtpd[19100]: NOQUEUE: reject: RCPT from unknown[212.242.40.53]: 550 5.7.1 <tusse@helgenaes.com>: Recipient address rejected: Mail appeared to be SPAM or forged. Ask your Mail/DNS-Administrator to correct HELO and DNS MX settings or to get removed from DNSBLs; MTA helo: cicero2.cybercity.dk, MTA hostname: unknown[212.242.40.53] (helo/hostname mismatch); from=<info@bilbasen.dk> to=<tusse@helgenaes.com> proto=ESMTP helo=<cicero2.cybercity.dk>
Aug 18 05:37:31 smedeweb postfix/smtpd[19100]: disconnect from unknown[212.242.40.53]


Hope this helps or do you want to see something else?


RE: Problems recieving emails - kilburn - 08-18-2009 04:15 PM

The error here is quite self-explanatory: either you are missing the /var/lib/postgrey folder or it has wrong permissions. Create the folder and/or chown it to the postgrey user, then restart postgrey and everything should be fine (... or finer than now at least).


RE: Problems recieving emails - Krisxxx - 08-19-2009 12:33 AM

Checked the chown and the folders were in place, but it still can't create database /var/lib/postgrey/postgrey.db, what can be wrong? What im also worried about is thos line in the log:
Aug 18 05:37:30 smedeweb postfix/smtpd[19100]: warning: connect to 127.0.0.1:60000: Connection refused


RE: Problems recieving emails - kilburn - 08-19-2009 01:22 AM

Quote:Checked the chown and the folders were in place, but it still can't create database /var/lib/postgrey/postgrey.db, what can be wrong?

My crystal ball isn't working too well either. There must be some silly mistake on the path/permissions of the postgrey db. Check again, or copy us the output of:

1. ls showing the permissions of /var/lib/postgrey folder
2. Output of manually creating a the /var/lib/postgrey/postgrey.db file when logged in as postgrey (use su/sudo)
3. ....?

Quote:What im also worried about is thos line in the log:
Aug 18 05:37:30 smedeweb postfix/smtpd[19100]: warning: connect to 127.0.0.1:60000: Connection refused
Guess what? 127.0.0.1:60000 is postgrey, which failed to start because it cannot create it's needed database.


RE: Problems recieving emails - Krisxxx - 08-19-2009 01:51 AM

Im pretty new at these things, so how can i easily show you the permissions of the /var/lib/postgrey folder and how do i copy output of manually creating a the /var/lib/postgrey/postgrey.db file when logged in as postgrey (use su/sudo). I have now migrated 3 ispcp servers and never run into these problems before :-(
This is the output of the permissions:

smedeweb:~# ls -al /var/lib/postgrey
totalt 10560
drwxrwxrwx 2 postgrey postgrey 4096 18 aug 18:16 .
drwxr-xr-x 47 root root 4096 17 maj 11:53 ..
-rw------- 1 postgrey postgrey 24576 18 aug 18:12 __db.001
-rw------- 1 postgrey postgrey 163840 18 aug 18:12 __db.002
-rw------- 1 postgrey postgrey 270336 18 aug 18:12 __db.003
-rw------- 1 postgrey postgrey 98304 18 aug 18:12 __db.004
-rw------- 1 postgrey postgrey 49152 18 aug 18:12 __db.005
-rw------- 1 postgrey postgrey 10485760 18 aug 18:12 log.0000000001
-rw------- 1 postgrey postgrey 16384 14 aug 15:52 postgrey_clients.db
-rw------- 1 postgrey postgrey 53248 14 aug 15:52 postgrey.db
-rw------- 1 postgrey postgrey 0 17 maj 11:53 postgrey.loc

Whats the name of the config file where i find the path?


RE: Problems recieving emails - Krisxxx - 08-19-2009 03:05 AM

Im going out of my mind here. Could someone please tell me how to configure the path or if the permissions are no good? Or if there is another problem.....


RE: Problems recieving emails - kilburn - 08-19-2009 03:15 AM

Something really weird is happening with this directory/file. If you are in a hurry I can try to find the cause if you give me access through SSH. Otherwise, I would first try to backup these files, remove them and let postgrey try to re-create them.