Hi -

My Notifications (and emails to users) hang "somewhere". I verified via the Wizard SMTP test that emails work. But when a notification (or email via Admin) is triggered, they hang. Then, sometimes a few hours, sometimes days/weeks, they all flow. I don't see them in inetpub anywhere. My SMTP IP in mail.config has to be right or they're not flow ever.

Some service etc seems to be stopping, then starting. Any ideas?

Keith

Here's some more info: Found the emails in the database in the yaf_Mail table. The "SendTried" column increments every few minutes, so it's trying.

Any clue why it's not succeeding?

Keith

I have exactly the same problem. I've spent all day trying to find a solution but like you, posting on this forum hasn't yielded any suggestions. In desperation I've mentioned this problem on Twitter to try and get some exposure.

David

Let me guess, these are in a shared hosted environment, right. You did great research on determining that YAF is attempting to send the email at intervals as designed, and that mail does (sporadically) arrive at its destination. It sounds like the problem lies outside of YAF and with the host provider.

Good luck,
Dave

Like Dave said, it sounds like an outside of YAF problem if it's trying to send the messages. Are you transporting over the network to a remote server, or to a local pickup folder (IIS)?

Sometimes, you can set the server host as "127.0.0.1" when you're on a shared server and should be able to send without authentication since it's your website sending through it's local mail server...

---

As with the original poster, Keith said which applies to me as well, we've both said that email is being sent when using the install wizard to test email settings so it's not an SMTP issue. The problem lies with email notifications not being sent when users register, instead they're queued in yaf_Mail.

In my case I am the hosting provider and have full control over the server, I also have multiple recipients in the notification and I believe this is the related to the problem in some way but without any errors in the log file it is difficult to tell. Setting the recipient to a single user has no effect.

David

I don't think it's an outside YAF event causing this. The YAF Installation Wizard works perfectly; also, I have another web application (on the same server) written in C# that has no issues with sending emails.

I did start deleteing the rows in the yaf_mail table. Not sure which record, but after 3-4 records, I deleted one and all the rows flushed and emails flowed.

I "suspect" there was a record in the table that caused the send mail method to fail. The "sporatic" actions, I'm guessing, are caused by the order of the sql query return (probably no ORDER BY in SELECT query). Sometimes a new email record would go into the table, change the order of rows returned by the query, and they'd be processed until the bad record was hit...then it'd hang again.

Sound reasonable?

Keith

I would agree with this summary. It seems that is there is a problem sending one mail item in the queue the whole process fails and no email is sent. I confirmed this by deliberately causing an error (more of this later), then registering as a new user so the registration notification was queued but not sent, removing the error, and registering another user. It wasn't until the first 'fault' email was cleared did the other queued email get processed.

There is a problem with the way queued email is being processed.

Now onto being able to deliberately cause the error. I have a customer who modified the english.xml localisation file via the web interface. This caused the fault in the queued email, replacing the modified english.xml with a sound copy eliminated the error. As yet I don't know which element in english.xml is causing the problem but it is clear that editing the localisation file can cause issues with processing queued email and this needs to be addressed.

I would agree with this summary. It seems that is there is a problem sending one mail item in the queue the whole process fails and no email is sent. I confirmed this by deliberately causing an error (more of this later), then registering as a new user so the registration notification was queued but not sent, removing the error, and registering another user. It wasn't until the first 'fault' email was cleared did the other queued email get processed.

There is a problem with the way queued email is being processed.

Now onto being able to deliberately cause the error. I have a customer who modified the english.xml localisation file via the web interface. This caused the fault in the queued email, replacing the modified english.xml with a sound copy eliminated the error. As yet I don't know which element in english.xml is causing the problem but it is clear that editing the localisation file can cause issues with processing queued email and this needs to be addressed.

Simply compare the differences of the english.xml file with the original one use WinMerge  to show the diffs.

And also if you have problems with yaf please mention which yaf version you use.

YAF 1.9.5.5

What's interesting is checking our database we see the same thing on ours (but we're still running an older beta so I never mentioned it. We'll be going to the current version in a week or so I figure and be able to report on it -- and we've also modified our english.XML file --

---

I can confirm the problem occurs in the version 1.9.6.1 RTW.

Unfortunately, this is proving to be a real headache as we HAVE to release a product that is bilingual as this is a public sector requirement and YAF doesn't support a language toggle.

This discussion has taken two paths. The mail hanging, and language.

Can we get back on the original mail branch?

Any suggestions on how to resolve this?:)

Not a suggestion, but just to inform that I have encountered no problems at all in mail flow leaving a standard english.xml file and working only on the Italian version of the language file.