To Robert or anyone who can help me,

On my cPanel, I have the following configuration instructions. Is the "server requires authentication" setting the one causing the problem? If so, how do I solve this? Thanks in advance.

Manual settings
Mail Server Username: mysite+mysite.com
Incoming Mail Server: mail.mysite.com
Outgoing Mail Server: mail.mysite.com (server requires authentication)
Supported Incoming Mail Protocols: POP3, POP3S (SSL/TLS), IMAP, IMAPS (SSL/TLS)
Supported Outgoing Mail Protocols: SMTP, SMTPS (SSL/TLS)

Comments

robert castelo’s picture

robert castelo commented

eNewsletter sends email through the PHP mail() function, the same as the rest of Drupal, which should work transparently with whatever mail system is on your server.

I'm not familiar with cPanel, but found the following:

http://www.rightstuffhosting.com/Support_Desk_C.html

Look under "Help! My eMail Isn't Working!"

Hope this helps.

noid’s picture

noid commented

Still can't send the newsletter:

Here's what I see on my cPanel:

Configuring Mail Client for mysite

Please select an application:

Auto-Configure Microsoft Outlook® for IMAP Access
Auto-Configure Microsoft Outlook® for POP3 Access
Auto-Configure Microsoft Outlook Express® for IMAP Access
Auto-Configure Microsoft Outlook Express® for POP3 Access

Manual Settings
Mail Server Username: mysite
Incoming Mail Server: mail.mysite.com
Outgoing Mail Server: mail.mysite.com (server requires authentication)
Supported Incoming Mail Protocols: POP3, POP3S (SSL/TLS), IMAP, IMAPS (SSL/TLS)
Supported Outgoing Mail Protocols: SMTP, SMTPS (SSL/TLS)

It says that the outgoing mail protocol is smtp or smtps. Could this be the issue? Should I follow the instructions here? --

Configuring Drupal to successfully relay SMTP mail to an external mail server using smtp.class...
http://drupal.org/node/29888

SMTP authentication on remote host?
http://drupal.org/node/25715

Thanks!

robert castelo’s picture

robert castelo commented

Does your Drupal installation send other email succesfully?

e.g. when someone signs up for a new account?

noid’s picture

noid commented

Robert,

Yes, but later I noticed that the contact module stopped working -- I have it disabled now. (Otherwise, I receive notifications for private messages and banner notices.) Perhaps it's the same problem? A conflict with another module perhaps?

noid’s picture

noid commented

I forgot to mention. I also have another Drupal installation (both are in a shared hosting setup) and it's the same problem. And I only have a few modules installed in the latter (flexinode, organic groups, tinymce, and event).

Am running 4.6 btw.

noid’s picture

noid commented

Also, whenever I manually run cron.php to send the newsletter I get something like:

warning: imap_open(): Couldn't open stream {mail.mysite.com:110/pop3/notls}mysite@mysite.com in /home/mysite/public_html/modules/bounced_email/bounced_email.module on line 98.

or

warning: imap_open(): Couldn't open stream {mail.mysite.com:995/pop3/ssl/novalidate-cert}mysite@mysite.com in /home/mysite/public_html/modules/bounced_email/bounced_email.module on line 98.

...depending on my configuration settings. As you can see I've been trying out various configurations to see if I get lucky.

I'm thinking the sending of mail is interrupted by this error.

robert castelo’s picture

robert castelo commented

Those error messages relate to getting bounced emails, not sending.

In earlier versions of the module it would stop the send proccess if this problem occured, but in the latest version it just carries on.

So make sure you have the latest version of eNewsletter installed (it will tell you if you need to update any of the component modules it relies on)

Sorry, didn't understand your previous answer, if someone registers on your site, does it send a welcome email OK?

Please check.

noid’s picture

noid commented

Already solved the imap error with the configuration setting:

Mailbox Port:
143/imap

Extra commands:
/notls

But still haven't received the newsletter.

noid’s picture

noid commented

Okay, Robert re imap.

Re welcome email, just tested registering at my installation and I did get a welcome email.

robert castelo’s picture

robert castelo commented

OK, next step is to check that an email should be sent:

Make sure you've created a newsletter.

Make sure you have subscribed to that newsletter.

Create a new node, include it in the newsletter and make sure you give it a taxonomy term that is in the newsletter.

Use 'Send Now' for that newsletter

run cron (www.yoursite.com/cron.php)

That should do it.

noid’s picture

noid commented

Hi Robert,

Followed your instructions and finally, I received my first newsletter! It turns out that my test nodes had only free-tagging (folksonomy backported to 4.6) terms associated with them so the newsletter wasn't sent because there was, technically, no taxonomy terms associated with the newsletter even if I checked these folksonomy terms to be included in the newsletter.

So when I finally created a node with a taxonomy term, and included the term in the newsletter, the module finally worked. However, the nodes with the free-tagging terms weren't included in the newsletter even if they were checked in the newsletter content . In this regard, is it possible to fix this so that it's possible to include folksonomy/free-tagging terms in the newsletter? (Whenever I try to include a certain node with a folksonomy term, and not belonging to the default taxonomy, in the newsletter -- it says "A category must be selected which has permission to be in the email newsletter.")

Along these lines too, a feature request. Is it also possible to include a node in the newsletter even if it doesn't belong to a certain category? (The blog entries in my site are set up that way.)

***

Okay, just discovered this bug. I have two terms which belong to my least-weighted category. term 4 and term 5. (The first four numbers belong to folksonomy terms.) Only nodes belonging to these two categories are being sent or included in the newsletter. However, nodes belonging to other terms (and which are not associated with terms 4 and 5) are not being sent even if these terms are checked in the newsletter settings. It's not a flexinode issue since if I assign term 4 or 5 to another flexinode content type previously without these terms, the nodes belonging to this type are then sent.

Thanks!

robert castelo’s picture

robert castelo commented
Status: Active » Fixed

Glad you got it up and running :-)

Regarding the other problem, could you please submit another issue or feature request, one per issue - it makes it much easier to work on particular problems/features.

I'm closing this thread as the original problem seems to have been fixed.

robert castelo’s picture

robert castelo commented
Status: Fixed » Closed (fixed)