I have just run x00's script and both received the email fine and got a page of information, of which the most salient parts are:
SMTP -> get_lines(): $data was ""
SMTP -> get_lines(): $str is "250 2.1.0 Sender OK "
SMTP -> get_lines(): $data is "250 2.1.0 Sender OK "
SMTP -> FROM SERVER:250 2.1.0 Sender OK
SMTP -> get_lines(): $data was ""
SMTP -> get_lines(): $str is "250 2.1.5 Recipient OK "
So, by my reckoning, there is no issue with phpmailer's ability to send an email via our smtp host to our mailboxes.
So any clues as to why creating new users comes back with the error and no emails being sent?
windows isn't officially supported but if should work. First you have to find if there is any out going mail traffic, which a task specific to your setup. That way you can rule out problems with vanilla.
The only other issues I can think for is preferences are not set up correctly for the the user, or either that or the activity table being corrupted or in need or repair.
Yes, it is Windows. The extremely odd thing is that I have just discovered in my Junk folder some emails from Vanilla. I checked with my other test users and they also had something in their Junk. Looking at the date stamp on them, they were generated during a period of testing where changes were being made. However, as Vanilla still kept returning the error messages, I was unaware that anything had gone out.
So, it would seem that at some point, something I changed enabled mail to get through but was junked by the Exchange server. Unfortunately, I cannot replicate it now :#
I'm still unclear as to why, if it had successfully sent a message (albeit getting junked), I still got the 'could not instantiate/could not connect' error?
Comments
try this script. you will need to edit it to match your case
grep is your friend.
I've tested fsockopen and it is enabled.
I have just run x00's script and both received the email fine and got a page of information, of which the most salient parts are:
SMTP -> get_lines(): $data was ""
SMTP -> get_lines(): $str is "250 2.1.0 Sender OK "
SMTP -> get_lines(): $data is "250 2.1.0 Sender OK "
SMTP -> FROM SERVER:250 2.1.0 Sender OK
SMTP -> get_lines(): $data was ""
SMTP -> get_lines(): $str is "250 2.1.5 Recipient OK "
So, by my reckoning, there is no issue with phpmailer's ability to send an email via our smtp host to our mailboxes.
So any clues as to why creating new users comes back with the error and no emails being sent?
what values are in $rt and what values are in the parameters in the lines with @mail ? when you debugged.
I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.
Sorry, I wasn't sure what your last post meant so I haven't applied any of that. Not sure where to make the changes or quite how e.g. add a var dump
Thanks for the continued support (and patience!)
can you post you conf/config.php file (obviously wit the sensitive parts removed)?
grep is your friend.
look in library/vendors/phpmailer/
make a copy of
class.phpmailer.php and store it somewhere on a local pc for safekeeping.
when you got the instantiate errors the error came from throw...
so modify class.phpmailer.php
throw new phpmailerException($this->Lang('instantiate'), self::STOP_CRITICAL);
change to by cutting and pasting this.
throw new phpmailerException(" val:" . $val . " to:" . $to . " subject:" . $this->Subject . " body:" . $body . " header:" . $header, self::STOP_CRITICAL);
this should tell you what parameters are used when attempting to mail.
I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.
hold on that for a second.
grep is your friend.
I think he took your advice x00 .
a long second.....
must be a lunch break, nap time or dinner
on a roll, and then no report back to command control.
I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.
Time works differently over here...
desensitised config.php:
Sorry, it's gone a bit wonky in the flesh for some reason, but the information is there
grep is your friend.
I presume you have the exact same details here than you used in the test.
you could tail the smtp log file
maybe try https://github.com/tualatin/tailforwindows or cygwin
You should be able to confirm, by triggering mail through forum posts.
grep is your friend.
wht smtp server are you using windows own or some other? Either way you will need to tap their logging.
grep is your friend.
Yes, these are the same details.
I'm about to get bogged down in other work duties, so I'll try your other suggestions later, thanks.
windows isn't officially supported but if should work. First you have to find if there is any out going mail traffic, which a task specific to your setup. That way you can rule out problems with vanilla.
The only other issues I can think for is preferences are not set up correctly for the the user, or either that or the activity table being corrupted or in need or repair.
grep is your friend.
Yes, it is Windows. The extremely odd thing is that I have just discovered in my Junk folder some emails from Vanilla. I checked with my other test users and they also had something in their Junk. Looking at the date stamp on them, they were generated during a period of testing where changes were being made. However, as Vanilla still kept returning the error messages, I was unaware that anything had gone out.
So, it would seem that at some point, something I changed enabled mail to get through but was junked by the Exchange server. Unfortunately, I cannot replicate it now :#
I'm still unclear as to why, if it had successfully sent a message (albeit getting junked), I still got the 'could not instantiate/could not connect' error?
you mail server mail have outgoing filters like spam assassin and clam.
You can try looking at the the mail header to see if there are any clues.
Also try an replicate the support name and email.
grep is your friend.