) - I known this is stupid
>>
>> In log i found "Connection timed out" and I dont known what value
>> exceeds
>>
>> 10.0.100.5 - this is dovecot with lmtp to deliver
>>
>> main.cf:
>>
>> virtual_transport = lmtp:inet:10.0.100.5:24
On 03.11.20 11:26, natan wrote:
For test I create aliasgroup ~100 user. For test i try send like:
for i in {1..10}; do echo "asdasdasdasda" |mail
aliasgr...@domain.ltd;done & (for test x 4) - I known this is stupid
In log i found "Connection timed out" and I dont
Hi
For test I create aliasgroup ~100 user. For test i try send like:
for i in {1..10}; do echo "asdasdasdasda" |mail
aliasgr...@domain.ltd;done & (for test x 4) - I known this is stupid
In log i found "Connection timed out" and I dont known what value exceeds
10.0.100.
Emanuel:
[ Charset windows-1252 converted... ]
> Hello, i see this error:
>
> Apr 16 13:13:51 host02 postfix/smtpd[32761]: warning: problem talking to
> server 127.0.0.1:20040: Connection timed out
> Apr 16 13:13:52 host02 postfix/smtpd[32491]: warning: problem talking to
>
Hello, i see this error:
Apr 16 13:13:51 host02 postfix/smtpd[32761]: warning: problem talking to
server 127.0.0.1:20040: Connection timed out
Apr 16 13:13:52 host02 postfix/smtpd[32491]: warning: problem talking to
server 127.0.0.1:20040: Connection timed out
Apr 16 13:13:53 host02 postfix
> On Aug 19, 2016, at 11:56 AM, Bill Cole
> wrote:
>
> So, is this policy server listening on port 1234 or port ?
> I'll assume this is just inconsistent (and pointless) obfuscation...
Just a pointless obfuscation. Sorry about this.
> As Wietse noted more tersely, the only way to handle c
requests, so i now run it with pypy to (hopefully) get better performance. But
unfortunately, still same issue.
When I saw lots of "Connection timed out" and "Connection reset by peer", the
output of repeat command "netstat -antp | grep : | awk '{print $6}' | sort
: Connection reset by peer
Aug 17 08:34:05 mail1 postfix/smtpd[24771]: warning: problem talking
to server 127.0.0.1:1234: Connection timed out
Then time Postfix raised these errors, my policy server is still
working and properly processing requests (checked its log file).
Your policy daemon may not be able
g what Postfix sends to a policy server.
I tested with shell commands below:
for i in $(seq 1000); do
(cat <
So, is this policy server listening on port 1234 or port ?
I'll assume this is just inconsistent (and pointless) obfuscation...
I get some "Ncat: Connection r
On 19/08/16 11:32, Zhang Huangbin wrote:
Dear Bill,
Thanks very much for helping.
On Aug 19, 2016, at 4:17 AM, Bill Cole
wrote:
What do you mean "run" the policy service? It's a python program.
Which must be running in order for it to be listening for connections.
Likely mechanisms would
Dear Bill,
Thanks very much for helping.
> On Aug 19, 2016, at 4:17 AM, Bill Cole
> wrote:
>
>> What do you mean "run" the policy service? It's a python program.
>
> Which must be running in order for it to be listening for connections.
> Likely mechanisms would be via a SysV init script in /
On 18 Aug 2016, at 11:14, Zhang Huangbin wrote:
On Aug 18, 2016, at 10:02 PM, Wietse Venema
wrote:
What are you using to "run" the policy service? Try using "telnet
127.0.0.1 9998" or "nc 127.0.0.1 9998" to test it.
Thanks Wietse. :)
What do you mean "run" the policy service? It's a pyth
> What do you mean "run" the policy service? It's a python program.
How does it handle concurrent connections? The symptoms that you
describe (connection refused / connection timed out) suggest that
it handles one connection at a time, somewhat like this:
forever:
> On Aug 18, 2016, at 10:02 PM, Wietse Venema wrote:
>
> What are you using to "run" the policy service? Try using "telnet
> 127.0.0.1 9998" or "nc 127.0.0.1 9998" to test it.
Thanks Wietse. :)
What do you mean "run" the policy service? It's a python program.
> In particular, what happens whe
Zhang Huangbin:
[ Charset windows-1252 converted... ]
>
> > On Aug 18, 2016, at 8:46 AM, Noel Jones wrote:
> >
> > There was an example on the link I sent earlier.
> >
> > # main.cf
> > 127.0.0.1:1234_time_limit = 3600
>
> Seems this setting is not ok for me: The example in Postfix doc
> does
way and the OS closed the connection.
Aug 17 08:34:05 mail1 postfix/smtpd[24771]: warning: problem talking
to server 127.0.0.1:1234: Connection timed out
That's a new Postfix smtpd process with PID 24771 trying and failing to
open a new connection to the policy service. How long it will wait
inet ... service for the policy
daemon is defined in master.cf. If postfix isn't managing the policy
daemon it looks like the "transport_time_limit" is not relevant. The
"Connection reset by peer"/"Connection timed out" might mean you've
temporarily run out
> On Aug 18, 2016, at 8:46 AM, Noel Jones wrote:
>
> There was an example on the link I sent earlier.
>
> # main.cf
> 127.0.0.1:1234_time_limit = 3600
Seems this setting is not ok for me: The example in Postfix doc does have a
transport (127.0.0.1:9998) defined in master.cf, but i don't have
> On Aug 18, 2016, at 8:46 AM, Noel Jones wrote:
>
> # main.cf
> 127.0.0.1:1234_time_limit = 3600
"postfix check" reported "unused parameter: 127.0.0.0:1234_time_limit=3600s", i
thought it was illegal parameter.
I added this one and restarted Postfix, let's see whether or not it fixes my
issu
On 8/17/2016 7:26 PM, Zhang Huangbin wrote:
>
>> On Aug 18, 2016, at 12:17 AM, Noel Jones wrote:
>>
>> Have you defined a time limit as described in
>> http://www.postfix.org/SMTPD_POLICY_README.html#client_config
>> The default time limit of 1000s may be too short.
>
> My policy server is a ine
> On Aug 18, 2016, at 12:17 AM, Noel Jones wrote:
>
> Have you defined a time limit as described in
> http://www.postfix.org/SMTPD_POLICY_README.html#client_config
> The default time limit of 1000s may be too short.
My policy server is a inet server (check_policy_service inet:127.0.0.1:1234),
problem talking to
> server 127.0.0.1:1234: Connection reset by peer
> Aug 17 08:34:05 mail1 postfix/smtpd[24771]: warning: problem talking to
> server 127.0.0.1:1234: Connection timed out
>
> Then time Postfix raised these errors, my policy server is still working and
> properly proce
mail1 postfix/smtpd[24771]: warning: problem talking to server
127.0.0.1:1234: Connection timed out
Then time Postfix raised these errors, my policy server is still working and
properly processing requests (checked its log file).
I don't know how to reproduce this issue, except wait (espec
15 21:37:54 +0200 From: Krzs
>> mailto:krozu...@autistici.org>>
>>
>> Hi list ... my smtp refuses to deliver mail to SOME adressess not
>> all giving me a connection timed out error . I show you logs in
>> charge:
>>
>> smtp[13847]: 27A6111B: to=> &
On Sun, Apr 19, 2015 at 09:37:54PM +0200, Krzs wrote:
> Hi list ...
> my smtp refuses to deliver mail to SOME adressess not all giving me a
> connection timed out error . I show you logs in charge:
>
> > smtp[13847]: 27A6111B: to=,
> relay=none, delay=86842, delays=86722/
deliver mail to SOME adressess not all giving
> > me a connection timed out error . I show you logs in charge:
> >
> > smtp[13847]: 27A6111B: to=,
> > relay=none, delay=86842, delays=86722/0.01/120/0, dsn=4.4.1,
> > status=deferred (connect to riseup.net[1.209.122.2
Original Message
> Date: Sunday, April 19, 2015 21:37:54 +0200
> From: Krzs
>
> Hi list ...
> my smtp refuses to deliver mail to SOME adressess not all giving
> me a connection timed out error . I show you logs in charge:
>
> smtp[13847]: 27A
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi list ...
my smtp refuses to deliver mail to SOME adressess not all giving me a
connection timed out error . I show you logs in charge:
> smtp[13847]: 27A6111B: to=,
relay=none, delay=86842, delays=86722/0.01/120/0, dsn=4.4.1,
status=defer
Aravindhan:
> * Telnet to the port 25 of the specific smtp server is working randomly
> (sometimes works and sometimes not).
> * Ping to the SMTP server is always successfull(Telnet to port 25 fails most
> of the time).
Many ISPs block traffic to remote port 25. Possible solutions:
- Connect to
/0,
dsn=4.4.1, status=deferred (connect to mx4.hotmail.com[207.46.8.199]:25:
*Connection timed out*)
I have tried to change the "inet_protocols" value to "ipv4" in the file
"/etc/postfix/main.cf" and restarted postfix server. But it wont fix the
issue.
Note:
* M
El 08/02/13 15:29, Viktor Dukhovni escribió:
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 easie
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
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
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
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
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
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.
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
and if the client decides to make a large order they
>>> end up pushing our volume up and we end up getting blocked by their
>>> mail server. I seem to be getting connection timed out on a lot of
>>> the hosts. I even try to telnet to ip and port 25 but it keeps
>>&g
up getting blocked by their
>> mail server. I seem to be getting connection timed out on a lot of
>> the hosts. I even try to telnet to ip and port 25 but it keeps
>> timing out. I used "grep" to search in /var/log/maillog and I got
>> this. Any ideas?
>
>
>
o be getting connection timed out on a lot of
> the hosts. I even try to telnet to ip and port 25 but it keeps
> timing out. I used "grep" to search in /var/log/maillog and I got
> this. Any ideas?
This isn't a postfix problem. If you can't telnet to any client
port 25, th
Alejandro Reyes Jimenez
Coordinador de Seguridad - SASI
E-mail: aare...@scitum.com.mx
Telefono: 91507489
Movil: (044) 55 85 81 04 62
De: Gonzo Fernandez [mailto:go...@usaepay.com]
Enviado: Monday, January 30, 2012 06:46 PM
Para: postfix users
Asunto: Re: Mail stuck (Connection Timed-Out
Thank you Noel. Our server sends out copies of email confirmations to our
clients and if the client decides to make a large order they end up pushing our
volume up and we end up getting blocked by their mail server. I seem to be
getting connection timed out on a lot of the hosts. I even try to
On 1/30/2012 5:07 PM, Gonzo Fernandez wrote:
> Hi All,
>
> My relay servers have mail being received but unable to send. When I
> type "mailq" I see: Delivery temporarily suspended….Connection timed
> out. I also noticed this line:
>
> Tarpitting active for [1.
Hi All,
My relay servers have mail being received but unable to send. When I type
"mailq" I see: Delivery temporarily suspended….Connection timed out. I also
noticed this line:
Tarpitting active for [1.2.3.4)
I restarted postfix, flushed mailq and still everything is stuck. Now th
s.sock: can't read SMFIC_BODYEOB reply packet
>> header: Connection timed out
> This means that the spam filter needed more than 300s to process
> the message body. You can increase milter_content_timeout in main.cf,
> but I suspect that the problem is caused by DNS lookup p
JKL:
> Hi there,
>
> This morning at 11:30am CET postfix started to log this message from
> a milter:
>
> Mar 20 19:43:39 logout postfix/cleanup[19241]: warning: milter
> unix:/spamass/spamass.sock: can't read SMFIC_BODYEOB reply packet
> header: Connection t
Hi there,
This morning at 11:30am CET postfix started to log this message from
a milter:
Mar 20 19:43:39 logout postfix/cleanup[19241]: warning: milter
unix:/spamass/spamass.sock: can't read SMFIC_BODYEOB reply packet
header: Connection timed out
I have since removed the milter from po
On Tue, Dec 07, 2010 at 02:01:18PM -0500, Randy Ramsdell wrote:
>> Hello,
>> I am getting the following error whenever try to send email to gmail :
>> connect to alt4.gmail-smtp-in.l.google.com
>> <http://alt4.gmail-smtp-in.l.google.com>[74.125.79.27]: Connection
t;> http://alt4.gmail-smtp-in.l.google.com>[74.125.79.27]: Connection timed
>> out (port 25)
>>
>> And for rediff :
>>
>> connect to mx.rediffmail.rediff.akadns.net <
>> http://mx.rediffmail.rediff.akadns.net>[202.137.235.10]: Connection timed
>> out
>>
>>
>> Can you suggest why this is happened?
>>
>> Thanks & Regards,
>> Avinash
>>
>
> Outage?
>
Avinash Pawar wrote:
Hello,
I am getting the following error whenever try to send email to gmail :
connect to alt4.gmail-smtp-in.l.google.com
<http://alt4.gmail-smtp-in.l.google.com>[74.125.79.27]: Connection timed
out (port 25)
And for rediff :
connect to mx.rediffmail.rediff.akad
Hello,
I am getting the following error whenever try to send email to gmail :
connect to alt4.gmail-smtp-in.l.google.com[74.125.79.27]: Connection timed
out (port 25)
And for rediff :
connect to mx.rediffmail.rediff.akadns.net[202.137.235.10]: Connection timed
out
Can you suggest why this is
>Ioannis, disable all the firewalls but for basic SPI NAT/PAT (if you're
using
>NAT) on the dedicated Shorewall guest. Route TCP 25 inbound via a PAT rule
to
>the Postfix guest. See if that eliminates the timeout and related TCP
errors.
>--
>Stan
Dear Stan, I was just about to get enthusiasti
In the original scenario, Exchange was in the same network with Postfix
(both in dmz). For a reason, when applied on the customer premises, dhcp
wouldn't go through for the local workstations, so exchange was moved to the
local zone. To be honest, the testing didn't include large attachments (if
an
Ioannis Tsouvalas put forth on 5/30/2010 2:56 PM:
> Stan, thanks again for your input, I am getting the idea and I'm working
> towards that direction, still from 3 months testing this implementation has
> moved to production, and I am working remotely, so "being careful" is one
> way to describe my
Ioannis Tsouvalas put forth on 5/30/2010 2:46 PM:
> I have disabled shorewall on Postfix machine using #shorewall clear , but
> I'm still working on clearing shorewall on the dedicated machine, but I
> haven't managed to make it happen since all the NAT has been implemented on
> the shorewall confi
Stan, thanks again for your input, I am getting the idea and I'm working
towards that direction, still from 3 months testing this implementation has
moved to production, and I am working remotely, so "being careful" is one
way to describe my actions.
Ps. The net diagram looked much better when I
I have disabled shorewall on Postfix machine using #shorewall clear , but
I'm still working on clearing shorewall on the dedicated machine, but I
haven't managed to make it happen since all the NAT has been implemented on
the shorewall configuration. I'm still trying to figure out a safe way to
mov
Ioannis Tsouvalas put forth on 5/30/2010 9:47 AM:
> Stan thanks for the reply, and please excuse me for the time interval in
> between your post and my reply. "Geek" and "neato!" wasn't exactly what I
> was aiming for, but still I appreciate that you identified the "geeky"
> complexity of the idea
>From: Stan Hoeppner (stanhardwarefreak.com)
>Date: Fri May 28 2010 - 18:09:48 CDT
>
>IIRC from his initial post, Ioannis has 3 virtual machines atop ESXi: one a
>dedicated Ubuntu Shorewall instance, one running Ubuntu Shorewall (again)
and
>Postfix, one running Microsoft SBS plus Exchange.
>
>A ba
t, except perhaps retry when the remote
> system is under less stress.
>
>>>> 421 4.4.1 Connection timed out (in reply to end of DATA command)
>>>> 421 4.4.2 mxfront39.mail.yandex.net Error: timeout exceeded (in
>>>> reply to end of DATA command)
>
> The
Postconf -n output:
alias_database = hash:/etc/postfix/aliases
alias_maps = hash:/etc/postfix/aliases
append_dot_mydomain = no
biff = no
config_directory = /etc/postfix
delay_warning_time = 4h
disable_vrfy_command = yes
inet_interfaces = all
local_recipient_maps =
mailbox_size_limit = 0
masquerade
tem is under less stress.
>
>> >> 421 4.4.1 Connection timed out (in reply to end of DATA command)
>> >> 421 4.4.2 mxfront39.mail.yandex.net Error: timeout exceeded (in
>> >> reply to end of DATA command)
>
>These could be a network-level problem such a
Ioannis Tsouvalas:
> >
> >Ioannis Tsouvalas:
> >> 451 Requested action aborted: local error in processing
> >> 451 Temporary local problem - please try later
These you can do nothing about, except perhaps retry when the remote
system is under less stress.
>
ot a Postfix error message. It is an error in a non-Postfix MTA.
>Please do not shoot the messenger.
>
>> 421 4.4.1 Connection timed out (in reply to end of DATA command)
>
>This is not a Postfix error message. It is an error in a non-Postfix MTA.
>Please do not shoot the messen
Stan Hoeppner put forth on 5/28/2010 06:41 AM
>
>Per the list welcome messages, you should post the complete output of
>"postconf -n". This will aid members in solving your issue, if the cause
of
>your problem is indeed related to your Postfix configuration.
>
>--
>Stan
Postconf -n output:
alia
r in a non-Postfix MTA.
Please do not shoot the messenger.
> 421 4.4.1 Connection timed out (in reply to end of DATA command)
This is not a Postfix error message. It is an error in a non-Postfix MTA.
Please do not shoot the messenger.
> said: 421 4.4.2 mxfront39.mail.yandex.net Error: timeout
Ioannis Tsouvalas put forth on 5/28/2010 6:41 AM:
> Stan thanks for the reply, as well as the insight regarding the difference
> between soft and hard nic devices. The only reason I'm pointing out the link
> pulse as well as the MTU, is that my search so far points me towards that
> direction. Now
>>Are there any firewalls between the Postfix and Exchange Server ?
>>
>>Mihira
>
>Yes there is, shorewall as implemented on the link provided
>http://flurdy.com/docs/postfix/
>
>--
>Ioannis
As well as the shorewall in the three interface firewall
http://www.shorewall.net/three-interface.htm
_
>Are there any firewalls between the Postfix and Exchange Server ?
>
>Mihira
Yes there is, shorewall as implemented on the link provided
http://flurdy.com/docs/postfix/
--
Ioannis
__ Information from ESET Smart Security, version of virus signature
database 5152 (20100528)
On Fri, 28 May 2010 14:41:46 +0300
"Ioannis Tsouvalas" wrote:
> reply
>
> Stan Hoeppner put forth on 5/28/201 5:42 AM:
>
> >The vmxnet 'NIC' is a virtual device, strictly a software driver.
> >The vmxnet driver communicates with the ESX kernel at the speed of
> >system memory, which on modern s
reply
Stan Hoeppner put forth on 5/28/201 5:42 AM:
>The vmxnet 'NIC' is a virtual device, strictly a software driver. The
>vmxnet driver communicates with the ESX kernel at the speed of system
>memory, which on modern servers is over 10x faster than the 10 Gbe
>signaling rate. There is no su
Ioannis Tsouvalas put forth on 5/28/2010 4:09 AM:
> My guess so far is to go and lower the link speed between the Shorewall,
> Postfix, and maybe even SBS2008, and that's because similar problems having
> been encountered where the MTU is bigger than 1500. Now, the only reason I
> haven't done it
command)
said: 421 4.4.1 Connection timed out (in reply to end of DATA command)
said: 421 4.4.2 mxfront39.mail.yandex.net Error: timeout exceeded (in reply
to end of DATA command)
(lost connection with mx1.mail.eu.yahoo.com[77.238.177.9] while sending end
of data -- message may be sent more than once)
E
Sahil Tandon put forth on 10/20/2009 8:57 PM:
> On Tue, 20 Oct 2009, Michael Jean wrote:
>
>> smtpd_sasl_auth_enable = yes
>
> smtpd != smtp; you never enabled SASL for the smtp *client*. Review the
> SASL_README, specifically the client section to which you have already
> been referred.
>
>> s
On Tue, 20 Oct 2009, Michael Jean wrote:
> smtpd_sasl_auth_enable = yes
smtpd != smtp; you never enabled SASL for the smtp *client*. Review the
SASL_README, specifically the client section to which you have already
been referred.
> sasl_passwd:
> [smtp.broadband.rogers.com] michaeljean:mypasswo
t; smtpd_tls_key_file = /etc/postfix/toots-key.pem
> > smtpd_tls_received_header = yes
> > smtpd_tls_security_level = may
> > smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
> > smtpd_use_tls = yes
> > tls_random_source = dev:/dev/urandom
> &g
On 20-Oct-2009, at 02:59, Angelo Amoruso wrote:
Try to troubleshooting doing a simple telnet on port TCP/25 on the
remote host.
If you can get the welcome banner from the remote SMTP server, the
issue is somewhere else.
Nope,. you have to check a full transaction. Rogers, like some ISPs,
m
Noel Jones wrote:[...]
mail.log:
Oct 14 23:31:16 mymailhost postfix/smtp[9166]: 5F01426400:
to=, relay=none, delay=60, delays=0.04/0.02/60/0,
dsn=4.4.1, status=deferred (connect to
filter.somewhere.ca[ipaddress]:25: Connection timed out)
Oct 14 23:31:51 mymailhost postfix/smtp[9188
log:
> Oct 14 23:31:16 mymailhost postfix/smtp[9166]: 5F01426400:
> to=, relay=none, delay=60, delays=0.04/0.02/60/0,
> dsn=4.4.1, status=deferred (connect to
> filter.somewhere.ca[ipaddress]:25: Connection timed out)
>
> Oct 14 23:31:51 mymailhost postfix/smtp[9188]: 7EFCE26403:
> t
ev/urandom
mail.log:
Oct 14 23:31:16 mymailhost postfix/smtp[9166]: 5F01426400:
to=, relay=none, delay=60, delays=0.04/0.02/60/0,
dsn=4.4.1, status=deferred (connect to
filter.somewhere.ca[ipaddress]:25: Connection timed out)
Oct 14 23:31:51 mymailhost postfix/smtp[9188]: 7EFCE26403:
to=, relay=n
st postfix/smtp[9166]: 5F01426400:
to=, relay=none, delay=60, delays=0.04/0.02/60/0,
dsn=4.4.1, status=deferred (connect to
filter.somewhere.ca[ipaddress]:25: Connection timed out)
Oct 14 23:31:51 mymailhost postfix/smtp[9188]: 7EFCE26403:
to=, relay=none, delay=60, delays=0.03/0.01/60/0,
dsn=4.4
> 10.11.12.13 is also the IP of localhost.com. Is it possible you have no
localhost entry in /etc/hosts, causing your machine to look up localhost.com
?
THANKS VERY MUCH. It's enough to have .com default domain suffix and it
explains some weirdnessess ;-)
Regards,
Andrzej
. Looks like localhost is considered 10.11.12.13. The error
message, /etc/hosts, and postconf -n are below.
Here is the error message:
snip
: delivery temporarily suspended: connect to
localhost[10.11.12.13]:25: Connection timed out
10.11.12.13 is also the IP of localhost.com
Andrzej Kuku?a wrote:
On Sun, Jul 19, 2009 at 11:32, mouss wrote:
Admin a écrit :
Hi there,
I am using fetchmail to pop3 mail from gmail. But when I receive email
I find that fetchmail is using postfix to deliver the mail to the
corresponding internal mailbox. postfix responds with the foll
On Sun, Jul 19, 2009 at 11:32, mouss wrote:
>
> Admin a écrit :
> > Hi there,
> >
> > I am using fetchmail to pop3 mail from gmail. But when I receive email
> > I find that fetchmail is using postfix to deliver the mail to the
> > corresponding internal mailbox. postfix responds with the followi
Admin a écrit :
> Hi there,
>
> I am using fetchmail to pop3 mail from gmail. But when I receive email
> I find that fetchmail is using postfix to deliver the mail to the
> corresponding internal mailbox. postfix responds with the following
> error and best I can tell the mail never ends up in m
localhost is considered 10.11.12.13. The error message,
/etc/hosts, and postconf -n are below.
Here is the error message:
snip
: delivery temporarily suspended: connect to
localhost[10.11.12.13]:25: Connection timed out
Reporting-MTA: dns; domain.com
X-Postfix-Queue-ID
On Tue, 2008-07-29 at 16:12 +0200, mouss wrote:
> > These restrictions are generally limited to port 25. Are you able to
> > telnet from other machines on port 25?
> Also, show examples of servers you fail to connect to.
Yes, I can telnet 25 from the other machines I have here.
mail.staugusti
Scott Kitterman wrote:
On Tue, 29 Jul 2008 14:59:25 +0100 Evan Ingram <[EMAIL PROTECTED]>
wrote:
On Tue, 2008-07-29 at 15:46 +0200, mouss wrote:
some sites drop traffic from residential blocks, which could explain why
you cannot connect.
Hmmm That would make sense. But what about the other ma
On Tue, 29 Jul 2008 14:59:25 +0100 Evan Ingram <[EMAIL PROTECTED]>
wrote:
>On Tue, 2008-07-29 at 15:46 +0200, mouss wrote:
>> some sites drop traffic from residential blocks, which could explain why
>> you cannot connect.
>
>
>Hmmm That would make sense. But what about the other machines I have
>
On Tue, 2008-07-29 at 15:46 +0200, mouss wrote:
> some sites drop traffic from residential blocks, which could explain why
> you cannot connect.
Hmmm That would make sense. But what about the other machines I have
here being able to connect to the problem mail servers via telnet etc
but my mail
Evan Ingram wrote:
On Tue, 2008-07-29 at 15:02 +0200, mouss wrote:
check the firewall configuration. and if the postfix machine has
firewall software (or selinux/apparamor), check that as well.
Everything outbound should be allowed, port 25 is forwarded to the mail
server.
For the majority
On Tue, 2008-07-29 at 15:02 +0200, mouss wrote:
> check the firewall configuration. and if the postfix machine has
> firewall software (or selinux/apparamor), check that as well.
Everything outbound should be allowed, port 25 is forwarded to the mail
server.
For the majority of mail servers its
Evan Ingram wrote:
On Tue, 2008-07-29 at 13:53 +0200, mouss wrote:
$ telnet aserver 25
...
EHLO yourhostname.example.com
...
QUIT
and post whatever you see.
From the mail server machine it doesn't connect, just sits there trying:
telnet mail.staugustines.uk.com 25
Trying 79.170.40.19...
On Tue, 2008-07-29 at 13:53 +0200, mouss wrote:
> $ telnet aserver 25
> ...
> EHLO yourhostname.example.com
> ...
> QUIT
>
> and post whatever you see.
>From the mail server machine it doesn't connect, just sits there trying:
telnet mail.staugustines.uk.com 25
Trying 79.170.40.19...
Works from
Evan Ingram wrote:
Hi all,
In need of some help. A lot of people sending me email are getting them
bounced. All i see in the logs is:
status=deferred (connect to aserver: Connection timed out)
yes, this happens when ...
do not truncate log lines or we will truncate our answers ;-p
What
Hi all,
In need of some help. A lot of people sending me email are getting them
bounced. All i see in the logs is:
status=deferred (connect to aserver: Connection timed out)
What can i do to check my config? The mail server is sat on a box which
is behind another box running as a firewall and
98 matches
Mail list logo
