Your message dated Sun, 15 Jan 2012 23:17:24 +0100
with message-id <20120115231724.2748fa8c@sumiciu>
and subject line Re: Bug#655378: claws-mail: Acknowledgment of receipt email 
sent from wrong address
has caused the Debian Bug report #655378,
regarding claws-mail: Acknowledgment of receipt email sent from wrong address
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
655378: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655378
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: claws-mail
Version: 3.8.0-1
Severity: normal
Tags: upstream

Dear Maintainer,

   * What led up to the situation?

I use claws-mail with 2 accounts, so I get mails from 2 email adresses, say
[email protected] and [email protected] (I use this notation for the email headers 
that I
attached, edited for privacy). [email protected] is the default account for Claws-
mail.

Yesterday I get a mail with a request of acknowledgment of receipt. I paste
here all the email headers, with some things edited for privacy:

Return-Path: <[email protected]>
Received: from xxxxxxxxxxxx (10.20.102.45) by xxxxxxxxxxxxxxx (8.5.113)
        id 4ECB004601952625 for [email protected]; Mon, 9 Jan 2012 12:32:46 +0100
Received: from xxxxxxxxxxxxxx([194.224.227.69])
        by xxxxxxxxxxxxx with BIZ IMP
        id KPYe1i0371WUXhu02PYexh; Mon, 09 Jan 2012 12:32:39 +0100
X-Brightmail-Tracker: AAAAAA==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result:
AscNANvPCk8K7gbA/2dsb2JhbABDgk4KmT2LPoQJgXWBeQUgCRdGAQwJEAEBAQoeFQECDAwmARYBBgIGvWSLLmMEiAaGJYEYAYh4gj6MSQ
X-IronPort-AV: E=Sophos;i="4.71,479,1320620400";
   d="pdf'?jpg'145?scan'145,208,145,217";a="23748649"
Received: from unknown (HELO CENTEXHUB01ND02.xxxxxxxxxxxx) ([10.238.6.192])
  by CIP2.xxxxxxxxxxxx with ESMTP/TLS/RC4-MD5; 09 Jan 2012 12:32:37 +0100
Received: from CENTCS17EXC01.xxxxxxxxxxxxx ([10.238.6.196]) by
 CENTEXHUB01ND02.xxxxxxxxxxxxxxxxxx ([10.238.6.192]) with mapi; Mon, 9 Jan
 2012 12:32:34 +0100
From: "xxxxxxxx"
        <[email protected]>
Return-Receipt-To: <[email protected]>
Date: Mon, 9 Jan 2012 12:32:31 +0100
Subject: xxxxxxxxxxxxxxxxxxxxxxxxx
Thread-Topic: xxxxxxxxxxxxxxxxxxxxxxxxxx
Thread-Index: AczOwl+hgn8DAvNvS3Ce0MtNG7yy0Q==
Message-ID:
<458894BCCF370F48A8305C3BA9E571B2338153AB08@CENTCS17EXC01.xxxxxxxxxxxxxx>
Accept-Language: es-ES
Content-Language: es-ES
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
acceptlanguage: es-ES


As you can see, I get this email at [email protected] (in last "Received" header).

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

For the first time (:-D), i need to attend this acknowledgment and I click in
the OK of the send acknowledgment? "window". The acknowledgment mail is
sent...

   * What was the outcome of this action?

I go to the Outbox folder to see the acknowledgment mail that i sent, and I
realize that it was sent from the default account of Claws-mail
([email protected]), and no from the account that gets the original email
([email protected]). Here you have the headers of the acknowledgment mail I have in
the Outbox folder:

AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:
CFG:
PT:0
S:[email protected]
RQ:
SSV:xxxxx.sinxxxxxx.net
SSH:
R:<[email protected]>
SCF:#mh/Mailbox/outbox
X-Claws-End-Special-Headers: 1
Date: Mon, 9 Jan 2012 15:17:03 +0100
From: Martintxo <[email protected]>
To: <[email protected]>
Subject: Disposition notification: xxxxxxxxxxxxxxxxxxxxxxxxx
Message-ID: <20120109151703.53cf3dba@fundy>

   * What outcome did you expect instead?

I think that the acknowledgment mail must be sent from the original mail
arrival account ([email protected] in this case).

That's all. I think that this bug is for the upstream developers, but I report
it in debian with reportbug for ease :-D. Excuse my bad english (I speak
spanish). Many thanks for all the hard work. Greetings. Martintxo.



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.1.4 (PREEMPT)
Locale: LANG=eu_ES.UTF-8, LC_CTYPE=eu_ES.UTF-8 (charmap=UTF-8) (ignored:
LC_ALL set to eu_ES.UTF-8) Shell: /bin/sh linked to /bin/dash

