From owner-freebsd-pf@FreeBSD.ORG Sat Nov 21 18:24:00 2009 Return-Path: Delivered-To: freebsd-pf@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1DBAF106568D for ; Sat, 21 Nov 2009 18:24:00 +0000 (UTC) (envelope-from mike@jellydonut.org) Received: from mail-fx0-f227.google.com (mail-fx0-f227.google.com [209.85.220.227]) by mx1.freebsd.org (Postfix) with ESMTP id B3CD08FC21 for ; Sat, 21 Nov 2009 18:23:59 +0000 (UTC) Received: by fxm27 with SMTP id 27so4744408fxm.3 for ; Sat, 21 Nov 2009 10:23:58 -0800 (PST) MIME-Version: 1.0 Received: by 10.102.160.15 with SMTP id i15mr1321340mue.130.1258827838720; Sat, 21 Nov 2009 10:23:58 -0800 (PST) In-Reply-To: <6c51dbb10911211007x4ea07528y7642460629788903@mail.gmail.com> References: <6c51dbb10911210706g3490e463x7fdf3809243e30d2@mail.gmail.com> <4B082302.3040704@gmx.de> <6c51dbb10911211007x4ea07528y7642460629788903@mail.gmail.com> Date: Sat, 21 Nov 2009 13:23:58 -0500 Message-ID: <1de79840911211023n165ecbd0h1051aaada4acefb@mail.gmail.com> From: Michael Proto To: Victor Lyapunov Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-pf@freebsd.org Subject: Re: sending mail with attachments always fails (FreeBSD/pf) X-BeenThere: freebsd-pf@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion and general questions about packet filter \(pf\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Nov 2009 18:24:00 -0000 On Sat, Nov 21, 2009 at 1:07 PM, Victor Lyapunov wrote: > rule 4/0(match): pass out on em0: (tos 0x0, ttl 127, id 19860, offset > 0, flags [DF], proto TCP (6), length 48) 192.168.0.5.1822 > > 209.85.129.111.465: =A0tcp 28 [bad hdr length 0 - too short, < 20] This looks to be your problem-- bad hdr length 0. I don't know enough of what mailer(s) you're using to relay this message outbound, but since port 465 is smtp over TLS/SSL are you sure your smtp encryption is working correctly? I often see these types of errors with other TLS/SSL apps when one side is expecting an encrypted connection and the other is not (correctly) providing it. Have you tried using unencrypted smtp on port 25? Does that work? -Proto