ZhangHuangbin wrote:Why not just step further and check whether there's a amavisd script under /etc/init.d/? It's /etc/init.d/amavis on Debian/Ubuntu.
Ok sorry for the delay, been a crazy weekend...
Here's pretty much what the log tells me (though it only goes back a few days and not far back to the day I ran into the issue, however as of today nothing seems to have changed so it's still perfectly relevant).
ct 20 07:35:24 foo postfix/pickup[8294]: 11C88208CA: uid=0 from=<root>
Oct 20 07:35:24 foo postfix/cleanup[8659]: 11C88208CA: message-id=<20131020073524.11C88208CA@foo.com>
Oct 20 07:35:24 foo postfix/qmgr[1720]: 11C88208CA: from=<root@foo.com>, size=469, nrcpt=1 (queue active)
Oct 20 07:35:24 foo postfix/smtp[8672]: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused
Oct 20 07:35:24 foo postfix/smtp[8672]: 11C88208CA: to=<root@foo.com>, relay=none, delay=0.03, delays=0.03/0/0/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)
Oct 20 07:42:34 foo postfix/qmgr[1720]: 125E120A17: from=<root@foo.com>, size=5845, nrcpt=1 (queue active)
Oct 20 07:42:34 foo postfix/qmgr[1720]: 11C88208CA: from=<root@foo.com>, size=469, nrcpt=1 (queue active)
Oct 20 07:42:34 foo postfix/smtp[9189]: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused
Oct 20 07:42:34 foo postfix/smtp[9191]: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused
Oct 20 07:42:34 foo postfix/smtp[9189]: 125E120A17: to=<root@foo.com>, relay=none, delay=444, delays=444/0.02/0/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)
Oct 20 07:42:34 foo postfix/smtp[9191]: 11C88208CA: to=<root@foo.com>, relay=none, delay=430, delays=430/0.02/0/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)
Oct 20 07:52:34 foo postfix/qmgr[1720]: 125E120A17: from=<root@foo.com>, size=5845, nrcpt=1 (queue active)
Oct 20 07:52:34 foo postfix/qmgr[1720]: 11C88208CA: from=<root@foo.com>, size=469, nrcpt=1 (queue active)
Oct 20 07:52:34 foo postfix/smtp[9212]: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused
Oct 20 07:52:34 foo postfix/smtp[9214]: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused
Oct 20 07:52:34 foo postfix/smtp[9212]: 125E120A17: to=<root@foo.com>, relay=none, delay=1045, delays=1045/0.02/0/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)
Oct 20 07:52:34 foo postfix/smtp[9214]: 11C88208CA: to=<root@foo.com>, relay=none, delay=1031, delays=1031/0.03/0/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)
Oct 20 08:12:34 foo postfix/qmgr[1720]: 125E120A17: from=<root@foo.com>, size=5845, nrcpt=1 (queue active)
Oct 20 08:12:34 foo postfix/qmgr[1720]: 11C88208CA: from=<root@foo.com>, size=469, nrcpt=1 (queue active)
Oct 20 08:12:34 foo postfix/smtp[9265]: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused
I replaced my hostname with "foo". As mentioned, during setup of iRedMail I used mail.foo.com and it sent the email just fine. I don't want my email addresses to be bob@mail.foo.com though, I want it to be bob@foo.com so I'm rather befuddled as to why adding that domain/alias in iredadmin doesn't work. Here's the result for looking if there's a amavisd script under /etc/init.d/
there is an
under /etc/init.d/:
/etc/init.d# ls
acpid friendly-recovery plymouth single
amavis ...
I cut the paste short, you get the idea.
I also checked the status of amavis:
sudo service amavis start
Starting amavisd: amavisd-new.
So i suppose it's running now. I'll try to send an email and see what happens. I'll keep this thread posted. I have to run to a meeting, so I'll update this soon!
** UPDATE **
Ok.. oddly enough it seems i can receive emails to the info@foo.com email/domain after all... how surprisingly odd. I tried to send an email from info@foo.com. I have a feeling sending will fail. Log:
Oct 21 14:41:44 foo postfix/cleanup[14328]: 14C15208BB: message-id=<69c2d6875e03ca5e7180547d1ed74d73@foo.com>
Oct 21 14:41:44 foo postfix/qmgr[1720]: 14C15208BB: from=<info@foo.com>, size=748, nrcpt=1 (queue active)
Oct 21 14:41:44 foo roundcube: User info@foo.com [192.148.105.26]; Message for derp@gmail.com; 250: 2.0.0 Ok: queued as 14C15208BB
Oct 21 14:41:44 foo amavis[14070]: (14070-02) (!!)file(1) utility (/usr/bin/file) FAILED: run_command: can't fork: Cannot allocate memory at /usr/sbin/amavisd-new line 3586.
Oct 21 14:41:44 foo amavis[14070]: (14070-02) (!)connect to /tmp/clamd.socket failed, attempt #1: Can't connect to UNIX socket /tmp/clamd.socket: No such file or directory
Oct 21 14:41:44 foo postfix/smtpd[14319]: disconnect from foo.com[127.0.0.1]
Oct 21 14:41:45 foo amavis[14070]: (14070-02) (!)connect to /tmp/clamd.socket failed, attempt #1: Can't connect to UNIX socket /tmp/clamd.socket: No such file or directory
Oct 21 14:41:45 foo amavis[14070]: (14070-02) (!)ClamAV-clamd: All attempts (1) failed connecting to /tmp/clamd.socket, retrying (2)
Oct 21 14:41:51 foo amavis[14070]: (14070-02) (!)connect to /tmp/clamd.socket failed, attempt #1: Can't connect to UNIX socket /tmp/clamd.socket: No such file or directory
Oct 21 14:41:51 foo amavis[14070]: (14070-02) (!)ClamAV-clamd av-scanner FAILED: run_av error: Too many retries to talk to /tmp/clamd.socket (All attempts (1) failed connecting to /tmp/clamd.socket) at (eval 114) line 603.\n
Oct 21 14:41:51 foo amavis[14070]: (14070-02) (!)WARN: all primary virus scanners failed, considering backups
Oct 21 14:41:52 foo postfix/smtp[14334]: 14C15208BB: to=<derp@gmail.com>, relay=127.0.0.1[127.0.0.1]:10024, delay=9.5, delays=1.1/0.02/0/8.4, dsn=4.4.2, status=deferred (lost connection with 127.0.0.1[127.0.0.1] while sending end of data -- message may be sent more than once)
Oct 21 14:41:52 foo amavis[14069]: (!)Net::Server: 2013/10/21-14:41:52 Bad fork [Cannot allocate memory]\n at line 139 in file /usr/share/perl5/Net/Server/PreForkSimple.pm
[strike]So i'm thoroughly confused... why would receiving an email at info@foo.com work, while sending fails? Send/receive works on @mail.foo.com. :\[/strike]
Well as of the writing of this, actually send/receive on either @foo.com or @mail.foo.com seem to fail. wtf