Hello from the Eighth Doctor
One of my clients still believes Linux, especially Slackware can't play well within a
Windows managed domain.

He wants me to setup a reasonably simple setup that would enable mail to be sent
from the Linux system to a Windows system.

I've started reading the man pages for fetchmail, and imap. My next step would be
the document pages and the howtos. Any further suggestions?
----
Gregg drwho8 att dot net

The Eighth Doctor wrote:

> Hello from the Eighth Doctor
> One of my clients still believes Linux, especially Slackware can't play
> well within a Windows managed domain.
>
> He wants me to setup a reasonably simple setup that would enable mail to
> be sent from the Linux system to a Windows system.
>
> I've started reading the man pages for fetchmail, and imap. My next step
> would be the document pages and the howtos. Any further suggestions?
>

Windows mail clients or Windows mail servers ?

Linux servers or Linux clients.

If you've never configured an email system at the server level before then
beware that you have an awful lot to do to understand the vital parts.

In article <Ht6dnfStUMEkEWzcRVnyjw@eclipse.net.uk>,
invalid@frequentous.co.uk says...
>
>The Eighth Doctor wrote:
>
>> Hello from the Eighth Doctor
>> One of my clients still believes Linux, especially Slackware can't play
>> well within a Windows managed domain.
>>
>> He wants me to setup a reasonably simple setup that would enable mail to
>> be sent from the Linux system to a Windows system.
>>
>> I've started reading the man pages for fetchmail, and imap. My next step
>> would be the document pages and the howtos. Any further suggestions?
>>
>
>Windows mail clients or Windows mail servers ?
>
>Linux servers or Linux clients.
>
>If you've never configured an email system at the server level before then
>beware that you have an awful lot to do to understand the vital parts.

Hello from the Eighth Doctor
Urm... Okay. Both at the client level. It would be a regular mail server sitting on
Linux.

Early on, I did look at the problems of setting up a mail server for Windows. I'd
rather not discuss it further.

The Linux one actually seemed easier.
---
Gregg drwho8 atsign att dot net

On Fri, 21 Jan 2005 22:32:05 GMT, The Eighth Doctor <drwho8__NOTME__@att.net>
wrote:
> One of my clients still believes Linux, especially Slackware can't
> play well within a Windows managed domain.
>
> He wants me to setup a reasonably simple setup that would enable mail
> to be sent from the Linux system to a Windows system.

You can try pointing him to the various RFCs for email (821, 822, 1939,
2821, 2822, etc), to explain that it's all protocol-based rather than
OS-specific.

You will need to take care with this, though. If you appear to be
having trouble getting this working, your client will still think the
same, so make sure you know what you're doing before you do in there.

> I've started reading the man pages for fetchmail, and imap. My next
> step would be the document pages and the howtos. Any further
> suggestions?

You'll need a reasonable understanding of how Internet mail works,
before you attempt this (you seem to be confusing the terms client and
server, at least). I'd start with this:
<URL:http://www.tldp.org/HOWTO/Mail-Administrator-HOWTO.html>.

