Содержание
- Лимиты в Postfix
- Редактирование конфигурационного файла Postfix
- 1. Размер почтового ящика
- 2. Размер отправляемого сообщения
- 3. Количество сообщений и одновременных подключений
- 4. Очередь сообщений
- 5. Таймаут на отправку сообщений
- 6. Отправка сообщений об ошибках (4xx or 5xx)
- 552 5.3.4 message size exceeds fixed limit
- Работа с конфигом postfix
- Sep 30, 2022: iRedMail-1.6.2 has been released.
- Posts: 9
- 1 Topic by shaiktharim 2014-05-22 17:52:39
- Topic: SMTP error: 552 5.3.4 Message size exceeds fixed limit
- 2 Reply by ZhangHuangbin 2014-05-22 18:58:49
- Re: SMTP error: 552 5.3.4 Message size exceeds fixed limit
- 3 Reply by shaiktharim 2014-05-22 20:23:38
- Re: SMTP error: 552 5.3.4 Message size exceeds fixed limit
- Smtp error 552 message size exceeds fixed limit
- Asked by:
- Question
- All replies
Лимиты в Postfix
Почтовый агент Postfix позволяет задавать различные ограничения, таймауты и лимиты. В данной инструкции мы рассмотрим примеры, как это сделать. Используемые значения подойдут для средне статистического сервера, однако, в каждой среде необходимо наблюдение и приведение параметром к оптимальному виду.
Редактирование конфигурационного файла Postfix
Изменения делаем в конфигурационном файле:
* для FreeBSD путь будет /usr/local/etc/postfix/main.cf.
После редактирования не забываем перечитывать изменения командой:
systemctl reload postfix
* для FreeBSD или старых систем на базе Linux вводим service postfix restart.
1. Размер почтового ящика
Для установки квоты на почтовые ящики редактируем следующее:
mailbox_size_limit = 209715200
virtual_mailbox_limit = 209715200
* значение указывается в байтах. В данном примере установлены квоты для почтовых ящиков и виртуальных почтовых ящиков в 200 мб. Для удобства, воспользуйтесь конвертером мегабайт.
Чтобы снять ограничения, можно выставить значения в 0:
mailbox_size_limit = 0
virtual_mailbox_limit = 0
2. Размер отправляемого сообщения
Открываем конфигурационный файл, находим и правим следующее (если строки нет, создаем):
* в данном примере установлено ограничение на размер письма в 70 мб.
Необходимо, чтобы данный размер не превышал размер почтового ящика (mailbox_size_limit и virtual_mailbox_limit, которые по умолчанию имеют значения 51200000 или 50 мб), в противном случае, в логе мы увидим ошибку fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit.
Для этого можно либо задать значения равные (или больше) message_size_limit:
message_size_limit = 73400320
mailbox_size_limit = 73400320
virtual_mailbox_limit = 73400320
. либо отключить ограничения:
message_size_limit = 73400320
mailbox_size_limit = 0
virtual_mailbox_limit = 0
3. Количество сообщений и одновременных подключений
В конфигурационном файле добавляем такие строки:
anvil_rate_time_unit = 60s
smtpd_client_message_rate_limit = 200
smtpd_client_recipient_rate_limit = 60
smtpd_client_connection_count_limit = 20
smtpd_client_connection_rate_limit = 40
* в данном примере мы установили следующие ограничения на количество отправляемых писем:
- anvil_rate_time_unit — параметр расчетного времени. Именно от него будут вести отчет другие значения. По умолчанию также равен 60s.
- smtpd_client_message_rate_limit — сколько клиенту можно отправлять сообщений за anvil_rate_time_unit. По умолчанию 0, то есть, ограничений нет.
- smtpd_client_recipient_rate_limit — максимальное количество получателей за anvil_rate_time_unit. По умолчанию 0, то есть, ограничений нет.
- smtpd_client_connection_count_limit — количество одновременно разрешенных подключений для клиента. По умолчанию 50.
- smtpd_client_connection_rate_limit — максимальное количество коннектов, разрешенных для клиента за anvil_rate_time_unit. По умолчанию 0, то есть, ограничений нет.
4. Очередь сообщений
queue_run_delay = 5m
minimal_backoff_time = 10m
maximal_backoff_time = 15m
maximal_queue_lifetime = 1d
* где queue_run_delay задает время, как часто сообщения из очереди будут отправляться повторно; minimal_backoff_time устанавливает время, на которое будет отложена отправка сообщений, которые не были отправлены по причине временных неисправностей (например, принимающий сервер не отвечает или просит повторить запрос позже), но не позднее maximal_backoff_time; параметр maximal_queue_lifetime установит, через какой период перестать делать попытки при отправке сообщения и вернуть его отправителю с ошибкой.
5. Таймаут на отправку сообщений
smtp_data_done_timeout = 600s
smtp_data_init_timeout = 120s
smtp_data_xfer_timeout = 180s
* где smtp_data_done_timeout — ограничение времени для отправки сообщения; smtp_data_init_timeout — ограничение времени для отправки команды SMTP DATA и для получения ответа удаленного SMTP-сервера; smtp_data_xfer_timeout — ограничение времени для отправки содержимого сообщений.
6. Отправка сообщений об ошибках (4xx or 5xx)
smtpd_error_sleep_time = 3s
smtpd_soft_error_limit = 5
smtpd_hard_error_limit = 10
- smtpd_error_sleep_time — задержка перед отправкой сообщения об ошибке (4xx or 5xx). По умолчанию 1s.
- smtpd_soft_error_limit — количество ошибок, которые должны быть сделаны, прежде чем наш сервер начнет замедлять ответы. По умолчанию 10.
- smtpd_hard_error_limit — максимальное количество ошибок, которые может сделать удаленный сервер SMTP. После с ним будет разорвана сессия. По умолчанию 20.
552 5.3.4 message size exceeds fixed limit
Если сталкиваемся с сообщением «552 5.3.4 message size exceeds fixed limit» (переводится как «Размер сообщения превышает установленные ограничения»), значит отправляемое письмо не вписывается в установленные лимиты. Чтобы исправить ситуацию, уменьшаем размер сообщения или редактируем лимиты (пункты 1 и 2).
То есть, размер message_size_limit не должен превышать mailbox_size_limit и virtual_mailbox_limit.
Работа с конфигом postfix
Неколько полезных консольных команд по работе с конфигурацией.
1. Посмотреть значение параметра по умолчанию:
Источник
Sep 30, 2022: iRedMail-1.6.2 has been released.
iRedMail → iRedMail Support → SMTP error: 552 5.3.4 Message size exceeds fixed limit
You must login or register to post a reply
Posts: 9
1 Topic by shaiktharim 2014-05-22 17:52:39
- shaiktharim
- Member
- Offline
- Registered: 2014-01-05
- Posts: 39
Topic: SMTP error: 552 5.3.4 Message size exceeds fixed limit
==== Required information ====
— iRedMail version: 2.1.1
— Store mail accounts in which backend (LDAP/MySQL/PGSQL): LDAP
— Linux/BSD distribution name and version: Ubuntu 12.04
— Related log if you’re reporting an issue:
====
When emails are fetched from our pop3 server its thrwoing an error SMTP error: 552 5.3.4 Message size exceeds fixed limit.
Can you please help.
Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Stable release is out.
2 Reply by ZhangHuangbin 2014-05-22 18:58:49

