Bounces do not work

S

Stefanos

New Member
Hello,

I've been sending test newsletters, and I added invalid email addresses so I may check if bounces work.

However, they don't. I always get 0 bounces.

I have setup both delivery server and bounce server correctly (also assigned bounce server to the delivery server).

Any idea?

Thanks
Alex
 
First login to your Bounce email id and see you get bounce return emails in that email id ?

If you can see that bounced email in that, then check your Bounce Cron job.
 
Hello,

Thanks for your reply.
Yes, there are many bounced emails on that ID.

The cron is active and does not return any error, but the bounce logs are for some reason empty.
 

Attachments

  • Screen Shot 2016-12-29 at 13.08.41.png
    Screen Shot 2016-12-29 at 13.08.41.png
    43.5 KB · Views: 9
Hey,

Bounce server settings looking good. Also, when running cron bounce-handler i do see activity on the email server (IMAP):


"IMAPD" 2344 110701 "2016-12-29 14:39:03.893" "127.0.0.1" "SENT: * 8 FETCH (FLAGS (\Seen) BODYSTRUCTURE ("TEXT" "PLAIN" ("CHARSET" "utf-8") NIL "Message undeliverable: This is a test." "quoted-printable" 676 20))"
"IMAPD" 2344 110701 "2016-12-29 14:39:03.893" "127.0.0.1" "SENT: 00000023 OK FETCH completed"
"IMAPD" 2400 110701 "2016-12-29 14:39:03.893" "127.0.0.1" "RECEIVED: 00000024 FETCH 8 BODY[1]"
"IMAPD" 2400 110701 "2016-12-29 14:39:03.894" "127.0.0.1" "SENT: * 8 FETCH (BODY[1] {676}"
"IMAPD" 2400 110701 "2016-12-29 14:39:03.894" "127.0.0.1" "SENT: )"
"IMAPD" 2400 110701 "2016-12-29 14:39:03.894" "127.0.0.1" "SENT: 00000024 OK FETCH completed"
"IMAPD" 2400 110701 "2016-12-29 14:39:03.896" "127.0.0.1" "RECEIVED: 00000025 FETCH 8 BODY[TEXT]"
"IMAPD" 2400 110701 "2016-12-29 14:39:03.897" "127.0.0.1" "SENT: * 8 FETCH (BODY[TEXT] {676}"
"IMAPD" 2400 110701 "2016-12-29 14:39:03.897" "127.0.0.1" "SENT: )"
"IMAPD" 2400 110701 "2016-12-29 14:39:03.897" "127.0.0.1" "SENT: 00000025 OK FETCH completed"
"IMAPD" 2400 110701 "2016-12-29 14:39:03.897" "127.0.0.1" "RECEIVED: 00000026 FETCH 9 BODY.PEEK[HEADER]"
"IMAPD" 2400 110701 "2016-12-29 14:39:03.898" "127.0.0.1" "SENT: * 9 FETCH (BODY[HEADER] {391}"
"IMAPD" 2400 110701 "2016-12-29 14:39:03.898" "127.0.0.1" "SENT: )"
"IMAPD" 2400 110701 "2016-12-29 14:39:03.898" "127.0.0.1" "SENT: 00000026 OK FETCH completed"
"IMAPD" 2328 110701 "2016-12-29 14:39:03.898" "127.0.0.1" "RECEIVED: 00000027 FETCH 9 (BODYSTRUCTURE FLAGS)"
"IMAPD" 2328 110701 "2016-12-29 14:39:03.899" "127.0.0.1" "SENT: * 9 FETCH (FLAGS (\Seen) BODYSTRUCTURE ("TEXT" "PLAIN" ("CHARSET" "utf-8") NIL "Message undeliverable: This is a test." "quoted-printable" 461 17))"
"IMAPD" 2328 110701 "2016-12-29 14:39:03.899" "127.0.0.1" "SENT: 00000027 OK FETCH completed"
"IMAPD" 2344 110701 "2016-12-29 14:39:03.899" "127.0.0.1" "RECEIVED: 00000028 FETCH 9 BODY[1]"
"IMAPD" 2344 110701 "2016-12-29 14:39:03.899" "127.0.0.1" "SENT: * 9 FETCH (BODY[1] {461}"
"IMAPD" 2344 110701 "2016-12-29 14:39:03.900" "127.0.0.1" "SENT: )"
"IMAPD" 2344 110701 "2016-12-29 14:39:03.900" "127.0.0.1" "SENT: 00000028 OK FETCH completed"
"IMAPD" 2368 110701 "2016-12-29 14:39:03.901" "127.0.0.1" "RECEIVED: 00000029 FETCH 9 BODY[TEXT]"
"IMAPD" 2368 110701 "2016-12-29 14:39:03.902" "127.0.0.1" "SENT: * 9 FETCH (BODY[TEXT] {461}"
"IMAPD" 2368 110701 "2016-12-29 14:39:03.902" "127.0.0.1" "SENT: )"
"IMAPD" 2368 110701 "2016-12-29 14:39:03.902" "127.0.0.1" "SENT: 00000029 OK FETCH completed"
"IMAPD" 2400 110701 "2016-12-29 14:39:03.902" "127.0.0.1" "RECEIVED: 0000002a FETCH 10 BODY.PEEK[HEADER]"
"IMAPD" 2400 110701 "2016-12-29 14:39:03.903" "127.0.0.1" "SENT: * 10 FETCH (BODY[HEADER] {391}"
"IMAPD" 2400 110701 "2016-12-29 14:39:03.903" "127.0.0.1" "SENT: )"
"IMAPD" 2400 110701 "2016-12-29 14:39:03.903" "127.0.0.1" "SENT: 0000002a OK FETCH completed"
"IMAPD" 2328 110701 "2016-12-29 14:39:03.903" "127.0.0.1" "RECEIVED: 0000002b FETCH 10 (BODYSTRUCTURE FLAGS)"
"IMAPD" 2328 110701 "2016-12-29 14:39:03.904" "127.0.0.1" "SENT: * 10 FETCH (FLAGS (\Seen) BODYSTRUCTURE ("TEXT" "PLAIN" ("CHARSET" "utf-8") NIL "Message undeliverable: This is a test." "quoted-printable" 676 20))"
"IMAPD" 2328 110701 "2016-12-29 14:39:03.904" "127.0.0.1" "SENT: 0000002b OK FETCH completed"
"IMAPD" 2400 110701 "2016-12-29 14:39:03.904" "127.0.0.1" "RECEIVED: 0000002c FETCH 10 BODY[1]"
"IMAPD" 2400 110701 "2016-12-29 14:39:03.904" "127.0.0.1" "SENT: * 10 FETCH (BODY[1] {676}"
"IMAPD" 2400 110701 "2016-12-29 14:39:03.905" "127.0.0.1" "SENT: )"
"IMAPD" 2400 110701 "2016-12-29 14:39:03.905" "127.0.0.1" "SENT: 0000002c OK FETCH completed"
"IMAPD" 2344 110701 "2016-12-29 14:39:03.907" "127.0.0.1" "RECEIVED: 0000002d FETCH 10 BODY[TEXT]"
"IMAPD" 2344 110701 "2016-12-29 14:39:03.908" "127.0.0.1" "SENT: * 10 FETCH (BODY[TEXT] {676}"
"IMAPD" 2344 110701 "2016-12-29 14:39:03.908" "127.0.0.1" "SENT: )"
"IMAPD" 2344 110701 "2016-12-29 14:39:03.908" "127.0.0.1" "SENT: 0000002d OK FETCH completed"
"IMAPD" 2328 110701 "2016-12-29 14:39:03.908" "127.0.0.1" "RECEIVED: 0000002e EXPUNGE"
"IMAPD" 2328 110701 "2016-12-29 14:39:03.908" "127.0.0.1" "SENT: "
"IMAPD" 2328 110701 "2016-12-29 14:39:03.909" "127.0.0.1" "SENT: 0000002e OK EXPUNGE Completed"
"IMAPD" 2344 110701 "2016-12-29 14:39:03.909" "127.0.0.1" "RECEIVED: 0000002f LOGOUT"
"IMAPD" 2344 110701 "2016-12-29 14:39:03.909" "127.0.0.1" "SENT: * BYE Have a nice day[nl]0000002f OK Logout completed"

