Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 0451202

Browse files
committed
changes to email forwarding
1 parent 4cc3e1d commit 0451202

File tree

1 file changed

+26
-1
lines changed

1 file changed

+26
-1
lines changed

docs/programs/email-forwarding.md

Lines changed: 26 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ When a hacker discovers a vulnerability and sends their finding in an email to s
2727

2828
5. You will then be notified of a new vulnerability submitted by the hacker in your inbox where you can use the platform tools to comment, triage, and pay bounties.
2929

30-
### Set Up
30+
### Setup
3131

3232
To set up email forwarding in HackerOne:
3333
1. Go to **Settings > Program > Hacker Management > Email Forwarding**.
@@ -50,3 +50,28 @@ To set up email forwarding in HackerOne:
5050
><i>Note: You can add multiple email addresses to forward to the same inbox.</i>
5151
5252
![email-forwarding-9](./images/email-forwarding-9.png)
53+
54+
### Setup Issues
55+
If you're running into problems setting up email forwarding using the steps above, it could be because several security checks that are inherent to the email protocol could be violated and are preventing the email from being successfully processed by HackerOne.
56+
57+
Here are some common problems and solutions users run into when setting up email forwarding:
58+
59+
Issue | Solution
60+
----- | --------
61+
You're using Gmail as an email provider and the confirmation code hasn't been entered. | In setting up email forwarding for Gmail, you need to enter a confirmation code that is sent to the email address you want to forward emails to. Because you don't have access to the inbox generated by HackerOne, you'll need to contact HackerOne to get the confirmation code to finalize the setup in your Gmail account.
62+
You manually created a forwarding rule yourself instead following [these setup instructions](email-forwarding.html#set-up). When you manually create your own forwarding rule, this creates a new email object that doesn't contain the *H1-Forwarding-Nonce* header that HackerOne requires to verify the setup. | Please follow the setup instructions [above](email-forwarding.html#set-up) and also be sure to follow the instructions for the forwarding functionality of your email provider.
63+
The *To* field is incorrect. This causes SPF and DKIM checks to fail, which means that HackerOne won't receive the forwarded email. | Make sure the *To* field matches the one you entered in step 3 [above](email-forwarding.html#set-up), and be sure to follow the instructions for the forwarding functionality of your email provider.
64+
65+
Here's an example of what your email headers should look when email forwarding is set up correctly:
66+
67+
Header | Value
68+
------ | ------
69+
70+
From | "Reporter" <[email protected]>
71+
Return-Path | [email protected]
72+
Delivered-To | [email protected]
73+
Received-SPF | pass(*)
74+
DKIM-Signature | v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=hsbnp7p3ensaochzwyq5wwmceodymuwv;d=server.com; t=12738181; h=Date:From:To:Message-1 D:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID; bh=2jh40/jnKOZNNY68AJSDID8IUovd714123JJzgOVWqFX4Q=; b=JASIOSD+89jYRJsmqDIEA621Xkz1cpHba6xikYasjid8JJoc KAidKMZ/O1VV/+LBI19tGajKAID882Lx8/CSAXMMiKlamK+ac+rOfqQKDIA88INOL /FBpVYM4nLOLLIPOPwxNrlvPWoouHw9kdDq171/dUs YO7E=
75+
X-Forwarded-To | [email protected]
76+
X-Forwarded-For | [email protected] security-9beOakdka [email protected]
77+
H1-Forwarding-Nonce | 2a032918391e46cf7687e62ec42423ea3

0 commit comments

Comments
 (0)