From Martin Diedrich <martin@mdiedrich.de>

The dispatch of email-appendices about the HAMSTER is possible normally only up to sizes of about 2 MB. Bigger mails cause a mistake message as well as the demolition of the news.

This behavior lies in the fact founds that the HAMSTER contains a size limitation for emails and news-Postings. This size limitation is put down in the file "hamster.ini" and between emails and news generally as well as between sending and receiving is distinguished from emails in the special. It is worth to the entries following:

Limit for line length and text length of the locally received articles,

; Separated after protocol:

Local.limit.linelen.nntp=1000

Local.limit.linelen.pop3=1000

Local.limit.linelen.smtp=1000

Local.limit.textsize.nntp=2097152

Local.limit.textsize.pop3=2097152

Local.limit.textsize.smtp=2097152

Around the limitations auszuhebeln, the numbers can be varied; the input of 0 (zeros) lifts the respective limitation completely.

The change of these entries is also possible under Einstellungen-> for local servers / user.

However, before the fuss or changing the limitations one should realize the following:

a) Email-appendices are coded specially by which their(her) size balloons by about 1/3 (factor 1,36). Therefore, e.g., a 2 MB file is blown up in the appendix of an email by base64-Kodierung on 2,72 MB.

[ The more exact in addition under http: // www.mdiedrich.de - > net (from) use]

b) Such big emails load mail server and data lines, because the file is transported by sender about the SMTP-server (mostly of the provider) in the Internet as well as about one or several mail servers to finally to the POP3-Server (receiver) and from there to the receiver. Once the SMTP-server and once the POP3-Server is loaded with it excessively and task what comes close to a DoS-attack (Denial-of-Service) opposite the mail servers partly already very much (who would like to try a 90 MB-email can send to his(its) HAMSTER, while to fetch three people, their(her) emails...).

c) For the transmission of such data amounts a FTP-server is predestined originally (just when such a thing is found(seems) more frequently); his(its) equipment(arrangement) should not be difficult for a hamster's-administrator. Examples to the construction of a FTP-server as well as indications to his(its) use are also under [http: // www.mdiedrich.de - > LAN in the net to find net (from) use].

d) Also the email-Client of the receiver can be glad, because:

Detailed emails are stored first in the Inbox. There they are deleted either by the receiver or are shifted in another file. Both actions result usually in that at least in the file Inbox still the complete email is contained, provided that one does not compress the file. Therefore lie the inflated file in form of the email-appendix as well as as a stored form (the receivers the file will evacuate probably still on the non removable disk) before what puts out then only already about 200 MB lying around data. If the email is shifted and the Inbox is not compressed, lie schonrund 300 MB on the plate(record) (two times as a mail-appendix, once as a file) on the non removable disk. Then one does not delete perhaps the emails on the hamster and is already present whole again in an about 120 MB text file.

e) The load of the main memory is enormous, because the email lies always two times in the warehouse: Once by HAMSTER (fetch / send) as well as once with the email-Client. With "correctly" big emails or systems with little main memory (64 MB is in this connection a little) can lead absolutely to the total one system-bumped off.

f) The FTP-protocol is able to protect the already transferred part by demolitions and to reload the remaining rest(remainder) with a new connection only.

In the mail protocol is considered(applies): completely or garnicht

Creates from Martin Diedrich <martin@mdiedrich.de>

With experiences of Wilfried Kramer <whdkramer@nikocity.de>