i turned something off when i first set this up because it wouldnt send anything from the machine out im pretty sure that was chroot but mabye not
Dude, you’re a hazard! If you don’t know what something does…might be best to leave it alone.
So, the question then becomes, “How did you turn off chroot?” Because those log entries tell me that Postfix is still doing something with the chroot. If the init script is no longer maintaining the chroot, but Postfix is using it, that would cause a lot of trouble. (I’m all for disabling the chroot, if you know how. But mostly we just recommend folks stick with their OS defaults. Everything works if you let it.)
and the email is still sitting in the mail queue even though it says it sent there?
In that case, the mail we saw in the logs was not the one you sent. It was an error from Postfix. The message we saw referenced in the log can’t possibly still be in the queue.
So, where’s the rest of the log entries relating to that message?
well that was the only email log, but then came that second bit whihc i posted just above ^^
i disabled it thru webmin editing the master.cf bit as it told me somewhere (i cant quite remember which website now)
and i had to disable it to let me send email it wouldnt work at all beore that
Alright, lemme read some of the history of the thread here before I make any definite suggestions
However, in general, the way to control what IP address Postfix listens on is to set inet_interfaces in the main.cf file. And unless you’re really sure of what you’re doing, you’d generally include the localhost interface in all that.
But lemme re-read what all you guys have been doing here
-Eric
Alright, to sort of play along with your current setup (which is, well, a little odd :-), I think part of the problem may be that Postfix is not listening on the local interface.
Assuming that nothing else on your server is, what you may need to do is add this line to your master.cf:
[code:1]127.0.0.1:«»smtp inet n - - - - smtpd -o smtpd_sasl_auth_enable=yes[/code:1]
And make sure 127.0.0.1 is added to your inet_interfaces line in your main.cf – then restart Postfix.
-Eric
have sent it one, its still setting in the queue at the moment still with the destination address as mbcis@ns4.webtastix.co.nz though? but will see what logs go thru if it ever does anything
Alright, do you think one of us could just log in and take a look?
Something’s definitely going on that we’re overlooking here in the forums, but it’ll likely stand out a little quicker if we were looking at your system.
If that’s okay, you can send your root login details to:
Essentially, you need to enable the Debian volatile repository, and pull down the clam related packages from it to replace the ones you currently have installed.
Once you do that, I think you’ll notice a pretty big performance difference
Also, though, you may want to enabling the "Server Scanner (clamdscan)" in Email Messages -> Spam and Virus Scanning for additional performance improvements.
You have a gig of RAM, that should be plenty for the Clam daemon.
Feel free to yell if you have any questions on any of the above.
have sent those