<div class="gmail_quote"><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div><div class="h5">
</div></div>You can simply setup a pop box that the returns would be sent to, then<br>
with php read the mailbox and parse the messages.<br>
<br>
<a href="http://framework.zend.com/manual/en/zend.mail.read.html" target="_blank">http://framework.zend.com/manual/en/zend.mail.read.html</a><br>
<br>
Other option would be to pipe the mails into a php script at the mail<br>
server, this is more complicated, pop is much easier....<br>
<br></blockquote><div><br></div><div>If it's your server that the mail is going to, it's actually not that complicated to setup, and doesn't require polling of the pop mailbox. For exim, you can just set the "command" option in the transport, if you've got a separate domain for your replies. Otherwise I think it's just a .forward to |your_command_here. I've done it a while ago for a single address, and it was pretty easy.</div>
<div><br></div><div>Reading through a pop box could have some interesting side effects - a) you're going to need a lock on the polling action, b) you're going to have to cope with crashing mid-poll. i.e. if the remote end hangs up on you, have you deleted the messages you've processed etc. </div>
<div><br></div><div>You can avoid those sorts of problems having the mail go directly to your script. - If the worst happens and your code crashes mid-receive (less likely as you're not reliant on an external connection), you've only lost/screwed that one message.</div>
<div><br></div><div>There may be other ways to do it too that maybe others will know.</div><div><br></div><div>Cheers,</div><div>Dave.</div></div>