On Mon, 18 Jan 2010, Spyros Tsiolis wrote:
> Hello again people,
>
> OK, I've built XMail v1.26 against a CentOS 5.4 Box (i386).
>
> When I start xmail with the help of the "xmail" script
> (/etc/init.d/xmail start), the daemon "plays" on the back.
> If I telnet to either port 25 or 6017, everything is fine.
> Once, I telnet to port 110, it refuses connection and the daemon gets stopped.
Did you try to run in debug mode?
1) Stop XMail
2) Run
# /$PATH_TO_XMAIL/XMail --debug -Md ...
Where '#' mean "from root" and '...' means the remaining command line
parameters you usually pass to it
3) Try again the connection to port 110
If that does not spit out anything interesting, then run:
# gdb --args /$PATH_TO_XMAIL/XMail --debug -Md ...
> r
Where 'r' mean type 'r' and ENTER inside GDB.
Then try again the 110 connection.
> I haven't done anything different from what I've normally done the last two
> hundred
> times, so I am a bit buffled.
You've configured XMail about hundred times, and yet you don't know the
command lines switches? :)
> The only difference is the OS. Used to be slackware for many years. However,
> now
> it's been _at least_ four to five times that I installed XMail on CentOS
> without any
> issues (except the one I writing about now).
>
> Also another cryptic error message on Horde (http://www.horde.org/horde).
> This time for the SMTP daemon.
> If I try to send an e-mail from within horde (used to work believe me it's got
> nothing to do with horde), the system pops-up with the following msg :
>
> ----
> There was an error sending your message: LOGIN authentication failure [SMTP:
> STARTTLS failed (code: 220, response:
> Ready to start TLS)]
> ----
Probably Horder is fine, but you misconfigured SSL. The "220 Ready to start TLS"
is an OK message, and likely XMail refuses to talk to Horde (or viceversa)
because of SSL misconfigurations.
- Davide
_______________________________________________
xmail mailing list
[email protected]
http://xmailserver.org/mailman/listinfo/xmail
