Re: Postfix can't find Postgserql's unix socket using "peer" method

2020-01-29 Thread Viktor Dukhovni
On Wed, Jan 29, 2020 at 01:21:03AM -0500, Hamid M. wrote: > Just curious if I wanted to disable chroot, should it only apply to smtpd > or some other few services? Generally all. If however you later decide to reenable chroot, some services will need to stay not chrooted. proxymap proxy

Re: 20200108 -- nexthop destinations separated by comma or whitespace

2020-01-29 Thread Viktor Dukhovni
On Wed, Jan 29, 2020 at 10:52:02AM +0100, Ralf Hildebrandt wrote: > > This looks wrong, it should be : > > > > exchange.charite.de > > exchange:s-mx14-ht01.charite.de,s-mx14-ht02.charite.de > > > > One "exchange" transport, multiple nexthop hosts. > > Cool. > > > Not sure why it worked

Re: COMMAND PIPELINING

2020-01-29 Thread Viktor Dukhovni
On Wed, Jan 29, 2020 at 08:45:35PM +0100, Jos Chrispijn wrote: > Can someone tell me what this server tries to accomplish: > > COMMAND PIPELINING from [183.89.214.13]:44487 after ???: > \000\234\000\235\000/\0005\300\022\000\n\001\000\000d\000\000\000\023\000\021\000\000\016mail.some.net\000\005

Re: LMTP and undeliverable addresses

2020-01-29 Thread Viktor Dukhovni
On Wed, Jan 29, 2020 at 06:23:37PM +, Nick wrote: >local_recipient_maps = $real_recipients, $virtual_alias_maps By the way, you DO NOT need to list $virtual_alias_maps in local_recipient_maps. Postfix will automatically check $virtual_alias_maps, you're just doing it twice. -- Vikt

COMMAND PIPELINING

2020-01-29 Thread Jos Chrispijn
Can someone tell me what this server tries to accomplish: COMMAND PIPELINING from [183.89.214.13]:44487 after ???: \000\234\000\235\000/\0005\300\022\000\n\001\000\000d\000\000\000\023\000\021\000\000\016mail.some.net\000\005\000\005\001\000\000\000\000\000\n\000\n\000\b\000\035\000\027\000\030\

Re: LMTP and undeliverable addresses

