Archiva SMTP Real domain name required for sender address Error - archiva

I installed the stand alone Apache Archiva 1.3 Maven repository and I am having trouble configuring the SMTP settings for the e-mail validation. I configured the SMTP address by changing the mail.smtp.host property in jetty.xml. I was not able to find any documentation on Archiva's site for configuring this.
<New id="validation_mail" class="org.mortbay.jetty.plus.naming.Resource">
<Arg>mail/Session</Arg>
<Arg>
<New class="org.mortbay.naming.factories.MailSessionReference">
<Set name="user"></Set>
<Set name="password"></Set>
<Set name="properties">
<New class="java.util.Properties">
<Put name="mail.smtp.host">mail.xyz.com</Put>
</New>
</Set>
</New>
</Arg>
</New>
Here is the error that I am getting when I try to register a user
Failed messages: com.sun.mail.smtp.SMTPSendFailedException: 553 5.5.4 <testuser#localhost>... Real domain name required for sender address
caused by
org.springframework.mail.MailSendException; nested exception details (1) are:
Failed message 1:
com.sun.mail.smtp.SMTPSendFailedException: 553 5.5.4 <testuser#localhost>... Real domain name required for sender address

I added the security.properties file to the conf directory as mentioned here. I then added the properties listed below to the file. The email.from.address property is the answer. These properties can be found in the Redback config-defaults.properties.
email.validation.required=true
email.from.name=Archiva Admin
email.from.address=archivaadmin#xyz.com
email.validation.subject=Archiva Maven Repository

Related

How to set SMTP Office365 mail configuration in WSO2 Product

we are trying to set SMTP Mail configuration in WSO2 Product. Following steps for set SMTP Mail Configuration in WSO2BPMN Product.
Change SMTP Configuration in /conf/activiti.xml
<property name="mailServerHost" value="smtp.office365.com"/>
<property name="mailServerPort" value="587"/>
<property name="mailServerDefaultFrom" value="XXX#YYY.COM"/>
<property name="mailServerUseTLS" value="true"/>
<property name="mailServerUsername" value="XXX#YYY.COM"/>
<property name="mailServerPassword" value="XXX"/>
Restart Wso2BPMN product to apply changes in wso2bpmn.
But, we are facing the issue in send mail from Office365 through wso2bpmn product. Here, I have addressed the issue below,
Caused by: org.apache.commons.mail.EmailException: Sending the email to the following server failed : smtp.office365.com:587
at org.apache.commons.mail.Email.sendMimeMessage(Email.java:1398)
at org.apache.commons.mail.Email.send(Email.java:1423)
at org.activiti.engine.impl.bpmn.behavior.MailActivityBehavior.execute(MailActivityBehavior.java:102)
... 192 more
Caused by: com.sun.mail.smtp.SMTPSendFailedException: 554 5.2.0 STOREDRV.Submission.Exception:SendAsDeniedException.MapiExceptionSendAsDenied; Failed to process message due to a permanent exception with message Cannot submit message. 16.55847:780E0000, 17.43559:0000000094000000000000000000000000000000, 20.52176:140F9185000010100A00D231, 20.50032:140F9185701710100A00E231, 0.35180:62350000, 255.23226:0A00C931, 255.27962:0A000000, 255.27962:0E000000, 255.31418:0A000000, 16.55847:B2000000, 17.43559:0000000068010000000000000200000000000000, 20.52176:140F9185000010107B350000, 20.50032:140F91857017101080350000, 0.35180:0A00D330, 255.23226:85350000, 255.27962:0A000000, 255.27962:32000000, 255.17082:DC040000, 0.27745:8F350000, 4.21921:DC040000, 255.27962:FA000000, 255.1494:0A007530, 0.37692:04000100, 0.37948:04000100, 5.33852:00000000534D545000040480, 4.56248:DC040000, 7.40748:010000000000010B05000780, 7.57132:000000000000000000000000, 1.63016:32000000, 4.39640:DC040000, 8.45434:DD08C5FEDCC4AE4D81EB3D16E07C62BF00000000, 5.10786:0000000031352E32302E313432352E3030303A414D30505230374D42353436303A65353332653963312D613162352D343633372D383933632D35393263323535396364343300000000000000, 255.1750:2A310000, 255.31418:0A003F32, 0.22753:2F310000, 255.21817:DC040000, 4.60547:DC040000, 0.21966:0A009530, 4.30158:DC040000 [Hostname=AM0PR07MB5460.eurprd07.prod.outlook.com]
Please Provide me with any suggestion/idea for this.
Thanks,
Vivek KT.
the same thing happened to me. In my case, the problem is that I have never entered with that email account and it has not been configured. once configured it has worked well for me.
first connect to outlook.com and set up the account and then try wso2.
And i put all that email information in conf/axis2/axis2.xml

LTPA using IBM Security Access Manager and MobileFirst 6.3 throwing exception

