You can use mailsend.exe to send emails from the command line or a script via a known SMTP server. More information and more ways to use this little useful utility here.

In MS Exchange environment I used this method to send emails from batch jobs to internal email addresses. If you want to use this to send messages to external recipients you may need to configure Exchange relay options. Some additional info here.

Read more: Send Email from a .bat script

You can't export message tracking results from GUI interface, however you can from Exchange Management Shell.

1. Open Exchange Management Console > Toolbox > Message Tracking
2. Customise your query as required and copy Shell command from the box below.
3. Paste the text into Exchange Management Shell and append | Export-Csv C:\Export.csv at the end.
For example get-messagetrackinglog -Server "servername" -MessageSubject "meeting" -Start "16/12/2010 13:40:00" -End "16/12/2010 13:41:00" | Export-Csv C:\Export.csv
This will export results into Export.csv file on the C: drive.

One problem with that is that it does not export recipients as it is passed as an array of strings. To get around the issue you can specify which columns needs to be exported with select and request recipients with  {$_.recipients}
For example to get all columns you can use query:
get-messagetrackinglog -Server "servername" -MessageSubject "meeting" -Start "16/12/2010 13:40:00" -End "16/12/2010 13:41:00" | select timestamp, eventid, source, sourcecontext, messageid, messagesubject, sender, {$_.recipients}, internalmessageid, clientip, clienthostname, serverip, serverhostname, connectorid, {$_.recipientstatus}, totalbytes, recipientcount, relatedrecipientaddress, reference, returnpath, messageinfo | Export-Csv C:\Export.csv

Obviously you can select only these columns which you are interested in.

MS Exchange 2007

By default MS Exchange 2007 uses self signed certificates for various services (SMTP, IMAP, IIS, POP, etc). Normally these certificates are valid for one year.

Once certificate starts approaching its expiry date following events will be logged in Application Logs on Exchange server:

Event Type: Warning
Event Source: MSExchangeTransport
Event Category: TransportService
Event ID: 12018
Date:
Time:
User: N/A
Computer: <server name>
Description:
The STARTTLS certificate will expire soon: subject: <server.domain.local>, hours remaining: 177700433E5D67615E8564373CAF08AB5842DEA0. Run the New-ExchangeCertificate cmdlet to create a new certificate.

Event Type: Warning
Event Source: MSExchangeTransport
Event Category: TransportService
Event ID: 12017
Date: 13/04/2008
Time: 09:01:00
User: N/A
Computer: <server name>
Description:
An internal transport certificate will expire soon. Thumbprint:135645393F5D74715F825A865CAF08BB8332DC10, hours remaining: 156

Once certificate expires following event will be logged:

Event Type: Error
Event Source: MSExchangeTransport
Event Category: TransportService
Event ID: 12016
Date:
Time:
User: N/A
Computer: <server name>
Description:
The STARTTLS certificate will expire soon: subject: <server.domain.local>, hours remaining: 124543103F37D661E48559A73FFBA84A5832DBA0. Run the New-ExchangeCertificate cmdlet to create a new certificate.

To renew the certificate perform following steps:
1. Open Exchange Management Shell
2. Check status of existing certificate(s). Make note of the "Thumbprint" value:
Get-ExchangeCertificate | List
3. Get a new self-signed certificate. Use "Thumbprint" from the old certificate:
Get-ExchangeCertificate –thumbprint "C9A4BB6094A167BD324618D8492C4C5281FDD34A" | New-ExchangeCertificate
4. Examine properties of the new certificate. Make sure all required services are enabled.
Get-ExchangeCertificate | List
5. If some of the required services are not enabled you can enable them with following cmdlet:
Enable-ExchangeCertificate -thumbprint "A0BB986024A347BAC24438D8432C1B123AFDF11B" -services IIS, POP, SMTP, IMAP
6. Ensure that all required services are working with new certificate and then remove the old certificate:
Remove-ExchangeCertificate -thumbprint "C9A4BB6094A167BD324618D8492C4C5281FDD34A"

After starting MS Outlook 2007 or 2010 and connecting to MS Exchange 2007 or 2010 server (on a local network) you get warning "The name of the security certificate is invalid or does not match the name of the site"

This happens because of certificate names mismatch. For more information read Microsoft article KB-940726

To fix the problem:

Open MS Exchange Management Shell.

To find our information about your Autodiscovery server run:
Get-AutodiscoverVirtualDirectory | FL

To fix the certificate error run following 4 commands replacing:
<server_name> - Your Exchange Client Access (Autodiscovery) server name.
<mail.yourdomain.com> - Your exchange server FQDN (valid for your trusted certificate).

Set-ClientAccessServer -Identity <server_name> -AutodiscoverServiceInternalUri https://<mail.yourdomain.com>/autodiscover/autodiscover.xml

Set-WebServicesVirtualDirectory -Identity "<server_name>\EWS (Default Web Site)" -InternalUrl https://<mail.yourdomain.com>/ews/exchange.asmx

Set-OABVirtualDirectory -Identity "<server_name>\oab (Default Web Site)" -InternalUrl https://<mail.yourdomain.com>/oab

This 4th command is not required on Exchange 2010
Set-UMVirtualDirectory -Identity "<server_name>\unifiedmessaging (Default Web Site)" -InternalUrl https://<mail.yourdomain.com>/unifiedmessaging/service.asmx

Exchange 2007
Exchange 2010
Outlook 2007
Outlook 2010