podcast feed gone.

Your episodes contain music from songs which are for sale on iTunes or otherwise issued commercially. This is a violation of copyright and is the most likely reason your podcast has been removed.

I also noticed that your mp3 file for the latest episode is being served as a streamed file - though this downloads OK when subscribing I don't know how well the Store would have coped with this: if it was causing problems in the Store that could also get you removed. The file should be served as an MP3 file directly - the test is that when you enter the URL in the address bar in Safari it plays in Safari, showing the duration, and you can move to a later point in the recording. At present it says 'live broadcast' and you can't navigate within it. It may have been that it played in the Store but you couldn't move to a later point there.

You will have to re submit it as an entirely new process, and you will have to change the title slightly or you will be told it has already been submitted. You will of course need to remove the copyright material or you will simply get rejected again: and it would be worth sorting out the server issue.

Basically, I would assume someone happened to notice it. They would probably say that you should have read the terms of use, which specifically forbid the use of uncleared copyright material. I've added a couple of notes to my previous post.

They will all be the same - it's just that I only checked the latest episode. I've just checked an earlier one with the same result.

If I remember correctly, someone else had the same situation a bit back, and the result was that though the Store page would play the episodes, it wasn't possible to move forward in them as it should be. It's OK when subscribing because the entire episode is downloaded before you can play it anyway.

All this may not matter to you, and I doubt it has anything to do with the removal. You could take it up with the people running your server - basically it's been set to act as a streaming server for mp3 files and this isn't what you want (they should understand the difference).

No. Feedburner uses Google Feedproxy, but this simply takes a note of the requests then passes them on to you own server, and it's from there that the file is served. It's the way your server is set up. Servers have to be set up for each type of file on them - html, txt, mp3, mov, etc. etc and sometimes the wrong setting gets used.

For mp3 yours is acting as a streaming server. Streaming is like the online radio stations, where the file is downloaded as it plays but isn't store other than temporarily. To the Store your files look like an internet radio station, so of course it doesn't know how long they are and can't move forward in the recording because it thinks that would be moving into the future.

As I say, it does work after a fashion from what I remember of the other issue, and it's not likely to be the reason you were removed. You can go on as you are, but it just doesn't work in all ways quite as it should.

The streaming is set on the server: only the people running it can alter that.