I agree, I'm looking for a technical solution to a much bigger problem. Unfortuneatly, you can't fix stupid. I often have to deal with people who can barely attach a file to an email, asking them to check what size that file is or to send it using another method is out of the question (imagine heads popping off and eyes glassing over). On top of this, the people that are sending the files are from a different organization, I have no control over what they do, and if they say "I sent the file", it is my ass that gets reamed if we don't get the file because the server didn't want to accept it or choked on it. I don't really care about efficiency, the longer it takes to get the file from here to there the more likely the people who want to send the files are to wake up and start looking for a better file transmission method. I just have to get it to work this way until then.
Spam protection is really a nice-to-have. While we have seen a little more spam lately, usually it isn't so much to be a bother. The Anti-Virus is a must, although I have gotten some suggestions to just skip virus scanning for large files. I'm not sure I understand why a large file would be less likely to contain a virus though. stuart > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of > Darren Spruell > Sent: Wednesday, February 21, 2007 12:57 PM > To: misc@openbsd.org > Subject: Re: Email server and large Emails. > > > On 2/21/07, stuartv <[EMAIL PROTECTED]> wrote: > > spamassassin. Lately, we have been receiving emails with > > larger and larger attachments which has been causing the > > clamav to take to long scanning them and thus a time-out and > > again, no more email until I get it straitened out. > > > > So now to my question. What software works really well for > > an internal mail server? I would like some spam protection > > and I NEED Anti-virus, and I need it all to work even when > > a customer sends an email with a 50M file attachment because > > they sometimes do. > > IMHO you're trying to find a technical solution to a bigger problem. > Consider limiting the size of attachments that go through your email > gateway; SMTP isn't an efficient protocol for bulk file transfers, and > like you've found out your CPU and I/O-heavy filtering applications > don't work well with it. Organizations commonly limit the size to 10 > MB or under; anything larger you can find an alternate (more suitable) > method for file transfer (SFTP, or FTP if not sensitive come to mind.) > For internal-only use a file server can be useful for this. > > If you're pounded by spam, consider implementing spamd in front of > your mta (externally) to cut down on the volume that your content > filters have to process. > > DS
