Re: Role of the (at) account

Ryan Delany <ryanrynogear.com>

> Our SLES10 server running postfix/SA/amavisd-maia was recently converted
> to virtual users and domains. After rebuilding our Maia databases users
> can now login and view their spam and ham quarantines. However it appears
&gt; that outgoing mail is either being dropped or held within the (at) account
&gt; if i enable that account to accept mail for non-local users. Setting up
> the (at) account to only accept for local users, outgoing mail from our
> domains is no longer cached. I thought that we could cache outgoing mail
> prior to converting to virtual users, but I might not understand the role
> of the (at) account. Any insight on how, if possible, I can get the
> domains to cache outbound email?

My understanding is that the (at) domain is a catch-all for any mail with
a DESTINATION that doesn't match a defined domain within Maia, if enabled
(see Should the System Default user (.) only catch mail for local
recipients? in System Configuration). By definition, outbound mail will
never have a matching domain on YOUR server, so the only place it can go
is the (at) domain.

As an example, if you define domain1.com as a domain you accept mail for,
only messages TO domain1.com addresses will end up in that users cache.
If someone FROM domain1.com sends an address to yahoo.com, and it goes
through your server, it's going to end up in the (at) users folder since
you obviously don't process inbound mail for yahoo.com. On the other
hand, if you filter for domain1.com and domain2.com, and someone from
domain1.com sends to domain2.com, then I would expect the sent mail to
be cached in the domain2.com's cache (since it's inbound and you process
mail for that domain). The important thing to note is that the only mail
that gets cached for any domain is inbound mail.

Maybe Robert/David can jump in if that isn't the case.

Regards,

Ryan