On Tue, Nov 19, 2013 at 05:33:30PM -0500, Wietse Venema wrote:
> --8<-snip-here--8<--
> #!/bin/sh
>
> case $# in
> 0) echo usage: $0 example.com ... 1>&2; exit 1;;
> esac
>
> VIRTUAL_MAP=/etc/postfix/virtual
> VIRTUAL_DOMAINS=/etc/postfix/virtual_domains
>
> for domainname
> do
> echo po
Pol Hallen:
> > Instead, use a script that generates explicit postmas...@example.com
> > entries etc. when you host a new domain.
>
> thanks for reply. Is there an example of that script? Need I create a
> virtual domain or only something that redirect (i.e.
> postmas...@example.org) to virtual do
> Instead, use a script that generates explicit postmas...@example.com
> entries etc. when you host a new domain.
thanks for reply. Is there an example of that script? Need I create a
virtual domain or only something that redirect (i.e.
postmas...@example.org) to virtual domain?
Thanks!
Pol
Pol Hallen:
> Hi all :-) I've several virtual domains and I looking for how create the
> aliases for each domains (aliases like postmaster, root, etc.)
>
> I found this
> http://serverfault.com/questions/171616/postfix-how-to-make-aliases-work-for-virtual-domains
>
> that says something like this
Hi all :-) I've several virtual domains and I looking for how create the
aliases for each domains (aliases like postmaster, root, etc.)
I found this
http://serverfault.com/questions/171616/postfix-how-to-make-aliases-work-for-virtual-domains
that says something like this: "putting postmaster, roo
>> Thanks. So my understanding is correct that Postfix gets the hostnames you
> see in the logs from PTR records?
>
> Yes.
>
>> You are saying that additionally, if the A record for the domain
> doesn't match the client IP, the PTR will be ignored and thus you'll
> still get "unknown"?
>
E.B. wrote:
> Thanks. So my understanding is correct that Postfix gets the hostnames you
> see in the logs from PTR records?
Yes.
> And that "connect from unknown[1.2.3.4]" is caused by a missing PTR (or DNS
> issue)?
A missing PTR is one cause. A DNS glitch that means the PTR lookup
fails is
On Nov 19, 2013, at 5:50, bitozoid wrote:
>
> I'm getting a TLS timeout (4.4.2) when connecting to the smarthost
> (port 465).
Port 465 is a legacy port and was only ever used by Outlook, as I recall. It is
generally not supported by other MUAs, and I seriously doubt any MUA that is
using it w
On 11/19/2013 7:50 AM, bitozoid wrote:
I'm getting a TLS timeout (4.4.2) when connecting to the smarthost
(port 465). If I try with no TLS (port 25) it connects and sends
emails.
I can successfully connect with 'openssl s_client ...' and this way it
says there is a 300 seconds timeout (same as i
I'm getting a TLS timeout (4.4.2) when connecting to the smarthost
(port 465). If I try with no TLS (port 25) it connects and sends
emails.
I can successfully connect with 'openssl s_client ...' and this way it
says there is a 300 seconds timeout (same as in the log below).
My postconf -n: http:/
>>> Hello,
>>>
>>> My understanding was clients for whom you see this in the logs:
>>>
>>> connect from unknown[1.2.3.4]
>>>
>>> Do not have a PTR/rDNS set up for themselves.
>>
>> For Postfix to include the rDNS in the log and Received: header, the PTR
>> name must then resolve back
> On Monday, November 18, 2013 7:57 AM, Kris Deugau wrote:
> > E.B. wrote:
>
>> Hello,
>>
>> My understanding was clients for whom you see this in the logs:
>>
>> connect from unknown[1.2.3.4]
>>
>> Do not have a PTR/rDNS set up for themselves.
>
> For Postfix to include the rDNS in
12 matches
Mail list logo
