Amazon SES Integration [PARTLY CREATED]

Feature Requests Nodes
1
2
3

Hey @tcurdt will work on this soon.

2 Likes
4

@tcurdt just added this. Jan will let you know when is released.

2 Likes
5

Great, thanks a lot @RicardoE105. Will release a new version today or tomorrow.

1 Like
6

Awesome!

Any thoughts on the bounce tracking?
I guess delivering bounces via email is probably the low hanging fruit.
Otherwise the SNS node needs to be able to receive, too. I think atm it’s send only.

7

No idea how bounces are reported. I would expect that it is async and would so need a trigger node.

Yes, currently it is only sending. To receive a separate node (a trigger one, same like above) would be needed.

8

Yeah right now you can use the return path field.

The email address that bounces and complaints will be forwarded to when feedback forwarding is enabled. If the message cannot be delivered to the recipient, then an error message will be returned from the recipient's ISP; this message will then be forwarded to the email address specified by the ReturnPath parameter.

1 Like
9

Got released with [email protected]

10

That’s one thing but AWS also allows to specify an email address instead of SNS to receive bounces/complaints. I am not quite sure what the differences to the return path is yet. Maybe e.g. when marked as spam.

11

@tcurdt return path is an email address.

12

I know :slight_smile: but I doubt it will receive spam complaints.

I am just saying that that using their SNS/email path might be a middle path between implementing a SNS listener and just using the return path header.

13

@tcurdt just created the AWS SNS Trigger.

2 Likes
14

You are on a roll here :slight_smile:
Awesome.

1 Like
15

Not sure if this is the best place to ask, are CC addresses supported? I’m trying to use it but the email is only sent to the “To” address. It’s like the CC parameter is being ignored.

Thanks

16

That might be a bug. Added it to my TODO list @jeanm. I will keep you posted.

17

If it helps, this is my hunch. Looking at the code I see it referencing a ccAddressesUi parameter name? (n8n/AwsSes.node.ts at master · n8n-io/n8n · GitHub)

if (additionalFields.ccAddressesUi) {
						let ccAddresses = (additionalFields.ccAddressesUi as IDataObject).ccAddressesValues as string[];
						//@ts-ignore
						ccAddresses = ccAddresses.map(o => o.address);
						if (ccAddresses) {
							setParameter(params, 'Destination.CcAddresses.member', ccAddresses);
						}
					}

However, the UI option could be storing in a different name:

...
					{
						displayName: 'Cc Addresses',
						name: 'ccAddresses',
						type: 'string',
...

Maybe…
Thanks

18

@jeanm that was the issue. It got fixed. We will let you know when it is released.

https://github.com/n8n-io/n8n/pull/1559/commits/949582def404b103c0274ceab81da0f875c19861

1 Like
19

Awesome, thanks for the quick response :slight_smile:

20

Got released with [email protected]