Page MenuHomePhabricator

MailProject
ActivePublic

Watchers

  • This project does not have any watchers.
  • View All

Details

Description

A piece of software of standard value and little note.

Recent Activity

Thu, Jan 14

aleb added a comment to T12404: Implement a first-party SMTP client.

Recently smtp-relay.gmail.com stopped accepting email from our Phabricator instance because it turns out Phabricator was sending HELO localhost.localdomain instead of HELO smtp-relay.gmail.com when doing the SMTP connection.

Thu, Jan 14, 6:45 PM · Infrastructure, Mail

Sep 15 2020

epriestley closed T13235: Replace "SimpleEmailService" with a subclass of "PhutilAWSFuture" that surfaces errors more clearly, a subtask of T13570: Amazon is retiring SMTP V3 Signatures, as Resolved.
Sep 15 2020, 8:03 PM · Mail
epriestley closed T13235: Replace "SimpleEmailService" with a subclass of "PhutilAWSFuture" that surfaces errors more clearly as Resolved by committing rP3dfa89dd5d27: Update SES API to use AWSv4 signatures.
Sep 15 2020, 8:03 PM · Mail
epriestley added a comment to T13235: Replace "SimpleEmailService" with a subclass of "PhutilAWSFuture" that surfaces errors more clearly.

I've marked D21461 as resolving this, since the new errors surface the particulars:

Sep 15 2020, 4:19 PM · Mail
epriestley added a revision to T13235: Replace "SimpleEmailService" with a subclass of "PhutilAWSFuture" that surfaces errors more clearly: D21461: Update SES API to use AWSv4 signatures.
Sep 15 2020, 4:15 PM · Mail
epriestley added a revision to T13570: Amazon is retiring SMTP V3 Signatures: D21461: Update SES API to use AWSv4 signatures.
Sep 15 2020, 4:15 PM · Mail
epriestley added a subtask for T13570: Amazon is retiring SMTP V3 Signatures: T13235: Replace "SimpleEmailService" with a subclass of "PhutilAWSFuture" that surfaces errors more clearly.
Sep 15 2020, 4:08 PM · Mail
epriestley added a parent task for T13235: Replace "SimpleEmailService" with a subclass of "PhutilAWSFuture" that surfaces errors more clearly: T13570: Amazon is retiring SMTP V3 Signatures.
Sep 15 2020, 4:08 PM · Mail

Aug 13 2020

epriestley claimed T13570: Amazon is retiring SMTP V3 Signatures.

I think every other AWS interaction already uses v4, since D14978 (January 2016).

Aug 13 2020, 4:00 PM · Mail
aeiser updated the task description for T13570: Amazon is retiring SMTP V3 Signatures.
Aug 13 2020, 1:55 PM · Mail
aeiser created T13570: Amazon is retiring SMTP V3 Signatures.
Aug 13 2020, 1:54 PM · Mail

Oct 26 2019

epriestley added a comment to T13233: Consider supporting GPG/PGP.

I am running through GPG for the first time:

Oct 26 2019, 6:44 PM · Diffusion, Mail

Sep 8 2019

epriestley updated the task description for T12910: Allow SES to be used for inbound mail.
Sep 8 2019, 2:58 PM · Mail

Aug 12 2019

epriestley triaged T13375: Treat "'to'" address failures as permanent in Mailgun adapter as Low priority.
Aug 12 2019, 3:14 PM · Mail

Jun 29 2019

epriestley added a comment to T13233: Consider supporting GPG/PGP.

This is sort of generically concerning to me:

Jun 29 2019, 8:47 PM · Diffusion, Mail

Jun 19 2019

epriestley closed T13317: Unverified/nonsense account emails can trigger inbound CCs (was: Inbound support pact email sometimes CCs disabled user `@maxhodges` in Phacility) as Resolved by committing rPcaaa1394ef15: Don't count "Cc: x@y.com" as a legitimate recipient if the user who has "x@y..
Jun 19 2019, 7:51 PM · Mail, Phacility
epriestley added a revision to T13317: Unverified/nonsense account emails can trigger inbound CCs (was: Inbound support pact email sometimes CCs disabled user `@maxhodges` in Phacility): D20593: Don't count "Cc: x@y.com" as a legitimate recipient if the user who has "x@y.com" attached to their account has not verified the address.
Jun 19 2019, 6:15 PM · Mail, Phacility

Jun 18 2019

epriestley renamed T13317: Unverified/nonsense account emails can trigger inbound CCs (was: Inbound support pact email sometimes CCs disabled user `@maxhodges` in Phacility) from Inbound support pact email sometimes CCs disabled user `@maxhodges` in Phacility to Unverified/nonsense account emails can trigger inbound CCs (was: Inbound support pact email sometimes CCs disabled user `@maxhodges` in Phacility).
Jun 18 2019, 5:22 PM · Mail, Phacility
epriestley added a comment to T13317: Unverified/nonsense account emails can trigger inbound CCs (was: Inbound support pact email sometimes CCs disabled user `@maxhodges` in Phacility).

