After running the cron.php I receive the following error:

warning: imap_open(): Couldn't open stream {pop.wanadoo.nl:110/pop3}albert.tiesinga@wanadoo.nl in /www/htdocs/sirensis/ul/drupal/modules/bounced_email/bounced_email.module on line 98.

The ip shown = 159.46.248.226 I believe this is my own router.

Is it possible that this error has got someting to do with my local security / firewall / router settings?
As far as I can see the other settings (pop3) are OK.

Any suggestions?

Comments

robert castelo’s picture

This error message affects collecting bounced messages, but shouldn't stop email from being sent out.

Make sure you are running the latest version of enewsletter.module.

Then set up a test newsletter, subscribe to it, create a node and include it in newsletter, click 'send now', run cron - you should receive the email.

Apstar’s picture

I have tried to send e-mail by selecting the button. The other settings are checked and seem correct.
After running cron.php nothing happens except for the error message discribed earlier.

It seems sending and receiving e-mail form e-mail newsletter isn't functioning right now.
I installed this version about a week ago, so it must be up to date I would think.

robert castelo’s picture

"I installed this version about a week ago"

Try downloading the eNewsletter module today and drop that into your installation, I frequently update it, you might be experiencing problems that where fixed a while back.

Also read back through the instructions above and make sure to complete each one. Sending is working fine, receiving is also working but configuring it can be difficult (i.e. you need to know exact settings on your sever).

Apstar’s picture

Tried again:

- Downloaded new module
- Installed using: enewsletter_combined.mysql
- 'bounced-email' table already exists error
- dropped 'bounced-email' tables
- Again Installed using: enewsletter_combined.mysql
- 'table xxx' already exists error
- disabled 'bounced-email' module
- enabled 'bounced-email' module
- Selected 'send now'
- Executed 'cron.php'
- Same error as above (1st message)
- Also no e-mail has been send

3 questions?

1. Do I need to have Outlook installed to send e-mail?
2. Is the 'send e-mail' account setting used in any way for sending (or is it only used to display the send adress)?
3. Is there a way to reinstall the module again, without dropping all tables involved first?

Thanks in advance! I'm really eager to get this module working as you can tell :)

robert castelo’s picture

"I'm really eager to get this module working as you can tell "

Yes I can tell, I'll try and help you out...

The enewsletter_combined.mysql database set up file is only for the first time that the modules are all set up.

After that update by downloading just the package on the eNewsletter page - where it says:

Releases
* Download latest release (cvs)

The direct link to the package is: http://drupal.org/files/projects/enewsletter-cvs.tar.gz

Once you've downloaded that, open the README.txt and scroll to the bottom - there are update instructions there listing any changes you need to make to the database.

Next install the two files in your modules/enewsletter/ directory:
enewsletter.module
enewsletter_send_receive.inc

Go to the module admin page on your site, if you need to update any of the component modules (e.g. bounced_email.module) you'll get a message to tell you. If so download the component module and upload the new files to your modules directory. Any database changes where already dealt with in the enewsletter README.txt above.

Sounds like your install is in a bit of a mess, I'd advise looking through the enewsletter_combined.mysql and dropping all the tables listed there, then run the enewsletter_combined.mysql file again. Also you could delete all the modules listed on http://drupal.org/project/enewsletter and upload the current versions to make sure you have a completely fresh install (note: if you run enewsletter_combined.mysql there's no need to use the database file of each component module).

Hope that helps.

In future I'll add a new UPDATE.txt file to the enewsletter directory and put these instructions and the update details in that.

robert castelo’s picture

Any luck?

Just uploaded a new version to cvs, there is now a UPDATES.txt file with instructions on updating this module.

Plus if you browse yoursite.com/cron.php it will give simple debug feedback.

Apstar’s picture

"Any luck" ... well a little

On friday I managed to send out an e-mail newsletter but it worked just once.
It worked when I changed the configuration of the mailbox port at the newsletter configuration.

I filled it with the following information: "110/pop3" because of the example written underneath.
(For POP connection usually: '110/pop3''. For IMAP usually: '143'.)
When I changed it to just "110" and started the 'cron.php' job I received the newsletter a little later.
But unfortunately I didn't manage to send a second newsletter.

In the admin section it I see the following error messages:

Type cron
Datum Zaterdag, 17 december, 2005 - 19:55
Gebruiker Albert
Locatie /drupal/cron.php
Bericht Laatste cron uitvoering is niet voltooid. English = Last cron run didn't complete
strengheid waarschuwing
Hostnaam 83.116.197.50 = The external IP adress of my router

Yesterday evening I downloaded the latest release of 'email newsletter' dropped all tables en reinstalled all modules by executing 'enewsletter_combined.mysql'. The result of the query was succesfull.

There are two things I can think of:

1. I need to run the cron.php job scheduled on the server, I will test this later on.
2. Also before I can connect to my test website I need to logon to the site first (before loggin on to my Drupal user account) So now I think I'm dealing with an security issue.

Question: what's the best way to schedule cron.php from a Windows XP machine. Also I will need to send name and password credentials to the server where 'cron.php' needs to be started.

robert castelo’s picture

When I changed it to just "110" and started the 'cron.php' job I received the newsletter a little later.

OK, so sounds like these are the correct settings for you.

The module requires a cron run to send out email, here's some info on how to do that:
Configuring cron jobs

Apstar’s picture

I still can't send out a new newsletter, unfortunately it only seemed to work once.
Think I got closer to the problem but still can't figure it out.

Things I tried the last couple of days.

- Complete new install
- Complete new configuration of the email newsletter module
- Removed extra password on our Drupal testwebsite
- Scheduled cron.php run with 'webcron' (every hour, every day)

At this time there are two mayor problems concerning the newsletter

1. After a succesfull cron.php job I don't receive any newsletters that have been send (to different accounts where I try to receive them). I assume the e-mail is being send by the same mechanism that it used for sending e-mail to other useraccounts. Tested this and received an e-mail almost immediately.

2. Cron.php only runs if I don't configure the 'receive' section in the configuration of the newsletter. When I do fill out any information the cron.php run displays a 'time-out' (page can't be displayed error message). This happens when it's run manually and also on a scheduled run.

