Most probably the problem is with firewall
Try stopping firewall and see if that works.
If so problem is with
SMTP_BLOCK = “1″ It should be “0″ for emails to work.
Most probably the problem is with firewall
Try stopping firewall and see if that works.
If so problem is with
SMTP_BLOCK = “1″ It should be “0″ for emails to work.
Round cube gives error “501: failed to set sender” while trying to send mails.
Solution :
Open Roundcube >> Settings >> Identity >> New identity.
Add the new identity and save the settings. Now the error should be vanished.
Getting following error while trying to login to webmail.
ERROR : Connection dropped by imap-server.
Solution:
Check mail log to see if there are any error
tail -f /var/log/maillog
Sep 8 11:04:21 server imapd: authdaemon: s_connect() failed: Connection refused
Sep 8 11:04:21 server imapd: [Hint: perhaps authdaemond is not running?]
Sep 8 11:04:21 server imapd: LOGIN FAILED, [email protected], ip=[::ffff:127.0.0.1]
Sep 8 11:04:21 server imapd: authentication error: Connection refused
If you are getting the above error restart
/etc/init.d/courier-authlib restart
Squirrel mail gives following error in direct admin
ERROR: Connection dropped by IMAP server. Query: CAPABILITY + directadmin
Also error :
ERROR: Could not complete request.
Query: SELECT “INBOX”
Reason Given: Internal error occurred. Refer to server log for more information. [2010-09-01 05:12:43]
Solution that worked for me :
Was a problem with DISK SPACE. Increase quota and it worked.
SMTP error from remote mail server after RCPT TO:<[email protected] >: host a24uall.info [ IP ]: 550-Verification failed for <[email protected]> 550-No Such User Here 550 Sender verify failed
Solution :
Login to remote server ( destinationdomain.com )and bypass the Ip for smtp sender verification check.
WHM >> Main >> Service Configuration >> Exim Configuration Editor >>
Edit ” Whitelist: Bypass SMTP time sender verifcation check ” and add the Ip address of “senderdomain.com”.
This should fix.
Following error is seen in tail -f /var/log/exim_mainlog
Berkeley DB error: PANIC: fatal region error detected; run recovery
SOLUTION
1 ) ===========
service exim stop
mv /var/spool/exim/db /var/spool/exim/db.bak
/scripts/restartsrv_exim
2 ) ===========
/scripts/exim_tidydb
Make sure exim is restarted and then watch mail log again after closing the current tab.
root@server [~]# service exim status
exim dead but subsys locked
Solution :
Stop cron
service crond stop
vi /usr/local/prm/ignore
Add the entry “exim”
Save and quit
service exim start
service crond start
service exim status