1) Postfix has NO impact on telnet. If you cannot telnet outbound to a
remote port 25 the problem is that something on your host is blocking
port 25 or something upstream from you is blocking port 25.
Can you perform the following:
telnet localhost 25
If this works, you CAN telnet to port 25
On 2014-02-21 03:41, Feel Zhou wrote:
-A INPUT -m state --state NEW -m tcp -p tcp --dport 25 -j ACCEPT
it might be geoip blocking you see to the recipient mailservers if you
not see it to all recipient ips
if that is it, then you can just remove recipient domain from dns with
bind9 rpz zone
On Thu, Feb 20, 2014 at 09:45:06PM -0500, Sahil Tandon wrote:
> > Viktor Dukhovni:
> > > On Sun, Feb 16, 2014 at 07:45:24AM -0500, Wietse Venema wrote:
> > >
> > > > This looks like the same problem that Viktor referred to yesterday.
> > > > Same symptom (crash in zlib+openssl), same resolution.
On Fri, Feb 21, 2014 at 10:31:18AM +0800, Feel Zhou wrote:
> Today, one of my postfix server can not telnet any other mail server's port
> 25.
If you cannot make a TCP connection to port 25, your problem is
outside Postfix. Your ISP may have blocked port 25 outbound.
> It's working before 9:00a
On Thu, Feb 20, 2014 at 9:31 PM, Feel Zhou wrote:
> Hello, My friend
> This is Tom, I'm sending my greeting from China.
> Today, one of my postfix server can not telnet any other mail server's port
> 25. It's working before 9:00am(bejing time CHina), I have restart the mail
> server and reinstall
On Sun, 2014-02-16 at 11:02:08 -0500, Wietse Venema wrote:
> Viktor Dukhovni:
> > On Sun, Feb 16, 2014 at 07:45:24AM -0500, Wietse Venema wrote:
> >
> > > This looks like the same problem that Viktor referred to yesterday.
> > > Same symptom (crash in zlib+openssl), same resolution.
> >
> > Perh
-A INPUT -m state --state NEW -m tcp -p tcp --dport 25 -j ACCEPT
firewall is ok
2014-02-21 10:37 GMT+08:00 Venkat :
> On Thu, Feb 20, 2014 at 6:31 PM, Feel Zhou wrote:
>
>> Hello, My friend
>> This is Tom, I'm sending my greeting from China.
>> Today, one of my postfix server can not telnet an
On Thu, Feb 20, 2014 at 6:31 PM, Feel Zhou wrote:
> Hello, My friend
> This is Tom, I'm sending my greeting from China.
> Today, one of my postfix server can not telnet any other mail server's
> port 25. It's working before 9:00am(bejing time CHina), I have restart the
> mail server and reinstall
Hello, My friend
This is Tom, I'm sending my greeting from China.
Today, one of my postfix server can not telnet any other mail server's port
25. It's working before 9:00am(bejing time CHina), I have restart the mail
server and reinstall the postfix. but it's looks like not working. How can
I fix t
On 19 Feb 2014, at 8:57, Svoop wrote:
Hmmm, the problem has vanished, I can't reproduce it anymore. However,
I
keep your instructions. If the problem occurs again, I'll have the
tools in
place.
This is almost certainly due to the way bluewin.ch has set up their DNS.
Note:
bluewin.ch. 432
On Thu, Feb 20, 2014 at 11:50:19AM -0500, Wietse Venema wrote:
> WHAT STATUS INFORMATION TO LOG
> ==
> If cost is not a concern, then we could log everything like this:
>
> ... tls_protocol=TLSv1.2 tls_cipher=ECDHE-RSA-AES256-GCM-SHA384
> tls_keysize=256/256 ..
On Thu, Feb 20, 2014 at 06:51:09AM -0500, Wietse Venema wrote:
> To fully understand what happens with a particular message requires
> a stateful logfile processor.
I tend to use the admittedly imperfect, but sufficiently useful
"collate" Perl script I slapped together. A fancier version would
c
> > ON THE SAME SERVER if I type
> > $ host mail15.wdc01.mcdlv.net
> >
> > I get
> >
> > mail15.wdc01.mcdlv.net has address 205.201.129.15
> > mail15.wdc01.mcdlv.net mail is handled by 10 mail.mail15.wdc01.mcdlv.net.
> >
> > So why Postfix says "Domain not found"?
>
> * maybe your smtpd is run
Salvatore Palazzolo:
> there is no link between the line related to the TLS connection
> and the subsequent queue message ID.
The link is the combination of SMTP server process ID (21492) and
the client name+address (unknown[10.204.61.131]) as shown below:
> Feb 20 11:05:47 sgsnoimsva002lx postfi
As implemented many years ago, Postfix SMTP client and server
processes log TLS status information like this:
postfix/smtp[process-id]: Untrusted TLS connection established
to host.example.com[192.168.0.2]:25: TLSv1 with cipher cipher-name
(actual-key-size/raw-key-size bits)
postf
Am 20.02.2014 14:46, schrieb Luigi Rosa:
> Feb 20 12:27:28 services postfix/smtpd[3054]: connect from
> unknown[205.201.129.15]
> Feb 20 12:27:29 services postfix/smtpd[3054]: NOQUEUE: reject: RCPT from
> unknown[205.201.129.15]: 450 4.1.8
> :
> Sender address rejected: Domain not found;
> from=
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi, I have a Postfix 2.11.0 with this recipient policy
smtpd_recipient_restrictions = permit_mynetworks
check_client_access hash:/etc/postfix/whitelist
reject_invalid_hostname
reject_non_fqdn_hostname
reject_non_fqdn_se
17 matches
Mail list logo