- ZhangHuangbin
- iRedMail Developers
- Offline
- Registered: 2009-05-06
- Posts: 30,018
Re: SMTP error: 552 5.3.4 Message size exceeds fixed limit
How do you deliver fetched mail to user mailbox? Also, show us output of command «postconf -n» to help troubleshoot.
3 Reply by shaiktharim 2014-05-22 20:23:38
- shaiktharim
- Member
- Offline
- Registered: 2014-01-05
- Posts: 39
Re: SMTP error: 552 5.3.4 Message size exceeds fixed limit
i have configured fetchmail to deliver fetched mails to user mailbox.
Here is my output of postconf -n:
# postconf -n
alias_database = hash:/etc/postfix/aliases
alias_maps = hash:/etc/postfix/aliases
allow_min_user = no
allow_percent_hack = no
append_dot_mydomain = no
biff = no
bounce_queue_lifetime = 4h
broken_sasl_auth_clients = yes
config_directory = /etc/postfix
content_filter = smtp-amavis:[127.0.0.1]:10024
delay_warning_time = 0h
disable_vrfy_command = yes
dovecot_destination_recipient_limit = 1
enable_original_recipient = no
home_mailbox = Maildir/
inet_interfaces = all
inet_protocols = ipv4
mailbox_command = /usr/lib/dovecot/deliver
mailbox_size_limit = 0
maximal_backoff_time = 4000s
maximal_queue_lifetime = 4h
message_size_limit = 31457280
minimal_backoff_time = 300s
mydestination = $myhostname, localhost, localhost.localdomain, localhost.$myhostname
mydomain = albawardi.com
myhostname = mailserver.albawardi.com
mynetworks = 127.0.0.0/8
mynetworks_style = host
myorigin = mailserver.albawardi.com
proxy_read_maps = $canonical_maps $lmtp_generic_maps $local_recipient_maps $mydestination $mynetworks $recipient_bcc_maps $recipient_canonical_maps $relay_domains $relay_recipient_maps $relocated_maps $sender_bcc_maps $sender_canonical_maps $smtp_generic_maps $smtpd_sender_login_maps $transport_maps $virtual_alias_domains $virtual_alias_maps $virtual_mailbox_domains $virtual_mailbox_maps $smtpd_sender_restrictions
queue_run_delay = 300s
readme_directory = no
recipient_bcc_maps = proxy:ldap:/etc/postfix/ldap/recipient_bcc_maps_user.cf, proxy:ldap:/etc/postfix/ldap/recipient_bcc_maps_domain.cf
recipient_delimiter = +
relay_domains = $mydestination, proxy:ldap:/etc/postfix/ldap/relay_domains.cf
relayhost = 216.25.6.131
sender_bcc_maps = proxy:ldap:/etc/postfix/ldap/sender_bcc_maps_user.cf, proxy:ldap:/etc/postfix/ldap/sender_bcc_maps_domain.cf
smtp-amavis_destination_recipient_limit = 1
smtp_data_init_timeout = 240s
smtp_data_xfer_timeout = 600s
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtp_sasl_security_options =
smtp_tls_CAfile = $smtpd_tls_CAfile
smtp_tls_security_level = may
smtp_tls_session_cache_database = btree:$/smtp_scache
smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu)
smtpd_data_restrictions = reject_unauth_pipelining
smtpd_end_of_data_restrictions = check_policy_service inet:127.0.0.1:10031
smtpd_helo_required = yes
smtpd_helo_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_non_fqdn_helo_hostname, reject_invalid_helo_hostname, check_helo_access pcre:/etc/postfix/helo_access.pcre
smtpd_recipient_restrictions = reject_unknown_sender_domain, reject_unknown_recipient_domain, reject_non_fqdn_sender, reject_non_fqdn_recipient, reject_unlisted_recipient, check_policy_service inet:127.0.0.1:7777, check_policy_service inet:127.0.0.1:10031, permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination
smtpd_reject_unlisted_recipient = yes
smtpd_reject_unlisted_sender = yes
smtpd_sasl_auth_enable = yes
smtpd_sasl_authenticated_header = no
smtpd_sasl_local_domain =
smtpd_sasl_path = ./dovecot-auth
smtpd_sasl_security_options = noanonymous
smtpd_sasl_type = dovecot
smtpd_sender_login_maps = proxy:ldap:/etc/postfix/ldap/sender_login_maps.cf
smtpd_sender_restrictions = permit_mynetworks, reject_sender_login_mismatch, permit_sasl_authenticated
smtpd_tls_CAfile = /etc/ssl/certs/iRedMail_CA.pem
smtpd_tls_cert_file = /etc/ssl/certs/iRedMail_CA.pem
smtpd_tls_key_file = /etc/ssl/private/iRedMail.key
smtpd_tls_loglevel = 0
smtpd_tls_security_level = may
smtpd_tls_session_cache_database = btree:$/smtpd_scache
smtpd_use_tls = yes
swap_bangpath = no
tls_random_source = dev:/dev/urandom
transport_maps = proxy:ldap:/etc/postfix/ldap/transport_maps_user.cf, proxy:ldap:/etc/postfix/ldap/transport_maps_domain.cf
virtual_alias_domains =
virtual_alias_maps = proxy:ldap:/etc/postfix/ldap/virtual_alias_maps.cf, proxy:ldap:/etc/postfix/ldap/virtual_group_maps.cf, proxy:ldap:/etc/postfix/ldap/virtual_group_members_maps.cf, proxy:ldap:/etc/postfix/ldap/catchall_maps.cf
virtual_gid_maps = static:2000
virtual_mailbox_base = /var/vmail
virtual_mailbox_domains = proxy:ldap:/etc/postfix/ldap/virtual_mailbox_domains.cf
virtual_mailbox_maps = proxy:ldap:/etc/postfix/ldap/virtual_mailbox_maps.cf
virtual_minimum_uid = 2000
virtual_transport = dovecot
virtual_uid_maps = static:2000
Please check and let me know my configurations are right or need any changes?
Источник
Smtp error 552 message size exceeds fixed limit
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Asked by:

