Support/Comments for KoopsMailinglistX

Hi again,
is this a dead thread?
I tried to use KoopsmailingslistX v. 1.5 and found its not working with a SMTP Server Connection nor providing user authentication. (my server definitely requires user authentication) but instead of an error message I got a server crash!
Now I found KoopsmailingslistX is NOT using smtp connection by default, but includes a Swift SENDMAIL connection !

Now I researched some info on Swift and found KoopsmailingslistX uses v.1.3.0 , the latest Swift version is 3.2.6 !!!
Swift offers all possible connection types, KoopsmailingslistX only SMTP or Sendmail (in my case neither working) ?
Nevertheless I got it to work with the latest Swift version and a NativeMail connection, but had to do a lot of editing.

Now it seems as if everything worked fine (newsletter sent), but I get the following error message:


which seems to affect only the log entry !?
Now I have to work on KoopsmailingslistX again to write a log of sent mails which would surely be nice feature the developers should consider to build in.
This is my first site I develop with modx and I have to say that modules like KoopsmailingslistX won’t do the project any good. At least the documention needs considerable re-working !

If you want to know how to build working plugins and user-friendly documentation you may learn a lot from the Joomla community.
Have a look here: http://extensions.joomla.org

I’ve installed the mod and it seems fine apart from it only sends emails with very few characters - even two paragraphs of lorem ipsum don’t send. Any ideas as to why?

1.6 release.

Mostly bugfixes, with an additional feature to allow manually adding subscribers.

Multiple lists can be accomplished by installing multiple instances using different names for the install folders and corresponding multiple modules. Set the database table prefix accordingly in each config.php file.

I’ve got one site working nicely with three lists.

I am working on a rewrite (80-90% rewrite) version that is completely connected to the web user system in modx and that allow you to send modx documents instead of the editor. I will post it on the forums soon for testing.

dimmy

Damn Dimmy!
That sounds really nice!

-sD-
Dr. Scotty Delicious, Scientist.

Quote from: Dimmy at Aug 04, 2007, 03:22 AM

I am working on a rewrite (80-90% rewrite) version that is completely connected to the web user system in modx and that allow you to send modx documents instead of the editor. I will post it on the forums soon for testing.

dimmy

Excellent! That’s been in the back of my mind for a long time now. I’ll work on an option to send the mail using smtp or sendmail instead.

Quote from: sottwell at Aug 04, 2007, 01:00 PM

Excellent! That’s been in the back of my mind for a long time now. I’ll work on an option to send the mail using smtp or sendmail instead.

Wow. Susan, that would be flat out awesome.

-sD-
Dr. Scotty Delicious, Scientist.

maybe we can join forces

Quote from: Dimmy at Aug 05, 2007, 04:34 AM

maybe we can join forces

Sounds good. Although basically all I’m going to do is add a few fields to the config file, add a section to the "send" function to check for default (php mail()) or smtp, and add the calls to the Swift smtp functions. I’ll have the options set in either/both the config file or the module configuration.

How are you going to have it send a MODx document? Run the document through the parser then cache it and pick up the cached version for mailing? Or the user will just have to make sure there’s no chunks/snippets etc in the final document to be sent?

I already have a subscription snippet pretty much working, although it needs to do the double-opt-in thing before it’s legal for newsletter subscriptions in some places. It checks to make sure the email isn’t already represented in the specified web user group.

Quote from: sottwell at Aug 05, 2007, 04:54 AM

Quote from: Dimmy at Aug 05, 2007, 04:34 AM

maybe we can join forces

Sounds good. Although basically all I’m going to do is add a few fields to the config file, add a section to the "send" function to check for default (php mail()) or smtp, and add the calls to the Swift smtp functions. I’ll have the options set in either/both the config file or the module configuration.

How are you going to have it send a MODx document? Run the document through the parser then cache it and pick up the cached version for mailing? Or the user will just have to make sure there’s no chunks/snippets etc in the final document to be sent?

its parsing a document and making al the urls absolute then the output of the parser is send to the mailer as body content

I already have a subscription snippet pretty much working, although it needs to do the double-opt-in thing before it’s legal for newsletter subscriptions in some places. It checks to make sure the email isn’t already represented in the specified web user group.

this we did like tho mailing list worked already so we added 2 fields to the webuser attributes table called time and key. and we did losts of checks and even made a plugin to disable the checkbox in the webuser part of modx so that adding or removing a user is only posible when a user does this him/her self. of course you can add people tru database etc. also when a user is not in any other webgroup and he wants to unsubscribe he is deleted completely, but if the user is in any other group then he is only removed from the newsletter group.
the webusergroup is set in the config, while the root folder id (where your documents, newsletter documents are in) is set in the module for easy axes.

also in the overview you can now also see the non activate mail adresses
dimmy