dailymail does not work properly

[rffeddes]

Hi,

I seem not to be able to get this working properly.

I have the cron job installed:

/usr/local/bin/wget -O /dev/null -T 0 http://mysite.com/listmail/dailymail.php?pw=mypassword 1> /dev/null 2> /dev/null

I get a daily report, but the messages are not sent.

I also tried:
/usr/local/bin/php /home/admin/domains/mydomain.com/public_html/listmail/dailymail.php?mypassword 1>/dev/null 2>&1

But that one did not do anything at all.

I run a freebsd server with directadmin installed on it.

[DW]

Are you sending followup messages or scheduled messages?  If followups, what are the Seq and Delays(and/or Cron) set to for your followups and users (User Database page)?

Regards

[rffeddes]

I am sending follow up messages.
seq  delay
1       0
2       1
3       2
4       3
5       4
6       5
7       6
8       7
9       8

User database
list  firstname last name  email  seq  delay
1    Robert      ----          xxxx    3       0
1    Robert      ---           xxxx    5       0
1    Robert      ---           xxxx    5       0

Here is my dailymail report for today:
Dailymail Report for 2007-04-17 00:00:01

Totals: 1 lists, 3 users (1 new), 0 followups sent

List 1: eCourse Back Pain
3 total users (1 new), 0 followups sent

It did not send any emails again

Appreciate the help

[DW]

Greetings,

Followups are delivered when the Delay reaches 0 for a user.  At that time the followup at the current Seq # is delivered and the delay is reset to that set for the next Seq #.

If you receive the report the followups should reasonably be expected to be processed and sent, if due.

