vBulletin Mods

Hello,

I'm facing a annoying problem with vB4.2.2 PL6: I cannot send e-mail anymore from vBulletin.

There is no e-mail for notification, no e-mail sent from the contact form, no e-mail sent to users... well, no e-mail :D

I ran the e-mail diagnostic utility and this is its reply:

The fact is that I can send and receive e-mails from my server. The contact e-mail address works fine when I use it with SquirrelMail, BUT it doesn't receive contact e-mails sent from the forum form.

Would you have any idea?

Thank you in advance!

Verify that smtp email processing is disabled.

If smtp is what you want to use, verify the login & server credentials are correct.

If you have log access on server level, send a test email while using for example tail while in a shell: tail -f mailllog | grep "[email protected]"

If not download the log, like thru ftp if it isnt a dedicated server with shell access & search for the email you sent to, im going to guess you should see a lot of errors if the site sends out daily notifications.

Hi Snakes1100 and thank you for your answer :)

The SMTP protocol is disabled in vBulletin options.

We have a dedicated server.

tail found nothing. We use exim4 and its log looks like this :

Block Disabled:      (Update License Status)
Suspended or Unlicensed Members Cannot View Code.

I skipped many lines that look like those ones.

I have no mail in queue as shown in main admin screen on vBulletin.

So I do not know where the problem lies... :confused:

Thank you for your help!

tail -f /var/log/exim_mainlog | grep "[email protected]"

If you say no outbound email works, then exim's mainlog should be full of clues as to why.

So to be sure I'm doing things right, I log on my server and run

tail -f /var/log/exim/mainlog | grep "[email protected]"

The i open the admin panel in vB and ask him to send a test e-mail via the diagnostic tools.

But nothing shows on the terminal of the server. The tail process is pending without any output.

I wonder where the chain is broken...

Thank you for your help, Snakes1100 ! :)

tail -f /var/log/exim_mainlog | grep "[email protected]"

Not exim/mainlog

Run that in a shell & then send a email.

Sorry for my silliness but the file doesn't exist:

Block Disabled:      (Update License Status)
Suspended or Unlicensed Members Cannot View Code.

It's in French but I guess you can understand :)

What goes wrong with these mails?

Thanks for your help!


edit: same error with tail -f /var/log/exim_mainlog | grep "[email protected]"

exim by default stores all its logs in /var/log.

not sure what your setup is or who may have did anything custom on it, but you'll need to find the exim logs & see why its failing to send out emails.

I'm surprised as I just checked on my computer by installing exim4 and the mainlog is in /var/log/exim4 as well.

I'm using Ubuntu 18.04 and our server runs on Debian 10. Maybe this point was different before, I don't know.

Do a search for the exim logs then.

find / -name exim_* -print

Here you are:

Block Disabled:      (Update License Status)
Suspended or Unlicensed Members Cannot View Code.

So I made the same for exim4 :

Block Disabled:      (Update License Status)
Suspended or Unlicensed Members Cannot View Code.

It appears they renamed & moved quite a bit in that OS version.

Youre gonna have to edit the config & find out where & what its naming the log files.

Once you find the correct log, then you can tail the log as you test & send out an email.

So... as far as I can understand, there is a big mess on our server. We actually have two different versions of PHP : 5.3 and 7. And vBulletin is using 5.3 which is not supported any longer. As our server uses PHP 7 for e-mails, it doesn't do the link between vB and the mail server...

I now have to plan cascading updates for vBulletin and PHP to make things right and only then make further mail tests.

I hope this will be sufficient.

Sorry for the disturbance and thank you again Snakes1100 for your help! I'll post news when I get some.

1st, you actually need to test - 5.3 may or may not be the issue, you simply need to verify that by checking the log php is using as explained in response to the PM.

Just because someone told you 5.3 is the issue, doesnt mean its so.

I didn't find in php.ini where errors are loggued...

Block Disabled:      (Update License Status)
Suspended or Unlicensed Members Cannot View Code.

Path is not specified so I guess it would be in syslog BUT when I try a diagnostic mail... nothing more shows in syslog.

Where could it be, by default ?