I am currently messing about with a virtual private server at Rimu Hosting, with a view to have it take over my e-mail serving after Vodafone turns off its provision of that service. Eventually I will have an MX record for my domain pointing at that server, so it will receive all e-mail addressed to me. Next part is, I want to periodically suck all that mail back to my main office machine. Currently I have a cron task that periodically connects to Vodafone’s POP server, fetches all the mail, and delivers it locally. When I try to do the same thing with the VPS, my local Postfix bounces the attempt at local delivery, saying something like <user(a)domain> (expanded from <user>): mail forwarding loop for user(a)domain A bit of hunting around online found this <http://postfix.1071664.n5.nabble.com/What-is-causing-this-mail-forwarding-loop-bounce-td62199.html> likely discussion, where the problem seems to be that the incoming message already has a “Delivered-To:” header pointing at my e-mail address, so Postfix concludes that the message is stuck in a forwarding loop, and refuses to pass it on. The exchange ends with this response from Wietse Venema, “Mr Postfix” himself: You can use header_checks to remove the problem header, but I will not help with implementing such iodiocy. Hmm, looking at the local(8) man page, it says In order to stop mail forwarding loops early, the software adds an optional Delivered-To: header with the final envelope recipient address. If mail arrives for a recipient that is already listed in a Delivered-To: header, the message is bounced. The key being that word “optional”. So it looks like I simply have to disable the addition of “Delivered-To:” on the VPS. Stay tuned.