2020-01-29 Thread Nick
On 2020-01-29 18:38 GMT, Wietse Venema wrote: > Nick: > >local_transport = lmtp:unix:private/dovecot-lmtp > >local_recipient_maps = $real_recipients, $virtual_alias_maps > >550 5.1.1 : Recipient address > > rejected: undeliverable address: host > > mail.acrasis.net[private/do

Re: LMTP and undeliverable addresses

2020-01-29 Thread Wietse Venema
Nick: > This isn't causing me any problem (that I can tell) so I ask out of > curiosity, about postfix 3.4.7 on debian stable... > > My main.cf sets local delivery to go to dovecot, > >local_transport = lmtp:unix:private/dovecot-lmtp > > In obedience to LOCAL_RECIPIENT_README it also sets >

LMTP and undeliverable addresses

2020-01-29 Thread Nick
This isn't causing me any problem (that I can tell) so I ask out of curiosity, about postfix 3.4.7 on debian stable... My main.cf sets local delivery to go to dovecot, local_transport = lmtp:unix:private/dovecot-lmtp In obedience to LOCAL_RECIPIENT_README it also sets local_recipient_maps to

Re: Pcre condition check "To" and "From"

2020-01-29 Thread Matteo Cazzador
Thanks ⁣Ottieni BlueMail per Android ​ Il giorno 29 gen 2020, 19:11, alle ore 19:11, Wietse Venema ha scritto: >Matteo Cazzador: >> Hi, is it possible to do a double pcre condition check like this: >> >> if /From:.*pi...@gmail.com/ >> /To:.*i...@example.com/ REDIRECT in...@example.com >> endif

Re: Pcre condition check "To" and "From"

2020-01-29 Thread Wietse Venema
Matteo Cazzador: > Hi, is it possible to do a double pcre condition check like this: > > if /From:.*pi...@gmail.com/ > /To:.*i...@example.com/ REDIRECT in...@example.com > endif > > Check the sender but execute action REJECT only for a specific "To" ? As documented, not with header_checks. It ma

Pcre condition check "To" and "From"

2020-01-29 Thread Matteo Cazzador
Hi, is it possible to do a double pcre condition check like this: if /From:.*pi...@gmail.com/ /To:.*i...@example.com/ REDIRECT in...@example.com endif Check the sender but execute action REJECT only for a specific "To" ? Thanks a lot. -- Rispetta l'ambiente: se non ti è necessario, non stampar

Re: rewrite of clients from and to

2020-01-29 Thread Noel Jones
On 1/29/2020 9:26 AM, Averlon wrote: Dear all, I have a client in my network, a technical device, which I can only set some parameters to send mails (mailserver, port, sender-address, receipient-address, …), but not manipulate or administrate. I have a Postfix installation in my INTRANET, us

rewrite of clients from and to

2020-01-29 Thread Averlon
Dear all, I have a client in my network, a technical device, which I can only set some parameters to send mails (mailserver, port, sender-address, receipient-address, .), but not manipulate or administrate. I have a Postfix installation in my INTRANET, using port 25, just to get e-Mails from c

Re: easy way to forward all root mail to devnull?

2020-01-29 Thread Matus UHLAR - fantomas
On Jan 29, 2020, at 4:16 AM, Eero Volotinen wrote: Is there easy way to forward all root mail to devnull? On 29.01.20 04:37, Viktor Dukhovni wrote: Assuming it is not unwise: aliases: root: root@discard.invalid virtual: rootroot@discar

Re: Postfix can't find Postgserql's unix socket using "peer" method

2020-01-29 Thread Christoph Moench-Tegeder
## Hamid M. (spam@gmail.com): > postfix/trivial-rewrite[8119]: warning: connect to pgsql server > /var/run/postgresql: could not connect to server: No such file or > directory??Is the server running locally and accepting??connections on Unix > domain socket "/var/run/postgresql/.s.PGSQL.5432"?

Re: 20200108 -- nexthop destinations separated by comma or whitespace

2020-01-29 Thread Ralf Hildebrandt
* Viktor Dukhovni : > > exchange.charite.de > > exchange:s-mx14-ht01.charite.de,exchange:s-mx14-ht02.charite.de > > This looks wrong, it should be : > > exchange.charite.de > exchange:s-mx14-ht01.charite.de,s-mx14-ht02.charite.de > > One "exchange" transport, multiple nexthop hosts.

Re: Postfix can't find Postgserql's unix socket using "peer" method

2020-01-29 Thread Viktor Dukhovni
> On Jan 29, 2020, at 4:32 AM, Jaroslaw Rafa wrote: > > If you have the socket in /var/spool/postfix/postgresql, then you need to > specify path to socket in Postfix configuration taking into account the > chroot jail, ie. not "/var/spool/postfix/postgresql", but just "postgresql". No, that's fr

Re: easy way to forward all root mail to devnull?

2020-01-29 Thread Claus R. Wickinghoff
Hi, Is there easy way to forward all root mail to devnull? In /etc/alias: root: /dev/null (and afterwards on Debian you have to run newaliases. Might be similar on other distros) Groetjes Claus -- Claus R. Wickinghoff, Dipl.-Ing. using Linux since 1994 and still happy... :-)

Re: easy way to forward all root mail to devnull?

2020-01-29 Thread Viktor Dukhovni
> On Jan 29, 2020, at 4:16 AM, Eero Volotinen wrote: > > Is there easy way to forward all root mail to devnull? Assuming it is not unwise: aliases: root: root@discard.invalid virtual: rootroot@discard.invalid r...@example.org

Re: Postfix can't find Postgserql's unix socket using "peer" method

2020-01-29 Thread Jaroslaw Rafa
Dnia 28.01.2020 o godz. 19:53:42 Hamid M. pisze: > Thanks for your reply. I moved the socket folder into Postfix's jail > "/var/spool/postfix/postgresql": > > ls -ld /var/spool/postfix/postgresql > drwxrwsr-x 2 postgres postgres 4096 Jan 29 00:45 postgresql/ > > Postgresql starts correctly and cr

Re: 20200108 -- nexthop destinations separated by comma or whitespace

2020-01-29 Thread Viktor Dukhovni
On Wed, Jan 29, 2020 at 09:56:45AM +0100, Ralf Hildebrandt wrote: > I don't see the change 20200108 reflected in the transport(5) man page. The HISTORY file writeup was: 20200108 UI cleanup: SMTP (and LMTP) client support for a list of nexthop destinations separate

easy way to forward all root mail to devnull?

2020-01-29 Thread Eero Volotinen
Hi List, Is there easy way to forward all root mail to devnull? Eero

20200108 -- nexthop destinations separated by comma or whitespace

2020-01-29 Thread Ralf Hildebrandt
I don't see the change 20200108 reflected in the transport(5) man page. While this isn't a problem per se, I have been using this form for internal routing: exchange.charite.de exchange:s-mx14-ht01.charite.de,exchange:s-mx14-ht02.charite.de to get rid of the pesky internal MX record for excha