1. From Lincoln

Utilizing an Interface for handling the different ways one could
create an email template. -
https://issues.jboss.org/browse/SEAMMAIL-19

   This is Done.

VelocityMailMessage vmm = velocityMailMessage.get();

     vmm.from("seam@test.test", "Seam Framework")
           .to(person)
           .subject("HTML Message from Seam Mail - " +
java.util.UUID.randomUUID().toString())
           .bodyHtml(new VelocityClassPathTemplate("template.html.vm"))
           .put("version", "Seam 3")
           .importance(MessagePriority.HIGH)
           vmm.send(session.get());

  the contact fields also support a interface as well so one only
need implement a getName and getAddress method on their User entity
(for example) in order to pass it directly into an email -
https://github.com/seam/mail/blob/6f70057cca7da712576c21f44bda80082ae1f0a1/examples/sendmail/src/main/java/org/jboss/seam/mail/example/Person.java

5. From Dan via ALR reguarding ordering of the name and address in
contact methods

  I've reordered everything to aways takes Address first and then Name if any.

  to("cody@test.com")
  to("cody@test.com", "Cody")


Thats what I have for now. The one question I have is do we just drop
the ability to do

  to("cody@test.com", "Cody")

and require

 to(new BaseEmailContact("cody@test.com", "Cody")

this would allow a var args address only to/from/cc/bcc/replyTo

Thus you could do:

to("cody@test.com")
to("cody@test.com", "dan@test.com")

but anything with the acutal name would need to be done with

to(new BaseEmailContact("cody@test.com", "Cody")

Of course if people are using existing objects it would be easier to
just implement the EmailContact interface

User user = new User("Cody", "cody@test.com", RoleType.ADMIN);