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 2 3 [4] 5 6 ... 250
46
General Help & How-To / Re: SMTP with Amazon SES Problem
« on: November 23, 2014, 05:08:13 pm »
Hi Franklin,

On two separate systems, the following PHP test script works:
Code: [Select]
<?php
error_reporting
(E_ALL);
$sock=fsockopen('tls://email-smtp.us-east-1.amazonaws.com',465);
if(
$sock) echo "Socket established\n"; else exit("Socket could not be established\n");
echo 
fgets($sock,1024);
echo 
"> EHLO localhost\n";
fputs($sock,"EHLO localhost\r\n");
$line='';
while(
substr($line,3,1)!==' '){
        
$line=fgets($sock,1024);
        echo 
$line;
}

The result when run from browser or commandline is e.g.:
Code: [Select]
Socket established
220 email-smtp.amazonaws.com ESMTP SimpleEmailService-908880847 2G85c3kZxdN3aiX48I3
> EHLO localhost
250-email-smtp.amazonaws.com
250-8BITMIME
250-SIZE 10485760
250-AUTH PLAIN LOGIN
250 Ok

For me, everything seems to be working as expected. The SMTP conversation should be able to continue as normal. LMP does it the same way.

If this test doesn't return similar results for you you will need to speak with your host as they may have limited or restricted such PHP socket connections or be experiencing a technical issue.

Regards

47
General Help & How-To / Re: SMTP with Amazon SES Problem
« on: November 23, 2014, 03:55:18 pm »
Hey Franklin,

I have heard of other clients using LMP with SES so I wonder if the encryption requirement is new.

We may be in luck pursuant to this and this.

Try using the hostname "tls://email-smtp.us-east-1.amazonaws.com" on port 465.

Regards

48
General Help & How-To / Re: SMTP with Amazon SES Problem
« on: November 22, 2014, 09:20:19 pm »
Hi Franklin,

It appears there are two separate issues in your post.

1. "php_network_getaddresses: getaddrinfo failed: Name or service not known" suggests a DNS error. The PHP script is not able to do a hostname lookup to determine the IP to connect to. You might talk to your host about fixing that or try connecting by IP after looking up the host yourself.

2. LMP doesn't currently have any support for STARTTLS connections, however I will consider it for the future. Until then, please use an unencrypted service if available.

Regards,

49
General Help & How-To / Re: Imported users deleted by dailymail
« on: July 09, 2014, 12:57:21 pm »
Great news, can you tell us if you are including support for Transactional Email Providers: Amazon SES, Mandrill, etc?  That would make a huge difference, as I am finding that running my own server, even with SPF, DKIM, FBLs setup is next to impossible to get a decent delivery rate.

My understanding is Amazon SES supports SMTP sending.  You may be able to use it now for your bulk mailings.

LMP's entire email-sending PHP mail/SMTP process has been rewritten into one single class so add-ons will be much more straightforward and easy to implement in the future.

Regards

50
Hello,

There are a number of things that might cause this.  Please submit a support request of the type "Other / Bug Investigation" at http://listmailpro.com/support and I will do some hands-on testing and tell you exactly what's going on.

Regards

51
General Help & How-To / Re: Imported users deleted by dailymail
« on: June 23, 2014, 09:22:49 am »
Hi Alan,

The issue is caused by importing the old "Date Added" field.  If you omit this field the date will be re-generated and the problem will not occur.  I will make a note and consider how this situation can be improved or at least be made obvious.

An update is being worked on but there is much to be done yet.

Regards

52
General Help & How-To / Re: Signup Confirm Email Link Incorrect
« on: May 27, 2014, 12:17:00 pm »
Hi Dennis,

The link is built using the "Full path to ListMailPRO" on the Configuration page.  Please ensure that path is correct.  If it is correct and you still have a problem, please submit a support ticket of the type "Other / Bug Investigation" at http://listmailpro.com/support.

Regards

53
Working with a client who downgraded PHP 5.4 to 5.3 I have discovered that the issue appears to be restricted to PHP 5.4 and above, where the htmlspecialchars function's default character set was made UTF-8, as noted here.  Smart quotes do in fact appear to be supported under ISO-8859-1, used by LMP 1.88 and PHP 5.3.

Therefore, a better workaround than above for PHP 5.4+ might be (replacing $var with the proper variable name for each line):

