Victor Duchovni schrieb:
I can't honestly recommend anything other than start with the
default:
I suspect, you are right :)
After another check of my logfiles, i reduced my restriction lists
to the following:
smtpd_client_restrictions = reject_unknown_reverse_client_hostname,
check_clien
Hello,
i read the documentation about the usage of "[" and "]" in relayhost
entries ...
I still not quite sure what happens or not happens when using an IP with
or without such signs...
relayhost = 1.2.3.4
may use MX records from DNS?
What if there is no nameserver configured? Will there be
As older postfix installations have a "fallback_relay" variable and
newer installations have a "smtp_fallback_relay", i wanted to use
postconf to check, which version is supported.
Usally, i would expect a program to return with a non-zero exit-code at
such a failure:
r...@localhost# postcon
Wietse Venema schrieb:
That is a bug in your operating system.
That made me test all of them :)
I used several runs of "ping" against the hostname after including it
with two entries into /etc/hosts
Cannot use "getaddrinfo" ...
Solaris 8 and 9:
Only uses the first IP in /etc/hosts (with "
Eddy Beliveau schrieb:
I know that I can try to find all individual combinations
and write them in some reject file to be used in check_recipient_access
Is there some way to define a rule based on phonetic
or another solution which detect mispelled words ?
I would recommend against that idea :
Maybe i should better explain the reasons behind this question:
We have some domains, where the mail-relay is mapped to several
IP-Adresses (and servers) over an DNS entry.
That is, we have ONE mailrelay that can be configured as relayhost.
So far, so good.
BUT, we also have systems without D
Hello,
normally, you can say "relayhost = domain" and postfix searches the MX
record for that domain in DNS to get the list of relayhosts.
For domains where no MX record is configured into the DNS, i would need
to use more than one relayhost ...
Is that possible?
The configuration seems not
Brian Evans - Postfix List schrieb:
'Postconf -d' means "show me the DEFAULTS not what is current".
Uh..
I already feared a realy stupid mistake on my side :)
I used it in this sense, so far - but assumed that this default will be
overwritten (and displayed) when actually set in main.cf
S
Ralf Hildebrandt schrieb:
postconf -n shows main.cf settings, not master.cf settings
Why not use:
postconf -e "smtpd_client_restrictions=reject_invalid_hostname"
But as far as i understand, this just sets the variable in main.cf - and
there, it is already included!
To show this:
r...@l
Hello,
i seem to be unable to set the "smtpd_client_restrictions" Variable!
In master.cf, there is an option for smtps that sets this to
"permit_sasl_authenticated,reject".
In main.cf, i try to set this to "reject_invalid_hostname".
In "postconf -n" the variable is empty!
So, i assume that th
Hello,
i use the recipient_delimiter (with a ".") quite often.
Some of those sub-recipients(?) of accounts are already spammed.
I would like to reject Mails to them ...
For example:
name.post...@$mydomain would be OK, while
name.s...@$mydomain should be rejected ...
What is the best way to con
Rocco Scappatura schrieb:
myhostname =
mydomain =
If the hostname is not valid, postfix fails to start. It have to be
resolved by DNS and the IP must be the IP of one of the interface of
the server which run Postfix.
So I have to use a name that is resolved in many different IPs,
Hello,
i am running postfix 2.4.5 on a OpenSuse 10.3 Linux server.
I think, i have done everything right to chroot most postfix service.
But i cannot proove or even see this!
My main.cf contains the following:
smtpsinet n - y - - smt
13 matches
Mail list logo
