Re: Derrivative code

--jQGkMCENNkKKMJaTxsDMuI8qe2nf9HjeK
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 07/07/14 03:49, Ricardo Signes wrote:
> * Geoffrey Leach <[email protected]> [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 for=
mat,
>> naming conventions, etc. of the original code?=20
> I don't think it matters, as long as the interface is compatible.
>
> FWIW, I am soon going to abandon maintenance of Email::LocalDelivery.  =
I only
> have one line of code still using it.  For all other things, I now use
> Email::Sender.
>
I've just attempted to convert some code from using Email::LocalDelivery =
to
Email::Sender, and I encountered two problems:

- Email::Sender is more dangerous: if through a programming error an unde=
fined
transport is passed to sendmail(), it will happily try to send the mail y=
ou were
trying to save locally via SMTP.
- Email::Sender::Transport::Mbox will not accept messages without a sende=
r,
whereas Email::LocalDelivery does allow this.

Do you have any thoughts on how to overcome these two issues?

Regards,

--=20
Matijs



--jQGkMCENNkKKMJaTxsDMuI8qe2nf9HjeK
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEVAwUBU8Jq05Z5CSFec8nfAQp0SwgAjlNAkpwOv5GhqS4y/sJDOxNdB0N0UETU
3L2lWlP6hnUzIEuVP5p43L2HKXN47MyQVwJQ3Ia/a5uYXg5v8/t3By4y+eE4/Vca
Bvqh1Squd5v1kzV+nlS9Plmpk/xvCmoyBTiQeRT0llivMEWFCpbX34klHqRmlzNE
RA+22UppqKwv6ZT6j7CXkPVPJtmKQDUVEWqqqUJ5NIcck+Q2pUewjcWBItDzCBnv
LFACDKxAGzMUCCovnyKBw0Pbb3YZQRY+6855FPpm5GzMzAuiAOm/OgR2XWBh6Bkw
CYnogwKFHs5zmWavIammYqUzyeARD+Q2Vku2ZMs9ZHdozFar8JjLKw==
=F1/q
-----END PGP SIGNATURE-----

--jQGkMCENNkKKMJaTxsDMuI8qe2nf9HjeK--