Re: Recipient Verification

THanks so much for that tip. It works now. I moved it to above permit_mynetworks and I can now see the db file. Thanks again. On Fri, Nov 27, 2020 at 11:29 AM Wietse Venema wrote: > > Software Info: > > Oh my apologies, I didn't realize. I ran that and got the same data >

Re: Recipient Verification

Oh my apologies, I didn't realize. I ran that and got the same data directory which is /var/db/postfix. Stumped as to why I am not seeing the verify_cache.db file. Shouldn't I be? On Thu, Nov 26, 2020 at 6:14 PM Wietse Venema wrote: > > 1) Please don't send HTML-only messages to a mailing list. >

Re: Unverified Recipients

me > > assistance. Thanks in advance. > > > > Regards > > > > Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for > > Windows 10 > > > > *From: *Software Info <mailto:softwareinfo...@gmail.com> > > *Sent: *Monday, D

Unverified Recipients

Hi All I am trying to set up Unverified Recipients on Postfix postfix-3.4.8,1 on FreeBSD. I configured a cache file for the unverified addresses. I reloaded postfix but I am not seeing any file in the location I specified in the address_verify_map parameter. I cannot seem to figure out why. Please

Timeout while connecting to postfix via php socket

Good morning all. I'm facing with a strange problem with PHP sockets and POSTFIX: 1) I have a Postfix machine that runs very well for sending/receiving emails to/from outside (via Outlook) 2) I'm working on a CRM software that connect to this Postfix via PHP socket_connect function. We

R: Identifing bounce messages whene queue lifetime is expired

Thank you Mr. Venema. I will "study" the bounce man page for customizing the message. Last question: is it possibile to send bounce messages derived from maxlife-in-queue-expiration to something like /dev/null :-) and not treating them as normal bounces? -Francesco -Messaggio originale- Da

Identifing bounce messages whene queue lifetime is expired

Hi all. I usually receive DSN messages from my postfix in the format as below. They are sent to a script for regex analysis. My question: is there a way to customize these "undelivered mail" messages when thay come from emails not delivered because max lifetime in the queue is expired? It seems lik

R: R: Un-hold only some messages and not all the queue

I'm not a wizard with grep+sed+awk :-) Thank you a lot for your precious advice. -F -Messaggio originale- Da: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org] Per conto di Wietse Venema Inviato: giovedì 9 giugno 2016 17:19 A: Postfix users Oggetto: Re: R: Un-hold

R: Un-hold only some messages and not all the queue

Thank you a lot Mr. Venema!!! Et voilà my little script for un-holding just n (n=100 in the example) and moving to deferred: postqueue -p | pcregrep -M "[0-9A-Z]{10}" | awk '{print $1;}' | sed 's/.$//' | head -100 | postsuper -H - Thank you again. -Francesco -Messaggio originale- Da: ow

Un-hold only some messages and not all the queue

Hi all. I have some messages in HOLD queue. Usually I use "postsuper" for moving messages from DEFERRED to HOLD and viceversa. Is there a way to move to deferred ONLY some (for example 100 of 1000) of the messages in HOLD ? Thank you -Francesco --- Questa e-mail è stata controllata per indi

R: R: Keep messages in deferred and retry after 4 hours

Mr. Venema, thank you again!! -Francesco -Messaggio originale- Da: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org] Per conto di Wietse Venema Inviato: martedì 7 giugno 2016 16:19 A: Postfix users Oggetto: Re: R: Keep messages in deferred and retry after 4 hours i

R: Keep messages in deferred and retry after 4 hours

Thanks a lot Wietse. But... is it possible to limit this backoff-time to specific destinations (i.e. yahoo.com or hotmail.com) and not to all messages sent through a postfix instance? -Francesco -Messaggio originale- Da: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.

Keep messages in deferred and retry after 4 hours

Hi all. I have the following settings in my Postfix main.cf. All is ok for destinations where I need to send a limited number of messages in a specific time: transport_maps = hash:/etc/postfix/transport veryslow_destination_rate_delay = 3s slow_destination_rate_delay = 1s Every message is

R: Starting postfix at boot time on Centos 7

Thank you all. I preferred to use the “/etc/rc.d/init.d/postfix start script” from my old Centos 6 and installed on C7 with a simple chkconfig. Many thanks again. -Francesco Da: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org] Per conto di Wolfe, Robert Inviato: me

Starting postfix at boot time on Centos 7

Hi all. I compiled postfix 3.0.3 from source code but (maybe a stupid question). don't know how to start it at boot of a Centos 7 machine! Tried with "chkconfig" and "systemctl" without any results! How can I do this? Is there a "postfix.service" to be enabled with systemctl? Thank you very muc

How to block annoying/dangerous smtpd connections?

Good morning all! My Postfix is logging a lot fo these: -- BEGIN LOG Apr 20 10:50:35 dante postfix/smtpd[29806]: warning: hostname totaldrama.eu does not resolve to address 94.102.53.179: Name or service not known Apr 20 10:50:35 dante postfix/smtpd[29806]: connect fr

