You're still missing the point Vinyl.
It's not about what should be able to happen or what could happen if they did this or that......it's about what DID happen i.e. the 4 emails, along with some other assorted emails, were not received by iNetbet. The OP could find out from their ISP what exactly happened to the emails if they wanted to...I've done it before. It is also common sense that one needs to reduce the file size of docs before sending them, especially if there are multiple attachments.
I'm amazed that anyone would think the casino would deliberately ignore someone...unless of course they think that the casino is straight out lying, in which case they should offer evidence of such or apologise. My understanding was that it was unacceptable to make accusations such as this against operators (especially accredited ones) in the forum...?
I am not saying that they are deliberately ignoring players, but not EVERY ISP has helpful CS. Mine are in Mumbai or Bangalore, and can only stick to the script. If a problem is not on their script, they don't have an initiative at their disposal. Often, they will give the wrong information, which usually means following company policy of denying any fault, and blaming any third party to the problem being encountered. In the case of a recent 6 month TV issue, they spent over 6 months blaming the BBC until some customers called their bluff and contacted the BBC and OFCOM. The fault was eventually traced to THEIR server, but they then blamed some previously unmentioned subcontractor.
I have actually made formal complaints to my ISP about all the emails that kept failing to make it through to Jackpot Factory, and every time I was "reliably informed" that the fault lay with JF or their ISP, not Virgin. It is a lottery, and there is every chance that this complainant will be told it is iNetBet's fault, and having head this from their ISP, will be more convinced than ever that iNetBet are dicking them around.
The problem with saying that the player should work with what is available is a problem because iNetBet had the player's money, and wouldn't give it back even if the player wanted to "walk away" from the situation. The player's ONLY option when backed into this corner was to fight, and if necessary "fight dirty". I am sure that if you were doing business with someone, and they told you they couldn't work with the facilities you had, you would want to leave with your money and go elsewhere.
I didn't see ANY effort in the part of iNetBet to HELP this player "reformat" his files, they just expected him to second guess what their systems would cope with and just keep trying again and again. As a result, he did just this, and when he DID "reformat" from a single large file to 4 individual emails, iNetBet said there was now a different problem, and again offered no help in getting around it. They didn't make any suggestions, or even indications of what they needed to get the sizes down to. This lead to the player thinking that whatever they did wouldn't work, and that this could be due to the issue having been "contrived" rather than real.
I would have expected the 4 smaller emails to exhibit the same error, getting through, but the 2.5Mb files still being too large to open because the reduction had not been enough. The idea that at least the "header" and "properties information" made it through the first time, yet not even this much made it through on FOUR subsequent emails does not sound believable. My suspicion is that iNetBet's own systems simply threw these 4 emails away on arrival, but kept no record nor recorded any "reason code" that would aid in diagnosing the problem. Had the problem been earlier in the chain, the sender would have received a "bounce" notification with an error code, although this could have ended up in their spam folder, a check that should be done before stating that iNetBet definitely didn't respond. Similarly, it is a check iNetBet should do before stating that the player didn't send, or they didn't receive, the emails.
It should be possible to get the size below 2.5Mb, but unless one is told HOW, it is something many ordinary users would have little idea of how to achieve, and thus would EXPECT help from a department which is, after all, called "Customer Service".