robert castelo’s picture

This has caught others out in the past...

Have you created some new nodes (pages) and included them in the newsletter?

If there is no new content the newsletter won't be sent out.

By tye way, what system are you running this on? (OS? Apache? PHP? MysQL?)

Apstar’s picture

We did create content (story) with our 'newsletter' node selected.
On the frontpage the node name 'newsletter' is also displayed so this seems correct.

Here the info you requested:

http://ul.sirensis.nl/drupal/inf.php

If you wish I could create an admin account on our testsite so you can check the settings.

robert castelo’s picture

OK, use the contact form on my Drupal account to get in touch:

http://drupal.org/user/3555/contact

robert castelo’s picture

Status: Active » Fixed

Sorted :-)

robert castelo’s picture

Status: Fixed » Closed (fixed)
brashquido’s picture

Hi Robert,

Sorry for the rehash on this issue, but I've run into the same problem as described in this bug report and even after reading through both bug reports covering the same topic the solution still seems to escape me. I first tried this on my Windows XP SP2 / Apache test machine at work earlier today with the same result, and at first thought it might simply have been a configuration issue there. However I am still getting the same thing after creating a fresh Drupal site on my main testing server (see specs below) with the only additional modules installed being the ones required by enewsletter. I have little doubt that the problem exists between my chair and my keyboard, but I just simply cannot for the life of me see why this doesn't work. I am also running the Xoops CMS on this test server, and I set it to use the PHP mail() function and I was able to send e-mails to users without any trouble. On my previous install of Drupal I had mail being sent and even checked without problems from serveral modules (dba, notify, mailhandler, survey and Drupal itself)

This is what I did on my test server tonight;

1. Fresh Drupal install

2. Created "Articles" category vocabulary which was linked to the "story" node type, and added "Test Articles" as a term.

3. Copied enewsletter module and 7 required modules to their own directory in the Drupal module directory.

4. Executed enewsletter_combined.mysql script from enewsletter directory against drupal database.

5. Enabled enewsletter module and 7 required modules from the Drupal module admin screen.

6. Entered enewsletter config admin and set valid e-mail addresses for "From:", Reply-To:" and "Bounce Mailbox:". I then set my e-mail server DNS name for "Mailbox Host:" (mail.mydomain.com) and set my mailbox username and password (all other options left at default values)

7. Entered enewsletter admin and created "articles" newsletter with "Test Articles" term selected (all other options set to default)

8. Went into "My Account" setting and subscribed to "Articles" enewsletter list.

9. Created new story making sure to tick the "Email Newsletter" option and submitted it as a published story.

10. Went back into enewsletter admin to the newsletters node and clicked the "send now" option, and then clicked "send" again to confirm.

11. In my browser window I accessed http://mydrupalsite.com/cron.php

12. This is the error I get in my browser window when running cron;

warning: imap_open(): Couldn't open stream {mail.it-hq.org:110/pop3/notls}bounce@it-hq.org in C:\web\drupal\modules\bounced_email\bounced_email.module on line 98.

Time to send newsletter: Articles

At least 1 subscriber: YES

Another thing is if I try and register a new account after having installed enewsletter and associated modules, I get this error;

Fatal error: Call to undefined function: subscribed_form_publications_array() in C:\web\drupal\modules\enewsletter\enewsletter.module on line 705

The following are my environment details and enewsletter related file versions;

Windows 2003 Server SP1 / IIS 6PHP 4.3.10 (PHP Info = http://www.it-hq.org/phpinfo.php )
MySQL 4.1.14
MailEnable Standard 1.91 SMTP/POP3
ISAPI_Rewrite
Drupal 4.6.5 (clean URL's enabled)

bounced_email.module,v 1.2
html2txt.module,v 1.5
identity_hash.module,v 1.3
publication.module, v 1.12
templates.module,v 1.4
schedule.module,v 1.4
subscribed.module,v 1.5
enewsletter.module,v 1.17
enewsletter_send_receive.inc,v 1.6

I'd really appreciate any pointers you might be able to give me.

Thanks

jivyb’s picture

Same problem here:

warning: imap_open(): Couldn't open stream {mail.sweetike.com:110}bounce@sweetike.com in /home/....public_html/drupal-4.6.3/modules/bounced_email/bounced_email.module on line 98.

No email was received in the bounce account or in the account the newsletter was supposed to go to.