Mails not sent

Hi,

No one has no idea about this issue ?

Thanks.

Hi,

I tried also with user form = emails are sent.

But, when using email fiels contact form, emails are not sent.

Any idea ?

Thanks

Hi,

I have still this issue. Any idea ? Thank you

I will work on this issue, but I am afraid I won't be able to before the end of August.

Robert

Ok,

Thank you.

hi!
This problem should be fixed now. There has been a bug with passing the mail_to value.
The fix is committed to the 6.x-1.x-dev version. Download the latest version from today and the problem should be solved for you

Hi,

Thank you.

Here are my findings thru my trial of today dev version :

1) I can access email form
2) I sent a message, but didn't see any OK message
3) I installed mail_logger module to try to see outgoing message
4) Now, I can't access to the email form
5) I uninstalled mail_logger module ( module + unistall)
6) I can't access to the email form

So, send didn't work for me, and there may be a conflict between email field and mail_logger

I will put an issue on mail_logger to.

Hope this may help.

Thanks

hi!
can you look into the email module folder and open the email.module file. in the 3rd line, there is the CVS version number. It should be v 1.9.2.8.4.6 2008/07/30 11:10:22 to get the sending working.
It's possible that the dev snapshot doesn't contain the latest changes yet.

Fine.

Mails are sent now with the 1.9.2.8.4.6 2008/07/30 11:10:22 Version.

Thanks a lot.

I have not tried one more time mail_logger. Do you want me to try both email field & mail_logger to know if the conflict pb remains ?

great that the contact form works for you now.
I tried the mail_logger module and I can't see any conflict.
I added a RC1 with the latest code. Try it out and report back, if you see any problems. Thanks :)

Great.

I tested this :

1) Email Field 6.x-1.0-rc1 = mails sent ok
2) Email Field 6.x-1.0-rc1 + mail logger 6.x-1.0= mails sent ok
3) Email Field 6.x-1.0-rc1 - mail logger 6.x-1.0= mails sent ok

Bravo & thank you.

Automatically closed -- issue fixed for two weeks with no activity.