[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [SAGE] choosing the proper max SMTP message size
- To: "a42n8k9 dejazzd.com" <a42n8k9@xxxxxxxxxxx>
- Subject: Re: [SAGE] choosing the proper max SMTP message size
- From: Tim Howe <vsync@xxxxxxxxxxx>
- Date: Wed, 02 Jan 2008 15:10:20 -0500
- Cc: sage-members <sage-members@xxxxxxxx>
- Dkim-signature: v=1; a=rsa-sha1; c=simple; d=quadium.net; h=to:cc: subject:references:from:date:in-reply-to:message-id: mime-version:content-type; q=dns/txt; s=blister; bh=JpxskmwIBX5j ToUWwNKpjgB17JE=; b=Q+G0dnnWvzoG+ymozuCHqPLtOSf6bPTwNSMmayL3O6uu +sLhkhsFEJDvuoZP1MxBoo3eox9b2fxPK4J0bXmZaILFCNQgybEPUJSMvEIxGLCD gt4talpm1k7JFcwLX8mzEeEvAiO7MYTD+r3N1r03CswU6HWY+L9jJIzbbmpi58I=
- Domainkey-signature: a=rsa-sha1; c=simple; d=quadium.net; q=dns; s=blister; b= d04EB86/U+ujd1ohX1tX8DRqSJyfYb/+3LT/wltT9GKu63AdvabTfpuID2BMHXy2 kyiP6xSu5CgKRkH4RmbvhclZqvItxxpd1hbh9v1qZHnOVQfySK9S3xnc1dANDOju xs3lww+fm90B4YT8tPgmeIxH0wlE+ZFuLk5yMPsiHuM=
- In-reply-to: <d2e3145810f2c780.477b9502@xxxxxxxxxxx> (a42n8k's message of "Wed, 02 Jan 2008 13:43:30 -0500")
- References: <d2e3145810f2c780.477b9502@xxxxxxxxxxx>
- Sender: owner-sage-members@xxxxxxxxxx
- User-agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.17 (Jumbo Shrimp, linux)
"a42n8k9 dejazzd.com" <a42n8k9@xxxxxxxxxxx> writes:
> The other side of the conundrum is that our users (and their
> correspondents) are not very technical and often have difficulty
> with FTP which results in help desk calls, etc.
[...]
> I'm curious about what most sites set the max SMTP message size to
> and how problems like this have been overcome or worked around.
Ran into this before myself.
If the problems users are running into are issues with
NAT/routers/firewalls, perhaps look into SFTP. User interfaces are
available such as Filezilla and WinSCP. It's still somewhat
"technical" in that users still need a username and hostname, but you
can set up key-based authentication, and it eliminates the nonsense
about ports and passive mode and anonymous and so forth. Bonus: it's
encrypted.
Another option would be WebDAV. Windows and Mac OS are supposed to be
able to just mount it and show it as a normal folder... very seamless.
You could run it through HTTPS to get the security. Apache can do
this out-of-the-box I think. Not sure, as I've only used the
Subversion module built on top of it.
It's frustrating... there isn't really any reason documents shouldn't
be sent back and forth. Except that users don't just send back and
forth but then it spreads out to a whole network of correspondents and
some get trimmed and variations of the document are created and not
tracked and ....
At least Microsoft has single storage of duplicated attachments
(although I haven't heard how intelligent it is, e.g., if the same
document is attached to a different message rather than forwarded).
If only the message store didn't fall apart given a slight breeze.
Cheers
Tim
--
But is [the U.S.A.] Christian? This is not a matter of angels dancing
on the heads of pins. Christ was pretty specific about what he had in
mind for his followers. What if we chose some simple criterion --
say, giving aid to the poorest people -- as a reasonable proxy for
Christian behavior? After all, in the days before his crucifixion,
when Jesus summed up his message for his disciples, he said the way
you could tell the righteous from the damned was by whether they'd fed
the hungry, slaked the thirsty, clothed the naked, welcomed the
stranger, and visited the prisoner. What would we find then?
-- Bill McKibben,
The Christian paradox: How a faithful nation gets Jesus wrong
<URL:http://www.harpers.org/archive/2005/08/0080695>