Page MenuHomePhabricator
Create Task
Maniphest T10277

Error Processing Mail (No Receivers)
Closed, DuplicatePublic
Actions

Description

I replied all to a Maniphest thread, CCing the address for the task, and got the following response:

[Subject: Error Processing Mail (No Receivers)]

Your email to Phabricator was not processed, because an error occurred while
trying to handle it:

Phabricator can not process this mail because no application knows how to
handle it. Check that the address you sent it to is correct.

(No concrete, enabled subclass of PhabricatorMailReceiver can accept this
mail.)

-- Original Message Body -----------------------------------------------------

I should have looked at this more thoroughly; we should also have a
column for can_be_invoiced.

On Thu, Feb 4, 2016 at 3:12 PM, Robert Hentzel <robert.hentzel@naqt.com> wrote:
> On Thu, Feb 4, 2016 at 3:00 PM, Jonah Greenthal
> <jonahgreenthal@gmail.com> wrote:
>> I can patch this, but ideally R would add an
>> Invoice_Status.can_be_confirmed column (true for NEW, ON_HOLD, and
>> QUOTE).
>
> Column added, no data entered.
>
> R.


-- Original Message Headers --------------------------------------------------

return-path: <jonahgreenthal@gmail.com>
x-original-to: phabricator+T1451+public+1c646c0f82e0713d@naqt.com
delivered-to: phabricator+T1451+public+1c646c0f82e0713d@naqt.com
received: from mail-oi0-f53.google.com (mail-oi0-f53.google.com [209.85.218.53]) by mercury.naqt.com (Postfix) with ESMTP id A2A0614A0518; Thu,  4 Feb 2016 15:15:21 -0600 (CST)
received: by mail-oi0-f53.google.com with SMTP id s2so26082070oie.2;        Thu, 04 Feb 2016 13:15:21 -0800 (PST)
received: by 10.202.180.6 with HTTP; Thu, 4 Feb 2016 13:15:20 -0800 (PST)
dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=gmail.com; s=20120113;        h=mime-version:in-reply-to:references:date:message-id:subject:from:to         :cc:content-type;        bh=PERa1nEmIaJ0cTT+B6FObcF90KgW0Tu1oIgfbRvqwq8=;        b=ytYTsRcIF4Mfjoi5OppTjZqzprf32k4/JFAlR+yyKAHnxc5wf9ff5aS4cg7BeCPlmD         idE3AwaZTKgpRtx6TgdLgq0IlYz2BCm13vzI1ck9oWUXUgSJ1+SlyJE8HHzcb/GQdrmT         LddGOGm39C4W7iD/HF883E2P9gw8L5fwAmEiy5owN07rB3z9Ag5Dh6yhes5H6Ehwpxqa         Z69AZ1pYxf9LzQl4jiH0ZUP9+HL4zKhh63KRnDpWHEnIBDz35vMEcGpi3oXFDpOyVH5w         uNXut7K7TTt0mXrBc1Y8F03r5snDhcZWaU5VTfV3RqPfm5OWb8ilnJZZN3/ha4s9qyQC         eTqg==
x-google-dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=1e100.net; s=20130820;        h=x-gm-message-state:mime-version:in-reply-to:references:date         :message-id:subject:from:to:cc:content-type;        bh=PERa1nEmIaJ0cTT+B6FObcF90KgW0Tu1oIgfbRvqwq8=;        b=cWutd1H/N4rbXOXKVsJRoF4Gs4Hu61jdrJAJNFHSsXlfTgFOieSQZcToKBU5hQhQSQ         Lgp49llHAm/kzQ2aQRfDwQlLL3zioG9pSzjRgmamgcSOl51wVnfZWXZSd0r4QRobrcgd         KDxDeRlSQwEl4PmSZ2E0uYdRvHQP55nrypAQWV5DFM2k0j2bwpVFKzfGEbs45kVTdaGl         EMcxgVa+1h5tOE239/j1SjTMlocQPJXGVDdVC72/DXHSXSiCnCnpRFNcMF/Zqv+qmkQE         PbjyFJFgwwTNp4CSafaZ+pwhNkco8sxQypd/hfkgqFGFI+JIgCF9iKLxIKSG70KpmaBK         DztQ==
x-gm-message-state: AG10YOS2qEJbumgMH3CJH4V5xFDWMSZeTsGvhBY78PL5ciHRcYUKE25rFwdGCO/UKcd70WOYx+GDIM6JYPkkuA==
mime-version: 1.0
x-received: by 10.202.190.194 with SMTP id o185mr5286244oif.1.1454620521044; Thu, 04 Feb 2016 13:15:21 -0800 (PST)
in-reply-to: <CAHDGTVwHHh0waM_SV+S61W6LdS0sZb0bcS8P9hsyRO8jWunSHw@mail.gmail.com>
references: <maniphest-task-PHID-TASK-iqlefxsza33xia7ze5ms@naqt.com> <CAM3JV=pGrjUF1ZArckqUFUqSdVtqFvaegjhnXpVsP+yBQ8OPjw@mail.gmail.com> <CAHDGTVwHHh0waM_SV+S61W6LdS0sZb0bcS8P9hsyRO8jWunSHw@mail.gmail.com>
date: Thu, 4 Feb 2016 15:15:20 -0600
message-id: <CAM3JV=rGs==H-vwAiH3yC3=pkFp+qXtSiFa7bkNssDZZyPdNRw@mail.gmail.com>
subject: Re: [Maniphest] [Created] T1451: Please allow invoice confirmation when Invoice Status is "Quote"
from: Jonah Greenthal <jonahgreenthal@gmail.com>
to: Robert Hentzel <robert.hentzel@naqt.com>
cc: phabricator+T1451+public+1c646c0f82e0713d@naqt.com,  "tech@naqt.com" <tech@naqt.com>
content-type: text/plain; charset=UTF-8

I expected my response to generate a new comment on the task (and no email to me).

Please let me know what further information you need, if any.

Related Objects

Event Timeline

jonah214 created this task.Feb 4 2016, 9:20 PM
chad added a subscriber: chad.Feb 4 2016, 9:28 PM

Why did you CC the task instead of leaving it in the TO field?

chad closed this task as a duplicate of T7477: Handle inbound email with phabricator address in the CC.Feb 4 2016, 9:29 PM
jonah214 added a comment.EditedFeb 4 2016, 9:33 PM

Because I wasn't replying directly to the task email, I was replying to a colleague's response in the thread. I did not change any recipients from the default when hitting reply all. The sequence of emails went like this:

  1. Email from Phabricator to a list, announcing the creation of the task
  2. I reply all (to: phabricator, cc: list); this shows up as a comment
  3. Colleague replies all (to: me, cc: phabricator, list); this does not show up as a comment; I assume he also got a bounce notification similar to what I got
  4. I reply to colleague (to: colleague, cc: phabricator, list); this does not show up as a comment and I get the above bounce notification

This seems like a reasonable, and perhaps common, workflow, and I want all the replies (unless Phabricator is explicitly removed from the to/cc) to be creating comments.

I did confirm that the same thing but with #4 being changed manually to [to: colleague, phabricator; cc: list] does properly create the comment — but I don't think I should have to manually change recipients.

chad added a comment.Feb 4 2016, 9:41 PM

Is the mailing list a Phabricator mailing list or external?

jonah214 added a comment.Feb 4 2016, 9:42 PM

External.

chad added a comment.Feb 4 2016, 9:43 PM

T7477 is tracking this, it's reasonable to support, but not very common overall.

Phabricator · Built by Phacility