marcoxiii at gmail
Jul 24, 2012, 12:31 AM
Post #3 of 3
(347 views)
Permalink
|
Hi Thomas, thanks for the answer.
Well, I thought that it wasn't a problem of RT - honestly i wasn't
sure that this was the correct ML where to write in.
I've fetchmail configured as daemon, with 2 minutes of pool intervals.
So there is any entry in the crontab..should I use it instead of the
daemon mode?
thank you
m
2012/7/24 Thomas Sibley <trs [at] bestpractical>:
> On 07/23/2012 03:12 AM, m4rco- wrote:
>> I'm experiencing a strange issue while processing incoming email
>> through RT-mailgate, and couldn't find a solution yet.
>> When fetchmail retrieves the emails from the IMAP server, RT processes
>> them not in the correct order (from the oldest, to the newest).
>> This behavior provokes RT to reject status update emails because they
>> are processed before the ticket-creation ones.
>>
>> Do you have any clues about how I can manage this?
>> Have been thinking about managing it by coding an RT mail-plugin, but
>> i'm quite sure there is a simpler solution at the system/daemon level.
>
> This isn't a problem caused by RT so much as it is a problem caused by
> concurrent delivery. That's the realm of fetchmail and your MDA
> (whatever is delivering SysAdm to RT). An RT mail plugin is a) not a
> good option and b) can't fix your problem in any practical way.
>
> How often do you run fetchmail from cron?
>
> Maybe you'll have better luck having fetchmail talk to rt-mailgate
> directly using the "mda" option rather than "is SysAdm here".
> --------
> List info: http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel
--
m4rco-
--------
List info: http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel
|
