NOTE:: Before reporting an issue, make sure you are running the latest version, currently 3.3.1
|Anonymous | Login | Signup for a new account||25-03-17 23:34 UTC|
|My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0008209||phplist application||Message Send Process||public||11-10-06 00:34||22-05-12 11:21|
|Target Version||FutureDevelopments||Fixed in Version|
|Summary||0008209: new queue processor|
|Description||This queue processor, loosely integrated with PHPList, will send out messages faster than the default processqueue.php.|
|Additional Information||This is just the initial revision - I am working to make this more complete such that it can be a replacement for the regular queue processor for a certain subset of PHPList users.|
|Tags||No tags attached.|
|Attached Files|| opq-0.1.tar.gz [^] (7,837 bytes) 11-10-06 00:34|
opq-0.2.tar.gz [^] (19,345 bytes) 21-10-06 02:16
opq-0.3.tar.gz [^] (31,600 bytes) 01-11-06 03:32
opq-0.4.tar.gz [^] (36,834 bytes) 11-11-06 02:58
implemented fast mail sending, sacrificing any personalization
i will have a plugin system to add features (usertracking, linktracking, etc)
default to fast mail sending if personalization not required
I think that as it stands, it might be a suitable replacement for the default queue processor for people who don't need the unimplemented features, and those who only send text+html (which is a standard for newsletters, i mean, really..) pretty soon now.
I will finish a few more bits of code and then run some more time tests.
from the readme
right now, the plugin system works and you can send out messages as long as you don't use the following placeholders:
FORWARD*, LISTS, LISTOWNER, SIGNATURE
clicktracking and usertracking are not implemented but they are next.
angle brackets on urls in the text version are also not there.
the footer addition code is very blunt. i will fix in the next version.
Still, only use this if you use USE_MANUAL_TEXT_PART. This will only send out text+html messages.
If you do not have any personalizable placeholders in your content, this will default (if OPQ_ALLOWFASTPROC is set) to fast mode which is ridiculously fast.
this doesn't do any error checking whatsoever with return codes from the MTA.
I also have not checked that the bounce processing system will still be able to manage messages sent by opq.
DO NOT USE IN PRODUCTION!
oh, and also, about the plugin system. the system is quite smart and also quite easy to understand, allowing people to modify the behavior of the system or extend the behavior of the system very easily. all the core features (footer, templates, placeholders, and eventually clicktracking and usertracking, etc) are implemented as plugins so they can be easily added/changed/removed.
version 0.4 from readme:
I just finished a sizeable redesign of the how things all worked together.
This should pretty much work now as a drop-in replacement for the regular processqueue, with the following caveats:
1. It can't be run from the web interface, only from the command line.
2. It will send text+html messages to all recipients. If you do not have USE_MANUAL_TEXT_PART set in your config, it will create a text version from the html.
3. Clicktracking is not yet implemented.
It is feature-complete for the small set of features that I currently use.
1. it sends out messages which can be handled by the bounce system when in regular mode
2. in mass mailing mode, PHPList's bounce system can handle the messages if the following patch is applied:
3. it is super-fast if you do not have any placeholders in your message, footer, or template, and you have VERP enabled.
I will be implementing click-tracking, and then cleaning up the code, refactoring, and documenting, and a 1.0 release should be relatively soon.
|Copyright © 2000 - 2017 MantisBT Team|