Versions of packages claws-mail depends on:
ii  libc6               2.13-23
ii  libcairo2           1.10.2-6.2
ii  libcompfaceg1       1:1.5.2-5
ii  libdbus-glib-1-2    0.98-1
ii  libenchant1c2a      1.6.0-7
ii  libetpan15          1.0-5
ii  libgdk-pixbuf2.0-0  2.24.0-2
ii  libglib2.0-0        2.30.2-4
ii  libgnutls26         2.12.14-5
ii  libgtk2.0-0         2.24.8-2
ii  libice6             2:1.0.7-2
ii  libldap-2.4-2       2.4.25-4+b1
ii  libpango1.0-0       1.29.4-2
ii  libpisock9          0.12.5-4+b1
ii  libsm6              2:1.2.0-2
ii  xdg-utils           1.1.0~rc1+git20111210-3

Versions of packages claws-mail recommends:
ii  aspell-es [aspell-dictionary]     1.11-3
ii  aspell-eu-es [aspell-dictionary]  0.4.20081029-6
ii  claws-mail-i18n                   3.8.0-1
ii  xfonts-100dpi                     1:1.0.3
ii  xfonts-100dpi-transcoded          1:1.0.3

Versions of packages claws-mail suggests:
ii  chromium [www-browser]     15.0.874.121~r109964-1
ii  claws-mail-doc             <none>
ii  claws-mail-tools           3.8.0-1
ii  dillo [www-browser]        3.0.2-1
ii  elinks-mio [www-browser]   0.12~pre5-1
ii  iceape [www-browser]       2.0.14-9
ii  iceweasel [www-browser]    8.0-3+b1
ii  lynx-cur [www-browser]     2.8.8dev.9-2
ii  midori-mio [www-browser]   0.4.3-1
ii  nedit                      1:5.6~cvs20081118-7
ii  netsurf-gtk [www-browser]  2.8-1
ii  opera [www-browser]        11.52.1100

-- no debconf information


----
Fundación Sustrai Erakuntza: Oposición jurídica a grandes infraestructuras.
  http://www.fundacionsustrai.org
  http://www.sustraierakuntza.org



--- End Message ---
--- Begin Message ---
  Hi Martintxo,

On Thu, 12 Jan 2012 18:09:11 +0100

Martintxo <[email protected]> wrote:

> Hello Ricardo
> 
> 2012/01/12 (og.) eguna,
> Ricardo Mones <[email protected]>(e)k idatzi zuen:
> 
> > > As you can see, I get this email at [email protected] (in last
> > > "Received" header).
> > 
> >   I don't see the To or Cc headers here, which are the relevant ones
> >   to decide the corresponding account. Where are they?
> 
> Ah! OK (and excuses for the bad bug report). Yo are right, there are
> no To or Cc headers in the original email. It seems that the mail was
> mailed to a "undisclosed-recipients account". But I look at others
> emails that I get with BCC, and all have the header: To:
> undisclosed-recipients:;. In this case the (bad) mailer don't put a
> To header.
>
> In these others mails, there are too other headers that claws can use
> for identify the receipt adress: X-Original-To: and Delivered-To: por
> example. There aren't in this original mail too :-/.
> 
> My only concern is: Are there X-Original-To: and Delivered-To: (or
> similar ones) used in claws-mail for identify the receipt adress?. If
> the answer is yes, this bugreport is not for claws-mail, is for the
> unknow bad mailer that send the original mail :-D. Then, you can
> close this bugreport at all. 

  I don't see how these headers (X-Original-To and Delivered-To) can be
better to identify an user account. According the Postfix docs¹ the
Delivered-To is simply the latest Received header which we already saw
it was not a good idea to use. The X-Original-To it's the recipient
address as given to Postfix. As I understand it this one is usually the
same as To header, unless there's some forward in between, in which
case it contains the original address which is not probably the one
you'll have in the account. So, again, I don't think is a good source
to find an account address.

  You're free to make a wishlist bug, either on the Debian BTS or the
upstream bugzilla², to add such headers in the search of an account for
the return receipt feature, but not sure what the actual usefulness of
them are, probably none. They wouldn't have served for your case, but
maybe you have another real examples where it could have worked.

  I'm closing this bug for now, as adding such headers is really a
feature and not a bug on current behaviour, as explained.

  regards,  

¹ http://www.postfix.org/local.8.html
² http://www.thewildbeast.co.uk/claws-mail/bugzilla/
-- 
 Ricardo Mones
 http://people.debian.org/~mones
 «Your lover will never wish to leave you.»

Attachment: signature.asc
Description: PGP signature


--- End Message ---

Reply via email to