PHP中使用Curl操作IMAP的两个技术问题求助

Hey there, I’ve worked with IMAP in PHP quite a bit, so let’s break down your two problems and find practical solutions:

1. Extracting Email Content (HTML/Text Body, Reply-To) into an Array #

First off, using raw CURL to interact with IMAP is possible, but it’s a bit like reinventing the wheel—PHP has a built-in imap extension that handles all the parsing and protocol heavy lifting for you. That said, let’s cover both approaches:

Option 1: Use PHP’s Built-in IMAP Extension (Recommended) #

This is the simplest and most reliable way. It automatically parses IMAP responses into structured data. Here’s a quick example that does exactly what you want:

// Connect to your IMAP server (SSL port 993)
$imapStream = imap_open('{myImapServer:993/imap/ssl}', 'MyUsername', 'MyPassword');

// Get the message sequence number from the UID (IMAP needs this for some functions)
$messageNum = imap_uid($imapStream, 63);

// Extract header details (including reply-to)
$header = imap_headerinfo($imapStream, $messageNum);

// Extract plain text and HTML bodies
$textBody = imap_fetchbody($imapStream, $messageNum, 1); // Plain text part
$htmlBody = imap_fetchbody($imapStream, $messageNum, 2); // HTML part (if exists)

// Organize everything into an array
$emailData = [
    'subject' => $header->subject,
    'reply_to' => isset($header->reply_to[0]) ? $header->reply_to[0]->mailbox . '@' . $header->reply_to[0]->host : null,
    'text_body' => trim($textBody),
    'html_body' => trim($htmlBody)
];

// Clean up the connection
imap_close($imapStream);

print_r($emailData);

Option 2: Stick with CURL (Custom Parsing) #

If you need to keep using your CURL function, you’ll have to parse the raw IMAP response manually. First, fetch the full message with send('UID FETCH 63 BODY[]'), then use string manipulation or regex to extract the parts you need. For example:

$rawResponse = send('UID FETCH 63 BODY[]');

// Extract plain text body (simple regex example, adjust based on your response format)
preg_match('/BODY\[TEXT\]\s+\{\d+\}\s+(.*?)\r\n\*/s', $rawResponse, $textMatches);
$textBody = isset($textMatches[1]) ? trim($textMatches[1]) : '';

// Extract reply-to from headers
preg_match('/Reply-To:\s+(.*?)\r\n/', $rawResponse, $replyMatches);
$replyTo = isset($replyMatches[1]) ? trim($replyMatches[1]) : null;

$emailArray = [
    'text_body' => $textBody,
    'reply_to' => $replyTo
];

Note: This regex approach is fragile—email formats vary, so the built-in extension is way more reliable.

2. Why Your Subject Fetch Only Returns Length, Not Content #

This is a classic IMAP protocol quirk! When you send UID FETCH 63 BODY[HEADER.FIELDS (SUBJECT)], the server first sends a length indicator ({29} in your case) to tell you how many bytes the subject data is. CURL is only capturing this first part of the response, not waiting for the actual subject content that comes right after the length indicator.

IMAP is an interactive protocol, not a simple request/response like HTTP. CURL isn’t designed to handle this back-and-forth natively, but you can adjust your function to capture the full stream:

function send($command) {
    $url = 'imaps://myImapServer';
    $ch = curl_init();
    $fullResponse = '';

    curl_setopt($ch, CURLOPT_URL, $url);
    curl_setopt($ch, CURLOPT_PORT, 993);
    curl_setopt($ch, CURLOPT_USERNAME, "MyUsername");
    curl_setopt($ch, CURLOPT_PASSWORD, "MyPassword");
    curl_setopt($ch, CURLOPT_RETURNTRANSFER, false); // Disable auto-return, use read function
    curl_setopt($ch, CURLOPT_HEADER, true);
    curl_setopt($ch, CURLOPT_CUSTOMREQUEST, $command);
    curl_setopt($ch, CURLOPT_TIMEOUT, 10);

    // Custom read function to capture all response data
    curl_setopt($ch, CURLOPT_READFUNCTION, function($ch, $fd, $maxlen) use (&$fullResponse) {
        $data = fread($fd, $maxlen);
        $fullResponse .= $data;
        return strlen($data);
    });

    curl_exec($ch);
    curl_close($ch);

    return $fullResponse;
}

Now when you run echo send('UID FETCH 63 BODY[HEADER.FIELDS (SUBJECT)]');, you’ll get the full response including the actual subject content after the length indicator.

Again, I can’t stress enough how much easier the built-in imap extension makes this kind of work—it handles all the protocol nuances and edge cases you’d have to code yourself with CURL.

内容的提问来源于stack exchange，提问作者user10663015