Melvyn Sopacua wrote:
On Saturday 31 January 2009 08:03:17 Wietse Venema wrote:
Melvyn Sopacua:
The problem is that postfix will see "success" initially:
- client sends
- postfix receives
- postfix relays, gets OK
----> postfix deletes queued message
- exchange checks quota, decides mailbox is full
- exchange sends DSN to client
Use reject_unverified_recipient, with a persistent database. This
will check the Exchange response BEFORE accepting mail, and will
avoid hammering the Exchange server with repeated requests.
http://www.postfix.org/ADDRESS_VERIFICATION_README.html
VRFY i...@example.com
252 2.1.5 Cannot VRFY user, but will take message for <i...@example.com>
yet, mailbox is full and DSN will come few seconds after mail is accepted.
Judging from the 2xx response, this means to postfix that VRFY succeeded, so
the problem persists.
This is a classic example of trying to fix a people problem using
technology. Exchange is broken. It is accepting then losing messages
that it can't deliver. You are not the exchange admin, so you can't fix it.
The next time someone complains, show them the postfix log entry where
Exchange accepted the message from Postfix, then suggest they go talk to
the Exchange admin.
If you persist in trying to fix Exchange from the outside, you will have
accepted responsibility (and later, blame) for a problem that you can't
fix and in the end, you'll be in trouble or fired and the Exchange admin
will claim no responsibility or knowledge of the situation.
Terry
