Adding our internal mailing list to the Create Mailing lists does not work, rather it allows us to add the email list, allows us to add that name in the tasks but will not send any mail to that list when the task i changes. It would be ideal to send emails to our internal mailing lists eg: xproject-reviews@company-name.com
Description
Description
Event Timeline
Comment Actions
It should be sending mail. Are you sure your mailing list is configured to accept mail from Phabricator?
You can use this command to see mail sent by Phabricator:
phabricator/ $ ./bin/mail list-outboundComment Actions
Here is an example what I did. I created a list called "Private" and added my gmail id to it. Added that to a task and then made changes no emails were sent , while it did send email to my login user id.
Comment Actions
I can't replicate this. I created a new list 'ChadPhacility', added it to a task and updated the description. Email was sent and received.
I would check what @epriestley noted above. Change the title of the task or something, and run the command above. You'll see something like this:
656 Void T13: My New Test Task 657 Sent T13: My New Test Task 658 Sent T13: My New Test Task 659 Sent T13: My New Test Task
One was Void (correctly) as it was the same email address as the mail list, the others all show sent.
Comment Actions
Hi Chad,
Thanks the command shows that email is sent. We did some more testing here.
- Modified the mailing list to have only to email id/user who was registered on phabricator it worked
- Modified the mailing list to have my gmail id which is not registered on my phabricator ( we have enabled only to login thorugh LDAP ) did not work rather mail was sent but was not received
- Modified the mailing list to have a mailing list ( cod-reviews@companyname.com) which is not registered on my phabricator ( we have enabled only to login thorugh LDAP ) did not work rather mail was sent but was not received
Any ideas why it does not work in the other scenarios ?
Comment Actions
If mail was sent, Phabricator handed it off to the MTA and got an affirmative reply. This means your MTA is misconfigured or has a deliverability issue. There's nothing we can do to resolve this, check your MTA / mailing list configuration.