[pfx] Re: private/dovecot-lmtp]: Connection refused)

On 2024/5/11 22:51, Jason Hirsh via Postfix-users wrote: My nonrandom action for tho morning OK I bandaided my going back to an older main.cf but updating the ssl/tls infoThat brought mail back on line Sort of Dovecot still not happy with me but this error seems more warning and best su

[pfx] Re: private/dovecot-lmtp]: Connection refused)

Jason Hirsh via Postfix-users skrev den 2024-05-11 16:51: status=sent (delivered via dovecot service (lda(ja...@theoceanwindow.com): Error: net_connect_unix(/var/run/dovecot/stats-writer) failed: Permis)) grep -r stats /etc/dovecot/ i get an helpfull url from it /etc/dovecot/conf.d/10-metri

[pfx] Re: private/dovecot-lmtp]: Connection refused)

My nonrandom action for tho morning OK I bandaided my going back to an older main.cf but updating the ssl/tls infoThat brought mail back on line Sort of Dovecot still not happy with me but this error seems more warning and best suited to be addressed else where status=sent (delivered via d

[pfx] Re: private/dovecot-lmtp]: Connection refused)

On Sat, May 11, 2024 at 11:11:30AM +0200, Benny Pedersen via Postfix-users wrote: > > I am running Postfix/Dovecot/MySQL mail server. It was doing ok > > until I tried to improve it., I > > maybe just reboot ? :) Unlikely to help. Just restarting dovecot would be about the most that's needed

[pfx] Re: private/dovecot-lmtp]: Connection refused)

Jason Hirsh via Postfix-users skrev den 2024-05-11 02:47: I am running Postfix/Dovecot/MySQL mail server. It was doing ok until I tried to improve it., I maybe just reboot ? :) dsn=4.4.1, status=deferred (connect to triggerfish.theoceanwindow.com [1][private/dovecot-lmtp]: Connection

[pfx] Re: private/dovecot-lmtp]: Connection refused)

0:11:27 triggerfish postfix/lmtp[47754]: 172816542AC3: > to=, orig_to=, relay=none, delay=38307, > delays=38307/0.01/0/0, dsn=4.4.1, status=deferred (connect to > triggerfish.theoceanwindow.com[private/dovecot-lmtp]: Connection refused) The Dovecot LMTP delivery agent is not listening on

[pfx] private/dovecot-lmtp]: Connection refused)

I am running Postfix/Dovecot/MySQL mail server. It was doing ok until I tried to improve it., I dsn=4.4.1, status=deferred (connect to triggerfish.theoceanwindow.com[private/dovecot-lmtp]: Connection refused) May 10 20:11:27 triggerfish postfix/lmtp[47754]: 172816542AC3: to=, orig_to=, relay

Re: Appricate some help in understanding a connection refused situation.

On Wed, January 19, 2022 14:45, Wietse Venema wrote: > > "Connection refused" means that the TCP SYN request from your system > got a TCP RST response. This response could be for a variety of > reasons. One is that the host accepted no TCP connections on port > 25, but

Re: Appricate some help in understanding a connection refused situation.

for that matter. > > However that may be, google's dns records are outside my span of control. I > still do not understand why a DSN delay message cannot be sent back to the > origin. Has google configured their mail servers to prevent this? Are the > bounces supposed to be sen

Re: Appricate some help in understanding a connection refused situation.

On Wed, January 19, 2022 13:29, Wietse Venema wrote: > James B. Byrne: > > > For me, alt4.gmail-smtp-in.l.google.com does not resolve to > 66.102.1.27, but instead to 142.250.153.26 (and some IPv6). > > Wietse > Repeated dns lookups of alt4.gmail-smtp-in.l.google.com return a different ip

Re: Appricate some help in understanding a connection refused situation.

