similar to: LMTP delivery honours .forward by default?

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 2 Dec 2016, MRob wrote: > I was under the impression that Dovecot does not look at .forward by default, > since of course, Sieve is where that kind of logic should go. However, I'm > seeing a .forward file being honoured by the LMTP delivery agent. Is this to > be expected? What version of Dovecot are you using? In my

On 2016-12-05 05:53, MRob wrote: > On 2016-12-04 23:18, Steffen Kaiser wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On Fri, 2 Dec 2016, MRob wrote: >> >>> I was under the impression that Dovecot does not look at .forward by >>> default, since of course, Sieve is where that kind of logic should >>> go. However,

On 2016-12-05 16:37, MRob wrote: > On 2016-12-05 05:53, MRob wrote: >> On 2016-12-04 23:18, Steffen Kaiser wrote: >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> On Fri, 2 Dec 2016, MRob wrote: >>> >>>> I was under the impression that Dovecot does not look at .forward by >>>> default, since of course,

On 2016-12-04 23:18, Steffen Kaiser wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Fri, 2 Dec 2016, MRob wrote: > >> I was under the impression that Dovecot does not look at .forward by >> default, since of course, Sieve is where that kind of logic should go. >> However, I'm seeing a .forward file being honoured by the LMTP >>

Hi to anyone who is willing to help, I have a csv. file which has 1999 horses as the rows and the age(in years) of the horse at each race as columns. Ive read this file into R and called it 'horses'. Im trying to find the longest break between each race in the horse's first year of racing. I already have a numeric called 'age.first' which is the age at which each horse had its