You then need to decide which machine is going to play the client role
and which is going to play the server role & decide on a transport
protocol. Will the Slackware box pass the email on by SMTP? Will the
Windows box collect the email by POP3/IMAP? What software will you be
using (fetchmail won't do what you describe)? Those are rhetorical
questions that you need to think about, by the way.


--
Simon <simon@no-dns-yet.org.uk> **** GPG: F4A23C69
"We demand rigidly defined areas of doubt and uncertainty."
- Douglas Adams

Simon wrote:
> before you attempt this (you seem to be confusing the terms client and
> server, at least).

or maybe not, and his client is really worried that if you're on a linux
desktop machine you cannot send an email to someone who will read it on a
windows desktop machine. people have asked me this, and appeared quite
surprised when i said that wasn't a problem at all.

--
Joost Kremers joostkremers@yahoo.com
Selbst in die Unterwelt dringt durch Spalten Licht
EN:SiS(9)

On 22 Jan 2005 00:44:58 GMT, Joost Kremers <joostkremers@yahoo.com> wrote:
> Simon wrote:
>> before you attempt this (you seem to be confusing the terms client and
>> server, at least).
>
> or maybe not,

Sorry, I probably wasn't clear. I was referring to his follow-up to
Keith, in which he implied that he wanted both of them to be clients
(whereas, to transfer email, one needs to act as a server, at least
temporarily).

> and his client is really worried that if you're on a linux
> desktop machine you cannot send an email to someone who will read it on a
> windows desktop machine. people have asked me this, and appeared quite
> surprised when i said that wasn't a problem at all.

I've had the same reaction. When talking to some people, they didn't
expect me to be able to read their email or visit a web site from
anything other than Windows, although they had an idea that it might be
possible on a Mac. In my old job, I spoke to a customer that didn't
think she'd be able to send email because our email servers didn't run
Windows.


--
Simon <simon@no-dns-yet.org.uk> **** GPG: F4A23C69
"We demand rigidly defined areas of doubt and uncertainty."
- Douglas Adams

In article <slrncv37gt.7a7.usenet@dustpuppy.no-dns-yet.org.uk>,
usenet@no-dns-yet.org.uk says...
>
>On Fri, 21 Jan 2005 22:32:05 GMT, The Eighth Doctor
<drwho8__NOTME__@att.net>
>wrote:
>> One of my clients still believes Linux, especially Slackware can't
>> play well within a Windows managed domain.
>>
>> He wants me to setup a reasonably simple setup that would enable mail
>> to be sent from the Linux system to a Windows system.
>
>You can try pointing him to the various RFCs for email (821, 822, 1939,
>2821, 2822, etc), to explain that it's all protocol-based rather than
>OS-specific.
>
>You will need to take care with this, though. If you appear to be
>having trouble getting this working, your client will still think the
>same, so make sure you know what you're doing before you do in there.
>
>> I've started reading the man pages for fetchmail, and imap. My next
>> step would be the document pages and the howtos. Any further
>> suggestions?
>
>You'll need a reasonable understanding of how Internet mail works,
>before you attempt this (you seem to be confusing the terms client and
>server, at least). I'd start with this:
><URL:http://www.tldp.org/HOWTO/Mail-Administrator-HOWTO.html>.
>
>You then need to decide which machine is going to play the client role
>and which is going to play the server role & decide on a transport
>protocol. Will the Slackware box pass the email on by SMTP? Will the
>Windows box collect the email by POP3/IMAP? What software will you be
>using (fetchmail won't do what you describe)? Those are rhetorical
>questions that you need to think about, by the way.
>
>
>--
> Simon <simon@no-dns-yet.org.uk> **** GPG: F4A23C69
> "We demand rigidly defined areas of doubt and uncertainty."
> - Douglas Adams
>
Hello from the Eighth Doctor
It happens that I am only reporting what the client told me in his questionare
regarding the job request. I do know the difference between the two. Pine, mutt,
mail, they are all clients. Imap is of course specie of a server.

My client is, ah, someone who isn't computer savy.
----
Gregg drwho8 atsign att dot net

The Eighth Doctor wrote:
> Imap is of course specie of a server.

erm, no, it's not. IMAP ("Internet Message Access Protocol") is a protocol
for communications between a mail server and a mail client, with the goal
of allowing the client access to the messages stored on the server.

i don't doubt that you know that, but in dealing with computers, it helps
to be extremely precise about things. helps prevents misunderstandings and
problems.

--
Joost Kremers joostkremers@yahoo.com
Selbst in die Unterwelt dringt durch Spalten Licht
EN:SiS(9)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Joost Kremers <joostkremers@yahoo.com> trolled:
> The Eighth Doctor wrote:
>> Imap is of course specie of a server.
>
> erm, no, it's not. IMAP ("Internet Message Access Protocol") is a protocol
> for communications between a mail server and a mail client, with the goal
> of allowing the client access to the messages stored on the server.
>
> i don't doubt that you know that, but in dealing with computers, it helps
> to be extremely precise about things. helps prevents misunderstandings and
> problems.

No, Joost. Being "precise" or, more correctly in your case,
"anal", just gets in the way of things most often.

cordially, as always,

rm

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8

iQA/AwUBQfG99OEckfDWS6x8EQID4ACgnjcN6xT8V0QVoqxYGhoFYc xQ3HMAnj4j
3zpEAS926IfIg1s5OKhuuH5G
=YJ8t
-----END PGP SIGNATURE-----

In article <V5jId.62449$W33.1892776@news20.bellglobal.com>,
rm@justlinux.nope.ca says...
>
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Joost Kremers <joostkremers@yahoo.com> trolled:
>> The Eighth Doctor wrote:
>>> Imap is of course specie of a server.
>>
>> erm, no, it's not. IMAP ("Internet Message Access Protocol") is a protocol
>> for communications between a mail server and a mail client, with the goal
>> of allowing the client access to the messages stored on the server.
>>
>> i don't doubt that you know that, but in dealing with computers, it helps
>> to be extremely precise about things. helps prevents misunderstandings and
>> problems.
>
>No, Joost. Being "precise" or, more correctly in your case,
>"anal", just gets in the way of things most often.
>
>cordially, as always,
>
>rm
>
>-----BEGIN PGP SIGNATURE-----
>Version: PGP 6.5.8
>
>iQA/AwUBQfG99OEckfDWS6x8EQID4ACgnjcN6xT8V0QVoqxYGhoFYc xQ3
HMAnj4j
>3zpEAS926IfIg1s5OKhuuH5G
>=YJ8t
>-----END PGP SIGNATURE-----
Hello from Gregg C Levine
No he corrected one of my many mistakes when typing quickly. Which I
expected. I certainly didn't expect you to insert your annoying remarks, although
I should have expected it. We didn't ask you for advice, as usual. I now realize,
what I realized when I sent the message, that imap is that name for a messaging
protocol. Imapd is one of the servers who sends them.
----
Gregg drwho8 atsign att dot net