Dropping email purporting to be from my domain received from the Internet
In my hypothetical environment, I have an external and an internal relay on either sides of a firewall. I want to configure the external system to relay both 1) email received from the internal relay to the Internet and 2) email received from the Internet to the internal relay (as long as the recipient is on my domain). This seems fairly straightforward to accomplish with a combination of mynetworks, relay_domains and relayhost or transport_maps configurations. Something I would like to drop, though, is email received from the Internet that has an address in the MAIL FROM on my domain but ONLY if received from the Internet (since it’s a core function of this relay to take identical messages relayed from the internal relay bound for Internet mail servers). I’ve been going through smtpd_sender_restrictions options look for something that fits the bill here, but I can’t seem to find anything that allows me to distinguish actions based upon whether or not the sender is not in my_networks (making them subject to “stranger rules” which include not sending FROM my domain). Is this something that’s relatively straightforward to configure in Postfix or do I need a more advanced anti-spam tool to get the configuration flexibility I need? Thanks, Scott
Re: Relationship between relay and transport
Thanks very much for the reply. I think my root difficulty was understanding the hierarchy behind forwarding rules (in this specific case; between relay and transport related parameters / tables). Your examples put me onto http://www.postfix.org/transport.5.html which gave me a much better idea of the order of precedence and which parameters win out over which in the event of a conflict. Thanks again, Scott From: owner-postfix-us...@postfix.org on behalf of Wietse Venema Sent: May 28, 2020 11:53 AM To: Postfix users Subject: Re: Relationship between relay and transport Scott A. Wozny: > In the standard config on an email gateway in > (http://www.postfix.org/STANDARD_CONFIGURATION_README.html#firewall) the > proposed config has relay_domains set for example.com and > transport_maps set to a hash with example.com using > smtp:[inside-gateway.example.com]. This would - Deliver example.com to the inside host. - Deliver other domains to the outside network. > My question is, how is this functionally different from setting > relayhost to [inside-gateway.example.com]? This would - Deliver example.com to the inside host. - Deliver other domains to the inside host. So they do different things for other domains. Wietse
Re: Postfix gateway with per relayed host outgoing IP
Matus UHLAR - fantomas: > >Matus UHLAR - fantomas: > >> >> how? > >> >> > >> >> if you define different smtp transports with different smtp_bind_address > >> >> defined in master.cf, the sender_dependent_default_transport_maps should > >> >> do > >> >> what you want. > >> > >> On 29.05.20 15:17, George wrote: > >> >Thanks for your response. My problem is that I do not know what to use in > >> >the file where sender_dependent_default_transport_maps is defined. > >> > > >> >Do I set it like this: > >> >@domain1_from_webserver1.com mastercf_transport1: > >> >@domain2_from_webserver1.com mastercf_transport1: > >> >@domain1_from_webserver2.com mastercf_transport2: > >> >@domain1_from_webserver2.com mastercf_transport2: > >> > >> do you have mastercf_transport1 and mastercf_transport2 defined in > >> master.cf? > >> > >> >Or is there any way for me to define the incoming webserver IP in > >> >sender_dependent_default_transport_maps? > >> > >> http://www.postfix.org/postconf.5.html#sender_dependent_default_transport_maps > >> > >> The tables are searched by the envelope sender address and @domain. > >> > >> so you can only configure sending user and sending domain there... > > On 29.05.20 09:44, Wietse Venema wrote: > >It is possible to use the 'filter' command for this. > > > >/etc/postfix/main.cf > >smtpd_client_restrictions = > > check_client_access hash:/etc/postfix/client_access > > > >/etc/postfix/client_access: > >1.2.3.4 filter smtp-for-4: > >1.2.3.5 filter smtp-for-5: > > > >/etc/postfix/master.cf: > >smtp-for-4 .. .. .. .. .. .. smtp > > -o smtp_bind_address=x.x.x.x > >smtp-for-5 .. .. .. .. .. .. smtp > > -o smtp_bind_address=y.y.y.y > > But this avoids local processing, doesn't it? > wouldn't this cause troubles if the mail was to be delivered locally? It is not needed for an outbound-only relay. To receive mail for their domains, they would need a second MTA. That MTA would also receive mail from the outbound-only relay. Each MTA needds a unique myhostname setting. Wietse
Re: 452 4.3.1 Insufficient system storage
On 29.05.20 15:42, Gabriele Bulfon wrote: This in mail.log: May 28 20:09:45 cloudserver postfix/smtpd[21079]: [ID 197553 mail.info] connect from sender-host[*.*.*.*] May 28 20:09:45 cloudserver postfix/smtpd[21079]: [ID 197553 mail.info] Anonymous TLS connection established from sender-host[*.*.*.*]: TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits) May 28 20:09:45 cloudserver postfix/smtpd[21079]: [ID 197553 mail.info] NOQUEUE: reject: MAIL from sender-host[*.*.*.*]: 452 4.3.1 Insufficient system storage; proto=ESMTP helo= May 28 20:09:45 cloudserver postfix/smtpd[21079]: [ID 947731 mail.warning] warning: not enough free space in mail queue: 38384640 bytes This last warning looks quite uncomprehensible, message size limit is 5000, and sure 38384640 is less than 1.5*msl, so what's the problem? _that_ is apparently the problem. you have 38384640 B (~38MB) of free space in queue, but message maximum size is 50MB, so you don't have enough of free space for maximum message size, not even for 1.5*maximum required by default: http://www.postfix.org/postconf.5.html#queue_minfree -- 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. The 3 biggets disasters: Hiroshima 45, Tschernobyl 86, Windows 95
Re: Postfix gateway with per relayed host outgoing IP
Matus UHLAR - fantomas: >> how? >> >> if you define different smtp transports with different smtp_bind_address >> defined in master.cf, the sender_dependent_default_transport_maps should >> do >> what you want. On 29.05.20 15:17, George wrote: >Thanks for your response. My problem is that I do not know what to use in >the file where sender_dependent_default_transport_maps is defined. > >Do I set it like this: >@domain1_from_webserver1.com mastercf_transport1: >@domain2_from_webserver1.com mastercf_transport1: >@domain1_from_webserver2.com mastercf_transport2: >@domain1_from_webserver2.com mastercf_transport2: do you have mastercf_transport1 and mastercf_transport2 defined in master.cf? >Or is there any way for me to define the incoming webserver IP in >sender_dependent_default_transport_maps? http://www.postfix.org/postconf.5.html#sender_dependent_default_transport_maps The tables are searched by the envelope sender address and @domain. so you can only configure sending user and sending domain there... On 29.05.20 09:44, Wietse Venema wrote: It is possible to use the 'filter' command for this. /etc/postfix/main.cf smtpd_client_restrictions = check_client_access hash:/etc/postfix/client_access /etc/postfix/client_access: 1.2.3.4 filter smtp-for-4: 1.2.3.5 filter smtp-for-5: /etc/postfix/master.cf: smtp-for-4 .. .. .. .. .. .. smtp -o smtp_bind_address=x.x.x.x smtp-for-5 .. .. .. .. .. .. smtp -o smtp_bind_address=y.y.y.y But this avoids local processing, doesn't it? wouldn't this cause troubles if the mail was to be delivered locally? -- 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. Christian Science Programming: "Let God Debug It!".
Re: smtp servers port
On 29 May 2020, at 08:19, Istvan Prosinger wrote: > 587 is so called submission, it's for communication between client <-> server Client to server, but not server to client. -- "A common mistake people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools.: - Douglas Adams
Re: smtp servers port
Le me contribute to the list. The mail transport between _two servers_ is always on port 25. 587 is so called submission, it's for communication between client <-> server best, Istvan On 5/29/20 2:16 PM, Matteo Cazzador wrote: Hi, excuse a question, during the comunication between 2 mail servers there is a phase of according about che port to use to comunicate? There is a checking about port 587 or 25 during these comunication? or two servers only use 25 port by default? Sorry for the level of the question I ask you. Thanks
Re: 452 4.3.1 Insufficient system storage
Gabriele Bulfon: > May 28 20:09:45 cloudserver postfix/smtpd[21079]: [ID 947731 mail.warning] > warning: not enough free space in mail queue: 38384640 bytes > ? > This last warning looks quite uncomprehensible, message size limit is? > 5000, and sure?38384640 is less than 1.5*msl, so what's the problem? Maybe this helps: OpenWrt has patched Postfix to look up the free space from "/overlay" instead of the actual queue location. https://marc.info/?l=postfix-users=156814845220945 https://github.com/openwrt/packages/issues/9970 -- Mike
Re: Postfix gateway with per relayed host outgoing IP
Hi, Wow! Your solution worked like a charm from first attempt. This is genius. Thanks a lot for the help everyone. It is possible to use the 'filter' command for this. > > /etc/postfix/main.cf > smtpd_client_restrictions = > check_client_access hash:/etc/postfix/client_access > > /etc/postfix/client_access: > 1.2.3.4 filter smtp-for-4: > 1.2.3.5 filter smtp-for-5: > > /etc/postfix/master.cf: > smtp-for-4 .. .. .. .. .. .. smtp > -o smtp_bind_address=x.x.x.x > smtp-for-5 .. .. .. .. .. .. smtp > -o smtp_bind_address=y.y.y.y > > This is supported as of Postfix 2.7. > > The 'filter' feature can also be used for rate limits > 1/s by using > paralel deliveries, for IP address reputations (see below) and more. > >
Re: Postfix gateway with per relayed host outgoing IP
Matus UHLAR - fantomas: > >> how? > >> > >> if you define different smtp transports with different smtp_bind_address > >> defined in master.cf, the sender_dependent_default_transport_maps should > >> do > >> what you want. > > On 29.05.20 15:17, George wrote: > >Thanks for your response. My problem is that I do not know what to use in > >the file where sender_dependent_default_transport_maps is defined. > > > >Do I set it like this: > >@domain1_from_webserver1.com mastercf_transport1: > >@domain2_from_webserver1.com mastercf_transport1: > >@domain1_from_webserver2.com mastercf_transport2: > >@domain1_from_webserver2.com mastercf_transport2: > > do you have mastercf_transport1 and mastercf_transport2 defined in > master.cf? > > >Or is there any way for me to define the incoming webserver IP in > >sender_dependent_default_transport_maps? > > http://www.postfix.org/postconf.5.html#sender_dependent_default_transport_maps > > The tables are searched by the envelope sender address and @domain. > > so you can only configure sending user and sending domain there... It is possible to use the 'filter' command for this. /etc/postfix/main.cf smtpd_client_restrictions = check_client_access hash:/etc/postfix/client_access /etc/postfix/client_access: 1.2.3.4 filter smtp-for-4: 1.2.3.5 filter smtp-for-5: /etc/postfix/master.cf: smtp-for-4 .. .. .. .. .. .. smtp -o smtp_bind_address=x.x.x.x smtp-for-5 .. .. .. .. .. .. smtp -o smtp_bind_address=y.y.y.y This is supported as of Postfix 2.7. The 'filter' feature can also be used for rate limits > 1/s by using paralel deliveries, for IP address reputations (see below) and more. Wietse Fragment from the release notes: [Feature 20100117] The FILTER action in access maps or header/body_checks now supports sender reputation schemes that dynamically choose the SMTP source IP address. Typically, mail is split into classes, and all mail in class X is sent out from an SMTP client IP address that is reserved for class X. This is implemented by specifying FILTER actions with empty next-hop destinations in access maps or header/body_checks, and by configuring in master.cf one Postfix SMTP client for each SMTP source IP address, where each client has its own "-o myhostname" and "-o smtp_bind_address" settings.
Re: 452 4.3.1 Insufficient system storage
This in mail.log: May 28 20:09:45 cloudserver postfix/smtpd[21079]: [ID 197553 mail.info] connect from sender-host[*.*.*.*] May 28 20:09:45 cloudserver postfix/smtpd[21079]: [ID 197553 mail.info] Anonymous TLS connection established from sender-host[*.*.*.*]: TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits) May 28 20:09:45 cloudserver postfix/smtpd[21079]: [ID 197553 mail.info] NOQUEUE: reject: MAIL from sender-host[*.*.*.*]: 452 4.3.1 Insufficient system storage; proto=ESMTP helo= May 28 20:09:45 cloudserver postfix/smtpd[21079]: [ID 947731 mail.warning] warning: not enough free space in mail queue: 38384640 bytes This last warning looks quite uncomprehensible, message size limit is 5000, and sure 38384640 is less than 1.5*msl, so what's the problem? Gabriele Sonicle S.r.l. : http://www.sonicle.com Music: http://www.gabrielebulfon.com Quantum Mechanics : http://www.cdbaby.com/cd/gabrielebulfon -- Da: Matus UHLAR - fantomas A: postfix-users@postfix.org Data: 29 maggio 2020 15.36.01 CEST Oggetto: Re: 452 4.3.1 Insufficient system storage On 29.05.20 15:21, Gabriele Bulfon wrote: the spool directory is inside a custom direcotry: /sonicle/var/spool/mqueue, which is under the root zfs dataset with more than 1TB of free space, and it's always been there for years. Also the binaries are built 32bit with large files, and they also worked like this for years. does the system produce any kind of logs at the time problem happens? I have a system running for some years, recently started to send "452 4.3.1 Insufficient system storage" errors randomly. Sometimes 2-3 during the night, sometimes many more (20-30). Postfix is running under an illumos zone, over a zfs data pool with more than 1TB of free space. Size of emails with error is small enough to fit max message size. The error email shows this: Transcript of session follows. Out: 220 servername ESMTP Postfix In: EHLO mail1.ferrari.it Out: 250-servername Out: 250-SIZE 5000 Out: 250-VRFY Out: 250-ETRN Out: 250-STARTTLS Out: 250-AUTH PLAIN Out: 250-AUTH=PLAIN Out: 250-ENHANCEDSTATUSCODES Out: 250-8BITMIME Out: 250 DSN In: STARTTLS Out: 220 2.0.0 Ready to start TLS In: EHLO sendingservername Out: 250-servername Out: 250-SIZE 5000 Out: 250-VRFY Out: 250-ETRN Out: 250-AUTH PLAIN Out: 250-AUTH=PLAIN Out: 250-ENHANCEDSTATUSCODES Out: 250-8BITMIME Out: 250 DSN In: MAIL FROM: SIZE=85683 Out: 452 4.3.1 Insufficient system storage In: QUIT Out: 221 2.0.0 Bye -- 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. M$ Win's are shit, do not use it !
Re: 452 4.3.1 Insufficient system storage
On 29.05.20 15:21, Gabriele Bulfon wrote: the spool directory is inside a custom direcotry: /sonicle/var/spool/mqueue, which is under the root zfs dataset with more than 1TB of free space, and it's always been there for years. Also the binaries are built 32bit with large files, and they also worked like this for years. does the system produce any kind of logs at the time problem happens? I have a system running for some years, recently started to send "452 4.3.1 Insufficient system storage" errors randomly. Sometimes 2-3 during the night, sometimes many more (20-30). Postfix is running under an illumos zone, over a zfs data pool with more than 1TB of free space. Size of emails with error is small enough to fit max message size. The error email shows this: Transcript of session follows. Out: 220 servername ESMTP Postfix In: EHLO mail1.ferrari.it Out: 250-servername Out: 250-SIZE 5000 Out: 250-VRFY Out: 250-ETRN Out: 250-STARTTLS Out: 250-AUTH PLAIN Out: 250-AUTH=PLAIN Out: 250-ENHANCEDSTATUSCODES Out: 250-8BITMIME Out: 250 DSN In: STARTTLS Out: 220 2.0.0 Ready to start TLS In: EHLO sendingservername Out: 250-servername Out: 250-SIZE 5000 Out: 250-VRFY Out: 250-ETRN Out: 250-AUTH PLAIN Out: 250-AUTH=PLAIN Out: 250-ENHANCEDSTATUSCODES Out: 250-8BITMIME Out: 250 DSN In: MAIL FROM: SIZE=85683 Out: 452 4.3.1 Insufficient system storage In: QUIT Out: 221 2.0.0 Bye -- 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. M$ Win's are shit, do not use it !
Re: 452 4.3.1 Insufficient system storage
Thanks, the spool directory is inside a custom direcotry: /sonicle/var/spool/mqueue, which is under the root zfs dataset with more than 1TB of free space, and it's always been there for years. Also the binaries are built 32bit with large files, and they also worked like this for years. message_size_limit is 5000, as it is visible in the error output ( Out: 250-SIZE 5000) mailbox_size_limit is not set, postconf says mailbox_size_limit = 5120 Postfix is configured to deliver to cyrus, as it has been for years. Thanks! Gabriele Sonicle S.r.l. : http://www.sonicle.com Music: http://www.gabrielebulfon.com Quantum Mechanics : http://www.cdbaby.com/cd/gabrielebulfon Da: Ahsan Khan A: Gabriele Bulfon Cc: Postfix users Data: 29 maggio 2020 14.56.12 CEST Oggetto: Re: 452 4.3.1 Insufficient system storage Hi Gabriele Can you check the spool directory where the mail is queued. For sendmail, i recall it was /var/spool/mqueue. Also check message_size_limit and mailbox_size_limit in main.cf Regards Ahsan On Fri, May 29, 2020 at 6:14 PM Gabriele Bulfon gbul...@sonicle.com wrote: Hello, I have a system running for some years, recently started to send "452 4.3.1 Insufficient system storage" errors randomly. Sometimes 2-3 during the night, sometimes many more (20-30). Postfix is running under an illumos zone, over a zfs data pool with more than 1TB of free space. Size of emails with error is small enough to fit max message size. The error email shows this: Transcript of session follows. Out: 220 servername ESMTP Postfix In: EHLO mail1.ferrari.it Out: 250-servername Out: 250-SIZE 5000 Out: 250-VRFY Out: 250-ETRN Out: 250-STARTTLS Out: 250-AUTH PLAIN Out: 250-AUTH=PLAIN Out: 250-ENHANCEDSTATUSCODES Out: 250-8BITMIME Out: 250 DSN In: STARTTLS Out: 220 2.0.0 Ready to start TLS In: EHLO sendingservername Out: 250-servername Out: 250-SIZE 5000 Out: 250-VRFY Out: 250-ETRN Out: 250-AUTH PLAIN Out: 250-AUTH=PLAIN Out: 250-ENHANCEDSTATUSCODES Out: 250-8BITMIME Out: 250 DSN In: MAIL FROM: SIZE=85683 Out: 452 4.3.1 Insufficient system storage In: QUIT Out: 221 2.0.0 Bye Never happened before. Any idea what's happening? Thanks! Gabriele Sonicle S.r.l. : http://www.sonicle.com Music: http://www.gabrielebulfon.com Quantum Mechanics : http://www.cdbaby.com/cd/gabrielebulfon
Re: 452 4.3.1 Insufficient system storage
Hi Gabriele Can you check the spool directory where the mail is queued. For sendmail, i recall it was /var/spool/mqueue. Also check message_size_limit and mailbox_size_limit in main.cf Regards Ahsan On Fri, May 29, 2020 at 6:14 PM Gabriele Bulfon wrote: > Hello, > > I have a system running for some years, recently started to send "452 > 4.3.1 Insufficient system storage" errors randomly. > Sometimes 2-3 during the night, sometimes many more (20-30). > Postfix is running under an illumos zone, over a zfs data pool with more > than 1TB of free space. > Size of emails with error is small enough to fit max message size. > The error email shows this: > > Transcript of session follows. > > Out: 220 servername ESMTP Postfix > In: EHLO mail1.ferrari.it > Out: 250-servername > Out: 250-SIZE 5000 > Out: 250-VRFY > Out: 250-ETRN > Out: 250-STARTTLS > Out: 250-AUTH PLAIN > Out: 250-AUTH=PLAIN > Out: 250-ENHANCEDSTATUSCODES > Out: 250-8BITMIME > Out: 250 DSN > In: STARTTLS > Out: 220 2.0.0 Ready to start TLS > In: EHLO sendingservername > Out: 250-servername > Out: 250-SIZE 5000 > Out: 250-VRFY > Out: 250-ETRN > Out: 250-AUTH PLAIN > Out: 250-AUTH=PLAIN > Out: 250-ENHANCEDSTATUSCODES > Out: 250-8BITMIME > Out: 250 DSN > In: MAIL FROM: SIZE=85683 > Out: 452 4.3.1 Insufficient system storage > In: QUIT > Out: 221 2.0.0 Bye > > Never happened before. > Any idea what's happening? > > Thanks! > Gabriele > > > > *Sonicle S.r.l. *: http://www.sonicle.com > *Music: *http://www.gabrielebulfon.com > *Quantum Mechanics : *http://www.cdbaby.com/cd/gabrielebulfon >
452 4.3.1 Insufficient system storage
Hello, I have a system running for some years, recently started to send "452 4.3.1 Insufficient system storage" errors randomly. Sometimes 2-3 during the night, sometimes many more (20-30). Postfix is running under an illumos zone, over a zfs data pool with more than 1TB of free space. Size of emails with error is small enough to fit max message size. The error email shows this: Transcript of session follows. Out: 220 servername ESMTP Postfix In: EHLO mail1.ferrari.it Out: 250-servername Out: 250-SIZE 5000 Out: 250-VRFY Out: 250-ETRN Out: 250-STARTTLS Out: 250-AUTH PLAIN Out: 250-AUTH=PLAIN Out: 250-ENHANCEDSTATUSCODES Out: 250-8BITMIME Out: 250 DSN In: STARTTLS Out: 220 2.0.0 Ready to start TLS In: EHLO sendingservername Out: 250-servername Out: 250-SIZE 5000 Out: 250-VRFY Out: 250-ETRN Out: 250-AUTH PLAIN Out: 250-AUTH=PLAIN Out: 250-ENHANCEDSTATUSCODES Out: 250-8BITMIME Out: 250 DSN In: MAIL FROM: SIZE=85683 Out: 452 4.3.1 Insufficient system storage In: QUIT Out: 221 2.0.0 Bye Never happened before. Any idea what's happening? Thanks! Gabriele Sonicle S.r.l. : http://www.sonicle.com Music: http://www.gabrielebulfon.com Quantum Mechanics : http://www.cdbaby.com/cd/gabrielebulfon
Re: Postfix gateway with per relayed host outgoing IP
how? if you define different smtp transports with different smtp_bind_address defined in master.cf, the sender_dependent_default_transport_maps should do what you want. On 29.05.20 15:17, George wrote: Thanks for your response. My problem is that I do not know what to use in the file where sender_dependent_default_transport_maps is defined. Do I set it like this: @domain1_from_webserver1.com mastercf_transport1: @domain2_from_webserver1.com mastercf_transport1: @domain1_from_webserver2.com mastercf_transport2: @domain1_from_webserver2.com mastercf_transport2: do you have mastercf_transport1 and mastercf_transport2 defined in master.cf? Or is there any way for me to define the incoming webserver IP in sender_dependent_default_transport_maps? http://www.postfix.org/postconf.5.html#sender_dependent_default_transport_maps The tables are searched by the envelope sender address and @domain. so you can only configure sending user and sending domain there... -- 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. The early bird may get the worm, but the second mouse gets the cheese.
Re: smtp servers port
Mail is transferred between domains always through port 25 according to multiple RFC. Port 587 can be used if a MUA (client) send mail through selected server. On Fri, May 29, 2020 at 02:16:29PM +0200, Matteo Cazzador wrote: Hi, excuse a question, during the comunication between 2 mail servers there is a phase of according about che port to use to comunicate? There is a checking about port 587 or 25 during these comunication? or two servers only use 25 port by default? Sorry for the level of the question I ask you. Thanks -- Rispetta l'ambiente: se non ti è necessario, non stampare questa mail. Le informazioni contenute in questa e-mail e nei files eventualmente allegati sono destinate unicamente ai destinatari della stessa e sono da considerarsi strettamente riservate. E' proibito copiare, salvare, utilizzare, inoltrare a terzi e diffondere il contenuto della presente senza il preventivo consenso, ai sensi dell'articolo 616 c.p. e della Legge n. 196/2003. Se avete ricevuto questo messaggio per errore siete pregati di comunicarlo immediatamente all'indirizzo mittente, nonché di cancellarne il contenuto senza procedere ad ulteriore o differente trattamento. ** Ing. Matteo Cazzador NetLite snc di Cazzador Gagliardi Corso Vittorio Emanuele II, 188 37069 Villafranca di Verona VR Tel 0454856656 Fax 0454856655 Email: mat...@netlite.it Web: http://www.netlite.it ** -- Sincerely yours, Dima Veselov Physics R Establishment of Saint-Petersburg University
Re: smtp servers port
On 2020-05-29 Matteo Cazzador wrote: > Hi, excuse a question, during the comunication between 2 mail servers > there is a phase of according about che port to use to comunicate? > > There is a checking about port 587 or 25 during these comunication? > or two servers only use 25 port by default? > > Sorry for the level of the question I ask you. No, mail servers don't negotiate which port to communicate on. Port 587 (submission) is the port for MUA to MTA communication. That port should be used when a mail client (MUA, mail user agent) is initially sending/submitting mail to its upstream mail server/relay. Also, submission normally requires both encryption (TLS) and authentication. Port 25 (smtp) is the starndard port for MTA to MTA communication (MTA means mail transfer agent, vulgo mail server). Unless the sending MTA is configured to use a different port for a specific next hop that port will be used. Of course an MTA can also use submission to send to a next-hop MTA if the latter supports that (since the sending MTA is acting as a client there), but you would need to specifically configure that on the sender. Regards Ansgar Wiechers -- "Abstractions save us time working, but they don't save us time learning." --Joel Spolsky
Re: Postfix gateway with per relayed host outgoing IP
> how? > > if you define different smtp transports with different smtp_bind_address > defined in master.cf, the sender_dependent_default_transport_maps should > do > what you want. > > > Hi, Thanks for your response. My problem is that I do not know what to use in the file where sender_dependent_default_transport_maps is defined. Do I set it like this: @domain1_from_webserver1.com mastercf_transport1: @domain2_from_webserver1.com mastercf_transport1: @domain1_from_webserver2.com mastercf_transport2: @domain1_from_webserver2.com mastercf_transport2: Or is there any way for me to define the incoming webserver IP in sender_dependent_default_transport_maps? Please let me know Thanks in advance
smtp servers port
Hi, excuse a question, during the comunication between 2 mail servers there is a phase of according about che port to use to comunicate? There is a checking about port 587 or 25 during these comunication? or two servers only use 25 port by default? Sorry for the level of the question I ask you. Thanks -- Rispetta l'ambiente: se non ti è necessario, non stampare questa mail. Le informazioni contenute in questa e-mail e nei files eventualmente allegati sono destinate unicamente ai destinatari della stessa e sono da considerarsi strettamente riservate. E' proibito copiare, salvare, utilizzare, inoltrare a terzi e diffondere il contenuto della presente senza il preventivo consenso, ai sensi dell'articolo 616 c.p. e della Legge n. 196/2003. Se avete ricevuto questo messaggio per errore siete pregati di comunicarlo immediatamente all'indirizzo mittente, nonché di cancellarne il contenuto senza procedere ad ulteriore o differente trattamento. ** Ing. Matteo Cazzador NetLite snc di Cazzador Gagliardi Corso Vittorio Emanuele II, 188 37069 Villafranca di Verona VR Tel 0454856656 Fax 0454856655 Email: mat...@netlite.it Web: http://www.netlite.it **
Re: Postfix gateway with per relayed host outgoing IP
On 29.05.20 12:29, George wrote: I have an anti spam postfix gateway running on an Ubuntu server. Currently I use relayhost on multiple web servers for sending mail through the gateway. On the postfix gateway I have multiple secondary IPs. What I want to do is to configure the gateway so mail sent from a particular web server through the gateway to go out from a particular secondary IP from the gateway server like below: webserver1 -> gateway -> secondaryIP1 webserver2 -> gateway -> secondaryIP2 I tried to use sender_dependent_default_transport_maps but had no luck so far. how? if you define different smtp transports with different smtp_bind_address defined in master.cf, the sender_dependent_default_transport_maps should do what you want. Can someone please advise on how I can go with implementing this? Thanks in advance. -- 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. "One World. One Web. One Program." - Microsoft promotional advertisement "Ein Volk, ein Reich, ein Fuhrer!" - Adolf Hitler
Re: Postfix relay to external and internal
On 29.05.20 10:14, Dino Edwards wrote: I have a postfix server that acts as a relay server for several domains and relays e-mail to several external e-mail servers based on the domain. This setup has been working for years with no problems. Now I have a need to install a local mailserver (dovecot?) server on this relay server and I'm trying to figure out the best way to accomplish that. So in the end, I want to maintain the relay ability for the several domains to outside e-mail servers but I also want to be able to deliver e-mail to local mailserver with ideally virtual users. Is this possible and what would be the best way to accomplish this? defining local domain should not affect other domains and other domains should not affect local domain, unless you break something horribly. I would simply define test domain, real or virtual, and try to deliver mail there. Should work. -- 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. I intend to live forever - so far so good.
Re: Postfix -> Whatapp
On Tuesday, 26 May 2020 18:42, Jos Chrispijn wrote: > Is there a way of Postfix sending a Whatsapp message to a user when there > came in email for her/him? > > Thanks, Jos > > -- With both feet on the ground you can't make any step forward Jos, I'm a bit late to this discussion (and I have not read all replies, so apologies if someone has already mentioned my suggestion). I would suggest you look at Doveot and its global IMAP Seive functionality. You can pipe stuff into shell scripts and hence do whatever you wish.
Postfix relay to external and internal
Hi, I have a postfix server that acts as a relay server for several domains and relays e-mail to several external e-mail servers based on the domain. This setup has been working for years with no problems. Now I have a need to install a local mailserver (dovecot?) server on this relay server and I'm trying to figure out the best way to accomplish that. So in the end, I want to maintain the relay ability for the several domains to outside e-mail servers but I also want to be able to deliver e-mail to local mailserver with ideally virtual users. Is this possible and what would be the best way to accomplish this? Thanks a lot in advance.
Postfix gateway with per relayed host outgoing IP
Hi, I have an anti spam postfix gateway running on an Ubuntu server. Currently I use relayhost on multiple web servers for sending mail through the gateway. On the postfix gateway I have multiple secondary IPs. What I want to do is to configure the gateway so mail sent from a particular web server through the gateway to go out from a particular secondary IP from the gateway server like below: webserver1 -> gateway -> secondaryIP1 webserver2 -> gateway -> secondaryIP2 I tried to use sender_dependent_default_transport_maps but had no luck so far. Can someone please advise on how I can go with implementing this? Thanks in advance.
