[pfx] Re: No Permissions To TLS Certificates
(Sorry, can't remember if I should be top-posting or bottom-posting :-) ) The answer for both queries: * The root folder is 555 root:root * All other folders are 755 root:root * The certs themselves are 600 root:root (I think I mentioned this one in my original post - I think) Having raised this issue, it now raises another Q in my mind: could this be something to do with SELinux interfering somehow (I'm not really up to speed on SELinux, unfortunately)? Cheers On 12/10/2023 01:40, Wietse Venema via Postfix-users wrote: duluxoz via Postfix-users: Oct 11 17:33:05 mail.me.local email_postfix[2038]: find: '/etc/postfix/./certs/me.local.pem': Permission denied Oct 11 17:33:05 mail.me.local email_postfix[2039]: postfix/postlog: warning: not owned by root: /etc/postfix/./certs/me.local.pem What is the output from: ls -ld / /etc /etc/postfix /etc/postfix/certs /etc/postfix/certs/me.local.pem Oct 11 17:33:05 mail.me.local email_postfix[2038]: find: '/etc/postfix/./certs/me2.local.pem': Permission denied Oct 11 17:33:05 mail.me.local email_postfix[2040]: postfix/postlog: warning: not owned by root: /etc/postfix/./certs/me2.local.pem What is the output from: ls -ld / /etc/postfix /etc/postfix/certs /etc/postfix/certs/me2.local.pem Wietse ___ Postfix-users mailing list --postfix-users@postfix.org To unsubscribe send an email topostfix-users-le...@postfix.org ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] user based transport
Hello, How can I setup username based transport? for incoming messages, such as use...@foo.com will be delivered to host a. use...@foo.com will be delivered to host b. Thanks. ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: Transport according to MX record
On Thu, Oct 12, 2023 at 02:02:55AM +0200, Daniel Ryšlink via Postfix-users wrote: > It's generally very useful to set up a specific transport for "sensitive" > domains like gmail.com with specific policy (throttling outgoing message > rate, etc). > > However, since more and more hosted domains use mail services for their > domains, it would be useful to be able to select apropriate transport not > according to domain or recipient e-mail, but according to the IPs address of > the server specified by the MX record of the domain. > > Could it be achieved via Postfix configuration somehow? The transport table > format does not seem to support this. Sadly, no. Transport selection and scheduling happens in the queue manager, which does not know which MX hosts an SMTP delivery might later resolver to. And even if it were MX-aware, what to when: - Some MX host IP addresses are associated with one transport choice and some with another? - The actual MX hosts that are up and going to be used are not the highest priority ones? - The IP addresses that have not saturated their concurrency are not the ones the SMTP delivery agent ultimately chooses when delivery happens. - ... Adding Postfix support for IP-based concurrency limits across separate nexthop domains would require a radical redesign of the queue manager and/or SMTP delivery agents. So not likely any time soon. Once a particular IP address is selected, the delivery would have to go back into some sort of queue, freeing up the delivery agent that performed the MX and address lookups, and that secondary queue would have to implement concurrency limits by IP and pass the envelope back for actual delivery. Something along the lines a 2-stage SMTP delivery agent, with a handoff to a second-stage queue along the way. -- Viktor. ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Transport according to MX record
Hello, It's generally very useful to set up a specific transport for "sensitive" domains like gmail.com with specific policy (throttling outgoing message rate, etc). However, since more and more hosted domains use mail services for their domains, it would be useful to be able to select apropriate transport not according to domain or recipient e-mail, but according to the IPs address of the server specified by the MX record of the domain. Could it be achieved via Postfix configuration somehow? The transport table format does not seem to support this. Thank you in advance for any useful info, and apologies for any potential flaws of this inquiry. -- Best Regards, Daniel Ryšlink ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: forward IP source from a postfix relay to a postfix server
testeur via Postfix-users: > Hi, > > Well. > i read it : > https://postfix.traduc.org/index.php/XFORWARD_README.html > But i don't know how to implement that in postfix (master.cf ?) ?! the > link explain the "protocol"... > there's no howto to do it... > > if someone know an howto somewhere ? You could try; postconf | grep xforward And then look at the parameters: To send XFORWARD: https://www.postfix.org/postconf.5.html#smtp_send_xforward_command To receive XFORWARD: https://www.postfix.org/postconf.5.html#smtpd_authorized_xforward_hosts Wietse > Regards, > > PG > > On 11/10/2023 00:20, Wietse Venema via Postfix-users wrote: > > testeur via Postfix-users: > >> Hi, > >> > >> I don't understand how the External_Postfix_relay server could send > >> XCLIENT commands to the final postfix server ? > >> is there some modifications to do in the master.cf file ? > > You asked how to impersonate a client or server TCP endpoint. Postfix > > supports receiving TCP endpoint impersonation commands using two > > protocols: XCLIENT (used by nginx) and the HaProxy protocol. The > > primary use cases are load balancers and policy testing. > > > > There is no code in Postfix to send XCLIENT or HaProxy commands > > for the simple reason that no-one has needed it. > > > > Postfix does support sending XFORWARD commands with remote SMTP > > client information for the purpose of logging, not impersonantion. > > It is typically used with SMTP-based content filters. > > > > Wietse > > > >> Regards, > >> > >> On 08/10/2023 22:19, Wietse Venema via Postfix-users wrote: > >>> testeur via Postfix-users: > Hi, > > I try to find a solution to forward the IP source from the postfix relay > to the final postfix server (internal). > > Mail_Message sent to -> External_Postfix_relay (ip source from client > ok) -> Internal_Postfix_server (ip source from external postfix relay, > not the one from client's mail_message) > > How can i do that ? > >>> If you want to propagate the remote SMTP client IP address or the > >>> External_Postfix_relay server IP address, the External_Postfix_relay > >>> server could send XCLIENT commands to the final postfix server > >>> (internal). See https://www.postfix.org/XCLIENT_README.html > >>> > >>> Or you could use Postfix's HaProxy protocol support in the final > >>> postfix server (internal) to get a similar result. > >>> > >>> Wietse > >>> ___ > >>> Postfix-users mailing list -- postfix-users@postfix.org > >>> To unsubscribe send an email to postfix-users-le...@postfix.org > >> ___ > >> Postfix-users mailing list -- postfix-users@postfix.org > >> To unsubscribe send an email to postfix-users-le...@postfix.org > >> > > ___ > > Postfix-users mailing list -- postfix-users@postfix.org > > To unsubscribe send an email to postfix-users-le...@postfix.org > ___ > Postfix-users mailing list -- postfix-users@postfix.org > To unsubscribe send an email to postfix-users-le...@postfix.org > ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: forward IP source from a postfix relay to a postfix server
Hi, Well. i read it : https://postfix.traduc.org/index.php/XFORWARD_README.html But i don't know how to implement that in postfix (master.cf ?) ?! the link explain the "protocol"... there's no howto to do it... if someone know an howto somewhere ? Regards, PG On 11/10/2023 00:20, Wietse Venema via Postfix-users wrote: testeur via Postfix-users: Hi, I don't understand how the External_Postfix_relay server could send XCLIENT commands to the final postfix server ? is there some modifications to do in the master.cf file ? You asked how to impersonate a client or server TCP endpoint. Postfix supports receiving TCP endpoint impersonation commands using two protocols: XCLIENT (used by nginx) and the HaProxy protocol. The primary use cases are load balancers and policy testing. There is no code in Postfix to send XCLIENT or HaProxy commands for the simple reason that no-one has needed it. Postfix does support sending XFORWARD commands with remote SMTP client information for the purpose of logging, not impersonantion. It is typically used with SMTP-based content filters. Wietse Regards, On 08/10/2023 22:19, Wietse Venema via Postfix-users wrote: testeur via Postfix-users: Hi, I try to find a solution to forward the IP source from the postfix relay to the final postfix server (internal). Mail_Message sent to -> External_Postfix_relay (ip source from client ok) -> Internal_Postfix_server (ip source from external postfix relay, not the one from client's mail_message) How can i do that ? If you want to propagate the remote SMTP client IP address or the External_Postfix_relay server IP address, the External_Postfix_relay server could send XCLIENT commands to the final postfix server (internal). See https://www.postfix.org/XCLIENT_README.html Or you could use Postfix's HaProxy protocol support in the final postfix server (internal) to get a similar result. Wietse ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: Question about postscreen_dnsbl_sites
Ivan Ionut: > Thx, but I noticed that there is only for cidr...and i want for > hosts/domains too. If you want client name/domain based policies, don't use postscreen, use smtpd_mumble_restrictions instead. An smtpd process can do complex things such as verifying fully-confirmed forward/reverse DNS for clients in arbitrary domains, and making nuanced decisions based on the combination of client, sender, and recipient information. postscreen is designed to answer only one question: "is this a spambot". That is completely orthogonal to the question of whether or not you like a client hostname. postscreen cannot afford doing complex things. It must be able to handle many more (like 10 times more) clients than hundreds of smtpd processes combined can handle. postscreen has to make a quick decision based on the client IP address which is guaranteed to be available, and queries only the domains listed in postscreen_dnsbl_sites, which are guaranteed to respond quickly. postscreen WILL NOT query other domains because there are no response time guarantees. Wietse ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: Backup outgoing mail from one user
Le 11/10/2023 à 20:15, Jack Raats via Postfix-users a écrit : One of my users (my wife) lost her sent mail folder on her pc. She asked me if I had a backup of all het sent mail on my mail server, which I donn't. I have a backup of all her ingoing mail using procmail, but how can I make a backup of all her outgoing mail? For this I would look at sender_bcc_maps to send a copy of evrey mail from the given sender to an archiving address. ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Backup outgoing mail from one user
One of my users (my wife) lost her sent mail folder on her pc. She asked me if I had a backup of all het sent mail on my mail server, which I donn't. I have a backup of all her ingoing mail using procmail, but how can I make a backup of all her outgoing mail? Thanks Jack ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: No Permissions To TLS Certificates
duluxoz via Postfix-users: > Oct 11 17:33:05 mail.me.local email_postfix[2038]: find: > '/etc/postfix/./certs/me.local.pem': Permission denied > Oct 11 17:33:05 mail.me.local email_postfix[2039]: postfix/postlog: > warning: not owned by root: /etc/postfix/./certs/me.local.pem What is the output from: ls -ld / /etc /etc/postfix /etc/postfix/certs /etc/postfix/certs/me.local.pem > Oct 11 17:33:05 mail.me.local email_postfix[2038]: find: > '/etc/postfix/./certs/me2.local.pem': Permission denied > Oct 11 17:33:05 mail.me.local email_postfix[2040]: postfix/postlog: > warning: not owned by root: /etc/postfix/./certs/me2.local.pem What is the output from: ls -ld / /etc/postfix /etc/postfix/certs /etc/postfix/certs/me2.local.pem Wietse ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] No Permissions To TLS Certificates
Hi All,
Hoping someone can point me in the correct direction to solve this one
(ie why is postfix "not playing well" with our TLS Certs)
This is all internal (ie NOT on the Internet), so the below logs, etc,
have NOT been "edited" or obscured.
We're running two (internal) email domains: me.local and me2.local on
the one (Postfix v3.8.1) server (Rocky Linux v9.1). Dovecot is our MDA
and we're using MariaDB for our backend. Everything *seems* to be
working except for some TLS "stuff" (see below).
Each/Both email domains have an appropriate ECC Wildcard Certificate
from our internal CA (Step-CA, if it makes a difference), with the Key,
Hostname (ie "me.local" & "*.me.local"), the Intermediate CA & the Root
CA Certificates included, in that order. These Certificates also work on
our (internal) NginX Server for our internal websites - so that's all
good (as far as I can determine).
These Certificates (in .pem format) are placed in the
"/etc/postfix/certs/" folder. The folder and the certificates have
ownership of root:root and permissions of 0755/0600 respectively.
The sni_maps file (see next) has been hashed with "postmap -F
/etc/postfix/sni_maps".
~~~
me.local /etc/postfix/certs/me.local.pem
me2.local /etc/postfix/certs/me2.local.pem
~~~
We're getting the following warnings/errors on postfix start when we do
a "journalctl -u postfix" (which the postfix log file confirms):
~~~
Oct 11 17:33:05 mail.me.local systemd[1]: Starting Postfix Mail
Transport Agent...
Oct 11 17:33:05 mail.me.local email_postfix[2038]: find:
'/etc/postfix/./certs/me.local.pem': Permission denied
Oct 11 17:33:05 mail.me.local email_postfix[2039]: postfix/postlog:
warning: not owned by root: /etc/postfix/./certs/me.local.pem
Oct 11 17:33:05 mail.me.local postfix/postfix-script[2039]: warning: not
owned by root: /etc/postfix/./certs/me.local.pem
Oct 11 17:33:05 mail.me.local email_postfix[2038]: find:
'/etc/postfix/./certs/me2.local.pem': Permission denied
Oct 11 17:33:05 mail.me.local email_postfix[2040]: postfix/postlog:
warning: not owned by root: /etc/postfix/./certs/me2.local.pem
Oct 11 17:33:05 mail.me.local postfix/postfix-script[2040]: warning: not
owned by root: /etc/postfix/./certs/me2.local.pem
Oct 11 17:33:05 mail.me.local email_postfix[2044]: find:
'/etc/postfix/./certs/me.local.pem': Permission denied
Oct 11 17:33:05 mail.me.local email_postfix[2044]: find:
'/etc/postfix/./certs/me2.local.pem': Permission denied
Oct 11 17:33:05 mail.me.local email_postfix[2056]: postfix/postlog:
starting the Postfix mail system
Oct 11 17:33:05 mail.me.local postfix/postfix-script[2056]: starting the
Postfix mail system
Oct 11 17:33:05 mail.me.local postfix/master[2058]: daemon started --
version 3.8.1, configuration /etc/postfix
Oct 11 17:33:05 mail.me.local systemd[1]: Started Postfix Mail Transport
Agent.
~~~
Our "postconf -n" output is:
~~~
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
biff = no
command_directory = /usr/sbin
compatibility_level = 3.8
daemon_directory = /usr/libexec/postfix
data_directory = /var/lib/postfix
debug_peer_list = 192.168.1.0/24 192.168.2.0/24
debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin ddd
$daemon_directory/$process_name $process_id & sleep 5
default_destination_concurrency_limit = 20
disable_vrfy_command = yes
dovecot_destination_recipient_limit = 1
fallback_transport =
header_size_limit = 4096000
home_mailbox = Maildir/
html_directory = no
inet_interfaces = all
inet_protocols = ipv4
local_recipient_maps = $virtual_mailbox_maps
mail_owner = postfix
mailbox_size_limit = 0
mailq_path = /usr/bin/mailq.postfix
manpage_directory = /usr/share/man
message_size_limit = 104857600
meta_directory = /etc/postfix
milter_connect_macros = j {daemon_name} v {if_name} _
milter_default_action = accept
milter_protocol = 6
my_domain = me.local
my_external_ip =
my_hostname = mail.$my_domain
my_networks = 127.0.0.0/8 192.168.1.0/24 192.168.2.0/24
my_origin = $my_domain
my_relayhost =
mydestination = $myhostname localhost.$mydomain localhost
mydomain = $my_domain
myhostname = $my_hostname
mynetworks = $my_networks
myorigin = $my_origin
newaliases_path = /usr/bin/newaliases.postfix
non_smtpd_milters = $smtpd_milters
postscreen_access_list = permit_mynetworks
postscreen_bare_newline_action = enforce
postscreen_bare_newline_enable = yes
postscreen_dnsbl_action = enforce
postscreen_dnsbl_sites = b.barracudacentral.org bl.spamcop.net
postscreen_dnsbl_whitelist_threshold = -2
postscreen_greet_action = enforce
postscreen_non_smtp_command_action = enforce
postscreen_non_smtp_command_enable = yes
postscreen_pipelining_action = enforce
postscreen_pipelining_enable = yes
postscreen_upstream_proxy_protocol =
postscreen_upstream_proxy_timeout = 5s
proxy_interfaces = $my_external_ip
queue_directory = /var/spool/postfix
readme_directory = /usr/share/doc/postfix3-3.8.1/README_FILES
recipient_delimiter = +
relay_destination_concurrency_limit = 1
[pfx] Re: Question about postscreen_dnsbl_sites
Ivan Ionut via Postfix-users: > > Hi, I'm using postscreen_dnsbl_sites to block some spam and I want some > domain/hosts/ip to bypass this option, like an whitelist. > > Does postscreen/postfix has this option? > Yes. Near the top of https://www.postfix.org/POSTSCREEN_README.html#quick Quick tests before everything else Before engaging in SMTP-level tests. postscreen(8) queries a number of local deny and allowlists. These tests speed up the handling of known clients. * Permanent allow/denylist test * Temporary allowlist test * MX Policy test See website for more. Wietse ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Question about postscreen_dnsbl_sites
Hi, I'm using postscreen_dnsbl_sites to block some spam and I want some domain/hosts/ip to bypass this option, like an whitelist. Does postscreen/postfix has this option? p.s. my postfix version: 3.6.4 -- Ivan Ionuț Str. Mircea cel Bătrân nr 1, Galati 800023 Tel/Fax: +40236 493277 Email: ivan.io...@tehnopol-gl.ro _The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you are not the intended recipient of this message, please notify the sender immediately, and delete the message and any attachments. Any disclosure, reproduction, distribution or other use of this message or any attachments by an individual or entity other than the intended recipient is prohibited. Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: *.mail.protection.outlook.com reporting "452 4.5.3 Too many recipients (AS780090)" for many domains
On 11.10.23 15:06, Ralf Hildebrandt via Postfix-users wrote: Since this morning, various MX hosts in *.mail.protection.outlook.com reporting are reporting back temporary errors for us: Exhibit A) host ohri-ca.mail.protection.outlook.com[104.47.75.228] said: 452 4.5.3 Too many recipients (AS780090) [YQBCAN01FT018.eop-CAN01.prod.protection.outlook.com 2023-10-11T02:11:41.144Z 08DBC99CDEC51952] (in reply to RCPT TO command) (for a mail with 4 recipients, in that particular case) Exhibit B) host fraport-de.mail.protection.outlook.com[52.101.73.16] said: 451 4.7.500 Server busy. Please try again later from [193.175.73.209]. (S77719) [AMS0EPF019E.eurprd05.prod.outlook.com 2023-10-11T01:32:21.804Z 08DBC9B278D9A989] (in reply to end of DATA command) (for a single recipient mail) This is happening for multiple tenants on *.mail.protection.outlook.com Has anybody made similar observations? According to https://sendersupport.olc.protection.outlook.com/snds/ : "All of the specified IPs have normal status." I'm just solving similar problem with our client. We are getting the same problems. This client had no problems sending mail until today ~06:00 UTC. -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. How does cat play with mouse? cat /dev/mouse ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: *.mail.protection.outlook.com reporting "452 4.5.3 Too many recipients (AS780090)" for many domains
Dnia 11.10.2023 o godz. 15:11:27 Josef Vybíhal via Postfix-users pisze: > Hi, no clue about MS service, but it does not seem postfix related. > You might want to direct this to the mailop list - > https://list.mailop.org/listinfo/mailop It can be possibly related to some failure at Microsoft, discussed currently on mentioned "mailop" list in the following thread: "outlook.com 421 try again later S77719". -- Regards, Jaroslaw Rafa r...@rafa.eu.org -- "In a million years, when kids go to school, they're gonna know: once there was a Hushpuppy, and she lived with her daddy in the Bathtub." ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: *.mail.protection.outlook.com reporting "452 4.5.3 Too many recipients (AS780090)" for many domains
Hi Interesting read and an answer https://learn.microsoft.com/en-us/answers/questions/1388575/e-mail-sending-to-offcie-microsoft365-customers-no Paul On 11/10/2023 14:06, Ralf Hildebrandt via Postfix-users wrote: Hi! Since this morning, various MX hosts in *.mail.protection.outlook.com reporting are reporting back temporary errors for us: Exhibit A) host ohri-ca.mail.protection.outlook.com[104.47.75.228] said: 452 4.5.3 Too many recipients (AS780090) [YQBCAN01FT018.eop-CAN01.prod.protection.outlook.com 2023-10-11T02:11:41.144Z 08DBC99CDEC51952] (in reply to RCPT TO command) (for a mail with 4 recipients, in that particular case) Exhibit B) host fraport-de.mail.protection.outlook.com[52.101.73.16] said: 451 4.7.500 Server busy. Please try again later from [193.175.73.209]. (S77719) [AMS0EPF019E.eurprd05.prod.outlook.com 2023-10-11T01:32:21.804Z 08DBC9B278D9A989] (in reply to end of DATA command) (for a single recipient mail) This is happening for multiple tenants on *.mail.protection.outlook.com Has anybody made similar observations? According to https://sendersupport.olc.protection.outlook.com/snds/ : "All of the specified IPs have normal status." ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: *.mail.protection.outlook.com reporting "452 4.5.3 Too many recipients (AS780090)" for many domains
11.10.23, 15:06 +0200, Ralf Hildebrandt via Postfix-users: > Since this morning, various MX hosts in *.mail.protection.outlook.com > reporting are reporting back temporary errors for us: > > Exhibit A) > > host ohri-ca.mail.protection.outlook.com[104.47.75.228] said: 452 4.5.3 Too > many recipients (AS780090) > [YQBCAN01FT018.eop-CAN01.prod.protection.outlook.com 2023-10-11T02:11:41.144Z > 08DBC99CDEC51952] (in reply to RCPT TO command) > (for a mail with 4 recipients, in that particular case) > > Exhibit B) > > host fraport-de.mail.protection.outlook.com[52.101.73.16] said: 451 4.7.500 > Server busy. Please try again later from [193.175.73.209]. (S77719) > [AMS0EPF019E.eurprd05.prod.outlook.com 2023-10-11T01:32:21.804Z > 08DBC9B278D9A989] (in reply to end of DATA command) > (for a single recipient mail) > > This is happening for multiple tenants on *.mail.protection.outlook.com > Has anybody made similar observations? According to > https://sendersupport.olc.protection.outlook.com/snds/ : "All of the > specified IPs have normal status." There are multiple reports of this problem with MS servers on the mailop list and on reddit too. Solutions for the problem I have seen none yet, though. -- Regards mks ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: *.mail.protection.outlook.com reporting "452 4.5.3 Too many recipients (AS780090)" for many domains
Hi, no clue about MS service, but it does not seem postfix related. You might want to direct this to the mailop list - https://list.mailop.org/listinfo/mailop Josef On Wed, Oct 11, 2023 at 3:06 PM Ralf Hildebrandt via Postfix-users < postfix-users@postfix.org> wrote: > Hi! > > Since this morning, various MX hosts in *.mail.protection.outlook.com > reporting are reporting back temporary errors for us: > > Exhibit A) > > host ohri-ca.mail.protection.outlook.com[104.47.75.228] said: 452 4.5.3 > Too many recipients (AS780090) [ > YQBCAN01FT018.eop-CAN01.prod.protection.outlook.com > 2023-10-11T02:11:41.144Z 08DBC99CDEC51952] (in reply to RCPT TO command) > (for a mail with 4 recipients, in that particular case) > > Exhibit B) > > host fraport-de.mail.protection.outlook.com[52.101.73.16] said: 451 > 4.7.500 Server busy. Please try again later from [193.175.73.209]. (S77719) > [AMS0EPF019E.eurprd05.prod.outlook.com 2023-10-11T01:32:21.804Z > 08DBC9B278D9A989] (in reply to end of DATA command) > (for a single recipient mail) > > This is happening for multiple tenants on *.mail.protection.outlook.com > Has anybody made similar observations? According to > https://sendersupport.olc.protection.outlook.com/snds/ : "All of the > specified IPs have normal status." > > -- > Ralf Hildebrandt > Geschäftsbereich IT | Abteilung Netz | Netzwerk-Administration > Invalidenstraße 120/121 | D-10115 Berlin > Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 > ralf.hildebra...@charite.de | https://www.charite.de > > ___ > Postfix-users mailing list -- postfix-users@postfix.org > To unsubscribe send an email to postfix-users-le...@postfix.org > ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] *.mail.protection.outlook.com reporting "452 4.5.3 Too many recipients (AS780090)" for many domains
Hi! Since this morning, various MX hosts in *.mail.protection.outlook.com reporting are reporting back temporary errors for us: Exhibit A) host ohri-ca.mail.protection.outlook.com[104.47.75.228] said: 452 4.5.3 Too many recipients (AS780090) [YQBCAN01FT018.eop-CAN01.prod.protection.outlook.com 2023-10-11T02:11:41.144Z 08DBC99CDEC51952] (in reply to RCPT TO command) (for a mail with 4 recipients, in that particular case) Exhibit B) host fraport-de.mail.protection.outlook.com[52.101.73.16] said: 451 4.7.500 Server busy. Please try again later from [193.175.73.209]. (S77719) [AMS0EPF019E.eurprd05.prod.outlook.com 2023-10-11T01:32:21.804Z 08DBC9B278D9A989] (in reply to end of DATA command) (for a single recipient mail) This is happening for multiple tenants on *.mail.protection.outlook.com Has anybody made similar observations? According to https://sendersupport.olc.protection.outlook.com/snds/ : "All of the specified IPs have normal status." -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netz | Netzwerk-Administration Invalidenstraße 120/121 | D-10115 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
