>I wonder how you all manage your users attachments? With DSL and other
>high-speed connections, attachments are running rampart. We have customers
>calling and complaining that they can't receive 30-40MB attachments because
>their mailbox is to small.

It's your decision.  You set the mailbox size and the users deal live with 
it.  Daniel said Imail does expose your mailbox size in the

SMTP 250-SIZE XXXXXXX

response code.  So at least huge files will be blocked at the protocol 
level rather than at the Imail disk directory level.

Open a few of your Imail log files and search on 250-SIZE to see what 
others are doing.  A lot of mail servers don't say anything, while in my 
log of Friday, I see (nothing), 0, 2, 2.5, 3, 4.1, 5.6, 6.5, 7, 10, 13, 14, 
16.7, 17, 20, 25, 100 megs.  I wonder if the last site had a typo of one 
extra zero?

>Do you all setup ftp servers for the customers to use?

That's the answer (as is Serv-U).  I've suggested this several times, but 
most users can barely manage their mail program never mind an ftp 
program.  Another approach would be using a browser to an ftp site.

>Do you have an anonymous ftp server for all?

That wouldn't work since everybody could DL everybody else's files.  And 
for a file site viewed through a browser, you need an authentication page, 
and, better, per-file DL authentication.

>That doesn't work in my book because all
>ttachments are available to everyone. Or do you set up a username for each
>customer that their clients can use?

That's the only practical way, if ftp was acceptable.  This brings up the 
issue of the ftp server and Imail being able to use an authentication 
protocol such as radius into an external radius server, so the mail users 
would only have one username/password for POP3, SMTP AUTH, and ftp.

A bigger issue is whether we need to sell our services with the notice that 
infinite bandwidth consumption and infinite disk space is NOT FREE.

Len

Please visit http://www.ipswitch.com/support/mailing-lists.html 
to be removed from this list.

Reply via email to