On Wed, Jan 19, 2022 at 01:13:56PM -0500, James B. Byrne wrote: > Jan 19 12:49:29 mx31 postfix/smtp[81175]: 14FDA745F9: > to=, relay=none, delay=2877, > delays=2877/0.02/0.13/0, dsn=4.4.1, status=deferred (connect to > alt4.gmail-smtp-in.l.google.com[66.102.1.27]:25: Connection re

Re: Appricate some help in understanding a connection refused situation.

test service could > be made. In consequence several messages resulted in a delayed > delivery notice. > > It is these messages for which I am seeing SMTP connection refused > from the original sending hosts. > > The diagnostic information that I have respecting a representativ

Appricate some help in understanding a connection refused situation.

messages resulted in a delayed delivery notice. It is these messages for which I am seeing SMTP connection refused from the original sending hosts. The diagnostic information that I have respecting a representative message is reproduced below. I just need to know if this is caused by something I can

Re: SpamC - connection refused

08:38:33PM +0200, Maurizio Caloro wrote: > >> Sep 28 15:11:22 nmail spamd[3826]: prefork: child states: II > > The "spamd" server appears to be running... > >> Sep 28 15:11:23 nmail spamc[4525]: connect to spamd on 127.0.0.1 failed, >> retrying (#1 of 3

Re: SpamC - connection refused

Sep 28 15:11:23 nmail spamc[4525]: connect to spamd on 127.0.0.1 failed, retrying (#1 of 3): Connection refused Sep 28 15:11:23 nmail spamc[4525]: connect to spamd on 127.0.0.1 failed, retrying (#2 of 3): Connection refused Sep 28 15:11:24 nmail spamc[4525]: connect to spamd on 127.0.0.1 failed

Re: SpamC - connection refused

On Tue, Sep 28, 2021 at 08:38:33PM +0200, Maurizio Caloro wrote: > Sep 28 15:11:22 nmail spamd[3826]: prefork: child states: II The "spamd" server appears to be running... > Sep 28 15:11:23 nmail spamc[4525]: connect to spamd on 127.0.0.1 failed, > retrying (#1 of 3): Conne

Re: SpamC - connection refused

Connection refused speaks to the socket not running. What does netstat -na report? -Dan > On Sep 28, 2021, at 11:38 AM, Maurizio Caloro wrote: > > Sending to spamassassin group, and no answer will by appair, possible this > are outdated? > Please how I can fix this con

SpamC - connection refused

Sending to spamassassin group, and no answer will by appair, possible this are outdated? Please how I can fix this connection refused, disabling IPv6 also not help. Sep 28 15:11:22 nmail spamd[3826]: prefork: child states: II Sep 28 15:11:23 nmail spamc[4525]: connect to spamd on

Re: Gateway to Internal Server random "Connection refused"

Nikolaos Milas: > A next move could be closer examination of dropped packets by our > firewall. I found this article for a start: > > https://networklessons.com/cisco/asa-firewall/cisco-asa-packet-drop-troubleshooting > I mentioned this, emphasis added: > This is a TCP-level problem. The remo

Re: Gateway to Internal Server random "Connection refused"

On 13/1/2021 4:41 μ.μ., Wietse Venema wrote: This is a TCP-level problem. The remote server's TCP/IP stack, or some middle box, is refusing connections at the TCP level. Thanks Wietse, We'll be checking this out. Although I have done some connectivity testing with repeated netcat (nc) polli

Re: Gateway to Internal Server random "Connection refused"

Nikolaos Milas: > connect to vmail2.noa.xxx[2001:648:2011:15::xxx]:25: Connection refused; This is a TCP-level problem. The remote server's TCP/IP stack, or some middle box, is refusing connections at the TCP level. All Postfix can do is make fewer connections. To reduce co

Gateway to Internal Server random "Connection refused"

]: 450 4.1.1 : Recipient address rejected: unverified address: connect to vmail2.noa.xxx[2001:648:2011:15::xxx]:25: Connection refused; from= to= proto=ESMTP helo= Jan 12 15:54:24 mailgw1 postfix/smtpd[2540]: disconnect from mailserver.comune.avellino.xxx[2.228.155.xxx] ehlo=2 starttls=1 mail=1

Re: Connection refused / telnet: connect to address 10.5.2.1: Connection refused

> On 29 Dec 2020, at 12:58, Wolfgang Paul Rauchholz > wrote: > > The server is listening on port 25, 587 and 465 > netstat -plutn | grep 25 and 587 > tcp0 0 127.0.0.1:250.0.0.0:* LISTEN > 28704/master > tcp0 0 127.0.0.1:587 0

Re: Connection refused / telnet: connect to address 10.5.2.1: Connection refused

ge: Could not connect to server > localhost. The connection was refused. > Testing with telnet from CLI I get > (1) telnet home smtp > Trying 10.5.2.1... > telnet: connect to address 10.5.2.1 <http://10.5.2.1>: Connection refused > (2) telnet home imap > Trying 10.5.2

Connection refused / telnet: connect to address 10.5.2.1: Connection refused

telnet from CLI I get (1) telnet home smtp Trying 10.5.2.1... telnet: connect to address 10.5.2.1: Connection refused (2) telnet home imap Trying 10.5.2.1... Connected to home. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS

Re: 'connection refused' for the "double-bounce" address, but mail's delivered?

On 4/19/2016 6:49 PM, jaso...@mail-central.com wrote: >> Now to wait for something to trigger one of those double-bounce messages. > > Ugh. Still undeliverable. > > Well, I actually GET the email. Something 'internal' seems to be > undeliverable. > > Now 'mail for example.com loops back to my

Re: 'connection refused' for the "double-bounce" address, but mail's delivered?

> Now to wait for something to trigger one of those double-bounce messages. Ugh. Still undeliverable. Well, I actually GET the email. Something 'internal' seems to be undeliverable. Now 'mail for example.com loops back to myself' (not sure what I've done to myself NOW. Grumble.) Apr

Re: 'connection refused' for the "double-bounce" address, but mail's delivered?

Sry, talking to myself a bunch :-/ I changed main.cf - address_verify_transport_maps = static:vpn:[back.mail01.example.com]:25 + address_verify_transport_maps = master.cf [mail01.example.com]:25 inet n - n - 1 postscreen

Re: 'connection refused' for the "double-bounce" address, but mail's delivered?

I keep staring at this Apr 19 14:48:31 mail01 postfix/vpn/smtp[21044]: connect to back.mail01.example.com[10.1.1.16]:25: Connection refused Apr 19 14:48:31 mail01 postfix/vpn/smtp[21044]: 3qqJYC3wYbz31Vm: to=, relay=none, delay=0.1, delays=0/0.01/0.09/0, dsn=4.4.1, status

Re: 'connection refused' for the "double-bounce" address, but mail's delivered?

> The "connection refused" is the part that needs to be fixed. VPN (temporarily?) down? firewall issue? "wrong" destination? something else? Starting with those^ to narrow down, looking backwards through my logs - for cases of 'double-bounce' & 'conn

Re: 'connection refused' for the "double-bounce" address, but mail's delivered?

over VPN to the backend > > At the moment, mail's getting both received OK from the net, and sent to it, > over the VPN. > > In my logs I see a 'connection refused' from the backend, even though mail's > getting delivered. > > My goal is to learn how

'connection refused' for the "double-bounce" address, but mail's delivered?

nd sent to it, over the VPN. In my logs I see a 'connection refused' from the backend, even though mail's getting delivered. My goal is to learn how to read & understand this particular log snip. Of course well enough to finally to find/fix the problem. I *think* it'

Re: 3x lost connection while performing the EHLO handshake -> Connection refused -> clear text delivery ok -> automated reply ESMTPS ok

00:22:22 postfix/smtp[23811]: SSL_connect error to >> cluster3vk.eu.messagelabs.com[85.158.139.3]:25: -1 >> 18 00:22:22 postfix/smtp[23811]: warning: TLS library problem: >> error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version >> number:s3_pkt.c:338: > > This re

Re: 3x lost connection while performing the EHLO handshake -> Connection refused -> clear text delivery ok -> automated reply ESMTPS ok

:22 postfix/smtp[23811]: 7C07C800084: to=<>, relay=none, > delay=54, delays=6.6/0.03/47/0, dsn=4.4.1, status=deferred (connect to > cluster3vk.eu.messagelabs.com[85.158.139.3]:25: Connection refused) They definitely have connection rate limiters in place. Nothing

3x lost connection while performing the EHLO handshake -> Connection refused -> clear text delivery ok -> automated reply ESMTPS ok

m&85.158.139.3&&D2903596AFC817BDF98DA58A8B9D0D2D81DF2FB786103A3AD6AF5E00A4A0CF61 from client cache 18 00:22:22 postfix/smtp[23811]: 7C07C800084: Cannot start TLS: handshake failure 18 00:22:22 postfix/smtp[23811]: connect to cluster3vk.eu.messagelabs.com[85.158.139.3]:25: Connection r

Re: Connection refused to local stunnel tunnel

Am 20.10.2013 20:33, schrieb Wietse Venema: > Olaf Marzocchi: >> postfix/smtp[2103]: [ID 947731 mail.warning] warning: relayhost >> configuration problem >> postfix/smtp[2103]: [ID 197553 mail.info] 311482A92D: >> to=, orig_to=, relay=none, delay=157834, >> delays=157833/0.01/0.08/0, dsn=4.3.5

Re: Connection refused to local stunnel tunnel

Olaf Marzocchi: > postfix/smtp[2103]: [ID 947731 mail.warning] warning: relayhost configuration > problem > postfix/smtp[2103]: [ID 197553 mail.info] 311482A92D: > to=, orig_to=, relay=none, delay=157834, > delays=157833/0.01/0.08/0, dsn=4.3.5, status=deferred (Host or domain name > not found.

Re: Connection refused to local stunnel tunnel

to mail31.ha.ovh.net Connection to localhost closed by foreign host. but… surprise! Now I tried this: $ telnet 127.0.0.1 11125 Trying 127.0.0.1... telnet: Unable to connect to remote host: Connection refused I checked stunnel.conf and I replaced "accept = localhost:11125" with "accep

Re: Connection refused to local stunnel tunnel

mailing list because postfix is an > extra package not part of the base OmniOS distro. If you tell me > everything seems ok, I will ask them. > > The error I get from postfix is the following, taken from the > output of "mailq": > (connect to 127.0.0.1[127.0.0.1]:1

Re: Connection refused to local stunnel tunnel

rror I get from postfix is the following, taken from the > output of "mailq": > (connect to 127.0.0.1[127.0.0.1]:11125: Connection refused) On the machine that runs Postfix, nothing is listening on 127.0.0.1 TCP port 11125. > Well, I tried "telnet 127.0.0.1 465" from a SSH promp

Re: Connection refused to local stunnel tunnel

Am 20.10.2013 01:34, schrieb Olaf Marzocchi: > If I use ssl0.ovh.net:25, I get a timeout. If I use port 587, I get "(TLS is > required, but was not offered by host ssl0.ovh.net[213.186.33.20])", so I > opted for SMTPS. > However, Postfix cannot do SMTPS on port 465, so I installed stunnel and I

Connection refused to local stunnel tunnel

The error I get from postfix is the following, taken from the output of "mailq": (connect to 127.0.0.1[127.0.0.1]:11125: Connection refused) Well, I tried "telnet 127.0.0.1 465" from a SSH prompt and I was able to connect to the remote mail server, so stunnel is working and listen

Re: SASL:Connect to private/auth failed: Connection refused -- throttling

On 08/08/2013 05:10 PM, v.dimit...@synergetic.ag wrote: Hi List. Is there a way to ensure that submission listener will not accept connections when dovecot is not running? Dovecot is pretty much as stable as postfix itself. The real question, therefore, is: why is dovecot not running ? For

Re: SASL:Connect to private/auth failed: Connection refused -- throttling

v.dimit...@synergetic.ag: > Hi List. > > Is there a way to ensure that submission listener will not accept > connections when dovecot is not running? No. There are alomst a bazilln possible errors that Postfix may run into, and there is no feature to detect them before handling an SMTP connectio

SASL:Connect to private/auth failed: Connection refused -- throttling

goal I want to achieve is to be able to benefit from load-balancer in such case. I appreciate any advise helping me to achieve this. postfix/smtpd[18998]: connect from client postfix/smtpd[18998]: warning: SASL: Connect to private/auth failed: Connection refused postfix/smtpd[18998]: fatal: no

Connection refused; status=deferred

ostfix/qmgr[6784]: B92B518431A: from=, size=438, nrcpt=1 (queue active) Aug 28 04:41:23 dur postfix/smtp[6792]: connect to dur.bounceme.net[70.71.113.158]:25: Connection refused Aug 28 04:41:23 dur postfix/smtp[6792]: B92B518431A: to=, relay=none, delay=62, delays=60/0.02/1.6/0, dsn=4.4.1, stat

Re: warning: psc_dnsbl_request: connect to private/dnsblog service: Connection refused

Sahil Tandon: > Just following up to close this discussion. > > On Sun, 2012-05-06 at 09:35:24 -0400, Wietse Venema wrote: > > > Sahil Tandon: > > > May 5 10:00:26 mx1 postfix/postscreen[38500]: warning: > > > psc_dnsbl_request: connect to private

Re: warning: psc_dnsbl_request: connect to private/dnsblog service: Connection refused

Just following up to close this discussion. On Sun, 2012-05-06 at 09:35:24 -0400, Wietse Venema wrote: > Sahil Tandon: > > May 5 10:00:26 mx1 postfix/postscreen[38500]: warning: psc_dnsbl_request: > > connect to private/dnsblog service: Connection refused > > May 5 10:0

Re: warning: psc_dnsbl_request: connect to private/dnsblog service: Connection refused

On Sun, 6 May 2012 03:39:19 -0400 Sahil Tandon articulated: >I could not find references to this issue in the archives, and I know >others manage much higher-volume sites, so I suspect it just indicates >a severely borked system (FreeBSD 8.3) on my side. Ever since updating to FreeBSD-8.3 STABLE,

Re: warning: psc_dnsbl_request: connect to private/dnsblog service: Connection refused

Sahil Tandon: > May 5 10:00:26 mx1 postfix/postscreen[38500]: warning: psc_dnsbl_request: > connect to private/dnsblog service: Connection refused > May 5 10:00:26 mx1 last message repeated 8 times When does FreeBSD report ECONNREFUSED on an open socket? I thought it would do that

Re: warning: psc_dnsbl_request: connect to private/dnsblog service: Connection refused

results are available > for this client. > > May 5 10:00:26 mx1 postfix/postscreen[38500]: CONNECT from > [83.59.10.37]:12954 to [69.147.83.52]:25 > May 5 10:00:26 mx1 postfix/postscreen[38500]: warning: psc_dnsbl_request: > connect to private/dnsblog service: Connection refu

warning: psc_dnsbl_request: connect to private/dnsblog service: Connection refused

/postscreen[38500]: CONNECT from [83.59.10.37]:12954 to [69.147.83.52]:25 May 5 10:00:26 mx1 postfix/postscreen[38500]: warning: psc_dnsbl_request: connect to private/dnsblog service: Connection refused May 5 10:00:26 mx1 last message repeated 8 times ... May 5 10:00:32 mx1 postfix

Re: 421 service not available (connection refused, too many connections): ALL servers

On 3/5/2012 1:44 PM, Stanisław Findeisen wrote: > My bad suspicion is that they are in the process of installing some > (more or less crappy) mail intercepting facility (i.e. to spy on users) > and that this is probably the government who ordered that. This is > Europe (Poland) but do you think su

Re: 421 service not available (connection refused, too many connections): ALL servers

On Mon, 05 Mar 2012 20:44:57 +0100 Stanisław Findeisen articulated: > My bad suspicion is that they are in the process of installing some > (more or less crappy) mail intercepting facility (i.e. to spy on > users) and that this is probably the government who ordered that. > This is Europe (Poland)

Re: 421 service not available (connection refused, too many connections): ALL servers

2012/3/5 Stanisław Findeisen : > My bad suspicion is that they are in the process of installing some > (more or less crappy) mail intercepting facility (i.e. to spy on users) > and that this is probably the government who ordered that. This is > Europe (Poland) but do you think such things are unc

Re: 421 service not available (connection refused, too many connections): ALL servers

hael Tokarev wrote: >>>>> On 04.03.2012 13:30, Stanisław Findeisen wrote: >>>>>> On 2012-03-04 09:20, Stanisław Findeisen wrote: >>>>>>> I am running a small Postfix server, and for a couple of >>>>>>> hours I

Re: 421 service not available (connection refused, too many connections): ALL servers

On Monday, March 5, 2012, 12:06:09, Wietse Venema wrote: > Rod Dorman: >> On Monday, March 5, 2012, 09:53:31, /dev/rob0 wrote: >> > ... >> > Another WAG: maybe your ISP's upstream provider got tired of >> > complaints and implemented this redirection upstream. This would >> > explain why the ISP

Re: 421 service not available (connection refused, too many connections): ALL servers

On Mon, Mar 05, 2012 at 11:06:26AM -0600, I wrote: > On Mon, Mar 05, 2012 at 11:21:30AM -0500, Rod Dorman wrote: > > On Monday, March 5, 2012, 09:53:31, /dev/rob0 wrote: > > > ... > > > Another WAG: maybe your ISP's upstream provider got tired of > > > complaints and implemented this redirection u

Re: 421 service not available (connection refused, too many connections): ALL servers

On Mon, Mar 05, 2012 at 11:21:30AM -0500, Rod Dorman wrote: > On Monday, March 5, 2012, 09:53:31, /dev/rob0 wrote: > > ... > > Another WAG: maybe your ISP's upstream provider got tired of > > complaints and implemented this redirection upstream. This would > > explain why the ISP would not know.

Re: 421 service not available (connection refused, too many connections): ALL servers

Rod Dorman: > On Monday, March 5, 2012, 09:53:31, /dev/rob0 wrote: > > ... > > Another WAG: maybe your ISP's upstream provider got tired of > > complaints and implemented this redirection upstream. This would > > explain why the ISP would not know. > > I would be horrified is this turned out to

Re: 421 service not available (connection refused, too many connections): ALL servers

On Monday, March 5, 2012, 09:53:31, /dev/rob0 wrote: > ... > Another WAG: maybe your ISP's upstream provider got tired of > complaints and implemented this redirection upstream. This would > explain why the ISP would not know. I would be horrified is this turned out to be the cause. Without dee

Re: 421 service not available (connection refused, too many connections): ALL servers

012 13:30, Stanisław Findeisen wrote: > >>>> On 2012-03-04 09:20, Stanisław Findeisen wrote: > >>>>> I am running a small Postfix server, and for a couple of > >>>>> hours I've been getting: "host ... refused to talk to me: > >>>>

Re: 421 service not available (connection refused, too many connections): ALL servers

>>>> I am running a small Postfix server, and for a couple of hours >>>>> I've been getting: "host ... refused to talk to me: 421 service >>>>> not available (connection refused, too many connections)" for >>>>> all the outgoin

Re: 421 service not available (connection refused, too many connections): ALL servers

ll Postfix server, and for a couple of hours I've been >>>> getting: "host ... refused to talk to me: 421 service not available >>>> (connection refused, too many connections)" for all the outgoing mail, >>>> all destination servers. >>>> >

Re: 421 service not available (connection refused, too many connections): ALL servers

ver, and for a couple of hours > >>> I've been getting: "host ... refused to talk to me: 421 service > >>> not available (connection refused, too many connections)" for > >>> all the outgoing mail, all destination servers. > >>> > >>

Re: 421 service not available (connection refused, too many connections): ALL servers

: "host ... refused to talk to me: 421 service not available >>> (connection refused, too many connections)" for all the outgoing mail, >>> all destination servers. >>> >>> What's wrong? >>> >>> I wasn't even able to subscribe to

Re: 421 service not available (connection refused, too many connections): ALL servers

On 04.03.2012 13:30, Stanisław Findeisen wrote: > On 2012-03-04 09:20, Stanisław Findeisen wrote: >> Hi! >> >> I am running a small Postfix server, and for a couple of hours I've been >> getting: "host ... refused to talk to me: 421 service not avail

Re: 421 service not available (connection refused, too many connections): ALL servers

On 2012-03-04 09:20, Stanisław Findeisen wrote: > Hi! > > I am running a small Postfix server, and for a couple of hours I've been > getting: "host ... refused to talk to me: 421 service not available > (connection refused, too many connections)" for all the ou

421 service not available (connection refused, too many connections): ALL servers

Hi! I am running a small Postfix server, and for a couple of hours I've been getting: "host ... refused to talk to me: 421 service not available (connection refused, too many connections)" for all the outgoing mail, all destination servers. What's wrong? I wasn't even

Re: transport private/smtp: Connection refused [solved]

trying to configure a transport map to send emails to another > server, but I got this error: > postfix-smtp/qmgr[29632]: warning: connect to transport private/smtp: > Connection refused > > in my master.cf: > 587 inet n - n - - smtpd > > That's smtpd, not smtp. > > > >

Re: transport private/smtp: Connection refused [solved]

igure a transport map to send emails to another server, but I got this error: postfix-smtp/qmgr[29632]: warning: connect to transport private/smtp: Connection refused in my master.cf: 587 inet n - n - - smtpd That's smtpd, not smtp.

Re: transport private/smtp: Connection refused

* Alfredo Saldanha : > Hi People, > > I'm trying to configure a transport map to send emails to another > server, but I got this error: > postfix-smtp/qmgr[29632]: warning: connect to transport private/smtp: > Connection refused > > in my master.cf: > 5

transport private/smtp: Connection refused

Hi People, I'm trying to configure a transport map to send emails to another server, but I got this error: postfix-smtp/qmgr[29632]: warning: connect to transport private/smtp: Connection refused in my master.cf: 587 inet n - n - - smtpd in my pos

Re: public NIC not answering - connection refused

yes,agree with matt inet_interfaces = localhost On Mon, 21 Mar 2011 09:45:29 -0400, Matt Hayes wrote: > On 3/21/2011 9:41 AM, lance raymond wrote: >> @John - thanks. Will post that output below. @Matt - SElinux disabled, iptables stopped, so I don't think that is the case. Original post d

Re: public NIC not answering - connection refused

On 2011-03-21 9:53 AM, lance raymond wrote: > *sigh* hate the obvious. But doing a grep inet_inerfaces on the > main.cf file, there was my all, then a bit lower, a > inet_interfaces = localhost so it was getting overwritten. This is why you don't grep the main.cf, you always go

Re: public NIC not answering - connection refused

*sigh* hate the obvious. But doing a grep inet_inerfaces on the main.cffile, there was my all, then a bit lower, a inet_interfaces = localhost so it was getting overwritten. A restart, outside telnet connect worked fine. Man, I do apologize to the group for starting off with such a noob mistake

Re: public NIC not answering - connection refused

can you post your ip information of interface? please run "ipconfig -a" On Mon, 21 Mar 2011 09:41:16 -0400, lance raymond wrote: > @John - thanks. Will post that output below. > @Matt - SElinux disabled, iptables stopped, so I don't think that is the case. > > Original post did have; > "

Re: public NIC not answering - connection refused

On 3/21/2011 9:41 AM, lance raymond wrote: > @John - thanks. Will post that output below. > @Matt - SElinux disabled, iptables stopped, so I don't think that is the > case. > > Original post did have; > "intet_interfaces = all which is the only thing I have found so far. " > so I am not sure if

Re: public NIC not answering - connection refused

Zitat von Matt Hayes : On 3/21/2011 9:25 AM, lance raymond wrote: I am close to having this production server in place and working, running on CentOS 5 patch updated (thanks Steve). I have mysql working nicely with dovecot, and can send mail using both squirrelmail and roundcube but all outsi

public NIC not answering - connection refused

@John - thanks. Will post that output below. @Matt - SElinux disabled, iptables stopped, so I don't think that is the case. Original post did have; " intet_interfaces = all which is the only thing I have found so far. " so I am not sure if something was omitted, or incorrect. @John, here is the

Re: public NIC not answering - connection refused

what do you expect if postfix is configured to listen only on loopback device? tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 2080/master signature.asc Description: OpenPGP digital signature

Re: public NIC not answering - connection refused

On 3/21/2011 9:25 AM, lance raymond wrote: > I am close to having this production server in place and working, > running on CentOS 5 patch updated (thanks Steve). I have mysql working > nicely with dovecot, and can send mail using both squirrelmail and > roundcube but all outsite mail in is refus

public NIC not answering - connection refused

I am close to having this production server in place and working, running on CentOS 5 patch updated (thanks Steve). I have mysql working nicely with dovecot, and can send mail using both squirrelmail and roundcube but all outsite mail in is refused. An outside port scan shows 25 as closed, and a

Re: warning: connect to private/anvil: Connection refused

.com[64.12.100.31] > Nov 20 08:52:19 mail postfix/smtpd[1277]: warning: connect to > private/anvil: Connection refused > Nov 20 08:52:19 mail postfix/smtpd[1277]: warning: problem talking to > server private/anvil: Connection refused > Nov 20 08:52:20 mail postfix/smtpd[1277]: warning:

warning: connect to private/anvil: Connection refused

Nov 20 08:51:32 mail postfix/smtpd[1525]: disconnect from unknown[211.172.215.191] Nov 20 08:52:19 mail postfix/smtpd[1277]: connect from imr-ma05.mx.aol.com[64.12.100.31] Nov 20 08:52:19 mail postfix/smtpd[1277]: warning: connect to private/anvil: Connection refused Nov 20 08:52:19 mail postfix/

Re: Connection Refused when sending on from local domain

> Aug 11 20:15:41 myhost sendmail[17048]: o7B9uJjQ015169: > to=, ctladdr= (0/0), > delay=15:19:22, xdelay=00:00:00, mailer=esmtp, pri=1560372, > relay=mail.example.com., dsn=4.0.0, stat=Deferred: Connection refused by > mail.example.com. That is the Sendmail MTA, not POSTFIX. Wietse

Connection Refused when sending on from local domain

client. Here is a snippet of a log entry, from the client, that shows the connection refused error: Aug 11 20:15:41 myhost sendmail[17048]: o7B9uJjQ015169: to=, ctladdr= (0/0), delay=15:19:22, xdelay=00:00:00, mailer=esmtp, pri=1560372, relay=mail.example.com., dsn=4.0.0, stat=Deferred

Re: Connection Refused on Port 25

Jim Wright wrote: On Jul 3, 2010, at 4:20 PM, Asai wrote: Thank you for your responses. Is there anything I can do on my end? To put it simply, you're going to need to find a way to contact them postmaster on the other end and let them know that legitimate mail is being blocked. You

Re: Connection Refused on Port 25

junkyardma...@verizon.net wrote: Have you verified your MTA's are not on a Black/Block list? Maybe draxlerinsurance.com has firewalled you off. I know I would. http://www.mxtoolbox.com/blacklists.aspx OK, why would you firewall me off? -- asai

Re: Connection Refused on Port 25

mail.egismail.com closing connection Connection closed by foreign host. -- From: "Asai" Sent: Saturday, July 03, 2010 2:20 PM To: Subject: Re: Connection Refused on Port 25 Jeroen Geilman wrote: Thank you for your responses. Is there anyt

Re: Connection Refused on Port 25

sing connection Connection closed by foreign host. -- From: "Asai" Sent: Saturday, July 03, 2010 2:20 PM To: Subject: Re: Connection Refused on Port 25 Jeroen Geilman wrote: Thank you for your responses. Is there anything I can do on my end? As

Re: Connection Refused on Port 25

On Jul 3, 2010, at 4:20 PM, Asai wrote: > Thank you for your responses. Is there anything I can do on my end? To put it simply, you're going to need to find a way to contact them postmaster on the other end and let them know that legitimate mail is being blocked. You will first need to find a

Re: Connection Refused on Port 25

On 07/03/2010 11:38 PM, /dev/rob0 wrote: On Sat, Jul 03, 2010 at 02:24:20PM -0700, Asai wrote: Jeroen Geilman wrote: On 07/03/2010 11:20 PM, Asai wrote: Jeroen Geilman wrote: On 07/03/2010 09:14 PM, Charles Marcus wrote: On 2010-07-02 7:20 PM, Asai wro

Re: Connection Refused on Port 25

On Sat, Jul 03, 2010 at 02:24:20PM -0700, Asai wrote: > Jeroen Geilman wrote: >> On 07/03/2010 11:20 PM, Asai wrote: >>> Jeroen Geilman wrote: On 07/03/2010 09:14 PM, Charles Marcus wrote: > On 2010-07-02 7:20 PM, Asai wrote: >> OK. Has anyone successfully been able to work around thi

Re: Connection Refused on Port 25

On 07/03/2010 11:24 PM, Asai wrote: Jeroen Geilman wrote: On 07/03/2010 11:20 PM, Asai wrote: Jeroen Geilman wrote: On 07/03/2010 09:14 PM, Charles Marcus wrote: On 2010-07-02 7:20 PM, Asai wrote: OK. Has anyone successfully been able to work around this issue? The only way is to have the

Re: Connection Refused on Port 25

Jeroen Geilman wrote: On 07/03/2010 11:20 PM, Asai wrote: Jeroen Geilman wrote: On 07/03/2010 09:14 PM, Charles Marcus wrote: On 2010-07-02 7:20 PM, Asai wrote: OK. Has anyone successfully been able to work around this issue? The only way is to have the admin for the CISCO PIX disable the

Re: Connection Refused on Port 25

On 07/03/2010 11:20 PM, Asai wrote: Jeroen Geilman wrote: On 07/03/2010 09:14 PM, Charles Marcus wrote: On 2010-07-02 7:20 PM, Asai wrote: OK. Has anyone successfully been able to work around this issue? The only way is to have the admin for the CISCO PIX disable the stupid smtp fixup garbag

Re: Connection Refused on Port 25

Jeroen Geilman wrote: On 07/03/2010 09:14 PM, Charles Marcus wrote: On 2010-07-02 7:20 PM, Asai wrote: OK. Has anyone successfully been able to work around this issue? The only way is to have the admin for the CISCO PIX disable the stupid smtp fixup garbage on the CISCO box. As far

Re: Connection Refused on Port 25

On 07/03/2010 09:14 PM, Charles Marcus wrote: On 2010-07-02 7:20 PM, Asai wrote: OK. Has anyone successfully been able to work around this issue? The only way is to have the admin for the CISCO PIX disable the stupid smtp fixup garbage on the CISCO box. As far as I know, there is NE

Re: Connection Refused on Port 25

On 2010-07-02 7:20 PM, Asai wrote: > OK. Has anyone successfully been able to work around this issue? The only way is to have the admin for the CISCO PIX disable the stupid smtp fixup garbage on the CISCO box. As far as I know, there is NEVER any reason to have this enabled on an internet facing

  1   2   >