Code: [Select]
htmlspecialchars($var, ENT_SUBSTITUTE, 'ISO-8859-1')
That way smart quotes may not be substituted with a UTF-8 sequence and need to be normalized.  (Apparently PHP doesn't recognize them as ISO-8859-1 compatible characters in UTF-8 mode.)

The easiest way to avoid the issue is to avoid smart quotes entirely.

The issue will be fixed in a future update when LMP moves to the UTF-8 character set.

Regards

54
The issue is with the PHP htmlspecialchars function, that returns a blank string when non-ASCII characters are processed.  The saved message data likely still exists in the database but is not displayed in LMP.  If you want to be able to load messages containing smart quotes so you can fix them instead of "losing" them, in editmsg.php (v1.88) do the following:

Change
Code: [Select]
                 <input type=text class=xbox name=txtsubj size=85 style=\"width: 488px\" value=\"".htmlspecialchars($txtsubj)."\"><br>to
Code: [Select]
                 <input type=text class=xbox name=txtsubj size=85 style=\"width: 488px\" value=\"".htmlspecialchars($txtsubj, ENT_SUBSTITUTE, 'ISO-8859-1')."\"><br>
Change
Code: [Select]
      <span class=table_inside_small>Text Message:</span><br><textarea style=\"width: 488px\" class=xarea name=txtcont rows=8 cols=85>".htmlspecialchars($txtcont)."</textarea><br>to
Code: [Select]
      <span class=table_inside_small>Text Message:</span><br><textarea style=\"width: 488px\" class=xarea name=txtcont rows=8 cols=85>".htmlspecialchars($txtcont, ENT_SUBSTITUTE, 'ISO-8859-1')."</textarea><br>
Change
Code: [Select]
      <textarea style=\"width: 488px\" class=xarea name=txthtcont rows=8 cols=85>".htmlspecialchars($txthtcont)."</textarea><br>to
Code: [Select]
      <textarea style=\"width: 488px\" class=xarea name=txthtcont rows=8 cols=85>".htmlspecialchars($txthtcont, ENT_SUBSTITUTE, 'ISO-8859-1')."</textarea><br>
This causes the htmlspecialchars function to substitute non-ASCII characters with a Unicode alternative, exposing the issue.  In LMP v1.88 and previous, Unicode characters will not display correctly and must be fixed before sending.  In the future, LMP will be fully UTF-8 compatible so you will be able to use and send messages containing smart quotes.

Edit: Updated with character set per next post.

Regards

55
General Help & How-To / Re: Daily Mail does NOT work!
« on: February 21, 2014, 04:04:01 am »
Hi Ruben,

Quote
I DID the Manual Dailymail and it APPEARED to be working properly... but then Two Days Later... it did NOT work properly!!!

By not working properly I assume you mean a message that the Dailymail Report said was sent was not received, as you previously described.  To troubleshoot such an issue I would again advise turning on the "Always write SMTP log" option on the Configuration page.  You can then check the log written to the LMP /attach folder to confirm that messages were received by the server as expected.  After that, LMP has no more control, and it's up to the SMTP server to make sure the messages get delivered.

Quote
Is there ANY way to test DailyMail and followups withOUT having to wait ANOTHER 24 hours?!?

Dailymail can be run manually at any time.  This will process and send followups and advance users receiving them one day.  You might disable the option "Do not allow dailymail to be run automatically until 23 hours 55 minutes has elapsed. (Recommended)" from within ListMailPRO on the Dailymail page if you're still in the testing phase with no live users receiving followups.  That option should actually be unchecked when using the suggestion of setting a task to run every minute or two for testing.

Quote
And, NOT having the timing of the Dailymail be kicked up that 24 hours?

You can run the cron task without processing any followups by calling the dailymail URL as follows via cron, however it is undocumented.  This would be the same as checking "Skip followup message/user processing and sending" when running Dailymail manually.

Code: [Select]
http://example.com/mail/dailymail.php?pw=YOURPASS&nofups=1
If there was the option to send followups and not advance users it might be overly confusing, and potentially harmful in a production environment...

Quote
I tried your suggestion of the "two minute" cron job.... but I really didn't understand HOW to make the silly thing work to USE the "two minute" cron job.

When a cron job is set up it runs automatically.  If it's set up correctly, i.e. the web-page-grabbing tool works, the Dailymail URL and password are valid, and the ~24hr time limit has passed or is disabled, then you should receive a Dailymail Report each time the task runs.

Quote
HOW do I go about doing that?

It would be done the same as on the Schedule Dailymail help page, however the timing would be different, a timing of * * * * * would be every minute.  */2 * * * * would be every two minutes.

Regards

56
General Help & How-To / Re: Daily Mail does NOT work!
« on: February 20, 2014, 09:31:29 pm »
Hi Ruben,

Quote
I waited two days for the Dailymail and Followups to send out, but they have not.

Setting up Dailymail is done with a scheduled task on your web host, as mentioned in the help files here.  Sometimes hosts don't support the wget program, or have a special way of setting up tasks that use it.  Some alternatives to wget can be found mentioned here.

It can be a little technical and tricky to test, so you may wish to ask your host if such a scheduled task, one that loads a URL each day, is supported and how to do it.  To test I might recommend removing all followups and setting a task to run every minute until the report starts coming through.  It may also be useful to remove the "1> /dev/null 2> /dev/null" part of the task which suppresses output when the task runs, so output is potentially emailed to you, which may result in some error messages you can use to diagnose the problem.  With followups, you could set up the task temporarily with the latter option and the wrong password, so the script doesn't run but an email might be received that indicates the page is loaded successfully - you could then update the password to the correct one and timing for once per day.

Quote
Only List 1 received the followup.

I can't say why only one email out of 2 expected were received.  It's possible the email landed in your Spam folder and you simply missed it.  It's also possible there was something that caused your web host SMTP server not to deliver the email once it was received by it.  If the Dailymail Report says the messages were sent they should have been sent to the SMTP server as expected.  You can enable the "Always write SMTP log" option on the Configuration page and check the log written to your attach folder to be sure.

For hands-on assistance you can use the official tech support options we offer.

Regards

57
Ruben,

Your message may have some "fancy" or "smart" quotes or apostrophes, i.e. ones that lean left or right and are not straight up and down, or other special characters that are not handled correctly by LMP's implementation of a PHP (5.4+) function that processes the message.  Remove the funny characters and it should work properly.

Regards

58
Hi Reg,

I am considering improving the sending process to include more options, such as SMTP-only sending, which would pave the way for using external services for all messages.  (Currently PHP mail is always used for some messages, even with SMTP enabled.)  Perhaps this could also be included.

I am currently deep in some other update stuff, so can't take this on immediately, but will keep it in mind.

You might be interested in implementing a DKIM hack to try to help improve deliverability.  It can be seen here.

Thanks for the suggestion.

59
General Help & How-To / Re: Changing the email sequence
« on: January 24, 2014, 08:46:50 pm »
Hi,

From the Followups page for the list, you can click "Reset Users" at the bottom of the followup listing which will display entry fields where you can choose a new sequence and delay for all users on the list.

If you only want to change those on sequence 1 to sequence 2 you will need to use a custom MySQL command from phpMyAdmin, commonly available through your web hosting control panel. To update users on list 389, sequence 1 to sequence 2, delay 0, login to phpMyAdmin, choose the ListMailPRO database in the left menu, click "SQL" near the top and enter:

Code: [Select]
update lm_users set cseq = '2', cdel = '0' where list = '389' and cseq = '1';
Regards

60
General Help & How-To / Re: installing on a linux box
« on: January 11, 2014, 11:45:16 am »
The reason they suggest port 587 is likely because port 25 is often blocked to prevent you acting as an email server.  The alternative port is needed if you want to use your web host, for example, to send email from an email client.  Hosts will typically open a port other than 25 for you to connect to.  It appears port 587 is an industry-standard port for doing just that:
http://en.wikipedia.org/wiki/Simple_Mail_Transfer_Protocol
http://en.wikipedia.org/wiki/Mail_submission_agent

When a mail server sends mail to an external provider, it connects to port 25, and this likely cannot be changed.

Quote
# host -t mx google.com
google.com mail is handled by 10 aspmx.l.google.com.

# telnet aspmx.l.google.com 25
Trying 74.125.129.27...
Connected to aspmx.l.google.com (74.125.129.27).
Escape character is '^]'.
220 mx.google.com ESMTP ob10si10920364pbb.37 - gsmtp

Quote
# host -t mx yahoo.com
yahoo.com mail is handled by 1 mta5.am0.yahoodns.net.

# telnet mta5.am0.yahoodns.net 25
Trying 63.250.192.45...
Connected to mta5.am0.yahoodns.net (63.250.192.45).
Escape character is '^]'.
220 mta1566.mail.gq1.yahoo.com ESMTP ready

The tests above were performed using a commercial server.  You can confirm whether or not your ISP blocks outgoing connections to port 25 by performing a similar test using telnet from a shell or command prompt.  If the connections are not blocked, you should check with your ISP to see if there are any prohibitions or terms regarding the sending of bulk commercial email.

I would say you likely need a business internet plan that specifically allows the sending of email.  For business accounts, a static IP would likely be provided so your actions could not adversely affect other users, and so there would be no unexpected issues with the public connecting to your services, such as to return bounced messages, etc.

Regards

Pages: 1 2 3 [4] 5 6 ... 250