Topic: Large Incoming mail problem

[austwick]

Hi, I have been using sme server for about a year now for a community wireless network.  The mail server works perfectly for all but one small problem.  Each time an account receives a mail above 5mb lets say, it keeps recieving the mail over and over.  This floods the account with numourous copies of the mail.  The only way to stop the mail coming is to block the sending address in qmail via badmailfrom and then later re-allowing it.  I have tried putting a limit on the size of mails allowed but this made no difference (in the databytes file).  

The mailserver is hosted locally, and the internet link is a 2mb adsl 256kb upload.  Is this the problem?  Is there any way to tell qmail to refuse mails above 5mb?

Are their any logs I can provide that might give more information on what is happening?  I am not great with linux.

Thanks in advance for any assistance.

[raem]

austwick

Do a search on MaxMessageSize

[austwick]

Hi,

Thanks for this.  I have set a limit of 5mb to test.  

/sbin/e-smith/db configuration setprop smtpfront-qmail MaxMessageSize 5000000
/sbin/e-smith/signal-event email-update

I assume this limit is for INCOMING messages as well as outgoing?

[raem]

austwick

> I assume this limit is for INCOMING messages as well as outgoing?

Yes

[austwick]

RayMitchell - Wonderful!

Thanks for the prompt reply!  I am hoping this solves my problem.  Fingers crossed.

[raem]

austwick

Keep in mind if you are running clam you should also set the correct limits, see/search forums posts for the settings.

[austwick]

Okay... I have edited as follows:

clamav.conf & amavis.conf

In /etc/clamav.conf
ArchiveMaxFileSize 5M (from 10M)

In /etc/amavis-ng/amavis.conf
maxspace = 30M (from 60M)

I expect this should be okay.

Thanks again.

[smeghead]

.. I'd be wary of setting the maxspace too small; when you get an archive file that has to be unpacked for scanning it uses this value to decide how much disk space to use for the unpacking process, this doesn't affect the mail send/receive cycle directly.

You may wish to consider limiting the number of sessions that the server runs concurrently to allow more bandwidth per message during reception/sending (tho with 2Mb it shouldn't really be necessary):

running the following:- /sbin/e-smith/config show qmail
gives somthing like:
qmail=service
ConcurrencyLocal=10
ConcurrencyRemote=20
status=enabled

to change the concurrency values do (for example):

/sbin/e-smith/db configuration setprop qmail ConcurrencyLocal 5
/sbin/e-smith/db configuration setprop qmail ConcurrencyRemote 10
/sbin/e-smith/signal-event email-update
/etc/init.d/qmail restart

(Shamelessly stolen form a post by Ray Mitchell )

[austwick]

Thanks for the warning  I am going to run some tests to see if the problem is sorted.  

The concurrency thing seems to be quite a good idea - maybe this would solve the problem and allow me to increase the bandwidth of each message.  I don't use the mailserver for outgoing messages - these go straight to the ISP's mailserver.  The austwick mailserver is only for incoming messages (and messages sent via webmail).

The problem I was having was that my mailserver wasn't able to positively respond fast enough to the sending mailserver that it had succesfully recieved the mail usually because they have a small window size set (not sure of the correct terminology here - I am totally new to qmail).  

Thanks again guys.

[tandum]

Okay... I have edited as follows:

clamav.conf & amavis.conf

In /etc/clamav.conf
ArchiveMaxFileSize 5M (from 10M)

In /etc/amavis-ng/amavis.conf
maxspace = 30M (from 60M)

I expect this should be okay.

Thanks again.

Do you realise you need to make these changes in the templates for these files else risk losing the changes made at a reboot or similar?

[raem]

austwick

tandum is correct.

> clamav.conf & amavis.conf

In earlier versions these wre not templated.

In knuddis current version these are templated, but use
clamd.conf & amavis-ng.conf instead.

Make your changes to the appropriate fragments in
/etc/e-smith/templates-custom/etc/amavis-ng/amavis.conf/...
and
/etc/e-smith/templates-custom/etc/clamd.conf/...
and expand the templates.

[psdata]

Hello austwick,

I have one question. On what time did you have set to get het mail of you provider. 5 minutes, 15 minutes or 30 miniute's.

I have in the past a serveral SME boxes whith the same problem, you can set the max of a e-mail but that is not the solution.

Let us now the setting if the same with the problem here then the solutions follow's.

Regards

John

[pearless]

Hi,

 I followed this topic with interest as I have a 12MB attachement that I have received, but I can only ever download 8MB of the 12MB attachement using Thunderbird, or webmail.

I have tried setting the MaxMessageSize to 50MB, but no avail.

HELP!!!

I desparately need the attachement, is there any other way I can get it of my mail server?

Cheers Douglas.

[hkgonra]

I am very interested in this as well. I have been planning on running sme for primarily a mailserver. Currently our ISP hosts our mail providing us pop3 access and 20mb mailboxes. We are in the entertainmant industry and have the need to send large ( between 8 and 15mb ) attachments on a regular basis. I need a mailserver that can handle large attachments and be able to do imap with 1gb storage per user.

[raptor]

hi
i do try it and its work but how can i notify the user that his mail did not send due to limit, there are no notification message when i send message with attacment more than 5MB i thougt its gon but nothing

regards

Hi,

Thanks for this.  I have set a limit of 5mb to test.  

/sbin/e-smith/db configuration setprop smtpfront-qmail MaxMessageSize 5000000
/sbin/e-smith/signal-event email-update

I assume this limit is for INCOMING messages as well as outgoing?