Need email server aid

[Christopher Chan]

>> Alvin, Chris has probably forgotten more about email than most people will
>> ever learn about it.
>
> Apparently not, if he thinks that:
>
> 1. HTTP is more reliable than SMTP.

Never said that. Just saying smtp won't necessarily make things any 
better for the wireless device remote control wise. Especially if the 
device itself is down. But as shown already, Alvin was not thinking 
embedded smtp server in device like Chuck was thinking so there is no 
right or wrong here.


> 2. SMTP adds too much "parsing overhead" (his words, not mine) for
> sending messages. What! Sending messages is SMTP's *job*, so I imagine
> the overhead is acceptable.

See above.


> 3. You'll lose mail sent to you if your SMTP server goes down.

Like when the device is down long enough for the mta to bounce the email.


> 4. You need a separate MX entry for each client that uses your mail server.

Again, Alvin missed the part where Chuck was thinking of embedding a 
smtp server in the devices for accept remote commands via email. Each 
device would need either an MX or a host record in DNS.


> 5. Spam can still get in your queue if the SMTP server requires a valid
> client certificate.

Never said that nor did I argue the point of using certificates. If I 
were to say something, it would be, this is painful for setting up.


> 6. Mail servers only have one queue.

Which is true depending on mta and setup but I never said mail servers 
only have one queue.


>
> Those are all ridiculous points he's tried to make.
>

I am sure we have both provided plenty of amusement for those who are 
interested.