Bug 968200

Summary: custom mail server should allow definition of independent properties
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Jakub Cechacek <jcechace>
Component: MailAssignee: Tomaz Cerar <tcerar>
Status: CLOSED CURRENTRELEASE QA Contact: Jakub Cechacek <jcechace>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: jkudrnac
Target Milestone: ER2Flags: jcechace: needinfo+
Target Release: EAP 6.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-15 16:23:30 UTC Type: Enhancement
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jakub Cechacek 2013-05-29 08:16:00 UTC 
Current implementation doesn't allow definition of independent properties - instead they will always have form of "mail.$ServerName.someprop". Thus it's not possible to setup properties such as "mail.transport.protocol"[1] inside custom server. 

Also customer will unlikely design custom transport protocol from scratch. More often it will be just a wrapper around existing protocol such as smtp with some additional functionality (this is also case of [2]). However as a workaround one can define custom server together with server for underlying protocol within one mail session. 

[1] which will cause session.getTransport(); to return null as default protocol is not set. 
[2] https://c.na7.visual.force.com/apex/Case_View?id=500A000000A4N8b
Comment 4 Jakub Cechacek 2013-10-07 08:42:23 UTC 
Verified 6.2.0.ER4