Mails not getting sent

yea, the problem is that the db schema must have changed somewhere along the way for the bounce processing. Just change the newsletter_id in line 123 of bounced_email.module to publication_id instead. I also get major imap warnings in the cron execution as well, even though I am using pop for my bounce retrieval. I haven't looked into that..

cheers
-o

sorry this was really supposed to be a reply for http://drupal.org/node/33546 - whoops, and now i see about the imap stuff too..

I have the same issue. Mail is not sending...

Same here, but I haven't had chance to look at it,perhaps tomorrow I'll take a harde look. Using latest versions of this module on 4.6.3.

@oliver soell: I have the same issue with IMAP errors even tho I haven't set up the bounced e-mail settings. Commenting out the contents of bounced_mail_cron does the trick if you're not intending using this. Not sure if this will affect the issue of actually sending mails, tho.

I guess there should be an option or a check on the bounced e-mail receiving settings to see whether to run the mail check in bounced_mail_cron?

This is the main problem I'm concentrating on at the moment.

I've been doing some work on bounced module to make it more 'fault' tolerant:

* check to see if PHP IMAP module is available (watchdog message is set if false)
* check if username and password have been set
* check if mailbox exists

If any of these are false it gracefuly finishes trying to do bounce functions.

Should be ready for download soon-ish

OK, who's in the mood for some testing?....

I've updated bounced_email.module, should now fail gracefully if it can't connect.

Publications.module and enewsletter.module have also been updated, make sure to read the UPGRADE notes in the enewsletter README.txt

Thanx for your work.

I updated my insatllation with the 1.6 version of enewsletter.module, v1.2 bounced_mail.module, publication.module,v 1.9, aplied upgrading query "ALTER TABLE `publications` CHANGE `description` `description` TINYTEXT NOT NULL " and still got no sent message. It still says qued: Array, sent: 0, and after cron again sent:0, qued:0
I have no error messages neither in watchdog, nor in apache error log...

"qued: Array" is a presentation bug that needs to fixed.

Have you created new content, i.e. a node, and included it in newsletters?

If there is no content it won't send the newsletter.

I works! Urahh!))

I didnt' create new node, cause I had old ones, and thought that they should be sent... so created new node, and it gone!
Amazing module!
Thanx a lot!

Thumbs up!