Re: Maia-users Digest, Vol 172, Issue 18

Confirmed that was it, son of a gun! Now looks like my only other
issue seems to be my process-quarantine.pl script is not happy for
some reason keeps barking at me. Any ideas? Thank you very much for
all your help.

[root@manny scripts]# ls -al

total 308

drwxr-xr-x  2 maia maia  4096 Apr 29 01:15 .

drwxrwxrwx 11 maia maia  4096 May 14 16:22 ..

-rwxr-xr-x  1 maia maia 23037 Apr 28 13:12 configtest.pl

-rwxr-xr-x  1 maia maia   927 Apr 28 13:12 detectvba.pl

-rwxr-xr-x  1 maia maia 36156 Apr 28 13:12 expire-quarantine-cache.pl

-rwxr-xr-x  1 maia maia 22586 Apr 28 13:12 load-sa-rules.pl

-rwxr-xr-x  1 maia maia 79071 Apr 28 13:12 maiadbtool.pl

-rwxr-xr-x  1 maia maia 53339 Apr 28 13:12 process-quarantine.pl

-rwxr-xr-x  1 maia maia 12534 Apr 28 13:12 resend.pl

-rwxr-xr-x  1 maia maia 17939 Apr 28 13:12 send-quarantine-digests.pl

-rwxr-xr-x  1 maia maia 19310 Apr 28 13:12 send-quarantine-reminders.pl

-rwxr-xr-x  1 maia maia 14234 Apr 28 13:12 stats-snapshot.pl

-rw-r--r--  1 root root    23 Apr 29 01:15 user.txt

[root@manny scripts]# su maia

[maia@manny scripts]$ ./process-quarantine.pl

Subroutine DBI::db::mysql_fd redefined at
/usr/local/lib64/perl5/DBI.pm line 1403.

Subroutine DBI::db::mysql_async_result redefined at
/usr/local/lib64/perl5/DBI.pm line 1403.

Subroutine DBI::db::mysql_async_ready redefined at
/usr/local/lib64/perl5/DBI.pm line 1403.

Subroutine DBI::st::mysql_async_result redefined at
/usr/local/lib64/perl5/DBI.pm line 1403.

Subroutine DBI::st::mysql_async_ready redefined at
/usr/local/lib64/perl5/DBI.pm line 1403.

