special char in email object

SeLLeRoNe

SeLLeRoNe

Super Moderator
Joined
Oct 9, 2004
Messages
6,516
Location
A Coruña, Spain
Hi,

ive just noticed that there is something weird going on on mine smtp server.

I was trying to send an email to a friend with a special char in the object (not so special but ok... was à that i used for many words in italian language same as è ì ò ù)

When i was sending the message i had from Thundebrird error on connection with smtp server.. ive removed the à and the email gone without any error.

Exim version:

Code: 
>exim -bV
Exim version 4.69 #1 built 21-Jan-2008 17:54:51

Any suggestion?
 
I'm not sure what you mean by object. Do you mean the email subject? Note that none of the headers are checked when doing an smtp connect, so there may be some other cause.

Jeff
 
You should check your /var/log/exim/mainlog to see where the error occurs; you said the problem is with smtp connect, but smtp connect doesn't look at the subject; only the data portion of the connection looks at the headers.

Jeff
 
yes i understood what u mean, but well dunno why if i take off that char the mail gonna be sent without any problem, gonna try a test mail and check log, ill update here for news ^^

thanks
 
Ok, here the result

Code: 
Mar 13 22:28:38 Psycho kernel: [5114697.151699] exim[25692]: segfault at 185bfe5a ip 185bfe5a sp bff95830 error 4 in ISO8859-15.so[b7b6e000+2000]
 
Something more to add, yesterday when i made those test the email seems never gone away from client (thundebird) but today ive received this:

Code: 
This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  [email protected]
    local delivery failed

------ This is a copy of the message, including all the headers. ------

Return-path: <[email protected]>
Received: from ppp-52-181.32-151.iol.it ([151.32.181.52] helo=[192.168.1.7])
	by Psycho.CrazyNetwork.it with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.69)
	(envelope-from <[email protected]>)
	id 1NqYqe-0006dr-PJ; Sat, 13 Mar 2010 22:26:16 +0100
Message-ID: <[email protected]>
Date: Sat, 13 Mar 2010 22:26:03 +0100
From: Commerciale - Crazy Network <[email protected]>
Reply-To: [email protected]
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; it; rv:1.9.1.8) Gecko/20100227 Lightning/1.0b1 Thunderbird/3.0.3
MIME-Version: 1.0
To: [email protected], Alesandra Iannucci <[email protected]>
Subject: =?ISO-8859-15?Q?a=E0=E0=E0?=
Content-Type: multipart/related;
 boundary="------------010001060905030109060800"
X-Antivirus-Scanner: Clean mail though you should still use an Antivirus

This is a multi-part message in MIME format.
--------------010001060905030109060800
Content-Type: text/html; charset=ISO-8859-15
Content-Transfer-Encoding: 8bit

So, the mail cliente fail the send but seems that the process start (with that error in message log and then the email that seems has never been sent come back with this error

And the email subject was just à and check this
Code: 
Subject: =?ISO-8859-15?Q?a=E0=E0=E0?=
 
Without knowing where in the smtp protocol the error is caused (perhaps you can figure that out by running exim from shell (see man exim for exim -bh) it's hard to even begin to guess what's happening. This thread on the Planet's forum mayu be helpful.

A sigfault may mean that exim can't handle the special codes in the subject.

Jeff
 
Ok ive done some test and ive notice 2 things.

Using another of my server with exim_

Exim version 4.71 #1 built 16-Feb-2010 11:16:33

and the email with "à" in subject was sent correctly without problem

I made a test with the command from planet's forum and the result is this

Code: 
>>> using ACL "check_message"
>>> processing "deny"
>>> check demime = *
>>> check condition = ${if >{$demime_errorlevel}{2}{1}{0}}
>>>                 = 0
>>> deny: condition test failed
>>> processing "deny"
>>> check demime = *
>>> check malware = *
>>> deny: condition test failed
>>> processing "deny"
>>> check demime = bat: com: pif: prf:scr : vbs
>>> deny: condition test failed
>>> processing "warn"
>>> warn: condition test succeeded
>>> processing "accept"
>>> accept: condition test succeeded
>>> unspool_mbox(): unlinking '/var/spool/exim/scan/1NrGdl-0008Pp-3l/1NrGdl-0008Pp-3l.eml'
>>> unspool_mbox(): unlinking '/var/spool/exim/scan/1NrGdl-0008Pp-3l/1NrGdl-0008Pp-3l-00000                  .com'
LOG: 1NrGdl-0008Pp-3l <= [email protected] H=psycho.crazynetwork.it [194.177.98.220] P                  =smtp S=368 T="à" from <[email protected]> for [email protected]
250 OK id=1NrGdl-0008Pp-3l

**** SMTP testing: that is not a real message id!

this exim is Exim version 4.69 #1 built 21-Jan-2008 17:54:51

I should try to reinstall exim with newer version maybe...

Better use custombuild for update or from source?
 
In the past I've always used the DirectAdmin shell script to install/update custombuild, but I've always saved and reinstalled my previous exim.conf file.

Others may have other experiences; perhaps someone else will write.

Jeff
 
Nope i didnt had exim listed there thats why ive asked :)

ive used http://help.directadmin.com/item.php?id=125

exim - install/update Exim using "./build exim" or "./build all". Possible values: yes/no (default: no). This option is only available from CustomBuild 1.2.

im using custombuild 1.1 thats why. Is custombuild 1.2 stable or still beta? How i can update and use that instead of 1.1?

Btw after update exim to latest version ive no more that problem.

Thanks for your help, as always very appreciated
 
I am using custombuild version 1.2.13, I think it is safe to use version 1.2x, but don't know if it still actual is called a beta version. Please see this statement:

http://directadmin.com/forum/showpost.php?p=174368&postcount=4

If you upgrade custombuild to version 1.2x, you should be careful to set the versions you want for php, mysql etc, because it defaults to newer versions that you might not want to use yet.

I don't know if the reason for the missing exim could be your custombuild version. I am a beginner, and can't help more.

If I was you, I would send a PM with your questions to user "smtalk", as I think he is the expert on this field.

Sorry that I can't be of more help! I am still learning.
 
for sure is cause i was using 1.1 cause i didnt wanted to use beta version, ill think about use newer version or not (and in case ill take care about newer version).

Your suggest are appreciated like everyone else, cause everyone can put his 2cent for make a stuff work better ;)

I just saw that php4 is not supported in custombuild 1.2 and so i cant use it cause some customer (on some server) use still php4.. so.. for the moment ill keep it for have all servers in same work condition for less problems :)

thanks
 
You must log in or register to reply here.
Back
Top