Sample code for 30+ languages & platforms
Zig

Set Uncommon Email Options

See more Email Object Examples

Demonstrates the Chilkat Email.UncommonOptions property, a catch-all for uncommon needs. It defaults to the empty string and should typically remain empty. Recognized keywords include NoBccHeader (do not add the Bcc MIME header for BCC addresses — which must be set before calling AddBcc or AddMultipleBcc) and NO_FORMAT_FLOWED (do not automatically add format=flowed to a Content-Type header). This example sets NoBccHeader.

Background: Long-lived libraries accumulate rare, situational tweaks that do not each deserve their own property. Chilkat gathers these into a single keyword-driven UncommonOptions string. NoBccHeader is a good example: normally a Bcc header is generated (and stripped at send time), but certain workflows want it omitted entirely. Only documented keywords have any effect — unrecognized text is ignored — so leave this empty unless a specific compatibility need arises.

Chilkat Zig Downloads

Zig
const std = @import("std");
const chilkat = @import("chilkat");

pub fn main(init: std.process.Init) !void {
    const alloc = init.arena.allocator();

    // Demonstrates the Email.UncommonOptions property, a catch-all for uncommon needs.
    // It defaults to empty and should usually remain empty.  Recognized keywords include
    // "NoBccHeader" (do not add the Bcc MIME header) and "NO_FORMAT_FLOWED".

    const email = try chilkat.Email.init();
    defer email.deinit();
    email.setSubject("UncommonOptions example");
    email.setFrom("alice@example.com");

    // Do not add the Bcc MIME header for BCC recipients.  This keyword must be set
    // before calling AddBcc or AddMultipleBcc.
    email.setUncommonOptions("NoBccHeader");

    email.addBcc("Joe", "joe@example.com") catch {};

    std.debug.print("UncommonOptions = {s}\n", .{try email.getUncommonOptions(alloc)});
}