View Issue Details

IDProjectCategoryView StatusLast Update
0002414phpList 3 applicationSubscribe Processpublic14-03-05 12:55
Reporterblootplazma Assigned To 
Status resolvedResolutionunable to reproduce 
Product Version2.8.12 
Summary0002414: Admin Copies of subscribe messages fail
DescriptionI have enabled the feature "Does the admin get copies of subscribe ..." by setting the value to "true" on the config page. Starting from that momment, I get the following entries in the event log whenever such message is sent (e.g., when a user subscribes):

Error: empty To: in message with subject Lists subscription to send

The message _is_ successfully sent to webmaster@[DOMAIN], however, it is apparently not sent to any administrators.

The messages in the eventlog stop immediately when I disable the feature again.

Please note that I have configured two admins, i.e. the preconfigured admin account and one extra account with admin priviliges (but without super-admin priviliges). Both definitely have an email-address configured in the
TagsNo tags attached.



18-02-05 00:47

administrator   ~0003554

I can't replicate this in 2.9.3, so I will presume it's fixed. If you can replicate it post a comment, otherwise we can close this.


11-03-05 21:24

reporter   ~0003869

I'm getting the same error "Error: empty To: in message with subject List unsubscription to send" but the source of the problem has nothing to do with admin getting feedback.

Today we sent out 1700 messages to our mailing list. After about 135 messages we got the above error message, followed by "Sleeping for 20 seconds, aborting will now quit" and then "A process for this page is already running and it was still alive 2397 seconds ago"

This continued on until event 800 when phplist decided it had enough and quit. No event message, it just stopped.

Any ideas? Sorry if this isn't the correct place for this. The above error message isn't well documented at the moment.



14-03-05 12:55

administrator   ~0003874

if you get "A process for this page is already running and it was still alive 2397 seconds ago" it means you have fired off two send processes, and one of them is still running. In order to not get your server to grind to a halt, you can only have one process at a time. Try firing one off later.