Ticket system (support at mikrotik.com) is down?

A few weeks I have no answers to my mails. Earlier I immediately received a mail saying that new ticket was created. Now I have neither automated answer nor support answer… What’s wrong? I’m using gmail.com and tut.by mail servers.

strange as many emails come and go - just as usual …

do you use spam filter? can you check whether it blocks my mails? chupaka (at) gmail.com

last mail from you “02/12/2008 15:55:02”

just sent one more mail:

Received: by 10.142.135.17 with HTTP; Mon, 7 Apr 2008 03:01:50 -0700 (PDT)
Message-ID: <7206c0e80804070301p6b6ad666qa34dea538285dc1f@mail.gmail.com>
Date: Mon, 7 Apr 2008 13:01:50 +0300
From: "=?KOI8-R?B?/tXQwS3+1dDT?=" <chupaka@gmail.com>
To: support@mikrotik.com
Subject: test mail
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_12136_16265315.1207562510513"
Delivered-To: chupaka@gmail.com

------=_Part_12136_16265315.1207562510513
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

empty

------=_Part_12136_16265315.1207562510513
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

empty

------=_Part_12136_16265315.1207562510513--

It seems that our ticketing system doesn’t like the Cyrilic font in your FROM name.


Чупа-Чупс wrote:

Yep, thanks. Workaround is to change ‘from’ name, but… Could you restore old behaviour of ticketing system, so that it understand Cyrillic symbols again? =)

we won’t downgrade it as new version has more important stuff :slight_smile:

no downgrade, of course, but… modify =)

dont’ you know that majority of email clients will not support your cyrilic FROM anyway? have some respect for the recipient :slight_smile:

anyway:

there’s no Cyrillic! and I faced this problem first time =)
don’t say ‘majority’ - it’s not true :wink:

even worse. yes, majority is very true. look at what OS people still use. they use crappy old MS products

ok this is WAY OFFTOPIC!

we fixed the issue with the ticketing system