Chilkat Examples

ChilkatHOME.NET Core C#Android™AutoItCC#C++Chilkat2-PythonCkPythonClassic ASPDataFlexDelphi ActiveXDelphi DLLGoJavaLianjaMono C#Node.jsObjective-CPHP ActiveXPHP ExtensionPerlPowerBuilderPowerShellPureBasicRubySQL ServerSwift 2Swift 3,4,5...TclUnicode CUnicode C++VB.NETVBScriptVisual Basic 6.0Visual FoxProXojo Plugin

Tcl Examples

Web API Categories

ASN.1
AWS KMS
AWS Misc
Amazon EC2
Amazon Glacier
Amazon S3
Amazon S3 (new)
Amazon SES
Amazon SNS
Amazon SQS
Async
Azure Cloud Storage
Azure Key Vault
Azure Service Bus
Azure Table Service
Base64
Bounced Email
Box
CAdES
CSR
CSV
Certificates
Cloud Signature CSC
Code Signing
Compression
DKIM / DomainKey
DNS
DSA
Diffie-Hellman
Digital Signatures
Dropbox
Dynamics CRM
EBICS
ECC
Ed25519
Email Object
Encryption
FTP
FileAccess
Firebase
GMail REST API
GMail SMTP/IMAP/POP
Geolocation
Google APIs
Google Calendar
Google Cloud SQL
Google Cloud Storage
Google Drive
Google Photos
Google Sheets
Google Tasks
Gzip
HTML-to-XML/Text
HTTP

HTTP Misc
IMAP
JSON
JSON Web Encryption (JWE)
JSON Web Signatures (JWS)
JSON Web Token (JWT)
Java KeyStore (JKS)
MHT / HTML Email
MIME
MS Storage Providers
Microsoft Graph
Misc
NTLM
OAuth1
OAuth2
OIDC
Office365
OneDrive
OpenSSL
Outlook
Outlook Calendar
Outlook Contact
PDF Signatures
PEM
PFX/P12
PKCS11
POP3
PRNG
REST
REST Misc
RSA
SCP
SCard
SFTP
SMTP
SSH
SSH Key
SSH Tunnel
ScMinidriver
Secrets
SharePoint
SharePoint Online
Signing in the Cloud
Socket/SSL/TLS
Spider
Stream
Tar Archive
ULID/UUID
Upload
WebSocket
XAdES
XML
XML Digital Signatures
XMP
Zip
curl
uncategorized

 

 

 

(Tcl) Email Received Header Fields

Received emails will contain one or more "Received" header fields at the beginning of the email header. Each SMTP server (along the delivery path) adds a Received header to the top of the incoming message. The delivery route can be ascertained by the sequence of Received headers. There is a good summary of the Received header here.

The following explanation is taken from the reference URL above:

In theory, the value of a Received field is tokenizable. It contains

    1) optionally, a "from" atom followed by an encoded domain name;
    2) optionally, a "by" atom followed by an encoded domain name;
    3) optionally, a "via" atom followed by another atom;
    4) zero or more of the following: a "with" atom followed by another atom;
    5) optionally, an "id" atom followed by either (1) an atom or (2) a < token, an encoded address, and a > token;
    6) optionally, a "for" atom followed by an encoded address;
    7) a semicolon; and
    8) a timestamp. 

In practice, SMTP servers put all sorts of badly formatted information into Received lines. It is probably best for readers to treat everything before the final semicolon as unstructured text, purely for human consumption.

This example demonstrates iterating over each of the Recevied headers and getting the content of each.

Chilkat Tcl Extension Downloads

Chilkat Tcl Extension Downloads

load ./chilkat.dll

set email [new_CkEmail]

# Load a .eml file into the email object.
set success [CkEmail_LoadEml $email "/home/users/chilkat/eml/myEml.eml"]
if {$success == 0} then {
    puts [CkEmail_lastErrorText $email]
    delete_CkEmail $email
    exit
}

set sbHdrName [new_CkStringBuilder]

set i 0
set numHeaders [CkEmail_get_NumHeaderFields $email]
while {$i < $numHeaders} {
    CkStringBuilder_SetString $sbHdrName [CkEmail_getHeaderFieldName $email $i]
    if {[CkStringBuilder_ContentsEqual $sbHdrName "Received" 0] == 1} then {
        puts "Received: [CkEmail_getHeaderFieldValue $email $i]"
    }

    set i [expr $i + 1]
}

delete_CkEmail $email
delete_CkStringBuilder $sbHdrName

 

© 2000-2024 Chilkat Software, Inc. All Rights Reserved.