Re: Derrivative code

2014-07-13 Thread Matijs van Zuijlen
On 13/07/14 19:50, Ricardo Signes wrote: > * Matijs van Zuijlen [2014-07-13T07:17:39] >> - Email::Sender is more dangerous: if through a programming error an >> undefined transport is passed to sendmail(), it will happily try to send the >> mail you were trying to save locally via SMTP. > Don't us

Re: Derrivative code

2014-07-13 Thread Ricardo Signes
* Matijs van Zuijlen [2014-07-13T07:17:39] > - Email::Sender is more dangerous: if through a programming error an > undefined transport is passed to sendmail(), it will happily try to send the > mail you were trying to save locally via SMTP. Don't use Email::Sender::Simple, use the Mbox (or whate

Re: Derrivative code

2014-07-13 Thread Matijs van Zuijlen
On 07/07/14 03:49, Ricardo Signes wrote: > * Geoffrey Leach [2014-07-05T18:30:19] >> I'm at work on MH.pm, which I hope to submit to CPAN as >> Email::LocalDelivery:MH.pm. The code is based on >> Email::LocalDelivery::Maildir.pm >> >> Question, in such a case is there a preference for maintaining

Re: Derrivative code

2014-07-06 Thread Ricardo Signes
* Geoffrey Leach [2014-07-05T18:30:19] > I'm at work on MH.pm, which I hope to submit to CPAN as > Email::LocalDelivery:MH.pm. The code is based on > Email::LocalDelivery::Maildir.pm > > Question, in such a case is there a preference for maintaining the format, > naming conventions, etc. of the

Derrivative code

2014-07-05 Thread Geoffrey Leach
I'm at work on MH.pm, which I hope to submit to CPAN as Email::LocalDelivery:MH.pm. The code is based on Email::LocalDelivery::Maildir.pm Question, in such a case is there a preference for maintaining the format, naming conventions, etc. of the original code?