sendmail broken
 

This is not really a vBulletin problem, but perhaps someone else has run into it.

I moved our vBulletin to a new machine. It is a colocation server running Centos/Cpanel/WHM. I just copied everything over there as it was on the previous machine and repointed the domain to the new machine by editing the ip address.

Everything seems to be working, but it is possible that some of the file permissions may not be correct. I did have to edit the permissions on the attachment tree.

The big problem is that sendmail is not working at all.

Since we are using email verification in registration and many users use email notifications on new threads, posts, etc. none of those features are working.

I can't even get the mail routing to work from the cpanel. Is there a good source of information on how to manage this stuff? We are not planning to use email services in any general way on this machine, so we did not do much to set up the email.

Can anyone give me a pointer on what needs to be checked and done?

You should be checking the exim_mainlog in /var/log and sending out a test mail while tailing it if you have ssh access to the server and find out the error code.

tail -f /var/log/exim_mainlog | grep "putemailherebetweenthequotes"

As you dont provide a domain, i can not check your domain for RFC failures.

Hmm - wouldn't this be the Exim log and not the sendmail one ?

/var/log/mail - maillog - mail.err - however it is called should be the file.

And is sendmail set setuid ?

ls -la `which sendmail`

Should show. Usually this setuid flag is removed on a simple copy process for a good reason ;)

chmod +s `which sendmail`

Sets this flag - of course if you really run Sendmail and not use another MTA like Postfix / Exim / Qmail.

And finally check if all Groups / Users are present with:

getent passwd
getent group

Just in case something is missing there.

Simple check if everything is working can be done while tail'ing the mail log:

tail -f /var/log/mail.err (if that's the file)

And on another console mail'ing yourself:

mail -s Test myownmailaddress@anotherdomain.com

Then some text, a Ctrl+D ends the editor and sends out the mail. This should give you some more info what could be wrong.

Ok seeing as you know everything, what email program does a cpanel server use, i'll give you a hint its not sendmail.

As stated in my first post, tail the exim_mainlog, you will find nothing in the maillog file.

I will try the suggestions so far.

I have no idea at the moment how to generate an email on this new server. In addition, it is not my email choice, but whichever one vBulletin is using. We have no intention of using this machine for serving mail.

Our domain is nawcc.org, however the vBulletin site is mb.nawcc.org. The mx record for nawcc.org points to an exchange server. All I want from the mail services on the whm/cpanel machine is to send out the mail generated by vBulletin and other applications. It would be nice to support the email integration mod, but we have another facility that performs a very similar mail reflector service, so I could do without that.

I have full root access to this machine, but I did not install the whm/cpanel. I did create the mb.nawcc.org domain on the machine and copied the vBulletin to it. I was a PDP-8/PDP-11/VAX developer for Digital Equipment years ago but I am very rusty with unix/linux. I spend a lot of time with --help.

There is currently no mx entry to mb.nawcc.org, only for nawcc.org.

--------------- Added [DATE]1255702892[/DATE] at [TIME]1255702892[/TIME] ---------------

The tail of exim_mai.nlog is shown below. There are lots of entries and several .gz files also, so it looks like vBulletin is trying to send out mails, but is not succeeding because the network does not believe it is authorized.

I would guess this is related to the missing mx record.

This was working just fine on our dedicated server at WestHost where they set up the server for us. We are mostly on our own with the colocation server.:confused:

--------------- Added [DATE]1255703505[/DATE] at [TIME]1255703505[/TIME] ---------------

Here is the tail from the maillog file.

Remove the ppls emails that you posted as well.

It appears you have issues on this server in terms of setup, unfortunately, there is not much we can do from here as you failed again to supply us with a valid domain to check for RFC issues.

Your domain is not setup correctly on the server, plus there might be basic setup issues like servername being incorrect, not much we can do from here, you should have your server admin correct these issues for you.

Once you fix these setup issues, yahoo should automagically un-defer your domain, but you might need to go file a form to correct it.

The mx record will not cause these issues as the sub-domain follows the main domain.

Do you mean the log entries from my previous post? I don't understand ppls emails.

I don't understand. Is http://mb.nawcc.org not an adequate domain name?

Sadly, I am the server admin along with an even greener employee of our organization. WHM does complain about the name of the server when we log on. I have asked my friend to look into that. The server itself is at nawcc-host.net, but the name locally appears to be centos-5.

I hope so, it is really inconvenient to have vBulletin unable to generate the internal emails. It means that I have to manually register all new users.

I don't quite understand this remark. The mail server for nawcc.org is an exchange server on a different machine than the message board. Most of our web services are on this machine with mb.nawcc.org, but mail and business operations are on windows systems with separate machines for our database and files, mail, and .net services. These are all inside the firewall.

Our "outside" sites are nawcc.org, mb.nawcc.org, nawcc-index.net and horology.edu. We also have community.nawcc.org which is served by an asp. Those sites which are subdomains of nawcc.org are to be included in the Single Sign On environment with net.nawcc.org as the authentication server (behind the firewall).

--------------- Added [DATE]1255706561[/DATE] at [TIME]1255706561[/TIME] ---------------

Ah yes. ppls = people's. Done

I'll chk the domain for you.

Our authoritative name servers are at Bulk Register. The name serving on the co-location site is intended to be "inside the firewall" type name management.

If we need additional ip addresses to sort things out, those are available, but I don't have the documentation on how to set up the virtual nic's. I would need to get that or have my associate do it.

Thanks for the help. I think I will eventually understand this, but I had not intended to learn this much about these systems this late in my career.

Yes, but when WHM sets up a site, it add's its own dns records on the server.

Additional ip's are not going to correct the issues, this is just a simple matter of correcting a few things on your server, proper hostname etc, also appears that i didnt notice that spamass is having issues as well, that shouldnt bother the out bound mail tho, but still needs to be fixed or turned off if there is no inbound mail for the domains on the server.

No problem on the help, your welcome.