Thanks it solved the problem
:)
--
View this message in context:
http://postfix.1071664.n5.nabble.com/unable-to-send-email-TLS-not-offered-by-host-tp74498p74555.html
Sent from the Postfix Users mailing list archive at Nabble.com.
On 2/5/2015 5:06 PM, wie...@porcupine.org (Wietse Venema)
wrote:
> Charles Marcus:
>> Ok... but... this sounds like you are saying that it is expected that my
>> simple postmap -q test would fail, but that someone attempting to relay
> I am saying that you should RTFM the access(5) manpage and ma
Charles Marcus:
> >user@domain
> > Matches the specified mail address.
> >domain.tld
> > Matches domain.tld as the domain part of an email address.
> >.domain.tld
> > Matches subdomains of domain.tld, but only when the ...
> >
On 6. feb. 2015 13.49.31 Charles Marcus wrote:
I had found some $random examples when googling that suggested I should
be able to do this with a simple access map. Guess they were wrong.
possible a single access map can be used in multiple restrictions ?, just
guessing :)
its not always si
On 2/6/2015 8:26 AM, wie...@porcupine.org (Wietse Venema)
wrote:
> Charles Marcus:
>>>user@domain
>>> Matches the specified mail address.
>>>domain.tld
>>> Matches domain.tld as the domain part of an email address.
>>>.domain.tld
>>>
Am 06.02.2015 um 14:43 schrieb Charles Marcus:
Well... ok, so now I just have to figure out what I'm missing/doing wrong.
Hmmm... ok, just moved it from smtpd_relay_restrictions to
submission_client_restrictions and it works now...
But it still looks to me like it should have worked when call
Am 06.02.2015 um 14:52 schrieb li...@rhsoft.net:
Am 06.02.2015 um 14:43 schrieb Charles Marcus:
Well... ok, so now I just have to figure out what I'm missing/doing
wrong.
Hmmm... ok, just moved it from smtpd_relay_restrictions to
submission_client_restrictions and it works now...
But it still
On 2/6/2015 8:58 AM, li...@rhsoft.net wrote:
> and BTW one reason more to make a transport
> it is not affected by other restrictions
>
> it just comes at the end of the chain when postfix now would accept the
> message even by a explicit OK in any restriction table
>
> http://www.postfix.org/tra
On 2/6/2015 8:52 AM, li...@rhsoft.net wrote:
> it's simple
>
> * if there is any permit in front - well
> * if you are using specific "submission_client_restrictions"
>and have placed the access table in front of any permit it
>works
>
> in that context postfix is dead-simple
>
> the f
wie...@porcupine.org (Wietse Venema) wrote:
LuKreme:
On 05 Feb 2015, at 05:07 , Wietse Venema wrote:
Have you considered the possibility that the mail was sent with a
bogus Delivered-To: header (i.e. the header is present, but not
added by Postfix).
Yes, but I'm unsure how to diagnose that.
> On 05 Feb 2015, at 15:53 , Wietse Venema wrote:
>
> LuKreme:
>> On 05 Feb 2015, at 05:07 , Wietse Venema wrote:
>>> Have you considered the possibility that the mail was sent with a
>>> bogus Delivered-To: header (i.e. the header is present, but not
>>> added by Postfix).
>>
>> Yes, but I'm
Only other thing I can think of is that this is somehow related to always_bcc?
--
A dyslexic walks into a bra...
LuKreme:
>
> > On 05 Feb 2015, at 15:53 , Wietse Venema wrote:
> >
> > LuKreme:
> >> On 05 Feb 2015, at 05:07 , Wietse Venema wrote:
> >>> Have you considered the possibility that the mail was sent with a
> >>> bogus Delivered-To: header (i.e. the header is present, but not
> >>> added by Postf
On 06 Feb 2015, at 15:05 , Wietse Venema wrote:
> NORMALLY, that header is present AFTER mail is delivered to b...@covisp.net.
>
> If it is present BEFORE mail is delivered to b...@covisp.net, then you have
> a loop (or the sender has added this header to trigger an error).
Ah, right. I’ve added
14 matches
Mail list logo
