Bill Kwok wrote:
>
>
> On Jan 29, 2008 12:07 AM, Eric Shubes <[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>> wrote:
>
> Bill Kwok wrote:
> > Hi List,
> >
> > Some of my users' email are forwarded from regional office (another
> > qmail server). Most emails are fine, except email from google alert.
> > The only error message I can see is something like this:
> >
> >
> > Dec31 14:40:12 CHKUSER accepted rcpt: from
> > <[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>
> >
> <mailto:[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>>::>
> > remote <regionaloffice:unknown:x.x.x.x> rcpt <[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>
> > <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>> : found
> existing recipient
> > Dec31 14:40:13 tcpserver: end 24357 status 256
> >
> >
> > My guess is it's due to domainkeys is being used by Google and when we
> > forward from one server to another, it breaks. Am I correct? If yes,
> > any way to disable domainkeys checking?
> >
> > Thanks in advance.
> >
> > Best regards,
> > Bill
>
> That could be on older toaster versions, which did not log spf nor dk
> rejections. If your toaster is fairly recent, you would see a rejection
> message in the log for both of these conditions.
>
> If your toaster is a bit old, I suspect that your problem is more
> likely due
> to SPF misconfiguration, although domainkeys might also be a problem.
>
> Check the list archive for instructions on disabling domainkeys. The
> wizard
> at http://www.openspf.org <http://www.openspf.org/> is great helping
> to determine what should be in
> the spf record for your domain.
>
> --
> -Eric 'shubes'
>
> ---------------------------------------------------------------------
> QmailToaster hosted by: VR Hosted <http://www.vr.org
> <http://www.vr.org/>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> [EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>
>
>
>
> Hi Eric,
>
> It seems my qmt versions are not that outdated:
>
> # rpm -qa | grep toaster
> vpopmail-toaster-5.4.13-1.3.3
> ezmlm-cgi-toaster-0.53.324-1.3.2
> courier-authlib-toaster-0.59.1-1.3.5
> squirrelmail-toaster-1.4.9a-1.3.5
> spamassassin-toaster-3.1.8-1.3.7
> ripmime-toaster-1.4.0.6-1.3.2
> qmailmrtg-toaster-4.2-1.3.2
> isoqlog-toaster-2.1-1.3.3
> daemontools-toaster-0.76-1.3.2
> libdomainkeys-toaster-0.68-1.3.2
> libsrs2-toaster-1.0.18-1.3.2
> courier-imap-toaster-4.1.2-1.3.6
> send-emails-toaster-0.5-1.3.3
> qmail-pop3d-toaster-1.03-1.3.14
> autorespond-toaster-2.0.4-1.3.2
> qmailtoaster-plus-0.2.7-1.3.9
> control-panel-toaster-0.5-1.3.3
> simscan-toaster-1.3.1-1.3.5
> vqadmin-toaster-2.3.4-1.3.2
> qmailadmin-toaster-1.2.9-1.3.3
> ucspi-tcp-toaster-0.88-1.3.4
> maildrop-toaster-devel-2.0.3-1.3.4
> clamav-toaster-0.90.1-1.3.11
> ezmlm-toaster-0.53.324-1.3.2
> maildrop-toaster-2.0.3-1.3.4
> qmail-toaster-1.03-1.3.14
> To be honest, I have no idea about how to setup SPF. I will study it
> soon and hope can solve my problem soon. Thanks for pointing me to a
> new direction.
>
>
IIRC that logging problem was corrected somewhere around version 1.3.9 or
1.3.11 of qmail-toaster. The only changelog that I know of that's up to date
is in the rpm spec file, which I don't have handy at the moment. BL, you
appear to be current enough to have the change in there.
You can try turning off DK checking, but I'm guessing that won't fix your
problem. I could be wrong about this though (it's been known to happen!).
Since you're not getting a meaningful log message, the best way to really
tell what's going on is to turn on recordio during a test. Directions for
using recordio are in the archives somewhere. It'd be nice if they were on
the wiki, but I don't know that they're there yet.
--
-Eric 'shubes'
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
