David: Might be a good time to create a snapshot that you can fall back to should something get messed up as you tweak things. :)
Also, Eric -- interestingly enough I already had everything set up for dspam but it wasn't running. I went ahead and started it and it's running, but nothing is showing in the maillog file (other than to say a one-time notice that the daemon was starting). Two questions: 1) should there be anything in the log file (like I see for spam assassin, clam av and spamdyke) and 2) How to get it to auto-start at reboot. Obviously it's not doing that. Thanks! From: David Overman <[email protected]> Reply-To: <[email protected]> Date: Wednesday, November 30, 2016 at 12:00 PM To: <[email protected]> Subject: Re: [qmailtoaster] Whoops! Not receiving mail. Its working! thanks again and have a great day. Eric, on DO-they have an option for ipv6, which enables private networking between droplets. I always check it, but I don't use the feature. David Overman On Nov 30, 2016, at 10:25 AM, Eric Broch <[email protected]> wrote: > And don't forget > > # chmod 744 /etc/dspam.conf > > before you restart dspam > > On 11/30/2016 9:23 AM, Eric Broch wrote: >> >> If D.O. has some sort of spam filtering you can forgo dspam otherwise we can >> get it working. If you want to use dspam do the following: >> >> # mv /etc/dspam.conf /etc/dspam.conf.bak >> >> # wget -O /root/dspam.conf >> https://raw.githubusercontent.com/qmtoaster/dspam/master/dspam.conf >> >> # mv /home/vpopmail/domains/'yourdomain'/.qmail-default >> /home/vpopmail/domains/'yourdomain'/.qmail-default.bak >> # wget -O /home/vpopmail/domains/'yourdomain'/.qmail-default >> https://raw.githubusercontent.com/qmtoaster/dsapm/master/.qmail-default >> >> # systemctl restart dspam >> >> Send yourself an email and see if it ends up in the inbox. If not, let's >> have a look at the log and we'll go from there. >> >> On 11/30/2016 9:08 AM, David Overman wrote: >>> No, no setting like that. >>> >>> On Nov 30, 2016, at 10:05 AM, Eric Broch <[email protected]> >>> <mailto:[email protected]> wrote: >>> >>>> Okay. >>>> >>>> Look in /etc/dspam.conf and see if there is a setting "Trust vpopmail" >>>> >>>> >>>> >>>> On 11/30/2016 9:01 AM, David Overman wrote: >>>>> Thanks Eric, >>>>> test email is in inbox. >>>>> >>>>> On Nov 30, 2016, at 09:53 AM, Eric Broch <[email protected]> >>>>> <mailto:[email protected]> wrote: >>>>> >>>>>> Let's get mail delivery working before we look at dspam >>>>>> >>>>>> edit /home/vpopmail/domains/'yourdomain'/.qmail-default >>>>>> >>>>>> and put the following in it >>>>>> >>>>>> | /home/vpopmail/bin/vdelivermail '' delete >>>>>> >>>>>> >>>>>> >>>>>> On 11/30/2016 8:37 AM, Jaime Lerner wrote: >>>>>>> Check /var/log/qmail/send/current to see the delivery success (or >>>>>>> failure). >>>>>>> >>>>>>> I don't know what "dspam" is...I don't have that in my logs. Maybe Eric >>>>>>> knows what that is as it looks like that could be the issue now. >>>>>>> >>>>>>> From: David Overman <[email protected]> >>>>>>> Reply-To: <[email protected]> >>>>>>> Date: Wednesday, November 30, 2016 at 10:27 AM >>>>>>> To: <[email protected]> >>>>>>> Subject: Re: [qmailtoaster] Whoops! Not receiving mail. >>>>>>> >>>>>>> Thanks Jamie, >>>>>>> The nameservers survived after a reboot, and when I sent mail to the >>>>>>> server, it got past spamdyke, >>>>>>> but still no mail in roundcube inbox. here is tail of log. >>>>>>> >>>>>>> Nov 30 15:21:19 mail spamd[2074]: spamd: clean message (1.2/5.0) for >>>>>>> clamav:89 in 0.1 seconds, 2084 bytes. >>>>>>> Nov 30 15:21:19 mail spamd[2074]: spamd: result: . 1 - >>>>>>> AWL,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,RDNS_NONE >>>>>>> scantime=0.1,size=2084,user=clamav,uid=89,required_score=5.0,rhost=mail. >>>>>>> davomail.com,raddr=::1,rport=35950,mid=<0DA420C0-CFCD-47D6-9B4E-0AC965C5 >>>>>>> [email protected]>,autolearn=no autolearn_force=no >>>>>>> Nov 30 15:21:19 mail spamdyke[2829]: ALLOWED from: [email protected] to: >>>>>>> [email protected] origin_ip: 17.143.180.10 origin_rdns: >>>>>>> pv33p03im-asmtp001.me.com auth: (unknown) encryption: TLS reason: >>>>>>> 250_ok_1480519279_qp_2834 >>>>>>> Nov 30 15:21:19 mail dspam[2843]: Option --user requires special >>>>>>> privileges when user does not match current user, e.g.. root or Trusted >>>>>>> User [uid=89(vpopmail)] >>>>>>> Nov 30 15:21:19 mail dspam[2843]: Unable to initialize agent context >>>>>>> Nov 30 15:21:19 mail spamd[1759]: prefork: child states: II >>>>>>> >>>>>>> >>>>>>> On Nov 30, 2016, at 09:02 AM, Jaime Lerner >>>>>>> <[email protected]> wrote: >>>>>>> >>>>>>> No "e" at the end.... /etc/resolv.conf >>>>>>> >>>>>>> :) >>>>>>> >>>>>>> Try editing the DNS entries in your ifcfg-eth0 file. I think this will >>>>>>> make your resolv.conf hold after reboot. Basically the ONLY thing you >>>>>>> need to edit will be the DNS1 and DNS2 entries. I'm listing the entire >>>>>>> file (with IPs, etc. redacted) so you can compare the options in yours >>>>>>> to mine (which is also CentOS 7.2 on Digital Ocean hosting). You should >>>>>>> have all the same options. >>>>>>> >>>>>>> /etc/sysconfig/network-scripts/ifcfg-eth0 >>>>>>> >>>>>>> [root@mail network-scripts]# cat ifcfg-eth0 >>>>>>> >>>>>>> DEVICE='eth0' >>>>>>> >>>>>>> TYPE=Ethernet >>>>>>> >>>>>>> BOOTPROTO=none >>>>>>> >>>>>>> ONBOOT='yes' >>>>>>> >>>>>>> HWADDR= <---- leave this as YOUR address! >>>>>>> >>>>>>> IPADDR= <--- leave this as YOUR IP address!! >>>>>>> >>>>>>> NETMASK= <--- leave this as what it is set at for your server!! >>>>>>> >>>>>>> GATEWAY= <--- leave this as what it is set at for your server! >>>>>>> >>>>>>> NM_CONTROLLED='yes' >>>>>>> >>>>>>> IPADDR2= <-- leave this as what it is set at for your server! >>>>>>> >>>>>>> PREFIX2=16 >>>>>>> >>>>>>> DNS1=8.8.8.8 <-- CHANGE your DNS1 to this >>>>>>> >>>>>>> DNS2=8.8.4.4 <-- CHANGE your DNS2 to this >>>>>>> >>>>>>> >>>>>>> Once you've edited your ifcfg-eth0 file, edit your resolv.conf file, >>>>>>> then try rebooting and see if it holds. >>>>>>> >>>>>>> From: David Overman <[email protected]> >>>>>>> Reply-To: <[email protected]> >>>>>>> Date: Wednesday, November 30, 2016 at 9:48 AM >>>>>>> To: <[email protected]> >>>>>>> Subject: Re: [qmailtoaster] Whoops! Not receiving mail. >>>>>>> >>>>>>> tried again. putting v4 nameservers i then executed systemctl restart >>>>>>> network. >>>>>>> now i get this: >>>>>>> >>>>>>> [root@mail ~]# cat /etc/resolve.conf >>>>>>> cat: /etc/resolve.conf: No such file or directory >>>>>>> >>>>>>> same thing on reboot-or if the file is there, it's ipv6 >>>>>>> >>>>>>> David >>>>>>> On Nov 30, 2016, at 08:32 AM, Jaime Lerner >>>>>>> <[email protected]> wrote: >>>>>>> >>>>>>> Once again, that's in your /etc/resolv.conf file. >>>>>>> >>>>>>> Make sure it says the following in it: >>>>>>> >>>>>>> nameserver 8.8.8.8 >>>>>>> >>>>>>> nameserver 8.8.4.4 >>>>>>> >>>>>>> >>>>>>> From: David Overman <[email protected]> >>>>>>> Reply-To: <[email protected]> >>>>>>> Date: Wednesday, November 30, 2016 at 7:59 AM >>>>>>> To: <[email protected]> >>>>>>> Subject: Re: [qmailtoaster] Whoops! Not receiving mail. >>>>>>> >>>>>>> No, I was looking in qmail logs, but when I did, guess what reared it's >>>>>>> ugly head? >>>>>>> >>>>>>> spamdyke[30082]: ERROR: invalid/unparsable nameserver found: >>>>>>> 2001:4860:4860::8844 >>>>>>> >>>>>>> >>>>>>> On Nov 30, 2016, at 06:50 AM, Jaime Lerner >>>>>>> <[email protected]> wrote: >>>>>>> >>>>>>> Did you check /var/log/maillog to see if it was received but maybe >>>>>>> denied delivery for some reason? >>>>>>> >>>>>>> On Nov 30, 2016, at 6:44 AM, David Overman <[email protected]> wrote: >>>>>>> >>>>>>> After getting squirellmail and roundcube working, I decided to test the >>>>>>> primary function of the site sending/receiving emails. I successfully >>>>>>> sent an email to an outside account, but I never recieved the reply from >>>>>>> that account.Looked in Mialdir and did not receive a bounce either. How >>>>>>> do you test courier, I did try to telnet 993, which connected and then >>>>>>> dropped when i said ehlo. >>>>>>> >>>>>>> David >>>>>>> >>>>>>> >>>>>>> --------------------------------------------------------------------- >>>>>>> To unsubscribe, e-mail: [email protected] >>>>>>> For additional commands, e-mail: >>>>>>> [email protected] >>>>>>> >>>>>>> >>>>>> >>>> >> >
