Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - DW

Pages: 1 ... 4 5 [6] 7 8 ... 250
76
Server Optimization, Tweaks / Re: Exim optimization (CPanel)
« on: May 11, 2013, 05:09:57 pm »
Hi Arpit,

Yahoo seems to employ rate-limiting on IPs that are not whitelisted.

Check out this post for more information.

Regards

77
General Help & How-To / Re: back ups
« on: May 09, 2013, 02:57:42 pm »
Hi Paul,

I had a look at your backup file and found the lm_follow table and data in there.

Perhaps your text editor is having trouble loading the whole ~30MB uncompressed file, or you need to wait a little longer for the file to load completely.

Regards

---
Update: Cause/Solution/Potential issue for Mac users

Quote
What is happening is when I click on the file to download it from the admin panel, my Mac unzips the file for me and drops the contents in my downloads folder. That file is clearly not complete as it is only 3mb. When I download the file via ftp and unzip it myself the file is 30mb.

78
Dailymail messages are sent the same way as manually sent messages, so if manually sent messages are received as expected followups should be received too.  Could there be a delay at the server and you have now received the messages?  Could the messages have found their way to your Spam folder and been missed?  Could you have exceeded a limit for sending imposed by your web host, which might be seen in their terms of service?

If SMTP is enabled on the Configuration page, and by enabling the SMTP log feature (Check "Always write SMTP logfile" in the Mail Sending Method section) we can confirm that followup messages are indeed sent to the server as expected.  The log is written to the ListMail /attach folder.  Once the messages are sent to the server, it's up to the server to deliver and client to receive them.

Regards

79
Another user asked for this feature recently and I gave it some thought.  Unfortunately it would be quite involved to change Dailymail in that manner, and would likely introduce new bugs into what has come to be a very stable process.  Dailymail was designed to run just once per day, and the rest of ListMail was built with that in mind.  I do see the value in the feature, though, so it may indeed be implemented in time.

I came up with a possible hack that could work without modifying ListMail.

1. The Dailymail cron task could be set to run with the (undocumented) &nosched=1 option to suppress scheduled message processing.
2. A separate script set to run more frequently for scheduled messages alone could be created.
3. The time to send a scheduled message could be added to the Subject line of the message, and be removed at sending time.  This would eliminate the need to modify the UI or database with new fields for time.

Basically the script in #2 would check for scheduled messages as per usual with the addition of checking the subject line to see if the time to send has been reached or passed.

Unfortunately I didn't complete this hack for the user, so I can't provide any code.

I am currently working on a new support system and other things on the main site.  Perhaps after that I will be ready to take on some custom work such as this.

80
General Help & How-To / Re: back ups
« on: May 08, 2013, 12:17:04 pm »
Hi Paul,

I can't think of anything except perhaps a server timeout issue, which should only occur with a certain server configuration and a very large database.

Is any other data or table missing?

I could investigate with the appropriate access, i.e. ListMail and FTP.  You can find an email address at the bottom of the Support page where I can be reached.

I am working on a new support system and will soon be more responsive. :)

81
General Help & How-To / Re: List Creation Trouble
« on: December 21, 2012, 02:50:53 pm »
Hmm, it's hard to say exactly what's going on, but we can try a few things.

Does it work properly with a simple test file, such as seen at http://listmailpro.com/help/import ?

Code: [Select]
"John","Doe","john@example.com"
"Jane","Doe","jane@example.com"

Are you on a Mac?  Sometimes Mac users need to add the following to config.php anywhere between the first and last line (starting and closing php tags):

Code: [Select]
ini_set('auto_detect_line_endings', true);
It's odd because it appears ListMail is reading your file and checking the email address formats and finding them correct.

The problem is most likely with the MySQL query that inserts the users.

For v1.88, try changing line 796 of edituser.php from:

Code: [Select]
@mysql_query($cmd,$link);
to:

Code: [Select]
@mysql_query($cmd,$link) or die(mysql_error());
This should output more information in the event of a MySQL error.

Regards, DW

82
Customization, Integration / Re: Making !remove automatic on all emails
« on: November 16, 2012, 05:49:21 am »
Justin,

Custom Text message codes should be processed before other codes, so you could set up a footer in one of those and include a Remove Link code in it.  Then you would simply use the one code at the end of your messages.  If there are any problems with that, you'd have to use two codes.  While it may be possible to set up a hack to automatically add codes or text, it can't be recommended or supported.  To put you on the right track, you might add to the message body before the call to the processmsg() function in admin.php.

As of v1.88, that occurs on line 2411:

Code: [Select]
list($xsubj,$xmsg,$xhtmsg)=processmsg($userid,$subj,$msg,$htmsg,'0',$typ,$list);
 So before that you might put:

Code: [Select]
$msg.="!custom";
$htmsg.="!custom";

This will add the !custom code to both the text and HTML message bodies.  The code will then be processed by the processmsg() function call on the next line.

\n's should be interpreted properly if between double quotes within PHP script.  If using single quotes they will not be interpreted.  When editing a message code within ListMailPRO simply hit Enter to add a line break.

This modification may have unforeseen consequences with certain messages or notifications and cannot be guaranteed to work as expected.

Regards,

Dean

83
General Help & How-To / Re: Problems with Umlaut in subject
« on: November 16, 2012, 05:27:26 am »
You might try setting the $charset variable in config.php.

Perhaps:
Code: [Select]
$charset = "UTF-8";

84
If you can still access the email address you used at purchase, try using the Password Recovery feature on the Download page.

85
General Help & How-To / Re: Mailjet
« on: November 16, 2012, 01:06:23 am »
This type of non-standard SMTP service is not currently supported.

86
General Help & How-To / Re: Spreadsheets
« on: November 16, 2012, 01:05:59 am »
Yes, if you export to Comma Separated Values (CSV) ListMailPro should handle it fine.

87
General Help & How-To / Re: import using database
« on: November 16, 2012, 12:59:56 am »
It's been a while since I looked at the code, but the script may require that all tables being worked with reside in the same database...

88
General Help & How-To / Re: PHP 5.3 + register_globals
« on: November 16, 2012, 12:58:11 am »
Quote
Is the current version of ListMailPro (v1.88) compatible with PHP 5.3?
Yes, it should work fine.

Quote
Will the current version of ListMailPro (v1.88) work with register_globals set to OFF?
Yes, LMP was designed to work with servers with register_globals either on or off.

Regards,

Dean

89
General Help & How-To / Re: dailymail needed for bounce.cgi
« on: November 16, 2012, 12:55:01 am »
I responded re: bounce.cgi here.

Quote
is the dailymail cronjob only required if i setup in configuration to use an email account oppose to bounce.cgi?
Yes, although it's recommended to set it up anyway as some maintenance tasks are performed.

Quote
when i had the cronjobs enabled it was sending my mail out automatically.
This should only happen if followup or scheduled messages are configured.

Regards

90
General Help & How-To / Re: bounce.cgi actually doing its job?
« on: November 16, 2012, 12:51:44 am »
The TESTBOUNCE email is supposed to be processed automatically triggering a "bounce.cgi Success!" email to the Administrator Email.  If you are checking email and seeing the TESTBOUNCE message, then the email is not being automatically forwarded to the bounce.cgi script as expected.  When bounce.cgi is enabled and configured properly you will not be checking the mailbox manually or seeing any messages that way.  Please see the Online Help at http://listmailpro.com/help/cgi for how forwarding email to CGI script is accomplished on various servers.  You may need to contact your web host to see if this feature is supported or possible for you.

Regards,

Dean

Pages: 1 ... 4 5 [6] 7 8 ... 250