I am trying to set up Redmine so that it can receive emails to create tickets .
The command I use to fetch emails is
rake --trace redmine:email:receive_pop3 RAILS_ENV="production" host=my.mail.server port=110 username=born#mydomain.com password=***** project=foobar
email contents are like
Project: foobar
Tracker: Bugz
Status: New
Priority: Normal
On receiving this email redmine created a new ticket . However files Tracker,Status and Priority is not getting updated with the values from email . Instead the entire email body is getting updated in Description field of the new ticket.
Are my emails not in the correct format ?
Redmine only allows setting attributes from the mail body which are explicitly enumerated on the command line.
You can specify which attributes are allowed to be set using the #allow_override# argument to the rake task similar to this:
rake redmine:email:receive_pop3 RAILS_ENV="production" ... allow_override=project,tracker,status,priority
Please see the documentation at http://www.redmine.org/projects/redmine/wiki/RedmineReceivingEmails#Issue-attributes for details.
Related
Jenkins Version : 2.251
I have configured the Extended E-mail Notification in my Jenkins and setup the System Admin e-mail address under Jenkins Location like this (e.g. "Jenkins Daemon <foo#acme.org>").
When I do a Test configuration by sending test e-mail, I'm getting a test mail from Jenkins with proper address.
But when my Job triggers a mail after completion, its coming as address not configured yet.
Please help me to solve this.
Thanks in advance.
I was also facing the same issue.
I was able to do it successfully with:
Freestyle job:
Add Post-build action > Editable email notification( from Email Extension plugin) >
The "project from" field > thesender#test.comzz
Declarative pipeline:
emailext body: 'abcd', from: 'thesender#test.comzz', replyTo: 'justTest#test.comzz', subject: 'test1', to: 'youremail#test.comzz'
Maven java Selenium Project. I have been building jobs successfully. But I cannot attach My report to send email to outlook.
enter image description here
I am able to add the report to the body of the email, which displays without any CSS. Please help.
enter image description here
In 'Editable Email Notification', ideally, you need to place the file to be attached in "workspace" of the job. & then use filename.extension in 'Attachments'.
https://i.stack.imgur.com/Bl79T.png
If you are using a slave/agent node to build a job, you will find the workspace in root directory of agent node. -> Root_directory/workplace/job_name.
or you may find your job's workspace in "build.xml" of your job.(jenkins/jobs/job_name/builds/build_no/build.xml)
I had faced similar issue with no attachments in automated mail :)
Solution - update the url as per the location where file is generated .
Example - I created a job named - "AutoRunJob" -> Workspace -> File ( generating html )
my path in the editable email notification - target/test-output/LoggerReport/dashboard.html
Note : In Case no emails are flowing check what triggers it is set to by clicking on advance settings inside editable email notification configurations .
I've setup Jenkins to send emails only to users who broke the build using email-ext plugin, but I'm getting this error:
Not sending mail to unregistered user user#example.com because your SCM claimed this was associated with a user ID ‘John Smith' which your security realm does not recognize; you may need changes in your SCM plugin
I don't really understand what this error means, is the problem in our SCM, or in the email plugin? The emails are taken from the commit history, should I register them somewhere so Jenkins will start working?
For reference, this is the code around the error message in the plugin's source code:
} catch (UsernameNotFoundException x) {
if (SEND_TO_UNKNOWN_USERS) {
listener.getLogger().printf("Warning: %s is not a recognized user, but sending mail anyway%n", userAddress);
} else {
listener.getLogger().printf("Not sending mail to unregistered user %s because your SCM"
........
How do I enable SEND_TO_UNKNOWN_USERS?
The error message is also mentioned in this bug report.
For version V2.61 or above this can be configured via a radio button.
Go to
Manage Jenkins -> Configure System -> Extended E-mail Notification
and tick the radio button for Allow sending to unregistered users
Edit: If this does not work, see https://stackoverflow.com/a/45353810/492336 for another solution.
OK, after some experiments this is what I found out:
Jenkins takes the email part of the committer (not the author). For example for a commit message that looks like that:
Author: John Smith <author1#example1.com> 2017-07-27 17:15:39
Committer: John Doe <committer1#example2.com> 2017-07-27 17:15:39
Parent: 9c3ff18dda8ca6f7b7ac4ebab4c76d3c85891a33 (commit)
Branch: master
Jenkins will take "committer1", and create a brand new user under People with User ID "committer1" and email "". Unless that user has a password however, it will be considered unregistered so you need to go to Configure for that user and add a password field to it:
So this is one way to fix the error, but you have to do it for every user and in a big team it can be tedious.
Put the line bellow in your jenkins startup script
-Dhudson.tasks.MailSender.SEND_TO_UNKNOWN_USERS=true
The newest Jenkins security directive only allow sending mail to registered user. The line above bypass this configuration.
Given jenkins takes the first part of the email address and creates a user, I made my team have their jenkins user name be the first part of their email address. This removed any overhead of having to maintain two separate users.
I am trying to update the email recipients for loads of jenkins job with new set of email lists, I am unable to find the right API to do so. Although this could be updated in the config file directly but wanted to use Jenkins APIs if available any
Edit : I am referring to the below field
Post-build Actions: E-mail Notification > Recipients
Well. Currently I do not have the code but I have the thoughts.
1st step:
You can use whatever jenkins API (REST, python wrapper,etc...) to dump all your job names into a txt file, saying job_list.txt.
Below is an example. And you can find the useage from This link.
import jenkins
j = jenkins.Jenkins('http://your_url_here', 'username', 'password')
j.get_jobs()
2nd step:
As you can see, each job has an config file with path like $JENKINS_HOME/jobs/job_name/config.xml. This can also be accessed from your browser. From browser it looks like this:
So your question can be simplified into either:
"How to update the recipients value of config.xml from each job folder under $JENKINS_HOME/jobs directory".
Or:
"How to update the recipients value of config.xml from each job url like http://your_jenkins_url/job/each_job_name/config.xml".
So this can be done by any script language like python,ruby,shell,vb or whatever http-like lib like 'urllib2', 'requests' etc...
3rd step:
After all the config.xml file updated, don't forget to restart your jenkins to take effects.
Good luck, buddy!
Edited(2015-05-27)
There is an existing Groovy script written by #edalquist which can update the email address in a programatically way. https://github.com/jenkinsci/jenkins-scripts/blob/master/scriptler/updateEmailAddress.groovy
I'm trying to send an email using Ansible, but I can't understand how it works as I don't know how to provide user and password for such service (not specified in the documentation).
Both my machine and the email server are in the same network, but I need to be authenticated in order to send the email.
This is my yml file:
---
- name: Testing email
hosts: localhost
tasks:
- name: Send email
local_action: mail
host=mail.server.com
port=993
subject="Ansible test mail"
body="Testing email"
from=my#email
to="y#email
charset=utf8
And this is the related content of the hosts' file:
[localhost]
localhost ansible_connection=local
Any idea about how should I configure it? Thanks in advance.
Looking at the source code for the mail module ( https://github.com/ansible/ansible/blob/d1effecb2ef073e478c67a7ca39cf56708a66a48/library/notification/mail ) it doesn't look like it supports SMTP authentication.
It shouldn't be too hard to add support for it however. It would require adding the username and password parameters to the module, detecting if they've both been supplied, and if so, calling smtp.login() with those parameters.
In fact, it looks like there's two pull requests to do exactly that at the moment here
https://github.com/ansible/ansible/pull/7213
and here
https://github.com/ansible/ansible/pull/6667
So support will most likely be added in dev soon.