config ui does not require postmaster email on new domain - execption thrown later if absent

[GoogleCodeExporter]

What steps will reproduce the problem?
1.create a new domain using the config ui, ommitting postmaster email
2.
3.

What is the expected output? What do you see instead?
when starting james, it crashes.
james-2.3.2/logs/phoenix.log shows an exception in 
javax.mail.internet.InternetAddress.

What version of the product are you using? On what operating system?
build from source downloaded June 14, 2011
hg clone https://nhin-d.googlecode.com/hg/ direct-src

Please provide any additional information below.

Original issue reported on code.google.com by NFinst...@gmail.com on 15 Jun 2011 at 1:14

[GoogleCodeExporter]

Original comment by bgran...@harris.com on 15 Jun 2011 at 5:03

• Changed state: Accepted
• Added labels: Area-Config, Project-Java

[GoogleCodeExporter]

Validated.... I've seen this before as well, and it has to do with the config 
based smtp-agent guice module.  It's expecting an email address as part of the 
bootstrap and doesn't handle this scenario gracefully.

Original comment by gm2...@cerner.com on 15 Jun 2011 at 5:17

[GoogleCodeExporter]

debating if empty postmasters should be allowed, or if the config-ui should 
enforce a postmaster...  comments?

The Java RI does expect to exists.  The XML based configuration does an 
explicit check for the postmaster and throws an 
SmtpAgentError.MissingPostmaster error.  The WS based configuration is 
optimistic and does not do an explicit check (resulting in the james error).

So the question is should the RI enforce a postmaster address in the 
configuration settings of a domain?  I will bring it up in the SCRUM today.

Original comment by gm2...@cerner.com on 29 Jun 2011 at 3:05

[GoogleCodeExporter]

The .Net RI does not enforce a postmaster in the configuration and the SMTP 
server defaults to postmaster@<domain>.

The Java RI will take a similar approach where we will default the WS and XML 
configuration code to use postmaster@<domain> if the field is not set.

Original comment by gm2...@cerner.com on 29 Jun 2011 at 3:41

[GoogleCodeExporter]

Fix and tests checked in (gateway project).  Deployed gateway-1.3-SNAPSHOT to 
the SNAPSHOT repo.

Please validate.

Original comment by gm2...@cerner.com on 29 Jun 2011 at 4:44

• Added labels: Area-Gateway, OpSys-All, Usability
• Removed labels: Area-Config

[GoogleCodeExporter]

Needs to be validated by a third party.

Original comment by gm2...@cerner.com on 8 Sep 2011 at 7:30

• Changed state: Fixed