You stated you received a dailymail report with no followups sent, then mentioned that your users are at Delay 0.  With this in mind the (3) users should receive the next followup (Seq #3, #5 and #5 for the users you mentioned, respectively) next dailymail.

If dailymail is running and the users are not advancing even though they are at delay 0 and the Seq # they are on exists (for sending) then there could be a problem.

Regards

[rffeddes]

DW, thanks, I thought the delay was after signup day, looked in your helpfile again and see that it is written clearly there as well.

I moved over from a different solution where I was used to setting the delay after signup.

I set the cron job on every third minute just to check, it works ok.

I did however see some times the messages are not sent and I have to log in and do the resume thing.

What could be causing the not sending?

How can I add a resume to my cronjoB?

tnx sofar

[DW]

There is an auto-resume script, mentioned here:
http://www.listmailpro.com/help/autoresume.html

However it would probably be a good idea to look into why the mailings are stalling.  To get an idea of what's happening enable the option "Always write SMTP log" on the Configuration page.  You can then check the bottom of the log (in the ./attach folder via FTP) to possibly find an error message.

The problem might also be caused by this or this

Regards

[rffeddes]

OK,

Appeals to me better anyway to check the rootcause than get a workaround.

tnx so far

[rffeddes]

Hi Dean,

The issue is still persisting. emails not being sent. On a test list of 400, 348 were not sent.

I tried again on a small list and again stalls. I followed your two suggestions. Increased the timeout to 30secs. The timetester.php worked fine.

Here is the output of the logfile of the last fail:

> EHLO localhost
250-server.xxxxxx.com Hello server.xxxxxx.com [xx.xxx.xxx.xx]
250-SIZE 20971520
250-PIPELINING
250-AUTH PLAIN LOGIN
250-STARTTLS
250 HELP
LM: SMTP Pipelining Detected
LM: AUTH LOGIN Detected
> AUTH LOGIN
334 xxxxxxxxxxxxxxxxxxxx
> xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
334 xxxxxxxxxxxxxxxxxxxxxxx
> xxxxxxxxxx=
235 Authentication succeeded
> NOOP
250 OK
> MAIL FROM: <bounce@xxxxxxxxxxx.com>
> RCPT TO: <xxx@xxx.com>
250 OK
LM: Undeliverable. RCPT response was BLANK, possible timeout. Skipping.
> RSET
LM: Server did not respond to RSET.
LM: Reconnecting... Connected!
> EHLO localhost
250-server.xxx.com Hello server.xxx.com [xx.xxx.xxx.xx]
250-SIZE 20971520
250-PIPELINING
250-AUTH PLAIN LOGIN
250-STARTTLS
250 HELP
> MAIL FROM: <bounce@xxx.com>
> RCPT TO: <xxx@xxx.com>
250 OK
LM: Undeliverable. RCPT response was BLANK, possible timeout. Skipping.
> RSET
LM: Server did not respond to RSET.

[mike2]

I just glanced through this post, but I think I see your problem right away...

Why are you trying to send a 20MB email?

250-SIZE 20971520

This will likely never happen... and really probably shouldn't.

If you are sending some sort of huge attachment, I suggest uploading it to your website and just linking to it in the email.

[rffeddes]

Mike,

I am not trying to send a 20 mb file, it is all text autoresponder. I wouldn't have a clue where the filesize comes from. Definitely no attachments with these emails.

Thanks for thinking with me though!

[mike2]

Sorry about that, after a little closer look I believe that is the mail servers greeting showing you whats available.

I'll bet that's the size limit on the server...

What SMTP server are you on?

On mine after sending the Mail From and the RCPT to, I get these messages:

> MAIL FROM: <bounce@xxxx.com>
> RCPT TO: <mike@xxxx.com>
250 2.1.0 <bounce@xxxx.com>... Sender ok
250 2.1.5 <mike@xxxx.com>... Recipient ok

On yours I only noticed it said:

> MAIL FROM: <bounce@xxxxxxxxxxx.com>
> RCPT TO: <xxx@xxx.com>
250 OK
LM: Undeliverable. RCPT response was BLANK, possible timeout. Skipping.

Which seems fine, but is it?  Can you show a part of the log where it actually does deliver a message, since you say some are going?

[rffeddes]

mike,

I am on a freebsd 6.1 machine with directadmin, works with exim for mail.

here is a logfile where it went right, same size, so that is not the problem.


> EHLO localhost
250-xxx.xxx.com Hello xxx.xxx.com [xx.xxx.xxx.xx]
250-SIZE 20971520
250-PIPELINING
250-AUTH PLAIN LOGIN
250-STARTTLS
250 HELP
LM: SMTP Pipelining Detected
LM: AUTH LOGIN Detected
> AUTH LOGIN
334 xxxxxxxxxxx
> xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
334 xxxxxxxxxxxxxxx
> xxxxxxxxxxxxxxxxxxx
235 Authentication succeeded
> NOOP
250 OK
> MAIL FROM: <bounce@xxx.com>
> RCPT TO: <xxx@xxx.nl>
250 OK
250 Accepted
> DATA
354 Enter message, ending with "." on a line by itself
> SENT DATA
250 OK id=xxxxxxxxxxxxxxx
> MAIL FROM: <bounce@xxxx.com>
> RCPT TO: <xxxxx@xxxxxxxxxx.nl>
250 OK
250 Accepted
> DATA
354 Enter message, ending with "." on a line by itself
> SENT DATA
250 OK id=xxxxxxxxxxx
> QUIT
221 xxx.xxx.com closing connection

[DW]

> MAIL FROM: <bounce@xxx.com>
> RCPT TO: <xxx@xxx.com>
250 OK
LM: Undeliverable. RCPT response was BLANK, possible timeout. Skipping.
> RSET
LM: Server did not respond to RSET.

With the $smtp_timeout var in config.php set to 30, does this still happen?

Does the receiving email (RCPT TO) address have a valid domain, or is it invalid?

I don't suspect this is due to a per-connection limit - there is normally a very clear error message for that (ie. Too many messages this connection), so changing the SMTP "Reconnect" value should not help.  (Thinking aloud...)

Do you run the server?  There could be something in the mail logs when the error happens.

Regards

[rffeddes]

With the $smtp_timeout var in config.php set to 30, does this still happen?

Yes, I added that to the config.php and it still happens.

Does the receiving email (RCPT TO) address have a valid domain, or is it invalid?

They are all valid addresses. I just started a new test with a cron job to run dailymail every 3rd minute. With only 5 addresses I own on different domains. Still it stalls.

Do you run the server? There could be something in the mail logs when the error happens.

Yep I own and run the server it is a freebsd directadmin box. Tell me what to look for and I'll see if I can find it, if you want access to the machine, ok too.

[DW]

Ok, if you can provide root access, ListMail access and exact steps to recreate the problem I will be able to look closely at this.  Basically I will monitor the mail log (usually at /var/log/maillog or /var/log/exim_*log) while test mailing with ListMail to try to find a more descriptive error message.  You can "follow" the log with the shell command:

tail -f /var/log/<filename>

Then Ctrl-C to stop following

If you want me to take a look you can securely submit your info here:
http://listmailpro.com/support?t=other

Regards