[pfx] Re: Update mynetworks file without postfix restart

2024-09-04 Thread Burn Zero via Postfix-users
ix-users@postfix.org> wrote: > Burn Zero via Postfix-users skrev den 2024-09-04 07:42: > > > Is there any way to update the mynetworks file without doing a postfix > > restart? I use mynetworks cidr file. > > imho no, why is it needed in the first place ? > > PS: rest

[pfx] Update mynetworks file without postfix restart

2024-09-03 Thread Burn Zero via Postfix-users
Hi, Is there any way to update the mynetworks file without doing a postfix restart? I use mynetworks cidr file. Thank you. ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org

Re: queue file size limit exceeded

2022-06-23 Thread Burn Zero
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: &g

Re: queue file size limit exceeded

2022-06-21 Thread 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" ? On Tue, 21 Jun 2022 at 16:14, Matus UHLAR - fantomas wrote: > > On 21.06.22 16:05, Burn Zero

Re: queue file size limit exceeded

2022-06-21 Thread Burn Zero
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

Re: queue file size limit exceeded

2022-06-21 Thread Burn Zero
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 rela

Re: queue file size limit exceeded

2022-06-21 Thread Burn Zero
ying SIZE incorrectly. > > Op 21 jun. 2022 08:20 schreef 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 bel

queue file size limit exceeded

2022-06-20 Thread 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]: 66F259E10043: client=[xxx.xxx.x

Error 4.4.2 Error: timeout exceeded

2021-03-18 Thread Burn Zero
Hi, I have a relay server named smtprelayservername which accepts emails from various clients. So one of the clients complain that they receive this error while sending email: Error 4.4.2 Error: timeout exceeded But I have checked in the relay server smtprelayservername and no such timeout issu

Re: Restrict clients (IP address) to send outbound email

2021-01-06 Thread Burn Zero
Hi Ansgar, Thank you. It worked like a charm. On Wed, 6 Jan 2021 at 16:16, Ansgar Wiechers wrote: > On 2021-01-06 Burn Zero wrote: > > I need to restrict outbound email to the internet by client IP. i.e. > > if an IP is in a blocked list, it should only be allowed to be se

Restrict clients (IP address) to send outbound email

2021-01-06 Thread Burn Zero
Hi, I need to restrict outbound email to the internet by client IP. i.e. if an IP is in a blocked list, it should only be allowed to be sent to local domains. Is this possible? Please advise. I read http://www.postfix.org/RESTRICTION_CLASS_README.html but it is only using the usernames and not t

How to match From as MAILFROM

2020-03-16 Thread Burn Zero
Hi, I have configured an internal postfix server where users will use that as relay servers to relay emails to outside and internal users. I have restricted postfix to allow only one domain as MAILFROM and deny rest all. But how to restrict From address like this? Is there any way in postfix? Th

Re: Enabling TLSv1.2 support in postfix 2.8.2

2018-10-24 Thread Burn Zero
Hi, I use CentOS 6.5 On Wed, Oct 24, 2018 at 5:01 PM Matus UHLAR - fantomas wrote: > On 24.10.18 16:56, Burn Zero wrote: > >Yea, I got it. But even with that configuration when I connect to my > >server, my server is still accepting connections in TLSv1. If I disable > &

Re: Enabling TLSv1.2 support in postfix 2.8.2

2018-10-24 Thread Burn Zero
Hi, Yea, I got it. But even with that configuration when I connect to my server, my server is still accepting connections in TLSv1. If I disable TLSv1 in my server, warning: TLS library problem: 21975:error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol:s23_srvr.c:578: On Wed, Oc

Enabling TLSv1.2 support in postfix 2.8.2

2018-10-24 Thread Burn Zero
Hi, Currently my mail setup is using TLSv1 to connect to O365. Now that O365 has announced dropping their support for TLSv1, TLSv1.1, how to enable support for TLSv1.2 in postfix 2.8.2? My openssl version is OpenSSL 1.0.1e-fips 11 Feb 2013 It should also support TLSv1, TLSv1.1 for older clients

Queue active for long time

2017-04-19 Thread Burn Zero
Hi, We are having postfix as on-premise SMTP server and we send email via this SMTP server to O365 cloud. Recently we got throttled by MS and our queue size increased in postfix. I was checking the logs and I found these queue active messages that stayed for long time. ( I have removed some part

Re: Make postfix log to show how sender rewriting happens

2017-01-18 Thread Burn Zero
Thank you so much for the info and it works now. :) On Fri, Dec 23, 2016 at 7:59 PM, /dev/rob0 wrote: > > On Tue, Dec 20, 2016 at 7:35 PM, Viktor Dukhovni > > wrote: > > > > > > > On Dec 20, 2016, at 12:53 AM, Burn Zero > > > > wrote: > > >

Re: Make postfix log to show how sender rewriting happens

2017-01-18 Thread Burn Zero
Thank you viktor. It works fantastically now. On Tue, Dec 20, 2016 at 7:35 PM, Viktor Dukhovni wrote: > > > On Dec 20, 2016, at 12:53 AM, Burn Zero wrote: > > > > As you can see the orig_to parameter shows the original id to which > the email was sent and the to

Re: Make postfix log to show how sender rewriting happens

2016-12-23 Thread Burn Zero
error; from= to= proto=SMTP On Tue, Dec 20, 2016 at 7:35 PM, Viktor Dukhovni wrote: > > > On Dec 20, 2016, at 12:53 AM, Burn Zero wrote: > > > > As you can see the orig_to parameter shows the original id to which > the email was sent and the to= parameter explains th

Re: Make postfix log to show how sender rewriting happens

2016-12-19 Thread Burn Zero
I guess you didn't get my question. Pardon me if it wasn't clear. I use postfix rewrite feature to rewrite sender and recipient address. When I receive email from outside, my recipient rewrite is done using recipient_canonical file. I also check the same in log, Sep 12 17:23:32 rewritehost postfi

Make postfix log to show how sender rewriting happens

2016-12-19 Thread Burn Zero
Hi, I'm using postfix SMTP server and I'm rewriting sender and recipient addresses. From the postfix logs, I can see the recipient address rewriting logs, Sep 12 17:23:32 rewritehost postfix/smtp[1223]: 28A6701362: to=, *orig_to*=, relay=relay.host[xxx.xxx.xxx.xxx]:25, delay=56, delays=51/0/4.5/0