Question


i’m trying to troubleshoot an issue where my users send large files and i want to increase the file size possible to get to the exchange mailbox but i’m not having success. In a test internally from one exchange user to another i am able to send these set of jpg files totalling 19mb. But, when i send from the internet to the same user i get a failure. Below are the details of the failure. From my gmail accont to my exchange account. Any advice on where to check or change settings? Further troubleshooting steps?
Also. i’m running Exchange 2010 and not 2013. the web page did not allow me to choose 2010 for some reason.
———- Forwarded message ———-
From: Mail Delivery Subsystem
Date: Fri, Sep 6, 2013 at 3:49 PM
Subject: Delivery Status Notification (Failure)
To: aamato9072@gmail.com
Delivery to the following recipient failed permanently:
Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the server for the recipient domain salesmasterflooring.com by mobile.salesmasterflooring.com . [24.187.246.100].
The error that the other server returned was:
552 5.3.4 Message size exceeds fixed maximum message size
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=mime-version:in-reply-to: references:date:message-id: subject:from:to
:content-type;


Try these commands on your Hub Transport server:
Set-TransportConfig –MaxReceiveSize 50MB
Get-ReceiveConnector | Set-ReceiveConnector -MaxMessageSize 50MB
Get-Mailbox | Set-Mailbox -MaxReceiveSize 50MB
Note: Running this command will set the receiving size limit on all the receive connectors and all the mailboxes to 50 MB. You can change the size limit on these command to suit your need.


