Connection timed out due to dns timeouts

Hello, I have list servers that send mails through another relay servers. With this configuration all mail sent from our mail servers are delivered through our relay servers. All servers use postfix (list servers use 2.7.0 and relay 2.5.5) We are having problems with dns lookups to one dom

Re: questions about functions in postfix

Hi Viktor Thanks for all, at now Im with other problema, how to config CA file in postfix using Comodo certificates but is other thread :-) THanks -Mensaje original- De: Viktor Dukhovni Reply-to: postfix-users@postfix.org Para: postfix-users@postfix.org Asunto: Re: questions about funct

Re: Is a late header check possible?

Thu, 07 Feb 2013 10:03:32 -0600 skrev Noel Jones : > On 2/7/2013 8:58 AM, Titanus Eramius wrote: > > I'm running SpamAssassin as a content_filter on incoming mail which > > ads 4 spam-headers, one of them being "X-Spam-Level:". The precise > > header varies, depending on the spamscore. SpamAssassi

Re: Connection timed out due to dns timeouts

Am 08.02.2013 09:29, schrieb Angel L. Mateo: > Hello, > > I have list servers that send mails through another relay servers. > With this configuration all mail sent from our mail servers are > delivered through our relay servers. All servers use postfix (list > servers use 2.7.0 and relay 2.5.

Re: Connection timed out due to dns timeouts

Am 08.02.2013 10:02, schrieb Robert Schetterer: > as workaround you can use a a deditacted transport for that domain > > >> > ups lot of typos, example transport test1-domain.orgsmtp:mail.mx1-domain.org test2-domain.orgsmtp:mail.mx2-domain.org somedomain.comsmtp:[10.0.0.1]:25 s

Re: Connection timed out due to dns timeouts

El 08/02/13 10:02, Robert Schetterer escribió: Am 08.02.2013 09:29, schrieb Angel L. Mateo: Hello, I have list servers that send mails through another relay servers. With this configuration all mail sent from our mail servers are delivered through our relay servers. All servers use postfix

Re: tls for virtual mailbox domains?

Hello, > > is it possible to use multiple certificates for my virtual mail > > domains? > > > > Is it possible to add certificates/tls for the virtual domains? > > Your mail server has one (1) main identity; its own hostname. > > I would advise you to get a certificate for that one hostname, for >

Exceptions to reject_rbl_client *AND* SASL authentication enforcement

Hello list, I'm running a Postfix (2.6.6) server used by my company's customers to submit mail. Source IPs are not known in advance, so normally we grant relay access using SASL authentication. Additionally, we need to prevent as much as possible submissions from unauthorized clients using sto

Re: tls for virtual mailbox domains?

Am 08.02.2013 10:47, schrieb Markus Grunwald: > Hello, > >>> is it possible to use multiple certificates for my virtual mail >>> domains? >>> >>> Is it possible to add certificates/tls for the virtual domains? >> >> Your mail server has one (1) main identity; its own hostname. >> >> I would advi

transport table or relayhost only IPv4?

Hello, I'm using postfix-2.6.6-2.2.el6_1.x86_64. Relevant part from transport table: aa_volmejlt...@volny.cz lmtp1:[m1.volny.internal]:26667 Relevant part of logs: Feb 6 18:08:46 mx1 postfix/smtpd[14553]: AD0CC3006D9: client=host.domain.cz[2a00:1450::XXX::XXX] Feb 6 18:08:46 mx1 pos

Re: Connection timed out due to dns timeouts

Am 08.02.2013 10:42, schrieb Angel L. Mateo: > El 08/02/13 10:02, Robert Schetterer escribió: >> Am 08.02.2013 09:29, schrieb Angel L. Mateo: >>> Hello, >>> >>> I have list servers that send mails through another relay servers. >>> With this configuration all mail sent from our mail servers ar

Re: transport table or relayhost only IPv4?

Am 08.02.2013 11:25, schrieb Marek Matejka: > Hello, > > I'm using postfix-2.6.6-2.2.el6_1.x86_64. > > Relevant part from transport table: > aa_volmejlt...@volny.cz lmtp1:[m1.volny.internal]:26667 > > Relevant part of logs: > Feb 6 18:08:46 mx1 postfix/smtpd[14553]: AD0CC3006D9: > client=h

Re: transport table or relayhost only IPv4?

On Fri, Feb 08, 2013 at 11:25:28AM +0100, Marek Matejka wrote: > I'm using postfix-2.6.6-2.2.el6_1.x86_64. A bit old. > Relevant part from transport table: > aa_volmejlt...@volny.cz lmtp1:[m1.volny.internal]:26667 And where is the relevant config (postconf -n)? > Relevant part of logs: > F

Re: transport table or relayhost only IPv4?

Am 08.02.2013 11:35, schrieb Robert Schetterer: > Relevant part from transport table: >> aa_volmejlt...@volny.cz lmtp1:[m1.volny.internal]:26667 >> also try lmtp1:m1.volny.internal:26667 Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskaner

Re: tls for virtual mailbox domains?

On 2013-02-08 11:04, Reindl Harald wrote: Am 08.02.2013 10:47, schrieb Markus Grunwald: But then the hostname for the virtual domains won't match, won't it? Can I use the certificate for *.the-grue.de for *.virtualdomain.de? jesus christ so tell your customers use 'mail.the-grue.de' as hostn

Re: Connection timed out due to dns timeouts

El 08/02/13 11:27, Robert Schetterer escribió: Am 08.02.2013 10:42, schrieb Angel L. Mateo: El 08/02/13 10:02, Robert Schetterer escribió: Am 08.02.2013 09:29, schrieb Angel L. Mateo: Hello, I have list servers that send mails through another relay servers. With this configuration all m

permit_mx_backup needless when using relay_domains?

hello, ist the option "permit_mx_backup" needless when i use "relay_domains" in my main.cf? my thought is, that another mailserver cant relay mails for an domain that is not listed in "relay_domains". so what is the special of "permit_mx_backkup" ? thanks marko

relayhost problem

Hi, We use the relayhost option to send our mail through the ISP mail server (not really an option to do it in any other way).Works most of the time, but randomly some mails are rejected with the following internal error: Feb 4 14:20:57 www postfix/smtp[6592]: 6CF7EA41F89: to=, relay=smtp.m

Re: relayhost problem

Am 08.02.2013 13:02, schrieb Dominique: > Hi, > > We use the relayhost option to send our mail through the ISP mail server (not > really an option to do it in any > other way).Works most of the time, but randomly some mails are rejected with > the following internal error: > > Feb 4 14:20:57

Re: permit_mx_backup needless when using relay_domains?

we...@zackbummfertig.de: > ist the option "permit_mx_backup" needless when i use "relay_domains" > in my main.cf? > > my thought is, that another mailserver cant relay mails for an domain > that is not listed in "relay_domains". > so what is the special of "permit_mx_backkup" ? relay_domains: YOU

OpenSSL compatible Errors when openssl-1.0.1 installed (maybe for interest for others)

hello, on my gentoo linux mail machine i use openssl 1.0.1 and postfix 2.9.5 in the logs i found: Feb 5 23:06:38 mail postfix/smtpd[25884]: warning: run-time library vs. compile-time header version mismatch: OpenSSL 1.0.1 may not be compatible with OpenSSL 1.0.0 Feb 5 23:06:39 mail postfix

Re: OpenSSL compatible Errors when openssl-1.0.1 installed (maybe for interest for others)

Am 08.02.2013 14:40, schrieb we...@zackbummfertig.de: > on my gentoo linux mail machine i use openssl 1.0.1 and postfix 2.9.5 > > Feb 5 23:06:38 mail postfix/smtpd[25884]: warning: run-time library vs. > compile-time header version mismatch: > OpenSSL 1.0.1 may not be compatible with OpenSSL 1

Re: Exceptions to reject_rbl_client *AND* SASL authentication enforcement

On Fri, Feb 08, 2013 at 10:51:02AM +0100, Fabio Sangiovanni wrote: > Everything works fine, except when one client's IP is blacklisted by > Spamhaus. In this case, we need to whitelist that IP - and that > should be obtainable with the following: > > smtpd_recipient_restrictions = > reject_no

Re: Connection timed out due to dns timeouts

On Fri, Feb 08, 2013 at 09:29:22AM +0100, Angel L. Mateo wrote: > We are having problems with dns lookups to one domain. I know is > not a postfix problem, but a dns configuration error in that domain. > But it is affecting our servers. The easiest work-around is to stop sending mail to the

Trouble configuring backup MX to reject unauth destination

Hi all Please note that the last time I asked about the behavior of Postfix it turned out I had misunderstood the concept of relaying mail. It might be the case again. I'm running the mailserver that serves this domain + a few others, the mailserver at ubuntudanmark.dk and the mailservers at nt-d

Re: Trouble configuring backup MX to reject unauth destination

On Fri, Feb 08, 2013 at 04:06:57PM +0100, Titanus Eramius wrote: > Please note that the last time I asked about the behavior of Postfix it > turned out I had misunderstood the concept of relaying mail. It might > be the case again. > > I'm running the mailserver that serves this domain + a few oth

Re: Exceptions to reject_rbl_client *AND* SASL authentication enforcement

Viktor Dukhovni dukhovni.org> writes: > > Replace "OK" with: > > /etc/postfix/whitelist_client.cidr: > 192.0.2.1/32permit_sasl_authenticated > Awesome. I totally missed this part of documentation: http://www.postfix.org/access.5.html [...] OTHER ACTIONS restriction...

Re: Trouble configuring backup MX to reject unauth destination

Fri, 8 Feb 2013 09:45:07 -0600 skrev /dev/rob0 : snip > > --- > > titanus@ntdata:/var/log$ grep "048341743609" mail.log.1 > > > > Feb 7 22:12:48 ntdata postfix/pickup[24843]: 048341743609: uid=5005 > > from= > > pickup(8) picks up mail which was sent via sendmail(1). This is a > local/system u

Re: Exceptions to reject_rbl_client *AND* SASL authentication enforcement

On 2/8/2013 3:51 AM, Fabio Sangiovanni wrote: > Hello list, > > I'm running a Postfix (2.6.6) server used by my company's customers > to submit mail. > Source IPs are not known in advance, so normally we grant relay > access using SASL authentication. > Additionally, we need to prevent as much as

problem with certificate server

Hi list At now Im configuring the TLS function in my postfix 2.5.5 and Im having a new problem. First was that said untrusted issuer because not detect the certificates. At now the message every time you sends is status=deferred (Server certificate not verified) I was configuring using a howto

error using certificate server

Hi list At now Im configuring the TLS function in my postfix 2.5.5 and Im having a new problem. First was that said untrusted issuer because not detect the certificates. At now the message every time you sends is status=deferred (Server certificate not verified) I was configuring using a h

problem with certificate server

Hi list At now Im configuring the TLS function in my postfix 2.5.5 and Im having a new problem. First was that said untrusted issuer because not detect the certificates. At now the message every time you sends is status=deferred (Server certificate not verified) I was configuring using a howto

Re: error using certificate server

Am 08.02.2013 20:07, schrieb deco...@riseup.net: > At now Im configuring the TLS function in my postfix 2.5.5 and Im having a > new problem. > First was that said untrusted issuer because not detect the certificates. how often and with hom many subjects yiu will start the thread again? > Pleas

Re: error using certificate server

Hi Apologies for triplicate the mailing, my mail client blocks and send for and error two times the mail. The third was using webmail. If i use smtp_tls_security_level=may the smarthost not will accept mails because needs to use autentication using TLS inside relay_passwd In main.cf I not con

Re: error using certificate server

Am 08.02.2013 20:22, schrieb deconya: > Hi > > Apologies for triplicate the mailing, my mail client blocks and send for and > error two times the mail. The third > was using webmail. > > If i use smtp_tls_security_level=may the smarthost not will accept mails > because needs to use autenticat

Unable to send via port 587

FreeBSD-8.3 STABLE I just updated to Postfix (2.10-20130113). Prior to this update, everything was apparently working fine. I am now getting this error message in the maillog when I attempt to send via port 587: warning: TLS library problem: 7161:error:1408F119:SSL routines:SSL3_GET_RECORD:decr

Re: Unable to send via port 587

Am 08.02.2013 20:35, schrieb Jerry: > FreeBSD-8.3 STABLE > > I just updated to Postfix (2.10-20130113). Prior to this update, > everything was apparently working fine. > > I am now getting this error message in the maillog when I attempt to > send via port 587: > > warning: TLS library problem

Re: Unable to send via port 587

On Fri, 08 Feb 2013 20:38:45 +0100 Reindl Harald articulated: > and you did rebuild postfix against the new openssl? > this would be the first i do if i see such messages > > especially if i use snapshots (2.10-20130113) Yes I did. In fact, I also rebuilt the MUA and then rebooted the system. Ac

Re: Unable to send via port 587

--On Friday, February 08, 2013 2:35 PM -0500 Jerry wrote: There was also a minor update of the OpenSSL port from ver. 1.0.1c to 1.0.1d As noted numerous times on the openssl-dev list, OpenSSL 1.0.1d is broken. You need to grab

Re: error using certificate server

Hi -Mensaje original- De: Reindl Harald Para: postfix-users@postfix.org Asunto: Re: error using certificate server Fecha: Fri, 08 Feb 2013 20:34:47 +0100 Am 08.02.2013 20:22, schrieb deconya: > Hi > > Apologies for triplicate the mailing, my mail client blocks and send for and > erro

Re: Trouble configuring backup MX to reject unauth destination

On 02/08/2013 06:02 PM, Titanus Eramius wrote: Feb 7 22:12:48 ntdata postfix/pickup[24843]: 048341743609: uid=5005 from= So you are...not re-injecting spamassassin traffic, but instead re-submitting it via sendmail ? That's weird. Feb 7 22:12:48 ntdata postfix/pipe[30177]: 39E441743607:

Re: Unable to send via port 587

On Fri, 08 Feb 2013 11:57:18 -0800 Quanah Gibson-Mount articulated: > As noted numerous times on the openssl-dev list, OpenSSL 1.0.1d is > broken. You need to grab > > and apply it to the 1.0.1d source to fix it. Yes, that is