eugfri, Member
hi,
I have been successfully using "from/reply-to" address setup as part of mydbr environment settings in order to send emails from inside of my reports. However, now I must use more than one "from/reply-to" address for sending email messages (one type of report I have to email from address A and another report - from address B).
Could you suggest any possible ways to implement this?
Thank you!
Eugene
myDBR Team, Key Master
Eugene,
you can override the default sender information with dbr.mail.sender-option.
--
myDBR Team
eugfri, Member
yes I can, I tried that. But I need to be able to authenticate that "other sender" with the mail server. How do I pass the password?
myDBR Team, Key Master
What do you mean by authentication, the SMTP authentication? The SMTP authentication is not tied into the "from/reply-to" address.
--
myDBR Team
eugfri, Member
Yes, SMTP authentication info. I know its not tied to "from/reply-to" address itself, but if I am using different smtp accounts (email addresses) - their username/pwd for SMTP server are different.
I can specify one in Mail section of "Environmental Settings" page, but how would I supply SMTP login/pwd to dbr.mail if I want to use another sender?
myDBR Team, Key Master
Eugene,
for now myDBR supports only one SMTP server. We can add additional functionality to the mail extension to make it possible to use different mailer (smtp, mail, sendmail, qmail) and also use different settings for these. This will be an easy change.
What is the reason for using another SMTP server?
--
myDBR Team
eugfri, Member
I have to use same smtp server but different accounts (I.e. from addresses/mailboxes). Use case is very simple. For example, updates about processed RMAs should be sent to customers from one address, but follow ups on RFQs to customers should be sent from another address.
It's a typical situation for small client to use some hosted mail service such as Microsoft's Office or Google etc. In such case SMTP server would be the same for all senders, but each sender would have their own login and pwd for SMTP server.
myDBR Team, Key Master
As said, SMTP server does not dictate the from addresses seen in the mail. You can use the same SMTP connection and define different sender / reply-to. What is the benefit the other SMTP server offers you?
--
myDBR Team
eugfri, Member
Probably the most generic modification to help with this would be to enable feeding SMTP server password to dbr.mail as an option, just like allowing to feed different senders using dbr.mail.sender. I.e. have something like dbr.mail.password.
eugfri, Member
I am not trying to use more then one SMTP server at all. I simply have some messages that have to go from the system as being from "user1@outlook.com" and others - as "user2@outlook.com".
My SMTP server is Microsoft Office 365 mail server, so user1 and user2 have different SMTP passwords.
I must use user1/password1 to send msgs from user1@outlook.com and user2/password2 when I need to send msgs from user2@outlook.com
myDBR Team, Key Master
Your server rejects the outgoing mail if you specify user2@outlook.com as from/reply-to when you are logged in as user1@outlook.com?
--
myDBR Team
eugfri, Member
yes. Exactly.
myDBR Team, Key Master
OK,
we'll add an option to authenticate as another user, no problem.
--
myDBR Team
eugfri, Member
That wound be great!
eugfri, Member
Will you let me know here when to update mydbr to the latest patch version?
myDBR Team, Key Master
Eugene,
you can now use a new command dbr.mail.smtp.authentication to define an alternative user & password.
select 'dbr.mail.smtp.authentication', 'username', 'password';
--
myDBR Team
eugfri, Member
Excellent!
Thank you very much!
It does without saying I must update mydbr to the latest patch version.
eugfri, Member
Actually, I am still struggling with making this work.
It seems that order of dbr.mail options makes a significant difference and I am probably not using the correct one.
I have tried to switch things around, but still get an error.
Here is the sample code:
SELECT 'dbr.mail', 0;
SELECT 'dbr.mail.debug', 1;
SELECT 'dbr.mail.smtp.server', 'smtp.office365.com', 587, 1; SELECT 'dbr.mail.smtp.authentication', 'myemail@mycompany.com', 'mypassword'; SELECT 'dbr.mail.recipient', 'who@company.com', 'FirstName LastName';
SELECT email, name, subject, body FROM mytable;
Here is the error:
Debug
Invalid address: dbr.mail.smtp.authentication
I know that parameters I am passing to dbr.mail.smtp.authentication are valid, email address and password work when logging into Microsoft hosted Office365 exchange server.
I am not sure if I am using dbr.mail.smtp.server correctly though... Encryption method used is TLS, but I am not sure how to indicate that.
I also tried removing dbr.mail.smtp.server in order to use mail server from mydbr options, but the error is still the same - Invalid address: dbr.mail.smtp.authentication
myDBR Team, Key Master
Eugene,
there was an error in the example above. The correct command for defining the user / password is:
select 'dbr.mail.smtp.user', 'myemail@mycompany.com', 'mypassword';
The encryption method in dbr.mail.smtp.server is either 'tls', 'ssl':
select 'dbr.mail.smtp.server', 'smtp.office365.com', 587, 'tls';
Note that you do not need to define the server if it is the same as the the default.
--
myDBR Team
eugfri, Member
hi,
it seems like now all email functionality has stopped working....
I am using
SELECT 'dbr.mail', 0;
SELECT 'dbr.mail.debug', 1;
SELECT 'myemail@gmail.com' as email, 'MyName' as name, 'test msg' AS subject, 'test msg' AS body;
for simple test and i have updated my installation to the latest 4.6.4 build 3011.
I get
Sent 1 mail with no errors
But email never comes to my gmail box (sent to myself).
Also, there is no debug output either even though flag is set to 1.
This is all very strange.
Are you sure this change did not break anything in the latest build?
myDBR Team, Key Master
Eugene,
That does not sound right. You should get the debug messages when the debug flag is set. The mail delivery itself might fail elsewhere. It looks that the mail sending works though.
Make sure you have a fresh copy of myDBR: run the updater and try again.
If that does not solve the issue, open a support ticket.
--
myDBR Team
eugfri, Member
I ran update again to 4.6.4 build 3013 but my simplest test email proc still does not work and does not display debug info. I just sent all the details to your support mailbox - support@mydbr.com
eugfri, Member
Just to conclude this thread in case someone runs into the same issue.
It seems like hosted Microsoft Office 365 Exchange simply does not support "sending as" functionality.
Most likely its done for security purposes, so even use of dbr.mail.smtp.user did not help. The only way around is either to try to configure smtp relay, or give extra perms to the smtp login setup in mydbr environment in order to "send as" other users, which is what I have done.
This way even simple dbr.mail.sender function works just fine as intended.
You must log in to post.