Zeka

Wiremail and setLocale()

7 posts in this topic

I can't get wiremail to work as expected on remote host. On locale server it works as expected. On remote I'm getting emails like

=D0=B4=D0=B5=D0=B0=D0=BB=D1=8C=D0=BD=D1=8B=D1=85 =D0=B1=D1=80=D0=BE=D0=
=B2=D0=B5=D0=B9?= <no-replay@site.com>
X-Mailer: ProcessWire/WireMail
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

=D0=98=D0=BC=D1=8F: =0Adfadfsd=0A=D0=A2=D0=B5=D0=BB=D0=B5=D1=84=D0=BE=D0=
=BD: =0A+38 (065) 465-46-54=0A=D0=9D=D0=B0=D0=B7=D0=B2=D0=B0=D0=BD=D0=B8=
=D0=B5 =D1=81=D1=82=D1=80=D0=B0=D0=BD=D0=B8=D1=86=D1=8B=0A=D0=93=D0=BB=

I have tested it with different content types and content transfer encodings, but with no luck, so I'm curious about is wiremail functionality somehow bound with setLocale, because it is the only one thing that have been changed on remote server? 

Share this post


Link to post
Share on other sites

Is the first line complete? The missing from: header start and quoted-printable preamble is the only thing I see that's incorrect. If it's not, can you make sure that there are no line breaks in the fromName? setLocale shouldn't have any influence on WireMail's behavior.

1 person likes this

Share this post


Link to post
Share on other sites

Hi @BitPoet. Thank you about your clarification about setLocale. 

First snippet of code is just content of email that shows in webmail content area, here is the code from mail source

Subject: =?UTF-8?Q?=D0=A1=D0=BE=D0=BE=D0=B1=D1=89=D0=B5=D0=BD=D0=B8=D0=B5?=
 =?UTF-8?Q?=20=D1=81=20=D1=81=D0=B0=D0=B9=D1=82=D0=B0=20eyebrows=2Ecom=2Eu?=
 =?UTF-8?Q?a=20=7C=20=32=35-=30=33-=32=30=31=37=20=32=30=3A=32=32?=
From: =?utf-8?Q?Perfect.Eyebrows.=E2=80=94.=D1=81=D1=82=D1=83=D0=B4=D0=B8=D1=8F.=D0=B8=@web355.default-host.net
X-Delta-Virus-Check: ok
X-Delta-Spam-Symbols: Symbols: ONCE_RECEIVED(1.00), FROM_EXCESS_QP(1.19), BAYES_SPAM(4.60)(0.92); 
X-Delta-Spam-Score: 6,8
X-Delta-Virus-Check: ok
X-Delta-Spam-Symbols: Symbols: FROM_EXCESS_QP(1.19), BAYES_SPAM(4.60)(0.92); 
X-Delta-Spam-Score: 5,8

=D0=B4=D0=B5=D0=B0=D0=BB=D1=8C=D0=BD=D1=8B=D1=85 =D0=B1=D1=80=D0=BE=D0=
=B2=D0=B5=D0=B9?= <no-replay@site.com>
X-Mailer: ProcessWire/WireMail
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

=D0=98=D0=BC=D1=8F: =0Adfadfads=0A=D0=A2=D0=B5=D0=BB=D0=B5=D1=84=D0=BE=
=D0=BD: =0A+38 (054) 654-65-46=0A=D0=9D=D0=B0=D0=B7=D0=B2=D0=B0=D0=BD=D0=
=B8=D0=B5 =D1=81=D1=82=D1=80=D0=B0=D0=BD=D0=B8=D1=86=D1=8B=0A=D0=93=D0=
=BB=D0=B0=D0=B2=D0=BD=D0=B0=D1=8F=0A=D0=A1=D1=81=D1=8B=D0=BB=D0=BA=D0=B0 =
=D0=BD=D0=B0 =D1=81=D1=82=D1=80=D0=B0=D0=BD=D0=B8=D1=86=D1=83 =D1=81 =D0=
=BA=D0=BE=D1=82=D0=BE=D1=80=D0=BE=D0=B9 =D0=BE=D1=82=D0=BF=D1=80=D0=B0=
=D0=B2=D0=BB=D1=8F=D0=BB=D1=81=D1=8F =D0=B7=D0=B0=D0=BF=D1=80=D0=BE=D1=
=81=0A

 

Share this post


Link to post
Share on other sites

Could you try and shorten the fromName and toName (or replace it with plain ascii ones) for testing and see if that fixes it? It might be a line wrapping issue in one of those two.

1 person likes this

Share this post


Link to post
Share on other sites

Hi @BitPoet

I don't know how you knew about that, but you was right.

Original fromName

$mail->fromName(_t("Perfect Eyebrows — студия идеальных бровей"));

I have been shortening it letter by letter and tracked it down to next result:

In these cases I still get wrong result

$mail->fromName(_t("еальных бровей"));
$mail->fromName(_t("альных бровей"));

but that one works

$mail->fromName(_t("льных бровей"));

So, it looks like there is some limitation of fromName length? But why it works with wireMailSmtp? 

1 person likes this

Share this post


Link to post
Share on other sites

Since I am the one guilty of adding UTF-8 support to WireMail, I could take an educated guess ;)

WireMailSmtp uses some external libraries that have evolved over the years and have their own routines to handle character encoding in address headers. I'll take a look at what is done differently there (I have an idea, but I'll have to run some tests to be sure) . In the meantime, if using wireMailSmtp is an option, I'd go with that.

1 person likes this

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.