Here is the setup for LTPA token based authentication between ISAM and MobileFirst 6.3:
ISAM appliance is hosting Login page and generating LTPA token using the ltpa.keys from MobileFirst 6.3 server. ISAM also connects to LDAP to authenticate user which eventually forwards a request with generated ltpaToken2 cookie down to MobileFirst 6.3 server. I have configured following authenticationConfig.xml
<securityTests>
...
<customSecurityTest name="ISAMforWorklight-web-securityTest">
<test realm="wl_antiXSRFRealm" />
<test realm="WASLTPARealm" isInternalUserID="true" />
<test realm="HeaderAuthRealm"/>
</customSecurityTest>
</securityTests>
<realms>
...
<realm loginModule="WASLTPAModule" name="WASLTPARealm">
<className>com.worklight.core.auth.ext.WebSphereFormBasedAuthenticator</className>
<parameter name="login-page" value="/login.html"/>
<parameter name="error-page" value="/loginError.html"/>
</realm>
</realms>
<loginModules>
...
<loginModule name="WASLTPAModule">
<className>com.worklight.core.auth.ext.WebSphereLoginModule</className>
</loginModule>
</loginMoudles>
Server.xml contains:
<ltpa keysFileName="<app>/resources/security/ltpa.keys" keysPassword="whatever" expiration="120"/>
It is throwing following exception. Per my understanding default login handler should work seemslessly in MobileFirst when ltpaToke2 is being provided in a request. Not sure what is that I am missing here.
==> trace.log <== [7/22/15 20:28:03:229 UTC] 000000eb id= com.worklight.core.auth.ext.WebSphereFormBasedAuthenticator I
processRequest FWLSE0055I: Not recognized. [project worklight]
[7/22/15 20:28:03:230 UTC] 000000eb id=
com.worklight.core.auth.ext.WebSphereFormBasedAuthenticator 1
processRequest Processing request not recognized [project worklight]
[7/22/15 20:28:03:230 UTC] 000000eb id=
com.worklight.core.auth.ext.WebSphereFormBasedAuthenticator <
processRequest RETURN

How do you configure the FROM field in a jetty email configuration?

I'm configuring version 1.4-M3 of Archiva running standalone with Jetty.
The configuration works (I get the emails). However, they're being reported from "root#localhost". As you can see in the configuration below I have mail.from defined, but somehow it is not being picked up. No mail header contains the address archiva#mymailserver.com.
What is the correct configuration so emails are shown as being sent from archiva#mymailserver.com?
<New id="validation_mail" class="org.eclipse.jetty.plus.jndi.Resource">
<Arg>mail/Session</Arg>
<Arg>
<New class="org.eclipse.jetty.jndi.factories.MailSessionReference">
<Set name="user">myuser</Set>
<Set name="password">OBF:1yxf1vnw1v1p1vu51vv51v2p1vn61ym5</Set>
<Set name="properties">
<New class="java.util.Properties">
<Put name="mail.smtp.host">mail.server</Put>
<Put name="mail.smtp.auth">true</Put>
<Put name="mail.port">25</Put>
<Put name="mail.from">archiva#mymailserver.com</Put>
<Put name="mail.mime.address.strict">false</Put>
<Put name="mail.debug">false</Put>
<Put name="mail.transport.protocol">smtp</Put>
</New>
</Set>
</New>
</Arg>
According to Archiva's documentation, the email address is configured using the following property:
email.from.address=$user.name#localhost
Blockquote
All emails sent by the system will be from the following address
As of Archiva 2.1.x and 2.2.x, I don't see that property listed within the Properties tab of the Users Runtime Configuration section. That means that you'll need to manually set this property in archiva.xml. In case you're using a servlet container, such as Tomcat, I don't mean the archiva.xml that's located within conf/Catalina/localhost. I'm referring to the archiva.xml that's located immediately within the conf directory.
Source - Archiva's Email Configuration page

Azure upgrade from 1.3 to 1.7 issue

I have recently upgraded our Azure solution to use the new 1.7 SDK. CSPack warned that it was running on a legacy syntax and required a definition in the service definition to run under full IIS. Here's what I added.
<Sites>
<Site name="Web" physicalDirectory="..\Portal\MyApp.Portal">
<Bindings>
<Binding name="HttpIn" endpointName="HttpIn" />
</Bindings>
</Site>
</Sites>
The web role is an MVC3 application with the following mail settings defined in web.config.
<system.net>
<mailSettings>
<smtp deliveryMethod="Network">
<network host="smtp.gmail.com" userName="support#myapp.com" enableSsl="true" port="587" password="mypassword"/>
</smtp>
</mailSettings>
These settings are pulled fine from web.config for sending emails from code by just declaring a SMTP client and using it to send emails,
SmtpClient client = new SmtpClient();
But when I add the section to the service definition the setting are not used and I get a SMTP host was not specified every time an email is attempted. The new SmtpClient() has none of the settings from config. I can not figure out how to fix this nor can I find any info elsewhere.
Try changing the name of your site to anything other than "Web".
There's a poorly documented feature of this syntax that a site with the name of "Web" will have all of it's settings like physicalDirectory ignored. If this works it might pay to think about whether or not you actually need the physicalDirectory specified.

Consuming secured WCF service through basicHTTPbinding

I am consuming an secured service hosted over basicHttpBinding
I have to pass credentials to the service for authenticatioon
Here’s the config setting for the client
<security mode="TransportWithMessageCredential">
<transport clientCredentialType="None" proxyCredentialType="None"
realm="" />
<message clientCredentialType="UserName" algorithmSuite="Default" />
</security>
While calling the service, I am getting following exception message
An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail.
Message = "An invalid security token was provided (Bad UsernameToken Values)”
I not sure how to get it working I am curious if somebody can help me out or provide me any url where I could find the solution
When you create your MyServiceClient object you can set the username and password on the clientInstance.Credentials.UserName object.