@faizanakram99 #41651 similar?

@faizanakram99 #41651 similar?

@zspine Not sure tbh. Emails are sent while attachments with non-ascii characters in its filename are ignored (no errors whatsoever).

For now I used symfony string component to fix it.

// ....
use Symfony\Component\Mime\Email;
use function Symfony\Component\String\u;
// ....

$message = new Email();

// ....

$message->attach(
    $attachmentHandle,
    u($filename)->ascii()->toString(),
    $mimeType,
);

@faizanakram99 I haven't tested but it's definitely seems like a bug!

FYI. Found something similar in unrelated repositories' issue queue.
anymail/django-anymail#125 (comment)

Here's an example. I'm able to reproduce the first problem like this (using the Mailgun backend):

from django.core.mail import EmailMessage
msg = EmailMessage(to=["[email protected]"], 
                   subject="Mailgun attachment test", 
                   body="This has attachments")
msg.attach("ascii-name.txt", "some data", "text/plain")
msg.attach("unicøde-name.txt", "more data", "text/plain")
msg.send()

When this is sent, the attachment with the all-ASCII name makes it through, but the one with a Unicode character is silently dropped.

As I can understand, it seems to be related how the filenames are encoded in request's body.

Open for a PR and check the filenames via mb_detect_encoding($str, 'ASCII', true) and raise an exception otherwise ?

I think adding symfony/string as a dependency to mailgun mailer is a bit overkill for this case.

WDYT @nicolas-grekas ?

This might be similar to #41249
We need to figure out the proper way to encode UTF-8 file names before rejecting them.

Hey, thanks for your report!
There has not been a lot of activity here for a while. Is this bug still relevant? Have you managed to find a workaround?