7,920 questions
After a month I wouldnt think so. However check to see how much space is avail and add if necessary.
You can also recreate the mail.que to free up space.
I do this every once in awhile. Safe and easy:
https://techcommunity.microsoft.com/t5/exchange-team-blog/transport-database-understand-size-and-troubleshoot/ba-p/1113388
If there is no other drive available to move the transport database, you can recreate the database so that the immediate problem is resolved. And to ensure, there is no data loss, we must make sure there is no email waiting in the queue to be sent out. The steps are mentioned below:
Failover Exchange databases to a different server to avoid downtime for submission from local databases
Pause the Microsoft Exchange Transport Service
Run the Get-queue command on the Exchange server and make sure that all messages have been processed and no email is stuck in the queue.
Make sure no other servers have shadow messages waiting for this server (otherwise they would get delivered again). You can run the following command to see all the shadow queues for a particular server:
get-transportserver | get-queue | ?{$.deliveryType -eq "ShadowRedundancy" -and $.NextHopDomain -eq "Servername"}
Stop the Microsoft Exchange Transport and Microsoft Exchange Frontend Transport services
Navigate to queue folder path and rename it to something like QueueOld
Start the Microsoft Exchange Transport and Microsoft Exchange Frontend Transport services
A new queue folder would be created, make sure that Application event ID 7005 has appeared: "A new database file mail.que has been created."
If the transport service starts successfully, you can move the QueueOld to a different location for backup and delete it later.