I had to deal with a “huge” mail.que file this morning and thought of letting you know how to handle similar issues.So, here is the scenario

1. How To Large File From Qq Mail Address
2. Qq Mail Sign Up
3. How To Large File From Qq Mail To Pdf

• Came to know about this issue only when SCOM alerted for a low disc space
  
• On one of the hub transport servers, the mail.que file reached to 148GB (unbelievable)
  

A lil about the mail.que file:

Mar 29, 2019 Email was not designed for sending large files, and almost all mail servers will only allow attachments of 10 MB. Yahoo and Gmail will allow up to 20 MB, but if you have a large email to send, such as a group of photos, video files or other large attachments, the email will not go through. There are various methods to email large files. Windows Mail is frozen by incoming large file! I have not updated yet to Windows 7 so this is a Windows Vista Mail problem: I evidentally have a VERY large file being sent to one of my email accounts via Windows Mail. For example, if you had a 50MB file you wanted to email—or even a collection of large files—you could use a file compression program like 7-Zip to create an archive, and then split the archive into five 10MB pieces. After splitting the archive, you can then attach all the separated pieces to separate emails. This is an approach you may need to use for very large files, such as very large video files that are many gigabytes in size. The file transfer may take a while, but this is the kind of file transfer that FTP technology was intended for. Transferring Large Files via Email. As you can see, there are many ways to transfer very large files via email.

The mail.que file temporarily stores all emails before it is delivered to the target. It is an ESE database which means it is similar in architecture like an Exchange mailbox database, the edb file.

How To Large File From Qq Mail Address

As per a TechNet article

A queue is a temporary holding location for messages that are waiting to enter the next stage of processing. Each queue represents a logical set of messages that a transport server processes in a specific order. Queues exist only on servers that have the Hub Transport server role or Edge Transport server role installed.

Let’s take a look at the other files residing in this location:

Trn.chk – Checkpoint file like E0x.chk in exchange

Trn.log – The transaction log file which is getting committed now. Similar to E00.log in exchange

Trntmp.log – The next transaction log file which is created in advance.

Qq Mail Sign Up

Trnnnn.log – Next transaction log file created when Trn.log reaches its maximum size.

How To Large File From Qq Mail To Pdf

Trnres00001.jrs – First reserve log file. Only used when the hard disk drive that contains the transaction log runs out of space to stop the queue database cleanly

Trnres00002.jrs – Second Reserve log file.

Temp.edb – Temp database used to verify database schema on start-up.

Back to the issue:

You need to know 2 important terms before we proceed since this issue could have caused due to a combination of both:

• PipelineTracingEnabled: This is used for troubleshooting purposes and is not enabled by default.
  
• MaxDumpsterSizePerStorageGroup: This is for Exchange 2007. The maximum size of the transport dumpster queue per storage group. This is a universal setting for all storage groups; you can’t set variable sizes for each storage group. The recommended size is 1.5 times the maximum message size that can be sent. For example, if the maximum size for messages is 10 megabytes (MB), you should configure the MaxDumpsterSizePerStorageGroup parameter with a value of 15 MB. Read more here
  

You can use the cmdlet: Get-TransportServer | fl to get these details.

In my case, tracing was enabled and the dumpster was specified to be 50GB.

Enough talking and lets delete it now

This is the suggested way to get rid of the old mail.que file and get a new one without any downtime. I proceed under the assumption that you have multiple hub transport servers to process emails so, no emails will be processed at the time of this change. This
should take about less than a minute. I will call the Hub transport server HUB01. Remember that steps 6-8 are very important and will ensure none loses emails

1. Login to HUB01
   

2. 
   

3. Open exchange management shell and run “Get-TransportServer ” HUB01″ |fl
   
4. Here, look for PipelineTracingEnabled. This should be set to False. If not, run
   

   Set-TransportServer HUB01 -PipelineTracingEnabled $False
   

5. MaxDumpsterSizePerStorageGroup is in MB’s and not GB’s
   

   MaxDumpsterTime : 7.00:00:00
   

   If not, run
   

   Set-TransportConfig -MaxDumpsterSizePerStorageGroup <size> -MaxDumpsterTime <timespan>
   

6. Now run “Get-Queue” and take a look at the count of messages in HUB01
   
7. Goto services.msc and Pause the Microsoft Exchange Transport service
   
8. Again, run “Get-Queue” and ensure all pending messages are “zeroed” out
   
9. Once messages pending becomes zero, stop the Transport service
   
10. Move the mail.que file and all others to a new folder in the same location
    
11. Start the Transport service
    
12. Take a look at the queue again
    
13. You should see that messages would have started getting delivered
    
14. Now you can backup or safely delete the old mail.que file
    

Ratish Nair
MVP Exchange
Team@ MSExchangeGuru

Keywords: Delete mail.que file, delete large mail.que file, mail.que file large in size, huge mail.que file in exchange, exchange 2007 mail.que file, mail.que file too big