mail problem: authentication required

faberk

New member
Joined
Jan 15, 2008
Messages
3
Hi,
starting from yesterday my customers, start to have problem sending mail using outlook, no problem using webmail.
I found this message into /usr/local/directadmin/da-popb4smtp:
process_ips has more than 200 id's, emptying it

also I saw that /var/log/maillog is not written.
The day before yesterday, I got I problem with disk space in /var, so I've deleted some logs, as /var/log/messages.

I've searched in the forums, before post, but nothing solve my problem.
Any hints?

Thanks
 
If you delete logs you have to restart the services that write to those logs.
 
Hi,
thanks for your answer, but what is the reason for the message into /usr/local/directadmin/da-popb4smtp:
process_ips has more than 200 id's, emptying it
any ideas?

Thanks
 
starting from yesterday my customers, start to have problem sending mail using outlook, no problem using webmail.
I found this message into /usr/local/directadmin/da-popb4smtp:
process_ips has more than 200 id's, emptying it
I'm guessing that there's only room in the process table for 200 IDs, so at that point DirectAdmin empties the table, and those who use the POPb4SMPT method of authentication will have to re-authenticate. Sounds reasonable. If you need more information I'd suggest you contact DirectAdmin Support.
also I saw that /var/log/maillog is not written.
The day before yesterday, I got I problem with disk space in /var, so I've deleted some logs, as /var/log/messages.
To amplify a bit more on Floyd's response:

Linux and FreeBSD are both multi-tasking operating systems. A multi-tasking operating system can't just delete a file if a different task has that file open for writing. So instead it marks it for deletion, removes it from the directory, and as soon as the task holding it open closes it, it then deletes it.

The side effect is that even though you've deleted the file, it's still on the server, and it's still taking up space, and in fact, it's still growing.

So to avoid this problem, close it. In general the easy way to close a logfile is to manually run logrotate.

Jeff
 
Back
Top