Aha! This user very cleverly added noreply@admin.phacility.com to their user account before they were disabled.

Jun 18 2019, 5:22 PM · Mail, Phacility
epriestley created T13317: Unverified/nonsense account emails can trigger inbound CCs (was: Inbound support pact email sometimes CCs disabled user `@maxhodges` in Phacility).
Jun 18 2019, 5:15 PM · Mail, Phacility

Apr 15 2019

epriestley moved T13233: Consider supporting GPG/PGP from Backlog to Far Future on the Diffusion board.
Apr 15 2019, 3:59 PM · Diffusion, Mail

Apr 14 2019

epriestley closed T11314: Observe Mode + GitHub has weird mail interactions due to pull request refs as Resolved.

See D20419 and T13277.

Apr 14 2019, 6:46 PM · Diffusion (v3), Restricted Project, Mail, Haskell.org, Bug Report
epriestley added a revision to T11314: Observe Mode + GitHub has weird mail interactions due to pull request refs: D20419: Do not publish/notify about commits which are not reachable from any "Autoclose" ref.
Apr 14 2019, 6:39 PM · Diffusion (v3), Restricted Project, Mail, Haskell.org, Bug Report

Mar 16 2019

epriestley closed T13265: Allow the SMTP mailer to be configured as a "Does Not Support Message-ID Header" mailer as Resolved by committing rPb469a5134ddd: Allow "SMTP" and "Sendmail" mailers to have "Message-ID" behavior configured in….
Mar 16 2019, 7:36 PM · Mail

Mar 14 2019

epriestley added a comment to T13265: Allow the SMTP mailer to be configured as a "Does Not Support Message-ID Header" mailer.

I also vaguely think some mailer API historically rejected mail with a "Message-ID" header with an actual error ("You can't set this header, we're going to set it for you.") rather than just ignoring/replacing it (maybe SendGrid?), but I might be misremembering or that behavior may have changed. We could still always set the header and drop it in the Adapter nowadays, this whole thing is just a nest of hornets and kicking it has pretty limited upside.

Mar 14 2019, 3:10 PM · Mail
brhodes added a comment to T13265: Allow the SMTP mailer to be configured as a "Does Not Support Message-ID Header" mailer.

I was imagining keeping the Message-ID, while having the first email also include the same value for In-Reply-To — I completely agree that removing the Message-ID would not work out. If the first email always included both fields, thus referencing itself as a reply to itself, I suppose there could be MUAs that would go into infinite loops. So, maybe too risky.

Mar 14 2019, 3:07 PM · Mail
epriestley added a comment to T13265: Allow the SMTP mailer to be configured as a "Does Not Support Message-ID Header" mailer.

I can imagine that cases like this may exist:

Mar 14 2019, 2:58 PM · Mail
brhodes added a comment to T13265: Allow the SMTP mailer to be configured as a "Does Not Support Message-ID Header" mailer.

The only effect I can imagine of always setting the In-Reply-To would be to encourage threading where it's not currently happening, so removing the behavior and deleting all these little methods would be very attractive to me if it were my project. :)

Mar 14 2019, 2:46 PM · Mail
epriestley added a comment to T13265: Allow the SMTP mailer to be configured as a "Does Not Support Message-ID Header" mailer.

There's probably some argument here for removing this behavior and assuming we can never generate a "Message-ID", but I'm hesitant to make changes like that since client threading is largely unknowable black magic which we can not test, and the current approach seems to generally produce acceptable results without an overwhelming amount of collateral complexity.

Mar 14 2019, 2:20 PM · Mail
epriestley added a revision to T13265: Allow the SMTP mailer to be configured as a "Does Not Support Message-ID Header" mailer: D20285: Allow "SMTP" and "Sendmail" mailers to have "Message-ID" behavior configured in "cluster.mailers".
Mar 14 2019, 1:53 PM · Mail
epriestley renamed T13265: Allow the SMTP mailer to be configured as a "Does Not Support Message-ID Header" mailer from Restore In-Reply-To field to first email about a Differential revision to Allow the SMTP mailer to be configured as a "Does Not Support Message-ID Header" mailer.
Mar 14 2019, 1:03 PM · Mail

Feb 25 2019

epriestley added a comment to T13068: Refinements for "Mute Notifications".

A very mild point in favor of this feature is that we haven't seen any negative feedback or confusion, although I think you might be the first user to say they actually like/use it.

Feb 25 2019, 2:31 PM · Notifications, Mail
20after4 added a comment to T13068: Refinements for "Mute Notifications".

FWIW I appreciate and use the mute feature (though only occasionally)