I recommend you refer to the following commands to check the settings on the exchange server.
If any settings less than 19mb, you need to refer to PSS’s reply to change the settings.
Hope it helps you!
Regards, Please mark it as an answer if it really helps you.




I recommend you to check the size of the entire email which includes all the attachments.
It may be the gmail’s problem,the following article for your reference:
Attachment size limit
You can send messages up to 25 megabytes (MB) in size. If you’d like to send attachments that are larger than this, you can insert from Google Drive instead.
Hope it helps you !
Regards, Please mark it as an answer if it really helps you.


thanks. but this doesn’t seem to only occur from google. i have users sending from yahoo too.
From: «MAILER-DAEMON@yahoo.com»
To: markwat54@yahoo.com
Sent: Thursday, September 5, 2013 5:12 PM
Subject: failure notice
Hi. This is the qmail-send program at yahoo.com.
I’m afraid I wasn’t able to deliver your message to the following addresses.
This is a permanent error; I’ve given up. Sorry it didn’t work out.
:
24.187.246.100 failed after I sent the message.
Remote host said: 552 5.3.4 Message size exceeds fixed maximum message size
— Below this line is a copy of the message.
Return-Path:
Received: (qmail 74127 invoked by uid 1000); 5 Sep 2013 21:12:45 -0000
Received: (qmail 77601 invoked by uid 60001); 5 Sep 2013 21:12:41 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1378415556; bh=T+dhQNVA0wpUKUwLlln6h8AbaTft5iqjkTxUs1hE3Y4=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-RocketYMMF:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=x078bNnfJB4bFWwOja29W/ybcoVVrfNhgI+hZBSj4tv4W1fmg4VK14YA12UiWjO8kUhnWM61zHKlDIrZA33r0ak3FTPkKyGD/2i4tR9VzK7BH8+Y1IjaKwmLWJGnTPhup30lIBqkNE23Km5pjj2UYwKTYfla6YTWZrxR6v4Wr4Y=
DomainKey-Signature:a=rsa-sha1; q=dns; c=nofws;
s=s1024; d=yahoo.com;
h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-RocketYMMF:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type;
b=Im+I6/3iboPvtIZ7UbnV3MhaYXvBZhlEKdX58SE+gkln99Wb+ge89I+t/CSESANxHhh/BUPdF9+YVmqsMDzNOElDpOiK026TRX7pzgFb8KrI6S6ySxD3VJUl0S7wFHbOfcu0QW5UlRs7zDyxbE+oTt19ZFW4bmOFGFHEbb7IWII=;
X-YMail-OSG: TGR0dgMVM1nRh_JpcpNVjQBj9nGIB3oPn6t.3m4Ek7PLXrz
C5mlkogd4D0nXpru8Ekw.1i4scKqN.onVbpjRkBWlq5QOwA3zgYMnz0iH9tI
WA8V4x7rSuTxmL6mJDqN1DgOTTGIm4s81Uzv4AA7.JkufRCb.AwiKGSDbzZT
8cPs8Bg85yFBRUt2KHr6nXV43ACz8CGXylGcgSvzZmFFjkSGTyBzXHVoUke4
S1Bb8cyHjRR9EyHnun8YVc3wWAqzOX0s44waDOWPGFmk0k_VmVrR0Eum663e
ppMZBSmCvlzoKeZzByWETcEkSV3XXBYZ2ibF_9aXIgkQgNVVLVc7w5LWUC_u
djjDEF_cQiu9UoQl4mMjcsER5ctcwgJEkJ9z07Z3KmsgmxHgdZXb59nO9rs0
ghUGc1e.PiI.lWQuFQyoxN4c9wzfdV1uFuCMv8.NEzzjaoB2PqJhdw6L9JXm
a9LMLDtPLHhMnPACV4h1jfvZQzDc90ikbZMBr16KAlIS.7yq9SuPdMQNXiEC
IZ_VBv5dMmKn.N5.iZc6gaiu7Alee9Yhb5rFHMNewWKH6bWbG399QQhveozQ
U3toPc7bHrTfG8LbBmoY62EWVVR41Tc31eqq6xwPOfA—
Received: from [24.187.246.101] by web161301.mail.bf1.yahoo.com via HTTP; Thu, 05 Sep 2013 14:12:33 PDT
X-RocX-Mailer: YahooMailWebService/0.8.156.576
References:
Message-ID:
Date: Thu, 5 Sep 2013 14:12:30 -0700 (PDT)
From: mark watkins
Reply-To: mark watkins
Subject: Fw: 12.3 mb test salesmasterflooring
To: mark watkins ,
andy amato
In-Reply-To:
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary=»-201759553-724113204-1378415553=:76297″
—201759553-724113204-1378415553=:76297
Content-Type: multipart/alternative; boundary=»-201759553-1861093726-1378415553=:76297″
—201759553-1861093726-1378415553=:76297
Content-Type: text/plain; charset=us-ascii
Источник
- Remove From My Forums
-
Question
-
Hi,
We’re having an issue with an application sending attachments via our SMTP. We keep getting the message that the message size is exceeded, although all settings seem to be ok.Organizational settings :
Get-TransportConfig | Ft Name,MaxSendSize,MaxReceiveSize
Name : Transport Settings
MaxSendSize : 25 MB (26,214,400 bytes)
MaxReceiveSize : 25 MB (26,214,400 bytes)receive connector :
ServersAllowedForRelaying
max receive size : 25 MBMailbox settings :
get-mailbox user | fl *size*
MaxSendSize : Unlimited
MaxReceiveSize : UnlimitedWhen sending, we get the error 552 – «5.3.4 Message size exceeds fixed maximum message size»
The mail itself is (including attachment 19 MB)
Even if I would add 30% to this for encoding, I’d end up below 25MB.Can anyone tell which restriction we’re running up against?
For me the current config should be ok like it’s configured now.PS : We’re sending internally. Sending a file which is 15MB does work, so the limit seems to be near 20MB, although are limits are 25 MB.
Answers
-
Hi,
As is mentioned in the official document, the Base64 encoding increases the size of the message by approximately 33%, you should set the size limit larger than 25 MB. If you want to know more about the message size limits, you can check: Message
size limits in Exchange ServerRegards,
Lydia Zhou
Please remember to
mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact
tnsf@microsoft.com.-
Proposed as answer by
Thursday, October 3, 2019 8:40 AM
-
Marked as answer by
D_Goossens
Tuesday, October 8, 2019 12:04 PM
-
Proposed as answer by
Problem
While in the process of sending mail to a Microsoft Mail Server, the following message is received:
552 4.3.1 Message size exceeds fixed maximum message size.
The session between z/OS SMTP and the remote Mail Server is reset, inhibiting SMTP from sending the rest of the mail. SMTP then attempts to resend the mail, receives the 552 message again, the connection is reset, and the cycle is repeated.
Cause
When the Microsoft Mail Server detects that its maximum file size has been reached, it terminates the session before all the data is received and sends the 552 return code with text indicating message is too large.
Because the session has been terminated, SMTP treats the sending of the mail as a temporary error condition, effectively disregarding the 552 return code. This is because z/OS SMTP acts like a state machine according to the original design and RFC 821. It must finish sending the mail before accepting valid SMTP server replies. Replies received before mail has been sent will not be processed.
Because the receiving mail server is not processing large mail files properly (it is terminating when the mail size limit is reached), it causes the z/OS SMTP server to resend the mail. This triggers a loop condition.
What it should do is receive all the mail and discard the mail that exceeds its limit.
When the ending sequence of the message <CRLF>.<CRLF> is received, the receiving mail server should send the 552 return code to the sending site.
The sending site then will interpret the 552 correctly and process the mail as being undeliverable.
An SMTP trace will confirm this condition. Following is a sample which shows the condition.
Note the EZA5212 message prior to the 552. This indicates that SMTP was still in the process of sending the mail to the remote site when this message was received. The EZA5200I indicates the Foreign host (remote mail server) closed the connection. This will cause SMTP to retry sending the mail and this sequence will be repeated.
EZA5198I 2< 354 Start mail input; end with <CRLF>.<CRLF>
EZA5198I 1< 354 Start mail input; end with <CRLF>.<CRLF>
EZA5212I 2< Data arrived while Sending Mail Body:
EZA5214I 552 4.3.1 Message size exceeds fixed maximum message size
EZA5215I
EZA5200I 2> Connection closed at IP: 10.1.60.15 reason Foreign host
aborted the connection (8556)
EZA5212I 1< Data arrived while Sending Mail Body:
EZA5214I 552 4.3.1 Message size exceeds fixed maximum message size
EZA5215I
EZA5200I 1> Connection closed at IP: 10.1.60.49 reason Foreign host
aborted the connection (8556)
Resolving The Problem
- Implement a fix to the remote site to insure large mail files are properly handled.
- Raise the limit at the remote site for the size of mail file that it can receive.
- The following can be done though the local SMTP to limit the size of outbound mail but doing this would affect all outbound messages. Utilizing the following statements in the SMTP configuration file, some control can be achieved over the size of mail files that will be processed:
- MAILFILEVOLUME specifies the volume on which temporary note files will be created. Based on the type of DASD device on which the volume resided, MAILFILEVOLUME will determine the number of bytes a block can contain.
- CHECKSPOOLSIZE requests that if mail to be saved in the TEMP.NOTE file exceeds the primary allocation, it is to be truncated at that point. A shortened mail file WILL BE sent and a message will be appended to the end indicating that the data has been truncated.
Without this keyword, mail will continue to be written to the TEMP.NOTE file, secondary extents will be obtained until the secondary extent limit is reached or no space remains on the volume.
CHECKSPOOLSIZE uses another statement, MAXMAILBYTES in the algorithm to determine space allocation.
In general, the allocation used for the NOTE data sets is equivalent to specifying SPACE=(6144,(aaaaa,bbbb)),
where aaaa=round((MAXMAILBYTES/4000)+1) and bbbb=round(aaaa/2).
NOTE: The TEMP.NOTE file contains both the content of the note and commands needed to process it. A MAXMAILBYTES 1500000 will result in a SPACE=(6144,(377,188)) being used to allocate the file. Actual message data may exceed MAXMAILBYTES for outbound mail. However, this is not the case for inbound mail where MAXMAILBYTES is strictly adhered to.
If you continue to receive the 552 message with the maximum message size being exceeded, lower the MAXMAILBYTES value until a value is reached where this message is no longer received.
[{«Product»:{«code»:»SSSN3L»,»label»:»z/OS Communications Server»},»Business Unit»:{«code»:»BU054″,»label»:»Systems w/TPS»},»Component»:»All»,»Platform»:[{«code»:»PF035″,»label»:»z/OS»}],»Version»:»1.8;1.9;1.10;1.11;1.12;1.13;2.1;2.2″,»Edition»:»All Editions»,»Line of Business»:{«code»:»LOB35″,»label»:»Mainframe SW»}}]