Not right yet - Re: amavis question

[Robert Moskowitz <rg...@htt-consult.com>]

On 11/20/2014 07:45 AM, Robert Moskowitz wrote:
> Looks like I left out all the mysql stuff from amavis.conf that I had 
> in my old server.  Sigh.  I now have to reconcile the differences and 
> figure this out.

I am now seeing in the maillog:

Nov 20 08:36:20 z9m9z postfix/error[2698]: C379D620F2: 
to=<re...@communaljob.com>, relay=none, delay=3.7, 
delays=1.4/1.1/0/1.2, dsn=4.4.2, status=deferred (delivery temporarily 
suspended: lost connection with 127.0.0.1[127.0.0.1] while sending DATA 
command)

MIght be a firewalld issue with:

@lookup_sql_dsn =
    ( ['DBI:mysql:database=postfix;host=127.0.0.1;port=3306', 'postfix', 
'password'] );


>
> On 11/20/2014 06:21 AM, Robert Moskowitz wrote:
>> Don't know where better to ask this...
>>
>> I am running a new mailserver virtual domain environment with postfix 
>> and mysql for the virtual domain definitions. amavis-new seems to be 
>> rejecting all emails for my one domain not a sub domain of my main 
>> one.  That is, my domain (as you can see from my email addr) is 
>> htt-consult.com and I have not problems processing emails for 
>> labs.htt-consult.com addresses. However I am seeing in the logwatch 
>> email in the amavis-new section:
>>
>>  **Unmatched Entries**
>>         1   (26010-02-3) Open relay? Nonlocal recips but not 
>> originating:resume@communaljob.com
>>         1   (27713-04-4) Open relay? Nonlocal recips but not 
>> originating:resume@communaljob.com
>>         1   (24487-05-4) Open relay? Nonlocal recips but not 
>> originating:resume@communaljob.com
>>         1   (26339-01-2) Open relay? Nonlocal recips but not 
>> originating:resume@communaljob.com
>>         1   (27916-03-3) Open relay? Nonlocal recips but not 
>> originating:resume@communaljob.com
>>
>>
>>
>> Messages a plenty.
>>
>> No spamassasin section in logwatch, interestingly. Where do I allow 
>> this to work?
>>
>>
>
>

Maybe solved - Re: Not right yet - Re: amavis question

[Robert Moskowitz <rg...@htt-consult.com>]

Will probably have to wait some time to ensure all is now together.

On 11/20/2014 08:46 AM, Robert Moskowitz wrote:
>
> On 11/20/2014 07:45 AM, Robert Moskowitz wrote:
>> Looks like I left out all the mysql stuff from amavis.conf that I had 
>> in my old server.  Sigh.  I now have to reconcile the differences and 
>> figure this out.
>
> I am now seeing in the maillog:
>
> Nov 20 08:36:20 z9m9z postfix/error[2698]: C379D620F2: 
> to=<re...@communaljob.com>, relay=none, delay=3.7, 
> delays=1.4/1.1/0/1.2, dsn=4.4.2, status=deferred (delivery temporarily 
> suspended: lost connection with 127.0.0.1[127.0.0.1] while sending 
> DATA command)
>
> MIght be a firewalld issue with:
>
> @lookup_sql_dsn =
>    ( ['DBI:mysql:database=postfix;host=127.0.0.1;port=3306', 
> 'postfix', 'password'] );

Also needed:

$sql_select_policy = 'SELECT domain from domain WHERE CONCAT("@",domain) 
IN (%k)';


>
>
>>
>> On 11/20/2014 06:21 AM, Robert Moskowitz wrote:
>>> Don't know where better to ask this...
>>>
>>> I am running a new mailserver virtual domain environment with 
>>> postfix and mysql for the virtual domain definitions. amavis-new 
>>> seems to be rejecting all emails for my one domain not a sub domain 
>>> of my main one.  That is, my domain (as you can see from my email 
>>> addr) is htt-consult.com and I have not problems processing emails 
>>> for labs.htt-consult.com addresses. However I am seeing in the 
>>> logwatch email in the amavis-new section:
>>>
>>>  **Unmatched Entries**
>>>         1   (26010-02-3) Open relay? Nonlocal recips but not 
>>> originating:resume@communaljob.com
>>>         1   (27713-04-4) Open relay? Nonlocal recips but not 
>>> originating:resume@communaljob.com
>>>         1   (24487-05-4) Open relay? Nonlocal recips but not 
>>> originating:resume@communaljob.com
>>>         1   (26339-01-2) Open relay? Nonlocal recips but not 
>>> originating:resume@communaljob.com
>>>         1   (27916-03-3) Open relay? Nonlocal recips but not 
>>> originating:resume@communaljob.com
>>>
>>>
>>>
>>> Messages a plenty.
>>>
>>> No spamassasin section in logwatch, interestingly. Where do I allow 
>>> this to work?
>>>
>>>
>>
>>
>
>