yes, that is the problem. I need to add compose.mail.yml to be able to use mail_password but this forces me to also definde mail_key. Probably there need to be two seperate yml files, one for pure smtp and one for mail relay providers which need mail_key.
> MAIL_KEY is not needed when using smtp, see https://docs.bonfirenetworks.org/Bonfire.Mailer.html#3-direct-email-sending-methods
yes, that is the problem. I need to add compose.mail.yml to be able to use mail_password but this forces me to also definde mail_key. Probably there need to be two seperate yml files, one for pure smtp and one for mail relay providers which need mail_key.
or we could change the bonfire config code to consolidate on just one of those? eg. using MAIL_KEY for the password too, but still checking MAIL_PASSWORD as fallback for existing deploys
or we could change the bonfire config code to consolidate on just one of those? eg. using MAIL_KEY for the password too, but still checking MAIL_PASSWORD as fallback for existing deploys
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
MAIL_KEY is not needed when using smtp, see https://docs.bonfirenetworks.org/Bonfire.Mailer.html#3-direct-email-sending-methods
yes, that is the problem. I need to add compose.mail.yml to be able to use mail_password but this forces me to also definde mail_key. Probably there need to be two seperate yml files, one for pure smtp and one for mail relay providers which need mail_key.
ah I see yeah I think @kawaiipunk suggested that solution
or we could change the bonfire config code to consolidate on just one of those? eg. using MAIL_KEY for the password too, but still checking MAIL_PASSWORD as fallback for existing deploys
not relevant anymore