Metamta.placeholder-to-recipient doesn't upgrade CCs to To as it says so

jota 2017-06-19 11:06:48 UTC #22

Did you launch a new Bitnami Phabricator instance and migrate the data from your old instance to the new one? What steps did you follow?

Before starting the process, did you follow the steps that @arecio shared here some messages above?

Regards,
Jota

aravindh 2017-06-19 16:39:55 UTC #23

Did you launch a new Bitnami Phabricator instance and migrate the data from your old instance to the new one? What steps did you follow?

Sorry, I "mispoke". I misconstrued the question to be if I launched Phabricator after the upgrade. I am a little concerned about launching a brand new instance and migrating the data. So I haven't tried that yet.

Before starting the process, did you follow the steps that @arecio shared here some messages above?
Yes, I double checked the settings from the link @arecio shared. All that looks good and I continue to received reviewer emails.

jota 2017-06-21 09:56:04 UTC #24

Hi @aravindh,

In order to try to reproduce the issue, could you please answer the following questions?

Which is the Phabricator version you have now?
Which is the application version you launched?
Did you use a Bitnami installer, virtual machine or cloud image? Which is the Operating System?
Did you try the steps that @arecio shared with you?

https://community.bitnami.com/t/metamta-placeholder-to-recipient-doesnt-upgrade-ccs-to-to-as-it-says-so/42618/18?u=jota

Regards,
Jota

aravindh 2017-06-21 17:45:57 UTC #25

Which is the Phabricator version you have now?
This is what the version page shoes:

phabricator
    d3b7a0f37c975397455d633254e9b4a1246023f9 (Fri, May 26) (branched from 9d37ad3022bfff8a2900b9d728e6abbb6a1e27f0 on origin) 
arcanist
    21fe07925b07cab0f73ec824fe8ce02f53b24fe0 (May 19 2017) (branched from 129d51fa0936c9bae48fadf3a3f39e26d69d24da on origin) 
phutil
    d02cc05931b02c684d4c729510090591ca45f951 (Apr 29 2017) (branched from a900d7b63e954e221efe140f0f33d3d701524aae on origin) 
Local Version
    Bitnami Phabricator 20150929-0

Which is the application version you launched?

I am not sure what you mean by application version. How do I find this?

Did you use a Bitnami installer, virtual machine or cloud image? Which is the Operating System?

I used the Bitnami installer on Ubuntu 14.04.

Did you try the steps that @arecio shared with you?

Yes and they made no difference with the issue.

PS: A shout out to the Bitnami team for following up on this corner case issue. Thank you folks!

jota 2017-06-22 11:35:21 UTC #26

Hi @aravindh,

The information that I was looking for was the actual version of Phabricator you have (I understood in one of your messages that you performed an upgrade in the past, am I wrong?) and the original Bitnami Phabricator version you launched (this one can be retrieved from the changelog.txt file that you can find at the installation directory. This information will help us to know the exact configuration you have.

Ok, thank you for this information.

I suppose you test this in your current version and not in a new one, right?

Regards,
Jota

aravindh 2017-06-22 15:49:47 UTC #27

I understood in one of your messages that you performed an upgrade in the past, am I wrong?

Yes I performed three or four upgrades so far.

My current phabricator version from the version page:

phabricator d3b7a0f37c975397455d633254e9b4a1246023f9 (Fri, May 26) (branched from 9d37ad3022bfff8a2900b9d728e6abbb6a1e27f0 on origin) 
arcanist 21fe07925b07cab0f73ec824fe8ce02f53b24fe0 (May 19 2017) (branched from 129d51fa0936c9bae48fadf3a3f39e26d69d24da on origin) 
phutil d02cc05931b02c684d4c729510090591ca45f951 (Apr 29 2017) (branched from a900d7b63e954e221efe140f0f33d3d701524aae on origin)

Here is contents of my changelog.txt

============ CHANGELOG =============

Version 20150929-0      2015-09-29
* Updated PHP to 5.5.29

Version 20150901-0      2015-09-08
* Updated Phabricator to 20150901

Version 20150824-0      2015-08-24
* Updated Phabricator to 20150824

Version 20150817-0      2015-08-17
* Updated Phabricator to 20150817
* Updated phpMyAdmin to 4.4.13.1

Version 20150810-0      2015-08-12
* Updated Phabricator to 20150810
* Updated Apache to 2.4.16
* Updated PHP to 5.5.28
* Updated OpenSSL to 1.0.1p
* Updated MySQL to 5.6.25
* Updated phpMyAdmin to 4.4.7

Version 20150506-0      2015-05-08
* Dropping RC4 from Apache SSLCipherSuite directive
* Updated Phabricator to 20150506
* Updated phpMyAdmin to 4.4.3
* Updated PHP to 5.4.40
* Updated OpenSSL to 1.0.1m

Version 20150309-0      2015-03-09
* Updated Phabricator to 20150309
* Updated OpenSSL to 1.0.1l
* Fixed binaries for Git

Version 20150129-0 2015-01-30
* Updated Phabricator to 20150129

Version 20150108-0 2015-01-12
* Updated Phabricator to 20150108

Version 20141202      2014-12-02
* Initial release, bundles Apache 2.4.10, PHP 5.4.35,
MySQL 5.5.40, phpMyAdmin 4.2.12, OpenSSL 1.0.1j and 
Phabricator 20141202

jota 2017-06-23 15:53:14 UTC #28

Hi @aravindh,

Thank you for the information. We are going to try to reproduce your environment and will update this case as soon as we have more information.

Regards,
Jota

jota 2017-06-26 09:54:52 UTC #29

Hi @aravindh,

I've tried to reproduce the issue and everything worked fine for me when creating new diffs and user accounts. These are the steps I performed:

Launch Phabricator 20150929-0
Configure the SMTP settings by following the guide in our documentation
Create a new user account and check that the email worked fine
Create a test repository and a test diff. I set the new user as subscriber

Test that I received the email in my account
Upgrade Phabricator to the same version you have.
Add a comment in the diff and check the email again

I checked the Mail section of Phabricator and saw that the 2 mails were there

but the CC field was empty

but as I mentioned, I received the email in the jota's email. The user's email is user@example.com.

If you continue running into issues when sending emails, I suggest you check the spam folders of the email account and open an issue in the Phabricator's repository in order to get more information about the CC issue.

Regards,
Jota

aravindh 2017-07-10 20:52:17 UTC #30

I suggest you check the spam folders of the email

I did check the spam folders and the emails don't show up there. They are definitely not getting sent from the phabricator side with the error I mentioned in my prior posts.

open an issue in the Phabricator's repository in order to get more information about the CC issue

T11138 already tracks this.

I guess my only recourse is to do a fresh install and migrate the data and settings over and that will hopefully fix this issue.

jsalmeron 2017-07-11 08:36:04 UTC #31

Hi,

Please let us know if that solves the issue. If you come across other issues do not hesitate to post.

Best regards,

Javier J. Salmerón

Was my answer helpful? Click on

Bitnami provides free all-in-one installers, virtual machines and cloud images for popular open source applications. Get them now!