I believe you re mixing together two problems here, those are quite unrelated really.
First problem - making sure that the email was accepted by the corporate mail server (that is mail relay in this case). To solve this you can either build a local queue of messages (store them in the database, queue server, whatever) - and send them with a separate worker process, that will pull each message from a queue, try to deliver it and delete it only if it was accepted by the mail relay.
Or, if you don t need low-level manual control of the process, you can set up a simple local mail server on your machine and instead if sending emails directly to your corporate mail relay, just give them to your local mail server. It will then make sure that the emails were delivered to the corporate properly.
But in both cases you won t get any info about where the message was delivered to the final recipient - like whether the email address was valid, user s mailbox was not full, etc.
Second problem - track mail delivery errors. To properly and completely solve this problem you need to catch all mail bounced back to you from the remote servers and analyze it, as many errors are unknown at the moment when the email is send - but they come back later in the form of mail bounces. If you catch and track these bounces you ll be able to catch errors likefull mailboxes, invalid emails, just temporarily delivery failures, etc.
It s the way it is done in mail lists management software - for example, phpList operates in exactly the same way.