Some guesses below; hopefully an expert will eventually chime in.
On Wed, 2014-03-12 at 06:18:37 -0700, jmct wrote:
> ...
> When I try sending a basic test e-mail through PowerShell using my Postfix
> box as the SMTP server - I'm seeing 20-40+ second delays in the
> /var/log/maillog per e-mail.
>
On Wed, Mar 12, 2014 at 05:28:38PM +0530, tejas sarade wrote:
>> how should that be possible?
>> the hostname the client pretends?
>> how could you trust that?
>> how could you trust any hostname?
>> there is nothing else trustable than the connecting real IP
>
>No. Not the
Hello,
I have recently spun up a Postfix server that is currently in a testing
phase. It is currently not being used at the moment - so there is zero load
on this server.
I am actively using Postfix 2.11, SpamAssassin 3.3.1 and Dovecot 2.0.9 for
POP3.
When I try sending a basic test e-mail throu
tejas sarade:
> I just want to creat and access control system where I will provide the
> list of valid hostname(FQDN).
> Postfix will lookup the IP of that FQDN through public DNS and consider
> that IP as trusted IP.
Access control by hostname is not reliable if you rely on remote
DNS servers.
-
Am 12.03.2014 12:58, schrieb tejas sarade:
>> how should that be possible?
>> the hostname the client pretends?
>> how could you trust that?
>> how could you trust any hostname?
>> there is nothing else trustable than the connecting real IP
>
> No. Not the hostname that client pretends, I am talki
> how should that be possible?
> the hostname the client pretends?
> how could you trust that?
> how could you trust any hostname?
> there is nothing else trustable than the connecting real IP
No. Not the hostname that client pretends, I am talking about valid DNS A
record throuch DNS lookup.
>
>
Am 12.03.2014 12:06, schrieb tejas sarade:
> I want to allow a machine with dynamic IP address but static hostname through
> DynDNS.
> I know that hostname in smtpd_client_restricions works only through reverse
> DNS lookup.
> Is there any way, I can allow the client based on hostname which has
Hello,
I want to allow a machine with dynamic IP address but static hostname
through DynDNS.
I know that hostname in smtpd_client_restricions works only through reverse
DNS lookup.
Is there any way, I can allow the client based on hostname which has
dynamic IP?
On 11.3.2014, at 23.42, Eino Tuominen wrote:
> The listdelivery instance then expands the list using virtual(8), and then
> sends the message back to the main postfix instance via relayhost =
> [127.0.0.1]:10026.
Just found a flaw in my line of thought. This doesn’t work as expected as
virt
Hello All
Thank you for all your replies. I will put my solution below (just in
case someone other stumbles over it).
On 03/04/2014 04:32 PM, Noel Jones wrote:
> However, you can do this with either a smtpd restriction class or
> with a policy server such as postfwd.
> http://www.postfix.org/REST
10 matches
Mail list logo