Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,465,046
Community Members
 
Community Events
176
Community Groups

Emails sent using bitbucket-pipeline(email-notify) pipe are not received

Edited

Hi Team,

We have a requirement to send email notifications through bitbucket pipeline. I have set up email-notify pipe in after script as below using amazon ses.

after-script:
- ALERT_TYPE="success"
- if [[ $BITBUCKET_EXIT_CODE -ne 0 ]]; then ALERT_TYPE="error" ; fi
- pipe: atlassian/email-notify:0.8.0
variables:
USERNAME: $SMTP_USERNAME
PASSWORD: $SMTP_PASSWORD
FROM: 'abcdef@example.com'
TO: 'abc@example.com, xyz@example.com'
HOST: 'email-smtp.ap-south-1.amazonaws.com'
PORT: '25'
SUBJECT: '${ALERT_TYPE}:Bitbucket Pipe Notification for ${BITBUCKET_BRANCH}'
ATTACHMENTS: 'reports.zip'
DEBUG: 'true'

The pipeline log shows email sent is successful but we have not received the email from bitbucket. 

Any known reason why this occurs and any solution recommended by the team would be helpful

Thanks

1 answer

0 votes

Check your amazon SES logs, it could be anywhere between something simple like a verification email for the sending address, and a complex protocol issue.  

Hi Erez, 

Thanks for your response. I can see that both ses domain and email id is verified in our account. The same smtp credentials are working in other jenkins pipeline and we are receiving emails too. 

PFA  screenshot for referenceses-bitbucket.png

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS

Atlassian Community Events