There are two fields that are unique to the hidden envelope header: 'Reply-to' and 'Return Path'. If you elect to display the email source, as described below, search the source for these fields. If you find either of these fields, you have the full header.

The easiest way to provide the full header to support is to forward the email as an attachment, providing your email program offers this option. Email forwarded as an attachment usually includes the full header, whereas email forwarded inline only includes the visible portions of the email. If you aren't sure whether this works in your email software, forward a copy of an email to yourself as an attachment, then use the process outlined in the next section to view the email source. You could also look for this information in your email application's documentation.

You can use your MUA (i.e., the application you use to send email) to access the hidden envelope header for an email, but the way this is accomplished depends on the application. Here are some of the most common ways to access email source.

Perhaps you are using some platform not covered in the previous instructions—or you followed the instructions but still weren't able to access the source. Take one last look at the help for your MUA, and if you don't find the answers you need, it's probably time to contact your friendly support person. Be sure to provide the name and version of your OS (e.g., MacOS9, Windows98, , etc.), and the name and version of your MUA (the application you use to send email) and tell the support person you would like to provide a full email header for troubleshooting purposes—if only you knew how. Hopefully they will send you some instructions which you can save somewhere on your hard drive for future reference, because if you correspond regularly through email, you're going to want to access email header source again someday.

If you enjoy the sense of power and accomplishment derived from wresting the envelope header from its hiding place, you may be interested in learning more about how to troubleshoot email.

Kavi® has extensive documentation on email and troubleshooting available to the online community. This documentation is aimed at a users with a wide range of technical knowledge, so you may find some of it too technical for your immediate needs. Certain documents, particularly the troubleshooting flowcharts, include instructions for users with varying levels of access privileges, so you may find these documents contain links to Kavi tools that are unavailable to you. Even when this is the case, you may find the troubleshooting flowcharts useful if you follow the steps until you reach the limits of your knowledge or the tools available to you. If you reach this point without finding your solution, follow the instructions on preparing information to send to support that are included in the flowchart instructions. You'll already have the full header, for which the support team thanks you in advance.

Any of the following documents may serve as a starting point. Select the one that seems most likely to meet your needs.