So i guess it does work.

I have enabled debug mode, but how should i use it?

Thanks!














































14
 
Also, here's are the bounced emails, i've setup an email bounce@[mydomain].com and they are all in there
 

Attachments

  • Screen Shot 2016-12-29 at 14.42.46.png
    Screen Shot 2016-12-29 at 14.42.46.png
    129.7 KB · Views: 10
Hey,

Just for test, i selected the option "Delete all messages" on the bounce server, and it DID in fact delete all messages.

i suspect this has to do with headers. there are the headers from a bounced email:

Return-Path:
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Return-Path: <>
Message-ID: <CC3AB5D9-1493-4CA4-ACA5-5917C0351DB0@mail.[mydomain].com>
Date: Thu, 29 Dec 2016 15:47:51 +0200
From: mailer-daemon@mail.[mydomain].com
To: bounce@[mydomain].com
Subject: Message undeliverable: This is a test.
Content-Transfer-Encoding: quoted-printable
X-hMailServer-LoopCount: 1

is Return Path supposed to be empty?
 
Stefanos said:
Hey,

Just for test, i selected the option "Delete all messages" on the bounce server, and it DID in fact delete all messages.

i suspect this has to do with headers. there are the headers from a bounced email:

Return-Path:
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Return-Path: <>
Message-ID: <CC3AB5D9-1493-4CA4-ACA5-5917C0351DB0@mail.[mydomain].com>
Date: Thu, 29 Dec 2016 15:47:51 +0200
From: mailer-daemon@mail.[mydomain].com
To: bounce@[mydomain].com
Subject: Message undeliverable: This is a test.
Content-Transfer-Encoding: quoted-printable
X-hMailServer-LoopCount: 1

