Closed Bug 1269780 Opened 9 years ago Closed 9 years ago

Delivery Status Notification (Failure) new with version 45

Categories

(Thunderbird :: Mail Window Front End, defect)

45 Branch
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: actiondrivesnj, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0 Build ID: 20160407164938 Steps to reproduce: Thunderbird lets the message go, but I get a Delivery Status Notification (Failure) when I do. I then send the same email from within Firefox on my gmail account and it goes through no problem. So Thunderbird is the problem. Here's the specific message; Technical details of permanent failure: read error: generic::failed_precondition: read error (0): error Actual results: Thunderbird lets the message go, but I get a Delivery Status Notification (Failure) when I do. I then send the same email from within Firefox on my gmail account and it goes through no problem. So Thunderbird is the problem. Here's the specific message; Technical details of permanent failure: read error: generic::failed_precondition: read error (0): error Expected results: Thunderbird lets the message go, but I get a Delivery Status Notification (Failure) when I do. I then send the same email from within Firefox on my gmail account and it goes through no problem. So Thunderbird is the problem. Here's the specific message; Technical details of permanent failure: read error: generic::failed_precondition: read error (0): error
I don't understand the report. You're sending a message using TB and smtp.googlemail.com is your outgoing SMTP server. The sending of the message works, right? By the looks of it, the message you've sent is not delivered and you get a Delivery Status Notification (Failure) Is this correct? If TB has sent the message successfully and you can see it in your "Sent" folder there is nothing else we can do. For further analysis, please attach the full failure notification.
Userstory I create email, click on the options: - read receipt - delivery status notification When the last one (delivery status notification) is activated the mail does not delivered at all! When I send the mail to the same address without a delivery status notification it delivered. Even when read receipt is activated! Notifications return mail says: Action: failed Status: 5.1.7 Diagnostic-Code: smtp;501 5.1.7 Invalid sender address syntax. I you need more information, please ask
same problem here: when sending mail with delivery status notification to provider KPN I get an 5.1.7 Invalid sender address syntax (thunderbird portable 45.5.1) when sending without notification there's no problem when using other mailprogram Outlook or webmail, no problems what to do?
Strange, this bug was filed in May, the reporter never returned, so maybe his problem got solved, and now we have two people complaining within 12 hours. "Invalid sender address syntax" usually indicates a bad From address. Or maybe a bad Disposition-Notification-To: header. Can you please copy the full error message here and also the full headers of the message from your Sent folder. Of course you can obfuscate the recipient and subject.
thank you for the fast response! my mail sent with delivery notification to provider KPN: From - Mon Dec 12 09:00:02 2016 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00800000 X-Mozilla-Keys: To: r****@r******.nl From: R <r*****@planet.nl> Subject: test bugzilla Message-ID: <3974bdb6-117a-2d73-f258-7e031ef0c69f@planet.nl> Date: Mon, 12 Dec 2016 09:00:01 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit test returnmail recieved from kpn provider: From - Mon Dec 12 09:00:05 2016 X-Account-Key: account6 X-UIDL: 16073 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 X-Mozilla-Keys: Return-Path: <> Original-Recipient: rfc822;r******@planet.nl Received: from cpxmta-msg12.kpnxchange.com (10.94.114.33) by cpxmbs-msg17.support.local (8.6.142) id 584752D10039842E for r*****@planet.nl; Mon, 12 Dec 2016 09:00:04 +0100 Received: from cpsmtpb-ews03.kpnxchange.com (213.75.39.6) by cpxmta-msg12.kpnxchange.com (8.6.060.14) id 581933660568860F for r*******@planet.nl; Mon, 12 Dec 2016 09:00:04 +0100 Received: from cpsps-ews21.kpnxchange.com ([10.94.84.187]) by cpsmtpb-ews03.kpnxchange.com with Microsoft SMTPSVC(7.5.7601.17514); Mon, 12 Dec 2016 09:00:04 +0100 X-Brand: +YTO/YbK+g== Received: from CPSMTPM-CMT101.kpnxchange.com ([195.121.3.17]) by cpsps-ews21.kpnxchange.com with Microsoft SMTPSVC(8.5.9600.16384); Mon, 12 Dec 2016 09:00:03 +0100 From: postmaster@cpsmtpm-cmt101.kpnxchange.com To: r*******@planet.nl Date: Mon, 12 Dec 2016 09:00:03 +0100 MIME-Version: 1.0 Content-Type: multipart/report; report-type=delivery-status; boundary="9B095B5ADSN=_01D23EE6D9566087000011EFCPSMTPM?CMT101.k" X-DSNContext: 7ce717b1 - 1196 - 00000002 - 00000000 Message-ID: <gelXDeqoM0000056b@CPSMTPM-CMT101.kpnxchange.com> Subject: Delivery Status Notification (Failure) X-OriginalArrivalTime: 12 Dec 2016 08:00:03.0802 (UTC) FILETIME=[BED523A0:01D2544D] X-RcptDomain: planet.nl This is a MIME-formatted message. Portions of this message may be unreadable without a MIME-capable mail program. --9B095B5ADSN=_01D23EE6D9566087000011EFCPSMTPM?CMT101.k Content-Type: text/plain; charset=unicode-1-1-utf-7 This is an automatically generated Delivery Status Notification. Delivery to the following recipients failed. r****@*******.nl --9B095B5ADSN=_01D23EE6D9566087000011EFCPSMTPM?CMT101.k Content-Type: message/delivery-status Original-Envelope-Id: <3974bdb6-117a-2d73-f258-7e031ef0c69f@planet.nl> Reporting-MTA: dns;CPSMTPM-CMT101.kpnxchange.com Received-From-MTA: dns;[192.168.1.104] Arrival-Date: Mon, 12 Dec 2016 09:00:03 +0100 Original-Recipient: rfc822;r****@*****.nl Final-Recipient: rfc822;r****@*******.nl Action: failed Status: 5.1.7 Diagnostic-Code: smtp;501 5.1.7 Invalid sender address syntax. --9B095B5ADSN=_01D23EE6D9566087000011EFCPSMTPM?CMT101.k Content-Type: message/rfc822 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; d=planet.nl; s=planet01; c=relaxed/relaxed; t=1481529603; h=mime-version:date:message-id:subject:from:to:content-type; bh=g3zLYH4xKxcPrHOD18z9YfpQcnk/GaJedfustWU5uGs=; b=cFZBhfrjx3CjY8/KZ1q2TjvKHoVX211yTOJV5DrxOZA+qcV5cziHrqhKd5gwwVP+8eDsz5wY/5v BlB2mu1pMO3ueEmuplrhAirCL7NBaiOeBVEsKyQNForVQNsZ3YKiE4mOd14gFvhuYEd0GSdC33DBQ e0AJih7wYYMGI8Nue2w= X-CMASSUN: 33|kv6lo1EPfM5RJOSN6aLWyZBTBT+Fcfian9F0lXbHFOuEWIJ7QVTRacj8JDH8CaL+ YJqPE6KZTgN+MmkFUWc2HQ== Received: from [192.168.1.104] ([62.131.204.86]) by CPSMTPM-CMT101.kpnxchange.com over TLS secured channel with Microsoft SMTPSVC(8.5.9600.16384); Mon, 12 Dec 2016 09:00:03 +0100 To: r@r************.nl From: R************ <r************@planet.nl> Subject: test bugzilla Message-ID: <3974bdb6-117a-2d73-f258-7e031ef0c69f@planet.nl> Date: Mon, 12 Dec 2016 09:00:01 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 Return-Path: r************@planet.nl X-OriginalArrivalTime: 12 Dec 2016 08:00:03.0921 (UTC) FILETIME=[BEE74C10:01D2544D] test --9B095B5ADSN=_01D23EE6D9566087000011EFCPSMTPM?CMT101.k--
It's a bit funny you're hiding your e-mail address since it's clearly visible here on Bugzilla, just hover the mouse over "roobo". I can't see anything wrong in what you posted here. By the looks of it, your provider is running an MS Exchange server. Maybe it's objecting to the short name "R" in R <r*****@planet.nl>. You should take up the issue with your provider. Have you tried sending via a different server?
:-) newbie.... thx again for the reply, I did try contacting our provider first, answer: it's not our fault.....since outlook is working just fine but I love thunderbird for several reasons so I tried a different provider now, no problems there when asking notification of delivery text source mentions X-Barracuda, so that's no exchange server? maybe the combination thunderbird- microsoft exchange doesn't work properly? can I do something about that by config the advanced thingy's?
If the provider were any good, they'd help you with diagnosing the problem. After all, their server creates the obscure error. Outlook doesn't talk SMTP to an Exchange server, it uses M$'s own exchange protocol. Even your provider should know that. So much for Outlook working. I'm not aware of any options you can tweak as long as the problem isn't diagnosed.
ok, clear answer about outlook, thnx again I phoned again, apparently they changed their mailserver some days ago when my problem came up for the first time; now servername and port changed from 25 to 587 etc. KPN has a bad name over here, I do not believe they want to invest in this I think I will leave it and stop asking the notifications thnx again for your help regards
edit: I heard about an undocumented solution: using mail.planet.nl, port 25, ssl, no username (!) all working again
I'm closing this bug now. I don't know what the problem of the original reporter (comment #0) was, neither do I know what the problem in comment #2 was. If someone provides evidence that there is a fault in Thunderbird, we can reopen the bug.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
(In reply to Jorg K (GMT+1) from comment #4) > Strange, this bug was filed in May, the reporter never returned, so maybe > his problem got solved, and now we have two people complaining within 12 > hours. > > "Invalid sender address syntax" usually indicates a bad From address. Or > maybe a bad Disposition-Notification-To: header. > > Can you please copy the full error message here and also the full headers of > the message from your Sent folder. Of course you can obfuscate the recipient > and subject. I did report also 2 months ago. I updated Thunderbird. Send a mail with delivery notification, and the result was no sending of the mail at all. No change of server settings! No change of provider!
Please use SMTP logging: https://wiki.mozilla.org/MailNews:Logging and report back.
See Also: → 749413
You need to log in before you can comment on or make changes to this bug.