possible at all?
Thanks a lot,
Andy.
--
BAYERISCHER RUNDFUNK | Programmbereich Multimedia und Jugend
Dr. Andy Spiegl | mailto:andy.spi...@br-online.de
Rundfunkplatz 1 | Fon +49 (0)89 5900 16062
D-80335 Muenchen | Fax +49 (0)89 5900 16120
ve is the list of valid LOCAL recipients. Everything else I
have to relay to the MX of example.com...
Thanks,
Andy.
--
BAYERISCHER RUNDFUNK | Programmbereich Multimedia und Jugend
Dr. Andy Spiegl | mailto:andy.spi...@br-online.de
Rundfunkplatz 1 | Fon +49 (0)89 5900 16062
D-803
virtual-alias.domain anything entry is required for a
virtual alias domain. Without this entry, mail is rejected
with "relay access denied", or bounces with "mail loops
back to myself".
Thanks,
Andy.
--
BAYERISCHER RUNDFUNK | Programmbereich Multi
On 2009-02-11, 09:32, Noel Jones wrote:
> Andy Spiegl wrote:
>
>> Hm, but I don't have the list of valid recipients. :-(
>>
>> All I have is the list of valid LOCAL recipients. Everything else
>> I have to relay to the MX of example.com...
>
> If the re
Hi,
I'd like to configure postfix to accept recipient addresses like
foo.u...@domain
bar.u...@domain
baz.u...@domain
without defining an alias for each address.
If I understand the manual right the recipient_delimiter variable is
not good for this. Can you guys give me a hint on how this can
> More specifically, "u...@example.com" is a defined email address and
> you want to accept all "prefix.u...@example.com" variants for valid
> users and arbitrary prefixes?
Exactly!
> Well, it is not really an "extension", rather a prefix.
Oops, you are right of course.
> You need a "tcp table",
On 2011-01-11, 18:17, Victor Duchovni wrote:
> Postfix recipient validation works by locating valid user addresses
> in a suitable (address-class dependent) lookup table. Additionally,
> regardless of the address class, the virtual(5) table can alias an
> arbitrary recipient to one or more (hopeful
On 2011-01-29, 22:06, mouss wrote:
> > I set:
> > virtual_alias_maps = regexp:/etc/postfix/virtual_alias_regexp
> > and this file contains patterns like these:
> >
> > /^user@example\.com$/ u...@example.com
> > /.*\.user@example\.com$/ u...@example.com
>
> th
> dovecot_destination_recipient_limit = 1
I had this option in main.conf already.
Why did "postconf -n" not list it? Not even "postconf" does, uhm...
> if it still doesn't work, tell us how you defined the "dovecot"
> transport? is it a pipe based transport in master.cf?
Exactly.
dovecot unix
> the postconf command doesn't show "custom" variables, and
> {foobar}_destination_recipient_limit is a custom var.
Oh, I see.
> It's up to you. as far as your return a DSN, be it "relayed" or
> "delivered", I'd say it's ok. DSN seems to cause lot of debates. so
> let's not get into that trap!
:-)
10 matches
Mail list logo