Le 02/03/2012 04:24, Karol Babioch a écrit :
> Hi,
>
> I'm pretty sure that this was asked for already, but I couldn't
> find anything useful with the keywords I was using. I've tried to
> play with some configurations, but couldn't find a reliable
> solution so far.
>
> I will explain what I'm t
On 3/3/2012 12:48 πμ, Karol Babioch wrote:
So, when I understand this right, it is not possible to define common
aliases for all virtual domains?
You may also want to read this thread:
http://tech.groups.yahoo.com/group/postfix-users/message/267828
Regards,
Nick
Karol Babioch:
> Hi,
>
> Am 02.03.2012 23:32, schrieb Wietse Venema:
> > Postfix will not look in alias_maps when the domain is not listed
> > in mydestination.
>
> So, when I understand this right, it is not possible to define common
> aliases for all virtual domains? Because virtual domains won
On Fri, Mar 02, 2012 at 11:48:09PM +0100, Karol Babioch wrote:
> Am 02.03.2012 23:32, schrieb Wietse Venema:
> > Postfix will not look in alias_maps when the domain is not
> > listed in mydestination.
>
> So, when I understand this right, it is not possible to
> define common aliases for all virtu
Hi,
Am 02.03.2012 23:32, schrieb Wietse Venema:
> Postfix will not look in alias_maps when the domain is not listed
> in mydestination.
So, when I understand this right, it is not possible to define common
aliases for all virtual domains? Because virtual domains won't be listed
within $mydestinat
Karol Babioch:
> Hi,
>
> Am 02.03.2012 22:33, schrieb Reindl Harald:
> > theonly thing what is stronlgy recommended to match
> > is A-Record and PTR of the machine
>
> Ok, maybe I've mixed something up here :). Thanks for your replies.
>
> I've got it running now. However I've now got the proble
Hi,
Am 02.03.2012 22:33, schrieb Reindl Harald:
> theonly thing what is stronlgy recommended to match
> is A-Record and PTR of the machine
Ok, maybe I've mixed something up here :). Thanks for your replies.
I've got it running now. However I've now got the problem that my
alias_maps doesn't get
Am 02.03.2012 22:19, schrieb Noel Jones:
> On 3/2/2012 3:08 PM, Karol Babioch wrote:
>> Hi,
>>
>> Am 02.03.2012 22:02, schrieb Charles Marcus:
>>> What is your concern?
>>
>> to get flagged as spam without no other reason ;)?
>>
>> Best regards,
>> Karol Babioch
>>
>
> Any anti-spam system that
On 2012-03-02 4:19 PM, Noel Jones wrote:
On 3/2/2012 3:08 PM, Karol Babioch wrote:
Am 02.03.2012 22:02, schrieb Charles Marcus:
What is your concern?
to get flagged as spam without no other reason ;)?
Any anti-spam system that flags mail only because the sending
hostname doesn't match the
On 3/2/2012 3:08 PM, Karol Babioch wrote:
> Hi,
>
> Am 02.03.2012 22:02, schrieb Charles Marcus:
>> What is your concern?
>
> to get flagged as spam without no other reason ;)?
>
> Best regards,
> Karol Babioch
>
Any anti-spam system that flags mail only because the sending
hostname doesn't ma
Hi,
Am 02.03.2012 22:02, schrieb Charles Marcus:
> What is your concern?
to get flagged as spam without no other reason ;)?
Best regards,
Karol Babioch
signature.asc
Description: OpenPGP digital signature
On 2012-03-02 3:56 PM, Karol Babioch wrote:
Am 02.03.2012 19:02, schrieb Charles Marcus:
You are mistaken.
Could you elaborate on that please? Its definitely a common way of
dealing with spam to check whether the PTR record points to the domain,
which the mailserver claims to work for.
>
W
Hi,
Am 02.03.2012 19:02, schrieb Charles Marcus:
> You are mistaken.
Could you elaborate on that please? Its definitely a common way of
dealing with spam to check whether the PTR record points to the domain,
which the mailserver claims to work for.
When my PTR record points to "example.com", but
On 2012-03-02 12:53 PM, Karol Babioch wrote:
That's exactly what I'm trying to prevent, because the PTR record for
this IP points to "example.com". I'm guessing I'm getting into trouble
when there is a mismatch, because its standard procedure when trying to
block spam.
You are mistaken.
--
B
Hi,
Am 02.03.2012 18:51, schrieb Charles Marcus:
> name it mail.example.com, or smtp.example.com, or something like that.
> Then local mail is the form u...@mail.example.com, instead of
> u...@example.com.
That's exactly what I'm trying to prevent, because the PTR record for
this IP points to "ex
On 2012-03-02 12:46 PM, Karol Babioch wrote:
thanks for your reply. However I'm not quite sure whether I've
understood your advice in the right way. What value would $myhostname
have in the above example? Because when I set $myhostname to
"example.com"
example.com is a FQDN, not a hostname.
Hi,
Am 02.03.2012 10:26, schrieb Ansgar Wiechers:
> True, and the recommended way of handling things. However, the "main"
> domain of the server can be the server itself, and you can restrict the
> valid local mailboxes via $local_recipient_maps:
>
> 8<
> mydestination = $myhostname
> loc
On 2012-03-02 Karol Babioch wrote:
> I've got a server, which can be found at the domain "example.com"
> (including a PTR record for reverse DNS lookups).
>
> Now I want to run a mailserver for "example.com", but I don't want to
> create local users, but instead use virtual mailboxing.
>
> Furthe
Hi,
I'm pretty sure that this was asked for already, but I couldn't find
anything useful with the keywords I was using. I've tried to play with
some configurations, but couldn't find a reliable solution so far.
I will explain what I'm trying to do with two example domains:
I've got a server, whi
19 matches
Mail list logo
