headers
Ales Vizdal, AVONET, s.r.o. | 5 Dec 2006 10:56
Picon
Favicon

mail encoding

Hello developers,

I've sent a post to users list, but without reply, so I am asking here.
I do receive emails in various encodings (iso-8869-2, windows-1250,
utf8), but OTRS doesn't seem to support online recoding. Replying to
an email written in windows-1250 encoding and browser set to iso-8859-2
produces incorrect email. Does OTRS support recoding or do you plan to
add such a feature?

Regards

--

-- 
Ales Vizdal, AVONET, s.r.o.
_______________________________________________
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
Permalink | Reply | 0 comments |
headers
Denis Jedig | 6 Dec 2006 02:00
Picon

Re: X-OTRS header for identifying ticket number?

On Fri, 24 Nov 2006 09:59:15 +0100 Kees Leune wrote:

> to interact with OTRS. It would be very useful if there is an X-OTRS
> mail header that I can set that specifies to which ticket an incoming
> message should be linked. 

Any specific reason for you not to use the ticket number in the Subject:
line?

--

-- 
Denis Jedig
syneticon networks GbR             http://syneticon.net/service/

_______________________________________________
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
Permalink | Reply | 501 comments |
headers
Kees Leune | 6 Dec 2006 11:18
Picon

RE: Re: X-OTRS header for identifying ticket number?


> -----Original Message-----
> From: dev-bounces <at> otrs.org [mailto:dev-bounces <at> otrs.org] On Behalf Of
> Denis Jedig
> Sent: Wednesday, December 06, 2006 2:00 AM
> To: dev <at> otrs.org
> Subject: [dev] Re: X-OTRS header for identifying ticket number?
> 
> On Fri, 24 Nov 2006 09:59:15 +0100 Kees Leune wrote:
> 
> > to interact with OTRS. It would be very useful if there is an X-OTRS
> > mail header that I can set that specifies to which ticket an
incoming
> > message should be linked.
> 
> Any specific reason for you not to use the ticket number in the
Subject:
> line?

Yes, many :) The most important reason is that the subject line must
adhere to certain externally imposed requirements, and an OTRS id is not
included in that. This morning, I have however heard back from somebody
else, who wrote:

--- begin quote ---
OTRS recognizes that a new message belongs to an allready existing
ticket 
by

- researching the subject of the message for the ticket number,
(Continue reading)

Permalink | Reply | 0 comments |
headers
Manfred Dohmen | 13 Dec 2006 14:33
Picon

E-Mail-Parser

Under certain conditions it's possible that the MessageBody is empty, which results in a warning.

This is a quick solution:

diff -r otrs-2.0.4-01/Kernel/System/EmailParser.pm otrs/Kernel/System/EmailParser.pm
648a649
>         $Self->{MessageBody} = "" unless defined $Self->{MessageBody};

______________________________________________________________________________
"Ein Herz für Kinder" - Ihre Spende hilft! Aktion: www.deutschlandsegelt.de
Unser Dankeschön: Ihr Name auf dem Segel der 1. deutschen America's Cup-Yacht!

_______________________________________________
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
Permalink | Reply | 0 comments |
headers
Martin Edenhofer | 13 Dec 2006 15:39

CVS: 2.1 branch!

Hi,

after the pretty successful start of OTRS 2.1 we want to say thank you
to all!  :-)

Today we created a cvs branch for OTRS 2.1. That means this branch will
have all future bug fixes for OTRS 2.1.x (just bug fixes no new features).

So the cvs (HEAD) is ready for new features (see TODO file).

To checkout the 2.1 branch use:
===============================
"cvs -z3 -d :pserver:<user> <at> cvs.otrs.org:/home/cvs co -r rel-2_1 otrs"

To checkout the cvs HEAD use:
=============================
"cvs -z3 -d :pserver:<user> <at> cvs.otrs.org:/home/cvs co otrs"

Thanks, and happy coding! .-)

PS: The current stats about the OTRS framework source code (_without_
all additional modules like WebMail, FAQ, FileManager, SIRIOS, ...) is:

-----------------------------------------------------------------
Source code lines (*.sh) :     899
Source code lines (*.pl) :    5943
Source code lines (*.pm) :  150370
Source code lines (*.t) :     8384
Source code lines (*.dtl):   18499
Source code lines (*.xml):   14072
(Continue reading)

Permalink | Reply | 0 comments |
headers
adzr | 22 Dec 2006 11:51
Picon
Favicon

question about moderation

Hi,

I'm guessing if there is a way to moderate agents answers in a way like
forums.

Regards,

Antoine
_______________________________________________
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
Permalink | Reply | 0 comments |
headers
Robert Oliynichenko | 26 Dec 2006 09:03
Picon

Online encoding incoming email in OTRS

Hello Developers!

I've made some changes in Kernel/System/PostMaster.pm for online
encoding of incoming email messages into default charset.

I also added parameter $Self->{"EmailForceCharsetEncoding"} = 1; in
Config.pm . If EmailForceCharsetEncoding=0 the online encoding
switches off.

Here is diff (with otrs-2.1.4)
diff -Naur PostMaster.pm.orig PostMaster.pm
--- PostMaster.pm.orig  2006-12-20 11:57:27.000000000 +0200
+++ PostMaster.pm       2006-12-22 15:57:06.000000000 +0200
 <at>  <at>  -98,7 +98,6  <at>  <at> 
    my %Param =  <at> _;
    # ConfigObject section / get params
    my $GetParam = $Self->GetEmailParams();
-
    # check if follow up
    my ($Tn, $TicketID) = $Self->CheckFollowUp(%{$GetParam});

 <at>  <at>  -140,6 +139,8  <at>  <at> 
       );
       return 1;
   }
+
+
   # ----------------------
   # ticket section
   # ----------------------
(Continue reading)

Permalink | Reply | 0 comments |
headers
Robert Oliynichenko | 28 Dec 2006 16:14
Picon

problem with recoding names of attached files

Hello Developers!

In my last message I suggested some changes in
Kernel/System/PostMaster.pm for online encoding of incoming email
messages into default charset.

It works correctly but I still have problem with recoding names of
attached files.
Frankly speaking I don't know where (in whiche module, procedure) and how to
recode them correctly. If anyone could help I would try to solve the problem.

Best Regards,
Robert Oliynichenko
OS Consulting
tel.+38 (044) 426-10-20
_______________________________________________
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
Permalink | Reply | 0 comments |

Gmane