Am 07.05.2013 09:00, schrieb Josef Karliak:
> Ohh. So there is only one solution - on mail server generate an alias
> list that contains aliases and result. Like :
>
> chose OK
> user OK
> ...
> ...
>
>
> And in main.cf use directive
> smtpd_recipient_restrictions = ,check_recipient_access
Ohh. So there is only one solution - on mail server generate an
alias list that contains aliases and result. Like :
chose OK
user OK
...
...
And in main.cf use directive
smtpd_recipient_restrictions = ,check_recipient_access
hash:/etc/postfix/alias_list,
So we'll generate aliases
Josef Karliak:
>Hi,
>thanks for tip. I may be something missed:
>In main.cf I've added:
> address_verify_relayhost = 19.13.13.11 #ip of my mail server that
> knows all users
> address_verify_sender = mas...@mojedomena.cz
This overrides the "relayhost" setting, which is used ONLY for
Am 06.05.2013 15:08, schrieb Josef Karliak:
> communication between this incoming server and final imap server
at my knwoledge this dont work verify is done over smtp, you may ask for
relay permit ,over imap via saslauthd
Best Regards
MfG Robert Schetterer
--
[*] sys4 AG
http://sys4.de, +49 (
Hi,
thanks for tip. I may be something missed:
In main.cf I've added:
address_verify_relayhost = 19.13.13.11 #ip of my mail server that
knows all users
address_verify_sender = mas...@mojedomena.cz
communication between this incoming server and final imap server
(between them is anti
On 4/19/2013 1:28 AM, Tom Hendrikx wrote:
> Last time I read ADDRESS_VERIFICATION_README, I noticed that this isn't
> true: you can route your probes to the final delivery machine while
> leaving the current delivery mechanism intact:
> http://www.postfix.org/ADDRESS_VERIFICATION_README.html#probe
On 04/19/2013 12:07 AM, Stan Hoeppner wrote:
> On 4/18/2013 4:26 AM, Mikael Bak wrote:
>> Hi Josef,
>>
>> On 04/18/2013 11:06 AM, Josef Karliak wrote:
>>> Good morning,
>>> our outgoing smtp server gets into a backscatter blacklist. When I
>>> checked my logs, there were only one mailer daemon
On 4/18/2013 4:26 AM, Mikael Bak wrote:
> Hi Josef,
>
> On 04/18/2013 11:06 AM, Josef Karliak wrote:
>> Good morning,
>> our outgoing smtp server gets into a backscatter blacklist. When I
>> checked my logs, there were only one mailer daemon email to some server
>> in the time that is mentione
On 04/18/2013 12:20 PM, Josef Karliak wrote:
> Hi,
> thanks for reply. We thought that we have to copy existing "aliases"
> file from imap server to incoming MX. If we reject an emailduring smtp
> communication, we won't "relay" spam to victim. Am I right ?
> Best regards
> J.K.
>
Hi,
Ple
Hi,
thanks for reply. We thought that we have to copy existing
"aliases" file from imap server to incoming MX. If we reject an
emailduring smtp communication, we won't "relay" spam to victim. Am I
right ?
Best regards
J.K.
Cituji Mikael Bak :
Hi Josef,
On 04/18/2013 11:06 AM, Jo
Hi Josef,
On 04/18/2013 11:06 AM, Josef Karliak wrote:
> Good morning,
> our outgoing smtp server gets into a backscatter blacklist. When I
> checked my logs, there were only one mailer daemon email to some server
> in the time that is mentioned on the backscatter web.
> In all servers in th
Good morning,
our outgoing smtp server gets into a backscatter blacklist. When I
checked my logs, there were only one mailer daemon email to some
server in the time that is mentioned on the backscatter web.
In all servers in the way of the email (incoming MX->antispam
server-> our imap
12 matches
Mail list logo