OpenDkim signs incoming emails ???

Hi all. I've a strange behaviour of my Postfix server: it seems to sign all incoming emails! Here below a snippet from the log, where: pi...@externaldomain.it => sender email address pl...@internaldomain.it => recipient on my

R: R: SASL support is not compiled in

Thank you so much! I SOLVED with this command (that includes TLS e PCRE support): # make -f Makefile.init makefiles "CCARGS=-DUSE_SASL_AUTH -DUSE_TLS -DHAS_PCRE `pcre-config --cflags`" "AUXLIBS=-lssl -lcrypto -lz -lm" "AUXLIBS_PCRE=`pcre-config --libs`" # However, I still have a problem w

R: SASL support is not compiled in

Many thanks Dr. Venema. I just compiled with -DUSE_SASL_AUTH flag using these command: ###> make -f Makefile.init makefiles "CCARGS=-DUSE_SASL_AUTH -DHAS_PCRE `pcre-config --cflags`" "AUXLIBS_PCRE=`pcre-config --libs`" But compilation exit with: ### [src/smtpd] gcc -I. -I../../includ

R: SASL support is not compiled in

Thank you. Here http://www.postfix.org/SASL_README.html#server_which I read: "By default the Postfix SMTP server uses the Cyrus SASL implementation. If the Dovecot SASL implementation should be used, specify an smtpd_sasl_type value of dovecot instead of cyrus: /etc/postfix/main.cf:

SASL support is not compiled in

Hi all. I've recompiled a fresh version of Postfix 3. No problem with PCRE support (I read the specific readme!). The compilation was ok and Postfix is up and running with PCRE. Now I'm trying to add Dovecot SASL support, but postfix reply with: "warning: smtpd_sasl_auth_enable is true, but SASL

R: I: R: R: R: Strange behaviour of my multi-instance server

Mr. Venema & Mr. Dukhovni, thank you! -Messaggio originale- Da: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org] Per conto di Wietse Venema Inviato: martedì 31 marzo 2015 13:09 A: Postfix users Oggetto: Re: I: R: R: R: Strange behaviour of my multi-instance server

I: R: R: R: Strange behaviour of my multi-instance server

Dear Mr. Dukhovni, I'm sorry for re-posting my last message, but I'd like to know your answer regarding my last question: ### How many instances can I set up on the same machine without deteriorating perfomances? ### What's your advice? Thank you a lot -Francesco -Messaggio originale- Da

R: R: R: R: Strange behaviour of my multi-instance server

So, you suggest to: 1) use many singleIP-instances with specific smtp/slow/veryslow/etc. transports (all bound on the same IP) 2) not use a randomizer script in the master.cf BUT randomizing the outbound address through web application (that is a PHP script) Is it correct? But here I have a furthe

R: R: R: Strange behaviour of my multi-instance server

Dear Mr. Dukhovni, you're right, I'm not a great expert of Postfix but I'm here to learn! In fact, you're last answer is the solution of my problem: > Sure looks like you don't understand that each instance of an > smtp(8) transport needs all the relevant settings specified. > There's no "inherita

R: R: Strange behaviour of my multi-instance server

Thanks Dr. Venema. I'll try these settings (in particular for relay client in master.cf of each instance). However, here below a snippet of an email sent to yahoo where the problem is more evident: [...] X-Originating-IP: [xxx.xxx.xxx.79] Received: from 127.0.0.1 (EHLO mx4.DOMAIN1.it) (xxx.xxx.x

R: Strange behaviour of my multi-instance server

Thanks a lot, Mr. Venema. As you can see, I have a bind address in master.cf with: -o smtp_bind_address=xxx.yyy.zzz.79 Is it OK or "smtp_bind_address" in main.cf is different? Regarding "inet_interfaces" I usually have something like this (in every instance main.cf file, changing

Strange behaviour of my multi-instance server

Hello. I'm facing with a strange behaviour of my Postfix multi-instance server and I'll try. to explain. Every instance manages outbound emails from a specific IP. This is an example master.cf: -- /etc/postfix/master.cf (instance 1)-- smtp u

R: R: Sender transport settings not override default transport

Many thanks Mr. Venema. I just tried a "multi instance" solution and it works very well. The problem is when the number of IPs become very large: what if 20 IPs => 20 Postfix instances? I believe that this way is resource-consuming and can't be scalable as I'd like. I also tried to use sender_dep

R: Sender transport settings not override default transport

Good morning. Maybe I wasn't able to write a clear request :-( I'll try another way. I've a set of IPs. I need to authenticate against each of them (useing different accounts on the same domain: us...@domain.com , us...@domain.com , ) and want that emails are to be sent through the same IP. For

Sender transport settings not override default transport

Hi all, I'm facing with a strange problem with my Postfix machine. I have some different IP addresses and dovecot as po3-before-smtp authentication system. I can login to postfix using userna...@mydomain.com + password and send emails using default smtp transport (these emails are sent through the