Viktor Dukhovni:
> On Thu, Jun 23, 2022 at 05:46:50PM +0530, Burn Zero wrote:
>
> > Thank you all and to Wietse Venema. You are right, the issue is with
> > the client email system. When checked in their system, the email size
> > is 17 MB and while exporting and saving that message, it becomes
>
On Thu, Jun 23, 2022 at 05:46:50PM +0530, Burn Zero wrote:
> Thank you all and to Wietse Venema. You are right, the issue is with
> the client email system. When checked in their system, the email size
> is 17 MB and while exporting and saving that message, it becomes
> around 47 MB.
Perhaps some
Thank you all and to Wietse Venema. You are right, the issue is with
the client email system. When checked in their system, the email size
is 17 MB and while exporting and saving that message, it becomes
around 47 MB.
On Tue, 21 Jun 2022 at 20:00, Wietse Venema wrote:
>
> Burn Zero:
> > Okay, But
Burn Zero:
> Okay, But is there any difference between the error messages "NOQUEUE:
> reject: 552 5.3.4 Message size exceeds fixed limit" and "warning:
> queue file size limit exceeded" ?
These happen at different points in time.
After MAIL FROM: SIZE=too-large-number:
5441 /*
5442
Okay, But is there any difference between the error messages "NOQUEUE:
reject: 552 5.3.4 Message size exceeds fixed limit" and "warning:
queue file size limit exceeded" ?
On Tue, 21 Jun 2022 at 16:14, Matus UHLAR - fantomas wrote:
>
> On 21.06.22 16:05, Burn Zero wrote:
> >It is 17 MB only. messa
On 21.06.22 16:05, Burn Zero wrote:
It is 17 MB only. message_size_limit is not overridden in master.cf as
it is showing the correct value set in main.cf while advertising EHLO.
it can be overridden for e.g. cleanup process.
On Tue, 21 Jun 2022 at 16:01, Matus UHLAR - fantomas wrote:
On 21
Wietse Venema:
> Burn Zero:
> > Hi,
> >
> > Please find the output:
> >
> > ++
> >
> > ehlo domain
> > 250-smtp1
> > 250-PIPELINING
> > 250-SIZE 48916070
>
> Then, the message size is not 17MB.
You can use tcpdump/wireshark/etc to convince yourself.
Wietse
Burn Zero:
> Hi,
>
> Please find the output:
>
> ++
>
> ehlo domain
> 250-smtp1
> 250-PIPELINING
> 250-SIZE 48916070
Then, the message size is not 17MB.
Wietse
Hi,
It is 17 MB only. message_size_limit is not overridden in master.cf as
it is showing the correct value set in main.cf while advertising EHLO.
On Tue, 21 Jun 2022 at 16:01, Matus UHLAR - fantomas wrote:
>
> On 21.06.22 13:38, Burn Zero wrote:
> >Yes, the client is showing that it is 17 MB in
On 21.06.22 13:38, Burn Zero wrote:
Yes, the client is showing that it is 17 MB in size.
are you sure it's not e.g. 170M ?
or that you don't have message_size_limit overridden somewhere in master.cf?
On Tue, 21 Jun 2022 at 12:49, Jeroen Geilman wrote:
The message originates in cleanup_fina
Hi,
Please find the output:
++
ehlo domain
250-smtp1
250-PIPELINING
250-SIZE 48916070
250-ETRN
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 CHUNKING
++
On Tue, 21 Jun 2022 at 15:31, Wietse Venema wrote:
>
> Burn Zero:
> > Hi,
> >
> > I have a relay server where different app
Burn Zero:
> Hi,
>
> I have a relay server where different application servers send emails to
> it. An application server is sending email with the size around 17 MB but
> the relay server is not accepting it citing the below warning:
>
> ++
>
> Jun 18 09:47:05 smtp1 postfix/smtpd[43832]: 66
Hi,
Yes, the client is showing that it is 17 MB in size.
On Tue, 21 Jun 2022 at 12:49, Jeroen Geilman wrote:
> The message originates in cleanup_final.c, which reconciles the open queue
> file with the final on-disk size of the received message.
> Check if the client is supplying SIZE incorrect
13 matches
Mail list logo