Feb 25 2019, 2:16 PM · Notifications, Mail

Feb 15 2019

epriestley removed a project from T5969: Add timeouts to service calls to external mailers (was: PhabricatorMetaMTAWorker may hang indefinitely if "sendmail" hangs indefinitely): Daemons.
Feb 15 2019, 2:01 AM · Mail

Jan 29 2019

epriestley added a revision to T12921: Link to referenced object in transaction emails: D20057: Allow modular transactions to override transaction title and body text in mail.
Jan 29 2019, 8:09 PM · Mail, Feature Request

Jan 21 2019

epriestley triaged T12921: Link to referenced object in transaction emails as Low priority.
Jan 21 2019, 5:17 PM · Mail, Feature Request
epriestley added a comment to T13082: Sometimes, mail about attaching revisions to tasks doesn't render the revision title.

I believe D19969 has now fixed this, although I'm not entirely certain, since it was never reliably reproducible in production so there's no way to really test or verify it.

Jan 21 2019, 5:09 AM · Transactions, Mail
epriestley closed T13082: Sometimes, mail about attaching revisions to tasks doesn't render the revision title as Resolved by committing rPafd2ace0dc9c: Apply inverse edge edits after committing primary object edits.
Jan 21 2019, 5:03 AM · Transactions, Mail

Jan 19 2019

epriestley reopened T12921: Link to referenced object in transaction emails as "Open".

D19968 got us closer here, but the link targets aren't actually rendering properly.

Jan 19 2019, 1:08 PM · Mail, Feature Request

Jan 17 2019

epriestley added a comment to T13115: Handle mail bounces inside Phabricator.

When the time comes, this should almost certainly also handle contact numbers for non-email media (T920 / D19988).

Jan 17 2019, 3:55 PM · Mail

Jan 16 2019

epriestley closed T8636: Update "Configuring Inbound Email" to describe application email configuration in greater detail as Resolved by committing rPbd077bfcb7ac: Update inbound and outbound email documentation.
Jan 16 2019, 9:56 PM · Documentation, Mail
epriestley closed T13234: Application email addresses may shadow user email addresses as Resolved by committing rPc5f446defb52: Prevent application email addresses from shadowing user email addresses.
Jan 16 2019, 9:28 PM · Mail, Security
epriestley closed T11782: Inconsistent mail notification subject ([Updated] vs [Merged]) depending on from which task a duplicate task was merged as Resolved by committing rPdc4d7f1f3e8d: Reorder "Merge" transaction to make "Close as Duplicate" produce a "[Merged]"….
Jan 16 2019, 9:27 PM · Mail, Maniphest, Bug Report
epriestley closed T12921: Link to referenced object in transaction emails as Resolved by committing rP0c0cbb1c09e4: Fix an issue where transactions in mail were always rendered as text.
Jan 16 2019, 9:21 PM · Mail, Feature Request
epriestley closed T7477: Handle inbound email with phabricator address in the CC as Resolved by committing rPe3aa043a0272: Allow multiple mail receivers to react to an individual email.
Jan 16 2019, 8:28 PM · llvm, Restricted Project, Restricted Project, Mail
epriestley closed T13066: Refine inbound mail error behaviors, distinguishing between actual mail sender and acting-as sender as Resolved by committing rPe3aa043a0272: Allow multiple mail receivers to react to an individual email.
Jan 16 2019, 8:28 PM · Mail
epriestley added a comment to T13235: Replace "SimpleEmailService" with a subclass of "PhutilAWSFuture" that surfaces errors more clearly.

D19955 has how I think this likely breaks down, I'm not planning to touch it in this iteration since the badness, while bad, is mostly in a box (hopefully) until the next PHPMailer CVE. All yours!

Jan 16 2019, 7:35 PM · Mail
amckinley added a comment to T13235: Replace "SimpleEmailService" with a subclass of "PhutilAWSFuture" that surfaces errors more clearly.

When I was messing around with SMS sending last week, I put a rough cut of this together that is capable of sending an SMS using SNS, which has almost the same API as SES: D19982. I can tackle this unless you're already in the middle of it.

Jan 16 2019, 7:11 PM · Mail
amckinley added a revision to T13235: Replace "SimpleEmailService" with a subclass of "PhutilAWSFuture" that surfaces errors more clearly: D19982: Add infrastructure for sending SMS via AWS SNS.
Jan 16 2019, 7:09 PM · Mail

Jan 15 2019

epriestley added a comment to T11782: Inconsistent mail notification subject ([Updated] vs [Merged]) depending on from which task a duplicate task was merged.

(I'm not 100% sure that D19972 fixes this completely, but it appeared to locally. In the future, "Mail Stamps" should include this information in a more reliable format, although they do not currently include transaction information. See T13069.)

Jan 15 2019, 3:09 PM · Mail, Maniphest, Bug Report