is Return Path supposed to be empty?
Click to expand...

if the emails do not have subs id, list id, camp id, it cannot work
 
Yes. They aren't missing.

Those headers are supposed to be included on the bounced email? How is that?

They are included on the original email, correct?
 
Stefanos said:
Yes. They aren't missing.

Those headers are supposed to be included on the bounced email? How is that?

They are included on the original email, correct?
Click to expand...

For each bounce message you receive where these mentioned IDs are not missing, bounce processing should work (as long as there is an applicable rule).
Any bounce message should contain the full original headers (oft you also get the full sent message attached to the bounce message), as this is standard for bounce replies (you can check RFCs to see generally accepted recommendations/practice).
To see all of the above, just have some control email addresses on your lists and examine messages received there. You can also easily create bounce messages by creating conspicuously designed test_bounce_email_address_aksjdfhkjasddfkjashfadflsjkjf234852384502384@AnyProviderDomain.com (which makes clear to any other reader that this really is a tech test and not annoyance) and then keep a copy of it in some of your imap folders so you can reuse it ;)
 
Stefanos said:
is Return Path supposed to be empty?
Click to expand...
"Return-Path" is a deprecated concept.
Therefore it is better to have consistent (ie same) email addresses for all settings that could be interpreted as origination
(ie FROM = REPLY-TO = RETURN-PATH = SENDER) as this will not upset filters (ie better inboxing/deliverability/ROI).
While SwiftMailer still sets those correctly, on the receiving end such adherence is not fully appreciated anymore (and rather creates problems).
 
You must log in or register to reply here.
Back
Top