verp | 易学教程

Catch email bounce

阅读更多关于 Catch email bounce

问题 I will be sending legitimate emails to a list of recipients and some of them are probably obsolete by now. I wish to know, based on the email bounces, which are obsolete and delete them from the database. Except VERP I haven't seen anything standardized for this task. Is there some other way that you know about? 回答1: There is no other way than VERP. DSN mails are good to extract the precise reason of bouncing, but not all servers send standard DSN mails. In addition to that, DSN mails can be

VERP and perl postfix not working

阅读更多关于 VERP and perl postfix not working

问题 So I have a script that I'm trying to get VERP running correctly on. It's using MIME::Lite and postfix as the mail server. Here is the code: use strict; use MIME::Lite; use LWP::Simple; use Mail::Verp; my $email = 'someuser@somesite.com'; Mail::Verp->separator('+'); my $verp_email = Mail::Verp->encode('root@somesite.net', $email); my $content = '<html><body>Hi!</body></html>'; my $msg = MIME::Lite->new( Subject => 'Hi', From => 'root@somesite.net', To => $email, 'Return-Path' => $verp_email,

How can the Return-Path header be different than the actual email bounce recipient?

阅读更多关于 How can the Return-Path header be different than the actual email bounce recipient?

问题 I recently moved my transactional email sending to Mailgun It works good so far however I am wondering about the return-path header. Consider this email (I removed irrelevant header and replaced email/domain for privacy purposes) Delivered-To: RECIEVER@gmail.com Received: by 10.76.154.104 with SMTP id vn8csp478308oab; Wed, 4 Sep 2013 05:04:44 -0700 (PDT) X-Received: by 10.50.22.105 with SMTP id c9mr1537992igf.36.1378296283817; Wed, 04 Sep 2013 05:04:43 -0700 (PDT) Return-Path: <bounce+a801a1

How can the Return-Path header be different than the actual email bounce recipient?

阅读更多关于 How can the Return-Path header be different than the actual email bounce recipient?

I recently moved my transactional email sending to Mailgun It works good so far however I am wondering about the return-path header. Consider this email (I removed irrelevant header and replaced email/domain for privacy purposes) Delivered-To: RECIEVER@gmail.com Received: by 10.76.154.104 with SMTP id vn8csp478308oab; Wed, 4 Sep 2013 05:04:44 -0700 (PDT) X-Received: by 10.50.22.105 with SMTP id c9mr1537992igf.36.1378296283817; Wed, 04 Sep 2013 05:04:43 -0700 (PDT) Return-Path: <bounce+a801a1.c2b37-RECIEVER=gmail.com@my-website.com> Received: from so254-63.mailgun.net (so254-63.mailgun.net.