I have carefully set the "From" email address to a noreply address, that is also used for bounce tracking. Regardless, emails are going out with the From address equal to the DNN SMTP sending address.

Opt-In version: 4.2.0.1793, DNN version 5.4.2.

I am pretty sure this is new behavior, module was perviously working correctly. Can't say for sure the change that caused it, but we have been updating to more current DNN versions.

Hi Worth,

Let me first make sure you are on the latest build.  Can you please access Opt In Email 4.2.40 from your Snowcovered Account in Patches and Hotfixes (or in MyDownloads if you're a Collection 3.0 owner)? 

If the problem persists after you install the latest patch, can you please check a couple of places for me?  In Opt In Email - Advanced, please go to Control Panel, Module Configuration.  Then in Newsletter Settings/Template, what do you have there as the default From Email Address?

Also, when you create an email, in Advanced Settings, is this where you're adding your Reply To address?  Thanks!

Candace

 

Checking host settings, module definitions, I have 4.2.40 installed.

In Newsletter Settings/Template, default email address is noreply@domain.com.

I have learned a bit more. I used Alternate Configuration, and set up to use SMTP with my noreply@ credentials. That worked when I did "Send Immediate". However, when I ran using "Schedule Immediate", it went back to a from address of admin@domain.com, which is the email address of my host SMTP setting.

I'm beginning to think the only way I am going to get noreply@... as my from address is to make that my host DNN SMTP setting before I send a scheduled newsletter.

And just to be clear, I am not having a problem with reply to address, the problem is totally with from address, as this is where bounce checking happens, and with things working this way, bounce checking is broken.

 status?

Am I just out of luck?

Is send immediate my only option?

On the off chance I am getting no response because I haven't "upgraded" to the latest version, I did go to snowcovered and download latest (I am Collection 3 owner, I downloaded from MyDownloads). I attempted to install, got message that version was already installed.

So I have positively confirmed 4.2.40 is installed version.

I have a mailing to do today (375 recipients), I will use alternate configuration and send immediate, which hopefully will result in all messages going out from noreply@. I would prefer to use scheduler, but last try didn't work.

Hi Worth,

Thanks for downloading the latest patch.  I do want to mention that you weren't being 'ignored' because you didn't upgrade yet.  It's just that the community forums are not as closely monitored as tickets and contact us forms.   :-)

In fact, using the scheduler is what we recommend -- schedule immediately or schedule for a specific time.  Please test with a small test list and run a scheduled email blast and see if the noreply now works with the scheduler.

If you have any trouble at all, please use the Contact Us form or open a support ticket from Snowcovered.  Thanks!

Candace

Did as suggested, sent to a list of 2, schedule immediate, from was the DNN Smtp sender. Same email, send immediate, from was noreply@

Alternate configuration worked with send immediate, did not work with schedule immediate.

Tried to send to list of 375 with send immediate, crashed after ~50 addresses.

 Made major progress today. I am down to one small issue, which I believe is definitely an Opt-In Email glitch, but everything else is now resolved.

I am going to post a great deal of detail here, not to resolve my problem, but to help others who may run into the same peculiarities.

Our problem began a few weeks ago when we moved our domain email services away from our hosting service (3Essentials, who are terrific, by the way) to Google Apps. We thought we had made appropriate setting changes to use Google SMTP, but apparently not, and that was a major part of our trouble.

Late last night, we opened a ticket with 3E, and they quickly came back with an offer of a special email account we could use for SMTP sending. It took a little monkeying to get it right, but once that was in place and we could send a message with DNN bulk mail, we were on the way to solving our Opt-in problems. So with DNN SMTP set to use webxx.3essentials.com as the server, and our new account domain@webxx.essentials.com set as the credentialed account, with a successful send test, the rest of our problems began to disappear.

We no longer needed to use alternate configuration, and our default from address of noreply@domain.com worked as it was supposed to, whether via send immediate or schedule immediate.

So our bottom-line lesson was, if we move our domain email to a different service, we need an smtp sender in the hosting provider's network (in our case, the same server as is hosting our site). 

I said there was one glitch, and here it is:

Sending to a list of 376 addresses, all but three went fine. The three that didn't gave a message in the send schedule of:

Sending To (0 of 76 - Maximum of 100 can be distributed with this distribution): kenmrobbins@gmail.com 

From Email Address: The Harvard General Store

What these three addresses have in common is they were all three associated with accounts that were logged in when the schedule was executing. We thought at first it might be that they were local addresses, that had been moved to Google Apps, but in fact, only one is.

They ended up at the top of the list, but in fact, they originally occurred at differnt parts of the first three groups of 100. Because they failed each time, they were attempted again in the next run of the schedule.

Ideas?

 One other small problem - in a distribution of 375 emails, 326 are shown as "failed distributions", and there are no bounces, even though we know there are. We have double checked credentials for bounce checking, they are right.

What causes a distribution to be counted as failed?

I may be well along toward answering some more of my own questions. Looking back, I think our problems began when we moved mail for our domain away from our hosting service, to Google Apps. This necessitated changing MX records at our hosting site so mail for any@mydomain.com is redirected to Google.

At first, we tried using google SMTP for DNN mail, and by extension, for Opt-In mail. That mostly, but not totally, worked. After many false starts, we asked our hosting service (3essentials) for help, and they gave us an email account on our hosting server (not in our domain), and instructed us to use our hosting server as the SMTP server, and the special email account ourdomain@webxx.3essentials.com for smtp security.

That worked, mostly, in that emails were sent out, but nearly all were counted as "failed distribution", and bounces didn't get back to the from email noreply@ourdomain.com.

I'm wondering if that is because a bounce goes back to the smtp sender, and then to the sending mailbox, but because we have moved mail to google, the sender doesn't know how to get it back to the mailbox? Or something like that.

Do you have any experience with users who have moved their email to google, and what they need to do to configure DNN (and Opt-In email) to work correctly?

We're thinking that, maybe, we should create an alias for our DNN site, and use email accounts for that alias, e.g. admin@ourdomain.net and noreply@ourdomain.net, so that mail will again be coming from (and bouncing back to) the same host that it originated from?

Thoughts?

Hi... Well, if anything is returned other then a "" it should be logged in the database... We are using the standard DNN Email function calls so if they are not logging it we can probably add code to log it for the upcoming 4.3 release.

Can you tell me after this happens, if you go to admin/event viewer, do you see any error messages there? If so what do you see?

Sorry for the late response here... been working on the 4.3 release and I think you will enjoy some of the nice improvements!


-Chad