Sample code for 30+ languages & platforms
Zig

Add an Attachment from a BinData Object

See more Email Object Examples

Demonstrates the Chilkat Email.AddAttachmentBd method, which adds an attachment using the contents of a BinData object. The first argument is the attachment filename, the second is the BinData, and the third is the content type — if empty, it is inferred from the filename extension. This example loads a PDF into a BinData and attaches it.

Background: BinData is Chilkat's container for raw binary data. Attaching from a BinData is the right approach when the file's bytes are already in memory — generated on the fly, downloaded, or read from a database — rather than sitting on disk (which would use AddFileAttachment). Chilkat Base64-encodes the bytes into the message automatically.

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 AddAttachmentBd method, which adds an attachment using the contents of a
    // BinData object.  The first argument is the attachment filename, the second is the BinData
    // object, and the third is the content type (inferred from the filename extension if empty).

    const email = try chilkat.Email.init();
    defer email.deinit();
    email.setSubject("Attach from BinData");
    email.setBody("Please see the attached file.");

    // Load a file into a BinData object, then attach it.
    const bd = try chilkat.BinData.init();
    defer bd.deinit();
    bd.loadFile("qa_data/attachments/report.pdf") catch {
        std.debug.print("{s}\n", .{try bd.getLastErrorText(alloc)});
        return;
    };

    email.addAttachmentBd("report.pdf", bd, "application/pdf") catch {
        std.debug.print("{s}\n", .{try email.getLastErrorText(alloc)});
        return;
    };

    std.debug.print("NumAttachments = {d}\n", .{email.getNumAttachments()});

    // Note: The path "qa_data/attachments/report.pdf" is a relative local filesystem path,
    // relative to the current working directory of the running application.
}