Use of uninitialized value $autolearn_status in pattern match (m//) at
./process-quarantine.pl line 1397.

Use of uninitialized value $autolearn_status in pattern match (m//) at
./process-quarantine.pl line 1398.

Subroutine DBI::db::mysql_fd redefined at
/usr/local/lib64/perl5/DBI.pm line 1403.


-Manny

On Sat, May 16, 2020 at 2:23 PM jjs - mainphrame <[email protected]> wrote:
>
> Ah, very interesting, I forgot about the MTA, that's something I hadn't thought about since we default to postfix.
>
> That info could prove valuable for any other site using maia with exim.
>
> Jale
>
>
>
> On Sat, May 16, 2020 at 11:19 AM Manny Marinho <[email protected]> wrote:
>>
>> You're not kidding. Yesterday I thought maybe it was something in the
>> spamassassin config but I didn't find anything there. Just now I was
>> thinking maybe it's my MTA, Exim. Looks like exim added the following
>> to the exim.conf recently and this is most likely it, I just commented
>> it out and am waiting for some messages to confirm.
>>
>>
>> #BEGIN ACL-SPAM-SCAN-BLOCK
>>
>> # BEGIN INSERT default_spam_scan
>>
>>
>>   warn
>>
>>      # Remove spam headers from outside sources
>>
>>      condition = ${perl{spamd_is_available}}
>>
>>      !hosts = +skipsmtpcheck_hosts
>>
>>      remove_header  = x-spam-subject : x-spam-status : x-spam-score :
>> x-spam-bar : x-spam-report : x-spam-flag : x-ham-report
>>
>>
>>
>>   warn
>>
>>     condition = ${perl{spamd_is_available}}
>>
>>     condition = ${if eq {${acl_m0}}{1}{1}{0}}
>>
>>     spam =  ${acl_m1}/defer_ok
>>
>>     # Always make sure cPanel support mail can get through
>>
>>     !hosts = : +trustedmailhosts : +cpanel_mail_netblocks
>>
>>     log_message = "SpamAssassin as ${acl_m1} detected message as spam
>> ($spam_score)"
>>
>>     # add_header = X-Spam-Subject: ***SPAM*** $rh_subject
>>
>>     add_header = X-Spam-Status: Yes, score=$spam_score
>>
>>     add_header = X-Spam-Score: $spam_score_int
>>
>>     add_header = X-Spam-Bar: $spam_bar
>>
>>     add_header = X-Spam-Report: ${sg{$spam_report}{\N\n \n\N}{\n}}
>>
>>     add_header = X-Spam-Flag: YES
>>
>>     set acl_m2 = 1
>>
>>
>> -Manny
>>
>> On Sat, May 16, 2020 at 2:10 PM jjs - mainphrame <[email protected]> wrote:
>> >
>> > Curiouser and curiouser, maia is told not to alter the subject, and yet if a spam message passes through your system now, the subject is altered? There's a conundrum there, and I'm not sure what could cause a disconnect like that.
>> >
>> > Jake
>> >
>> > On Sat, May 16, 2020 at 11:01 AM Manny Marinho <[email protected]> wrote:
>> >>
>> >> Yes N for all.
>> >>
>> >> On Sat, May 16, 2020 at 1:53 PM jjs - mainphrame <[email protected]> wrote:
>> >> >
>> >> > How about the column to the left of the one that shows "1 for all"? Is it 'N' for all?
>> >> >
>> >> > Jake
>> >> >
>> >> > On Sat, May 16, 2020 at 10:48 AM Manny Marinho <[email protected]> wrote:
>> >> >>
>> >> >> Looks like I get 60 rows back, first column show 1 for all, second
>> >> >> column 5 for all and third column 5 for all.
>> >> >>
>> >> >> On Sat, May 16, 2020 at 1:36 PM jjs - mainphrame <[email protected]> wrote:
>> >> >> >
>> >> >> > That shouldn't be happening, since the DB dictates that behavior. You do seem to come up with some interesting corner cases.
>> >> >> >
>> >> >> > I see you're allowing all spam for every protection level except for high, but if everyone's on high I guess that's academic.
>> >> >> >
>> >> >> > Just as a sanity check, you might run a query:
>> >> >> >
>> >> >> > MariaDB [maia]> select id,spam_modifies_subj,spam_tag_level,spam_tag2_level,spam_kill_level from policy;
>> >> >> >
>> >> >> > On this db, they all pretty much look like this, except for the superuser account:
>> >> >> >
>> >> >> > | 28 | N                  |           -999 |               5 |               5 |
>> >> >> >
>> >> >> > jake
>> >> >> >
>> >> >> > On Sat, May 16, 2020 at 10:19 AM Manny Marinho <[email protected]> wrote:
>> >> >> >>
>> >> >> >> Thank you! So I've made those changes and re-started the maia daemon
>> >> >> >> but I'm still seeing the subject being modified here's what I have now
>> >> >> >> for those lines:
>> >> >> >>
>> >> >> >>  $protection = array( 'off'     => array
>> >> >> >> ('Y','Y','Y','Y','Y','Y','Y','Y','N','N','N','N','N','999','999','999'),
>> >> >> >>
>> >> >> >>                          'low'     => array
>> >> >> >> ('N','Y','Y','Y','N','Y','Y','Y','N','N','N','N','N','999','999','999'),
>> >> >> >>
>> >> >> >>                          'medium'  => array
>> >> >> >> ('N','N','Y','Y','N','N','Y','Y','N','N','N','N','N','5','999','999'),
>> >> >> >>
>> >> >> >>                          'high'    => array
>> >> >> >> ('N','N','N','N','N','N','N','N','N','N','N','N','N','1','5','5')
>> >> >> >>
>> >> >> >>
>> >> >> >> Nothing is set in the DB right now either:
>> >> >> >>
>> >> >> >> MariaDB [maia]> select id,spam_modifies_subj from policy where
>> >> >> >> spam_modifies_subj = 'Y';
>> >> >> >>
>> >> >> >> Empty set (0.000 sec)
>> >> >> >>
>> >> >> >> All my users/domains are currently set to high protection level.
>> >> >> >>
>> >> >> >>
>> >> >> >> -Manny
>> >> >> >>
>> >> >> >> On Sat, May 16, 2020 at 12:09 PM jjs - mainphrame <[email protected]> wrote:
>> >> >> >> >
>> >> >> >> > Hi Manny,
>> >> >> >> >
>> >> >> >> > The option to alter the Subject line with the ***SPAM*** tag is in the policy table of the maia db, which can be modified based on the user selection of a protection level in the web interface.
>> >> >> >> >
>> >> >> >> > To verify, in the db:
>> >> >> >> >
>> >> >> >> > MariaDB [maia]> select id,spam_modifies_subj from policy where spam_modifies_subj = 'Y';
>> >> >> >> >
>> >> >> >> > You can set them all to not mark:
>> >> >> >> >
>> >> >> >> > MariaDB [maia]> update policy set spam_modifies_subj = 'N';
>> >> >> >> >
>> >> >> >> > There's a legacy setting in config.php, that has maia modify the subject line when the spam protection level is set to medium, which needs to be changed if you don't want a user to inadvertently set their preferences to alter the header. We'll change it in the repo, since we'll just quarantine the spam instead of marking it.
>> >> >> >> >
>> >> >> >> > Your config.php should look like this, around lines 163-167: (Last column before the numbers is the subject modify option, it should be "N")
>> >> >> >> >
>> >> >> >> >   $protection = array( 'off'     => array ('Y','Y','Y','Y','Y','Y','Y','Y','N','N','N','N','N','999','999','999'),
>> >> >> >> >                          'low'     => array ('N','Y','Y','Y','N','Y','Y','Y','N','N','N','N','N','999','999','999'),
>> >> >> >> >                          'medium'  => array ('N','N','Y','Y','N','N','Y','Y','N','N','N','N','N','-999','7','7'),
>> >> >> >> >                          'high'    => array ('N','N','N','N','N','N','N','N','N','N','N','N','N','-999','5','5')
>> >> >> >> >         );
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > Apologies for not catching the mysql error sooner. We just hadn't seen it in any vanilla builds until ubuntu 18.04
>> >> >> >> >
>> >> >> >> > Jake
>> >> >> >> >
>> >> >> >> > On Sat, May 16, 2020 at 8:23 AM Manny Marinho <[email protected]> wrote:
>> >> >> >> >>
>> >> >> >> >> So I finally got maia working on my new CentOS7 server but I also
>> >> >> >> >> encountered this autolearn_status error yesterday while creating a new
>> >> >> >> >> maia db which drove me nuts until I found this thread. I'm using mySQL
>> >> >> >> >> MARIA DB. I simply pulled the new maia-mysql.sql script from GitHub
>> >> >> >> >> and dropped/re-created the db manually with the the new SQL and that
>> >> >> >> >> issue is now resolved.
>> >> >> >> >>
>> >> >> >> >> TROUBLE in check_mail: deal_with_spam FAILED: DBD::mysql::st execute
>> >> >> >> >> failed: Column 'autolearn_status' cannot be null at ./maiad line 4410,
>> >> >> >> >> <GEN8> line 3242.
>> >> >> >> >>
>> >> >> >> >> After many months of being down I finally have a working maia setup,
>> >> >> >> >> thanks Jake and all others that assisted! One odd thing I'm seeing
>> >> >> >> >> which I've never seen before is that for messages that are in the spam
>> >> >> >> >> cache all messages for all domains/users are getting the subject
>> >> >> >> >> re-written with ***SPAM*** and I can't figure out how to disable this.
>> >> >> >> >> I see the purpose of it but I don't want to use it as it will cause
>> >> >> >> >> confusion for my users.
>> >> >> >> >>
>> >> >> >> >> -Manny
>> >> >> >> >>
>> >> >> >> >> On Wed, May 13, 2020 at 3:00 PM <[email protected]> wrote:
>> >> >> >> >> >
>> >> >> >> >> > Send Maia-users mailing list submissions to
>> >> >> >> >> >         [email protected]
>> >> >> >> >> >
>> >> >> >> >> > To subscribe or unsubscribe via the World Wide Web, visit
>> >> >> >> >> >         http://www.renaissoft.com/cgi-bin/mailman/listinfo/maia-users
>> >> >> >> >> > or, via email, send a message with subject or body 'help' to
>> >> >> >> >> >         [email protected]
>> >> >> >> >> >
>> >> >> >> >> > You can reach the person managing the list at
>> >> >> >> >> >         [email protected]
>> >> >> >> >> >
>> >> >> >> >> > When replying, please edit your Subject line so it is more specific
>> >> >> >> >> > than "Re: Contents of Maia-users digest..."
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> > Today's Topics:
>> >> >> >> >> >
>> >> >> >> >> >    1. Re: autolearn_status error Ubuntu 18.04 LTS (jjs - mainphrame)
>> >> >> >> >> >    2. Re: autolearn_status error Ubuntu 18.04 LTS ([email protected])
>> >> >> >> >> >    3. Re: autolearn_status error Ubuntu 18.04 LTS (jjs - mainphrame)
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> > ----------------------------------------------------------------------
>> >> >> >> >> >
>> >> >> >> >> > Message: 1
>> >> >> >> >> > Date: Tue, 12 May 2020 15:44:35 -0700
>> >> >> >> >> > From: jjs - mainphrame <[email protected]>
>> >> >> >> >> > To: [email protected]
>> >> >> >> >> > Cc: Maia-Users Mailing List <[email protected]>
>> >> >> >> >> > Subject: Re: [Maia-users] autolearn_status error Ubuntu 18.04 LTS
>> >> >> >> >> > Message-ID:
>> >> >> >> >> >         <CABkzw7w-m=0KiRvT=u2sMgEJWDOc+8d+-BvxbjWpp=krzKGEvg@mail.gmail.com>
>> >> >> >> >> > Content-Type: text/plain; charset="utf-8"
>> >> >> >> >> >
>> >> >> >> >> > Now the database issue is sorted, you'll find that maiad isn't able to talk
>> >> >> >> >> > to clamav as configured.
>> >> >> >> >> >
>> >> >> >> >> > That's been fixed in the current install scripts, but  in the meantime you
>> >> >> >> >> > can either edit maiad.conf around lines 393-394 to use the unix socket, or
>> >> >> >> >> > run dpkg-reconfigure clamav-daemon to use tcp.
>> >> >> >> >> >
>> >> >> >> >> > We'd changed the default install to have maiad talk to clamd via tcp after
>> >> >> >> >> > jumping through way too many hoops fixing the path, ownership and
>> >> >> >> >> > permissions of the unix socket every time there was a software update. But
>> >> >> >> >> > YMMV, as they say.
>> >> >> >> >> >
>> >> >> >> >> > Jake
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> > On Tue, May 12, 2020 at 8:36 AM <[email protected]> wrote:
>> >> >> >> >> >
>> >> >> >> >> > > Hello Everyone,
>> >> >> >> >> > >
>> >> >> >> >> > > I've been out of the loop for a long while and decided to try the latest
>> >> >> >> >> > > build using the install script on Ubuntu 18.04 LTS. Everything seemed to go
>> >> >> >> >> > > along just fine and I am testing with a domain and getting the following
>> >> >> >> >> > > error.
>> >> >> >> >> > >
>> >> >> >> >> > > May 12 14:04:59 maia postfix/lmtp[33612]: EECC1859E0: to=<[email protected]>,
>> >> >> >> >> > > relay=127.0.0.1[127.0.0.1]:10024, delay=0.35, delays=0.22/0/0/0.12,
>> >> >> >> >> > > dsn=4.5.0, status=deferred (host 127.0.0.1[127.0.0.1] said: 451 4.5.0 Error
>> >> >> >> >> > > in processing, id=21314-03, Take Action! FAILED: DBD::mysql::st execute
>> >> >> >> >> > > failed: Column 'autolearn_status' cannot be null at /var/lib/maia/maiad
>> >> >> >> >> > > line 4408, <GEN20> line 156. (in reply to end of DATA command))
>> >> >> >> >> > >
>> >> >> >> >> > > The Maia server is at the head end, the user account was created in the
>> >> >> >> >> > > web interface and there is a transport file and relay_domain mappings file
>> >> >> >> >> > > to the recipient email server.
>> >> >> >> >> > >
>> >> >> >> >> > > Seems like its something minor but A google search isn’t helping me out
>> >> >> >> >> > >
>> >> >> >> >> > > Thanks,
>> >> >> >> >> > > Dave
>> >> >> >> >> > >
>> >> >> >> >> > >
>> >> >> >> >> > > _______________________________________________
>> >> >> >> >> > > Maia-users mailing list
>> >> >> >> >> > > [email protected]
>> >> >> >> >> > > http://www.renaissoft.com/cgi-bin/mailman/listinfo/maia-users
>> >> >> >> >> > >
>> >> >> >> >> > -------------- next part --------------
>> >> >> >> >> > An HTML attachment was scrubbed...
>> >> >> >> >> > URL: <http://www.renaissoft.com/pipermail/maia-users/attachments/20200512/5d00f99a/attachment-0001.html>
>> >> >> >> >> >
>> >> >> >> >> > ------------------------------
>> >> >> >> >> >
>> >> >> >> >> > Message: 2
>> >> >> >> >> > Date: Wed, 13 May 2020 06:47:12 -0400
>> >> >> >> >> > From: <[email protected]>
>> >> >> >> >> > To: "'jjs - mainphrame'" <[email protected]>
>> >> >> >> >> > Cc: 'Maia-Users Mailing List' <[email protected]>
>> >> >> >> >> > Subject: Re: [Maia-users] autolearn_status error Ubuntu 18.04 LTS
>> >> >> >> >> > Message-ID: <[email protected]>
>> >> >> >> >> > Content-Type: text/plain; charset="utf-8"
>> >> >> >> >> >
>> >> >> >> >> > No biggie It’s a work in progress, its easy at least for me to wipe the vm and try a clean install so I will give it a go.
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> > From: jjs - mainphrame <[email protected]>
>> >> >> >> >> > Sent: Tuesday, May 12, 2020 6:45 PM
>> >> >> >> >> > To: [email protected]
>> >> >> >> >> > Cc: Maia-Users Mailing List <[email protected]>
>> >> >> >> >> > Subject: Re: [Maia-users] autolearn_status error Ubuntu 18.04 LTS
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> > Now the database issue is sorted, you'll find that maiad isn't able to talk to clamav as configured.
>> >> >> >> >> >
>> >> >> >> >> > That's been fixed in the current install scripts, but  in the meantime you can either edit maiad.conf around lines 393-394 to use the unix socket, or run dpkg-reconfigure clamav-daemon to use tcp.
>> >> >> >> >> >
>> >> >> >> >> > We'd changed the default install to have maiad talk to clamd via tcp after jumping through way too many hoops fixing the path, ownership and permissions of the unix socket every time there was a software update. But YMMV, as they say.
>> >> >> >> >> >
>> >> >> >> >> > Jake
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> > On Tue, May 12, 2020 at 8:36 AM <[email protected] <mailto:[email protected]> > wrote:
>> >> >> >> >> >
>> >> >> >> >> > Hello Everyone,
>> >> >> >> >> >
>> >> >> >> >> > I've been out of the loop for a long while and decided to try the latest build using the install script on Ubuntu 18.04 LTS. Everything seemed to go along just fine and I am testing with a domain and getting the following error.
>> >> >> >> >> >
>> >> >> >> >> > May 12 14:04:59 maia postfix/lmtp[33612]: EECC1859E0: to=<[email protected] <mailto:[email protected]> >, relay=127.0.0.1[127.0.0.1]:10024, delay=0.35, delays=0.22/0/0/0.12, dsn=4.5.0, status=deferred (host 127.0.0.1[127.0.0.1] said: 451 4.5.0 Error in processing, id=21314-03, Take Action! FAILED: DBD::mysql::st execute failed: Column 'autolearn_status' cannot be null at /var/lib/maia/maiad line 4408, <GEN20> line 156. (in reply to end of DATA command))
>> >> >> >> >> >
>> >> >> >> >> > The Maia server is at the head end, the user account was created in the web interface and there is a transport file and relay_domain mappings file to the recipient email server.
>> >> >> >> >> >
>> >> >> >> >> > Seems like its something minor but A google search isn’t helping me out
>> >> >> >> >> >
>> >> >> >> >> > Thanks,
>> >> >> >> >> > Dave
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> > _______________________________________________
>> >> >> >> >> > Maia-users mailing list
>> >> >> >> >> > [email protected] <mailto:[email protected]>
>> >> >> >> >> > http://www.renaissoft.com/cgi-bin/mailman/listinfo/maia-users
>> >> >> >> >> >
>> >> >> >> >> > -------------- next part --------------
>> >> >> >> >> > An HTML attachment was scrubbed...
>> >> >> >> >> > URL: <http://www.renaissoft.com/pipermail/maia-users/attachments/20200513/44608c16/attachment-0001.html>
>> >> >> >> >> >
>> >> >> >> >> > ------------------------------
>> >> >> >> >> >
>> >> >> >> >> > Message: 3
>> >> >> >> >> > Date: Wed, 13 May 2020 08:09:14 -0700
>> >> >> >> >> > From: jjs - mainphrame <[email protected]>
>> >> >> >> >> > To: [email protected]
>> >> >> >> >> > Cc: Maia-Users Mailing List <[email protected]>
>> >> >> >> >> > Subject: Re: [Maia-users] autolearn_status error Ubuntu 18.04 LTS
>> >> >> >> >> > Message-ID:
>> >> >> >> >> >         <CABkzw7zxbrrfu1udYRTGQ-qYbYTm-HkC8tuikn4L+ZSRUJLUUA@mail.gmail.com>
>> >> >> >> >> > Content-Type: text/plain; charset="utf-8"
>> >> >> >> >> >
>> >> >> >> >> > David,
>> >> >> >> >> >
>> >> >> >> >> > Your feedback is helpful, thank you.
>> >> >> >> >> >
>> >> >> >> >> > Jake
>> >> >> >> >> >
>> >> >> >> >> > On Wed, May 13, 2020 at 3:47 AM <[email protected]> wrote:
>> >> >> >> >> >
>> >> >> >> >> > > No biggie It’s a work in progress, its easy at least for me to wipe the vm
>> >> >> >> >> > > and try a clean install so I will give it a go.
>> >> >> >> >> > >
>> >> >> >> >> > >
>> >> >> >> >> > >
>> >> >> >> >> > > *From:* jjs - mainphrame <[email protected]>
>> >> >> >> >> > > *Sent:* Tuesday, May 12, 2020 6:45 PM
>> >> >> >> >> > > *To:* [email protected]
>> >> >> >> >> > > *Cc:* Maia-Users Mailing List <[email protected]>
>> >> >> >> >> > > *Subject:* Re: [Maia-users] autolearn_status error Ubuntu 18.04 LTS
>> >> >> >> >> > >
>> >> >> >> >> > >
>> >> >> >> >> > >
>> >> >> >> >> > > Now the database issue is sorted, you'll find that maiad isn't able to
>> >> >> >> >> > > talk to clamav as configured.
>> >> >> >> >> > >
>> >> >> >> >> > > That's been fixed in the current install scripts, but  in the meantime you
>> >> >> >> >> > > can either edit maiad.conf around lines 393-394 to use the unix socket, or
>> >> >> >> >> > > run dpkg-reconfigure clamav-daemon to use tcp.
>> >> >> >> >> > >
>> >> >> >> >> > > We'd changed the default install to have maiad talk to clamd via tcp after
>> >> >> >> >> > > jumping through way too many hoops fixing the path, ownership and
>> >> >> >> >> > > permissions of the unix socket every time there was a software update. But
>> >> >> >> >> > > YMMV, as they say.
>> >> >> >> >> > >
>> >> >> >> >> > > Jake
>> >> >> >> >> > >
>> >> >> >> >> > >
>> >> >> >> >> > >
>> >> >> >> >> > > On Tue, May 12, 2020 at 8:36 AM <[email protected]> wrote:
>> >> >> >> >> > >
>> >> >> >> >> > > Hello Everyone,
>> >> >> >> >> > >
>> >> >> >> >> > > I've been out of the loop for a long while and decided to try the latest
>> >> >> >> >> > > build using the install script on Ubuntu 18.04 LTS. Everything seemed to go
>> >> >> >> >> > > along just fine and I am testing with a domain and getting the following
>> >> >> >> >> > > error.
>> >> >> >> >> > >
>> >> >> >> >> > > May 12 14:04:59 maia postfix/lmtp[33612]: EECC1859E0: to=<[email protected]>,
>> >> >> >> >> > > relay=127.0.0.1[127.0.0.1]:10024, delay=0.35, delays=0.22/0/0/0.12,
>> >> >> >> >> > > dsn=4.5.0, status=deferred (host 127.0.0.1[127.0.0.1] said: 451 4.5.0 Error
>> >> >> >> >> > > in processing, id=21314-03, Take Action! FAILED: DBD::mysql::st execute
>> >> >> >> >> > > failed: Column 'autolearn_status' cannot be null at /var/lib/maia/maiad
>> >> >> >> >> > > line 4408, <GEN20> line 156. (in reply to end of DATA command))
>> >> >> >> >> > >
>> >> >> >> >> > > The Maia server is at the head end, the user account was created in the
>> >> >> >> >> > > web interface and there is a transport file and relay_domain mappings file
>> >> >> >> >> > > to the recipient email server.
>> >> >> >> >> > >
>> >> >> >> >> > > Seems like its something minor but A google search isn’t helping me out
>> >> >> >> >> > >
>> >> >> >> >> > > Thanks,
>> >> >> >> >> > > Dave
>> >> >> >> >> > >
>> >> >> >> >> > >
>> >> >> >> >> > > _______________________________________________
>> >> >> >> >> > > Maia-users mailing list
>> >> >> >> >> > > [email protected]
>> >> >> >> >> > > http://www.renaissoft.com/cgi-bin/mailman/listinfo/maia-users
>> >> >> >> >> > >
>> >> >> >> >> > >
>> >> >> >> >> > -------------- next part --------------
>> >> >> >> >> > An HTML attachment was scrubbed...
>> >> >> >> >> > URL: <http://www.renaissoft.com/pipermail/maia-users/attachments/20200513/7f71b087/attachment-0001.html>
>> >> >> >> >> >
>> >> >> >> >> > ------------------------------
>> >> >> >> >> >
>> >> >> >> >> > Subject: Digest Footer
>> >> >> >> >> >
>> >> >> >> >> > _______________________________________________
>> >> >> >> >> > Maia-users mailing list
>> >> >> >> >> > [email protected]
>> >> >> >> >> > http://www.renaissoft.com/cgi-bin/mailman/listinfo/maia-users
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> > ------------------------------
>> >> >> >> >> >
>> >> >> >> >> > End of Maia-users Digest, Vol 172, Issue 18
>> >> >> >> >> > *******************************************
>> >> >> >> >> _______________________________________________
>> >> >> >> >> Maia-users mailing list
>> >> >> >> >> [email protected]
>> >> >> >> >> http://www.renaissoft.com/cgi-bin/mailman/listinfo/maia-users
_______________________________________________
Maia-users mailing list
[email protected]
http://www.renaissoft.com/cgi-bin/mailman/listinfo/maia-users