So then we started getting these messages in our logs:
@400000003f69830f2c2df1b4 info msg 47: bytes 1153 from <*************> qp 70866 uid 0
@400000003f69830f2ca1d1c4 starting delivery 60: msg 47 to local *******************
@400000003f69830f2cae02dc status: local 1/10 remote 0/20
@400000003f69830f34a902ac delivery 60: success: did_0+0+1/
@400000003f69830f34c072ac status: local 0/10 remote 0/20
@400000003f69830f34c0a18c end msg 47
This was basically allready better than having it fail to call vdelivermail, but this is still wrong, as an entry should look like this:
@400000003f69850e2b908cbc info msg 94300: bytes 5286 from <******************> qp 41793 uid 0
@400000003f69850e2bb94684 starting delivery 4877: msg 94300 to local ******************************
@400000003f69850e2bbf0efc status: local 1/10 remote 0/20
@400000003f69850e2c7fcebc delivery 4877: success: address:_/usr/local/vpopmail/domains/********/*********/Maildir//quota:_104857600/did_0+0+1/
@400000003f69850e2c91c07c status: local 0/10 remote 0/20
@400000003f69850e2c91d7ec end msg 94300
But like i said it was an improvement.
Are the messages being delivered? Different log output notwithstanding, you haven't said whether the changes you made fixed the root problem of message non-delivery.
Paul Theodoropoulos http://www.anastrophe.com
Paul Theodoropoulos http://www.anastrophe.com
