Maybe it won't completely invalidate your evidence. Your email server may have logs, backups, etc. that could (somehow) certify that the email hasn't been tampered with (eg. the email was already present in a backup tape put two years ago in a bank safe, with the bank certifying the date it had been stored). However, it will certainly make it much more weak.
The point is, if you have full access to the data stored, you could have tampered with it. There are cases where you are not really having that access to "your" mail server, such as it being provided by your hosting, or the CEO/company owner technically "owning" the server, but not managing the server themselves so they would be unable to tamper with that data without the collusion of certain other employees/contractors.
Even if you don't manage the server itself, it could be possible for you to copy a backdated email through IMAP. My recommendation would be to send the evidence email [to anywhere you can pick it] from a third party provider which supports DKIM (any big player does).
This way, when sending the email, the third party (eg. gmail) will be signing [some parameters of] the message with their DKIM key (usually the subject, date, recipients, body hash...). You could later prove that gmail certified [at the signature timestamp] those email contents. Thus, [barring some catastrophic bug] the only way for you to have that signature with that message being false, would be that you convinced gmail to fraudulently sign that email (which should then considered infeasible by the court, concluding that the email was indeed sent at the given date).