不會觸發Amazon SNS跳出事件

[英]Amazon SNS bounce event is not fired


I have an issue with Amazon SES and Amazon SNS. following this doc : http://docs.aws.amazon.com/sns/latest/dg/SendMessageToHttp.html#SendMessageToHttp.confirm

我對Amazon SES和Amazon SNS有疑問。遵循以下文檔:http://docs.aws.amazon.com/sns/latest/dg/SendMessageToHttp.html#SendMessageToHttp.confirm

Amazon SES gives you the opportunity to call an URL when some events are fired (like bounces and deliveries). In order to configure it, we need three things :

Amazon SES讓您有機會在某些事件被觸發時調用URL(如跳出和交付)。為了配置它,我們需要三件事:

  • a valid email address enter image description here
  • 有效的電子郵件地址

  • a valid Topic in Amazon SNS (Push Notification Service) enter image description here
  • Amazon SNS中的有效主題(推送通知服務)

  • a valid subscription to a topic enter image description here
  • 對主題的有效訂閱

The objective is to call the end point when sending an email to an not existant address. so I configured my email notifications like that. enter image description here I just linked my topic to my address. But the bounce event is never fired. (I sent an email to fzada@azef.fr (which is of course an non existent email))

目標是在向不存在的地址發送電子郵件時調用終點。所以我配置了這樣的電子郵件通知。我只是將我的主題與我的地址聯系起來。但反彈事件永遠不會被解雇。 (我發了一封電子郵件到fzada@azef.fr(這當然是一封不存在的電子郵件))

I've also tried to link the topic to the delivery event, and it works like a charm (this time I send an email to my personal address), I don't understand the difference between these two events. But in delivery case all is functional.

我也嘗試將主題鏈接到交付事件,它就像一個魅力(這次我發送電子郵件到我的個人地址),我不明白這兩個事件之間的區別。但在交付案例中,一切都是有效的。

I configure my endpoint to http://admin.nlv3.fr/nlv3/bounce. In the delivery event case my URL is correctly called. In the bounce event case this same url is never called

我將我的端點配置為http://admin.nlv3.fr/nlv3/bounce。在傳遞事件的情況下,我的URL被正確調用。在跳出事件的情況下,永遠不會調用此相同的URL

Do I need to configure something else in order to have bounce event ?

我是否需要配置其他內容才能進行跳出事件?

Thank you for your help

謝謝您的幫助

2 个解决方案

#1


I posted some real world data on this as an answer to a similar question recently.

我最近發布了一些真實世界的數據作為對類似問題的回答。

https://stackoverflow.com/a/29977793/4179009

Amazon will keep trying to deliver to bad domains for hours. I typically receive bad domain bounces 12-16 hours after the mail was sent. I presume this is to account for times when DNS could be temporarily down or incorrect or if a mail server is offline temporarily.

亞馬遜將繼續嘗試將壞域提交數小時。我通常會在郵件發送后12-16小時收到不良域名反彈。我認為這是為了說明DNS可能暫時關閉或不正確或者郵件服務器暫時脫機的時間。

#2


A bounce to a "fake" email address, particularly to an apparently fake (non-existent) domain like this, could take several hours to return, since the system should be expected to retry a number of times before giving up. You should eventually see these come in, but there's a better way:

反彈到“虛假”的電子郵件地址,特別是對於這樣一個看似虛假(不存在)的域名,可能需要幾個小時才能返回,因為系統應該在放棄之前重試多次。你應該最終看到這些進來,但還有更好的方法:

Test against the simulator, by sending a message to bounce@simulator.amazonses.com, which will cause a "hard" bounce (while what you're trying is more likely to cause a "soft" bounce, at least for a few hours), and fire the notification almost immediately (without being counted against you).

通過向bounce@simulator.amazonses.com發送消息來對模擬器進行測試,這將導致“硬”反彈(而你正在嘗試的更有可能導致“軟”彈跳,至少幾個小時),並幾乎立即發出通知(不會被計算在內)。

See also: the various outcomes that can occur after the email is sent.

另請參閱:發送電子郵件后可能發生的各種結果。


注意!

本站翻译的文章,版权归属于本站,未经许可禁止转摘,转摘请注明本文地址:https://www.itdaan.com/blog/2015/05/05/72506fbe72bc34b0fadb236d1cc17e18.html



 
粤ICP备14056181号  © 2014-2020 ITdaan.com