-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 30, 2011, at 2:08 PM, Noel Jones wrote:
> On 3/30/2011 3:53 PM, Ansgar Wiechers wrote:
>> On 2011-03-30 Corey Quinn wrote:
>>> On Mar 30, 2011, at 12:46 PM, Noel Jones wrote:
>>>> # main.cf
>>>> smt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 30, 2011, at 1:29 PM, Wietse Venema wrote:
> Corey Quinn:
>> On Mar 30, 2011, at 12:46 PM, Noel Jones wrote:
>>>
>>> # main.cf
>>> smtp_generic_maps =
>>> regexp:/etc/postfix/generic.regexp
>&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 30, 2011, at 1:16 PM, Nick Dokos wrote:
> The following problem started happening on March 24 and it has not stopped
> since.
> every 30 seconds somebody does the following:
>
> Mar 24 10:43:38 XX postfix/smtpd[5905]: connect from
> loc
On Mar 30, 2011, at 12:46 PM, Noel Jones wrote:
>
> # main.cf
> smtp_generic_maps =
> regexp:/etc/postfix/generic.regexp
>
> # generic.regexp
> IF /+.*@example\.com$/
> /^(.*)+/ $1...@example.com
> ENDIF
Threw this verbatim into my generic.regexp:
[root@mx1 postfix]# postmap -q "user+t...@ex
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 30, 2011, at 9:35 AM, Clayton Keller wrote:
> I would like to allow the use of the recipient_delimiter, but rewrite the
> address to ensure that it is delivered to the original address.
>
> i.e. clay+t...@domain.tld -> c...@domain.tld
I'm a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 23, 2011, at 11:52 PM, Etienne Pretorius wrote:
> Hello List,
>
> I have a email address say staff@domain that maps perfectly to all its
> intended recipients,
> but on the same machine I have user1@domain that is suppose to map to
> user1@
On Feb 21, 2011, at 4:09 PM, Jean-Francois Cantin wrote:
> We recently ditched M$Exchange
Don't do that. It doesn't reflect well upon you.
> and went to googleApps. Unfortunately we have some windows servers that need
> to send notification emails, but can't use TLS.
I suspect you mean SASL;
