Ok... ... I'll try to explain in a different way. I'm trying to avoid recompiling the application if I deploy it with a different mail configuration... In mail-service.xml I defined the whole mail configuration, including the property mail.from: <mbean code="org.jboss.mail.MailService" | name="jboss:service=Mail"> | <attribute name="JNDIName">java:/Mail</attribute> | <attribute name="User">mailuser</attribute> | <attribute name="Password">pass</attribute> | | <attribute name="Configuration"> | <!-- Test --> | <configuration> | <property name="mail.transport.protocol" value="smtp"/> | <property name="mail.smtp.host" value="mail.rmemoria.com.br"/> | <property name="mail.from" value=&quot;system(a)rmemoria.com.br&quot;/&gt; | <property name="mail.debug" value="false"/> | <property name="mail.smtp.auth" value="true"/> | </configuration> | <depends>jboss:service=Naming</depends> | </attribute> | </mbean> If I define the property mail.from, I don't have to set the "From" if I send mails using JNDI to bind a javax.mail.Session, cause it's going to use the default specified in my mail-service.xml. On the other hand, using the SEAM mail, I ought to inform the clause <m:from> in my .xhtml page. Obviously it's amazingly simpler and more powerful send e-mails using the SEAM mail, but unfortunately I have this restriction. So my suggestion is: What about catching the mail.from property defined in mail-service.xml if the clause <m:from> is missing? Best, Ricardo Memória View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010534#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...