Mail Archives: cygwin/2005/05/22/01:45:17
Never mind, I got ssmtp to work over SSL. ${EXIM_MAINTAINER} might want to
check if what I was trying to do can actually be done on Cygwin though.
--
Gary R. Van Sickle
> -----Original Message-----
> From: cygwin-owner AT cygwin DOT com
> [mailto:cygwin-owner AT cygwin DOT com] On Behalf Of Gary R. Van Sickle
> Sent: Saturday, May 21, 2005 10:47 PM
> To: cygwin AT cygwin DOT com
> Subject: I need some exim hand-holding
>
> Ok, I give. No mas, no mas.
>
> I have a new mutt build ready to go, but I can no longer test
> it since I've gone DSL. AT&T does [E]SMTP over SSL, and
> ssmtp (which I had been using) doesn't (the official Cygwin
> one anyway). So I'm trying to set up exim as a sendmail
> replacement, and of course getting millimeters away from it
> actually working and then being stopped cold by unknowns.
>
> I'm going to try building ssmtp with SSL support, but in the
> meantime, can somebody tell me what the secret is to getting
> exim to work in this
> situation:
>
> - This is on XP, NTFS, ntsec on.
> - This is send-only, as mutt has POP built in.
> - I'm trying to use it in this manner, in the Cyg-specific README's
> *nontsec* section:
> "6) Mail User Agent programs can use exim to send local and remote
> mail. If you are using mutt, add the following in .muttrc
> set sendmail="/bin/exim -i" . To use exim from cron, point the
> symlink /usr/sbin/sendmail to /bin/exim ."
> - I'm using mua_wrapper, and not using the daemon at all, so
> does this section still apply?
> "8) Due to file permission settings (there is no suid in Windows),
> Mail User Agent programs cannot call exim directly for local
> deliveries in a secure environment. They should smtp to exim on
> localhost (port 25).
> This restriction can be lifted (while maintaining some security)
> by using the -odq option and giving append permissions to the
> spool, input and msglog directories and the log files, and read
> permission to the /etc/exim.conf file.
> Deliveries are then made by the daemon on the next queue run.
> This restriction is also lifted if all modes are 0777 or 0666."
> I'm getting no failures that look like file permission problems.
> - I appear to have TLS/SSL set up correctly, since exim gets
> to the point where it receives a 221 and sends an EHLO or
> HELO. But then the AT&T server
> (apparently) just sits there, and after a few minutes drops
> the socket.
> - I've read everything I can find and FWICT what I have in
> /etc/exim.conf should work. I have of course tried many
> other permutations of options as well. Attached if a kind
> soul would care to look it over.
>
> The results of an "exim -d g DOT r DOT vansickle AT att DOT net" are also
> attached. Late breaking news: that was done using the same
> exim.conf which is attached, with my ATT username and
> password munged, but I get the same results when I have my
> real UN & PW in (what I believe to be) the proper exim.conf locations.
>
> So is it a Cygwin problem, an exim problem, or a Gary
> problem? I'll let you guys know how the ssmtp+SSL thing goes.
>
> --
> Gary R. Van Sickle
>
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -