The extension scrapes Amazon Search Results and gives you plenty of data to play with on Metabase. Integrate your Gmail Credentials in order to send automated pulses with the results of your. If you’ve already configured Metabase to use email, Metabase will send the new user an invite email. Otherwise, it’ll give you a temporary password that you’ll have to send to the person you’re inviting by hand.

• To deliver by email, just type in the Metabase user names, or email addresses you want to send the pulse to, separated by commas. Then, choose to either send it daily, weekly, or monthly, and the time at which you want it to be sent.
• The Metabase Store. Login to manage your Metabase Cloud account or other products. Looking to get started with Metabase or Metabase Cloud? Email: Password.
• On the left, there’s a Metabase pulse scheduled to be pushed to one of the team’s Slack channel. Different teams have created & subscribed to such actionable pulses which send out relevant metrics to them on Slack/email at a pre-set frequency. Similarly, alerts are set depending on some threshold.

windows server 2008 r2, iis7, cdo send email

Nov 04, 2010 11:33 AM|supportadl|LINK

Hi, I have an application classic asp that send emails from web site, the code is the following:

dim sender

cdoAuthenticationAccountValue='xxxx'

cdoAuthenticationPasswordValue='xxxx'

SmtpForEmail='xxxx'

cdoUsingAuthentication=true

' EMAIL settings

dim cdoSendUsingMethod, cdoSendUsingPort, cdoSMTPServer, cdoSMTPConnectionTimeout, cdoSMTPServerPort, SmtpPerEmail

cdoSendUsingMethod='http://schemas.microsoft.com/cdo/configuration/sendusing'

cdoSendUsingPort=25

cdoSMTPServer='http://schemas.microsoft.com/cdo/configuration/smtpserver'

cdoSMTPConnectionTimeout='http://schemas.microsoft.com/cdo/configuration/smtpconnectiontimeout'

cdoSMTPServerPort='http://schemas.microsoft.com/cdo/configuration/smtpserverport'

cdoAuthentication='http://schemas.microsoft.com/cdo/configuration/smtpauthenticate'

cdoAuthenticationValue=1

cdoAuthenticationAccount='http://schemas.microsoft.com/cdo/configuration/sendusername'

cdoAuthenticationPassword='http://schemas.microsoft.com/cdo/configuration/sendpassword'

Metabase Send Emails

'Function to send email

Function SendEmail(soggetto, dati, sender, email)

Dim Mail

Set Mail = Server.CreateObject('CDO.Message')

Mail.Configuration.Fields.Item(cdoSendUsingMethod)=cdoSendUsingPort

Mail.Configuration.Fields.Item(cdoSMTPServer)=SmtpForEmail

Mail.Configuration.Fields.Item(cdoSMTPConnectionTimeout)=10

Mail.Configuration.Fields.Item(cdoSMTPServerPort)=25

if cdoUsingAuthentication then

Mail.Configuration.Fields.Item(cdoAuthentication) = cdoAuthenticationValue

Mail.Configuration.Fields.Item(cdoAuthenticationAccount) = cdoAuthenticationAccountValue

Mail.Configuration.Fields.Item(cdoAuthenticationPassword) = cdoAuthenticationPasswordValue

endif

'Mail.Configuration.Fields.update

Mail.From = sender

Mail.To = email

Mail.Subject = soggetto

Mail.HTMLBody = dati

Mail.Send

testo = '

soggetto = '

set Mail = nothing

EndFunction

With windows 2003 R2 and IIS6 the application send emails correctly bat when I have migration my application on windows 2008 R2 with IIS7 don’t works.

The server SMTP is external at the system.

I have also installed SMTP server, start services and following this guide http://learn.iis.net/page.aspx/751/configure-smtp-e-mail-in-iis-7/ , but don’t send emails.

I also check this:

1. Give Read/Write permissions for the IIS_IUSRS group to the Mailroot folder (permissions will inherit down to Pickup/etc folders).
2. Now use a Metabase Permissions modifier (Metabase Explorer works, so does METAACL.VBS from 2003), Open LMSMTPSVC and SMTPSVC1 and add IIS_IUSRS with read permissions to those branches of the metabase.
   cscript metaacl.vbs IIS://LOCALHOST/SMTPSVC %computername%IIS_IUSRS R
   cscript metaacl.vbs IIS://LOCALHOST/SMTPSVC/1 %computername%IIS_IUSRS R

Still don't work.

Do you have any ideas?

Thanks a lot.

IIS7send emailscdowindows server 2008 r2

There are companies who prefer to use Distribution list as a sender. The people who use such features are either into “Support or Sales”. In our scenario we will be using distribution group name as “Support”.

Scenario 1

In this scenario we will be using Exchange Server 2003 with Outlook 2007.

Figure 1: Two Distribution Group Named as Sales and Support

In the above scenario I have created two distribution groups and I have added few members. By default anybody can send emails to a distribution groups. And the members will be receiving the email.

This is the main purpose of having a distribution group.

However it can be used for sending emails to internal and external recipients.

First let’s see the default behavior.

Figure 2: Test Email being sent with default settings. By default “From”& “BCC” fields are not available.

Figure 3: NDR Message stating that No Permission.

Now let’s apply the permission. We would be granting full control rights for Ratish on Support distribution group.

Note: In order for applying the permission we will be using ADSIEDIT.msc which is available in the windows support tools.

Figure 4: Adding Ratish.

In the above screen by default Ratish has only “Read” permission.

Figure 5: Granting full control permission.

Once permissions are granted this information has to be updated in the Metabase. Just restart the Microsoft Exchange System Attendant service.

Figure 6: Ratish Sending email using Support in the from field.

Figure 7: Customer is able to receive email from Support.

Figure 8: Members of “Support” received the email without any issue.

In the above scenario we have used one user. If your organization wants all members of the distribution group to be able to send email then you can simply create one Security Group and make all users member of that group and then Grant Full Control for that group.

Scenario 2

In this scenario we will be using Exchange Server 2007 with Outlook 2007.

In 2007 we have created the Distribution Group by the same name as “Support”. In Exchange Server 2003 we have seen that Ratish was having full control permission. The intended recipients will never realize that who sent the message. The same is possible in 2007; however in 2007 we are not going to use ADSIEDIT.msc. Instead we would be using Power shell.

In this scenario we will be granting a different permission.

Note: The account with which we are running the command should have proper permission.

Open Power shell and type the below command.

Figure 2.1: Get-DistributionGroup

In Figure 2.1 by default “GrantSendOnBehalfTo” is set to Null.

Figure 2.2: Set-DistributionGroup

In Figure 2.2 we have granted the permission to Ratish.

Since we are running these commands from Power Shell we don’t have to restart any services.

Now let’s play with Outlook and check how it works.

Metabase Send Email

Figure 2.3: Test Email Sent to Customer

Figure 2.4: Test Email Received by customer

In figure 2.4 when you look closely the from field appears as “Ratish on Behalf of Support”

When the customer replies to this email it directly goes to Support DL.

Figure 2.5: Email reply from customer

The above scenario is also applicable for Exchange Server 2010. I will be covering that in the next part series of “Moderation in Exchange Server 2010”.

Sunder

Team@ MSExchangeGuru

Keywords: Send as from DL, Send from DL, Send on behalf from DL’s.