Re: forwarding email from files format postfix

I added the debug and now I get : root@:/home# postdrop -r - test_newmail.eml [...] postdrop: chdir /var/spool/postfix postdrop: open maildrop/A331AC2F9D postdrop: send attr queue_id = A331AC2F9D postdrop: vstream_fflush_some: fd 1 flush 21 queue_idA331AC2F9Dpostdrop: rec_put: type T len

Re: [SPAM] Re: forwarding email from files format postfix

Hi, Thanks for your help ! can I just change the To header within the files and move the file in a postfix folder for it to "resend" it ? if so .. which folder ... Stéphane Le 18/11/2015 16:02, Noel Jones a écrit : On 11/18/2015 2:53 AM, Stéphane MERLE wrote: Hi, Someone made a little

Re: [SPAM] Re: forwarding email from files format postfix

I found the folder : /var/spool/postfix/maildrop I also found a postdrop example, but not very usefull ;) http://www.empire-woodworks.com/running_trim/post_drop.html if I use : postdrop mailname.eml I got a queueid85E11C0212 but it stay stuck here no log in the mail.log Stéphane Le

Re: DKIM Signature fails

FWIW, I have the same problem. I saw it  as intermittent, but now that you tracked it down to the width of the lines , this makes sense. I do have access to my server console at the moment, but I'm running the highest rev of postfix 2. I believe it is rev 11.  So is this problem present in

Re: DKIM Signature fails

Andy A: >Following is the original message which?fails?the DKIM verification >at the verifier's end. As you can see, the lines have been chopped >off and a '=' has been added towards the end of the line where the >lines have been longer than 74 characters. > >Hi? , > >An account has been created

Re: DKIM Signature fails

I get the body hash failure on plain text. ‎   Original Message   From: Wietse Venema Sent: Thursday, November 19, 2015 10:24 AM To: Postfix users Reply To: Postfix users Subject: Re: DKIM Signature fails Andy A: >Following is the original message which?fails?the DKIM verification >at the

Re: DKIM Signature fails

yahoogro...@lazygranch.xyz: > I get the body hash failure on plain text. To send 8bit mail, you must provide appropriate MIME headers and ESMTP attributes, otherwise you violate email RFCs, and there is no guarantee whatsoever. In addition, it is wise to convert 8bit mail to quoted-printable

Re: socket: malformed response

On Thu, Nov 19, 2015 at 03:26:27PM -0800, Vicki Brown wrote: > The only program that uses /usr/local/cutedge/postfix/etc is.. postfix. Well, the real Postfix uses /etc/postfix, as evidenced by the errors logged by postdrop(1). Whatever is asking sendmail(1) and postdrop(1) to use that other

Re: DKIM Signature fails

Ignore my comment. I was thinking s/mime.‎ Sorry about that.    Original Message   From: Wietse Venema Sent: Thursday, November 19, 2015 12:33 PM To: Postfix users Reply To: Postfix users Subject: Re: DKIM Signature fails yahoogro...@lazygranch.xyz: > I get the body hash failure on plain text.

Re: socket: malformed response

On Thu, Nov 19, 2015 at 03:11:14PM -0800, Vicki Brown wrote: > > You have programs that STILL USE /usr/local/cutedge/postfix/etc as > > > > the Postfix configuration directory. > > No, I do not. > > There is no /usr/local/cutedge/postfix/etc configuration directory; it's > a symbolic link.

Re: socket: malformed response

> On Nov 19, 2015, at 14:44, Wietse Venema wrote: > > You have programs that STILL USE /usr/local/cutedge/postfix/etc as > the Postfix configuration directory. Those programs will not work. The only program that uses /usr/local/cutedge/postfix/etc is.. postfix. In a

Re: socket: malformed response

cutedge is a company that makes a mail /postfix startup service front end. This was a spurious (coincidental) error, long past resolved and unrelated. /usr/local/cutedge/postfix/etc is actually a symlink to /etc/postfix... Today I see postfix/qmgr[21552]: warning: private/filter socket:

Re: socket: malformed response

Two questions: When qmgr says "socket: malformed response" - is there any way yo find out what response it got? When qmgr says "Connection refused", does that actually mean the filter refused to connect? Or that mgr refused to try the filter? - Vicki

Re: socket: malformed response

We use the Cutedge LaunchDaemons to start postfix and SMTP at boot time. I don't use it to configure postfix (although I could); I just edit the files (very rarely up until this past week). > IIRC from an earlier post of yours, you're using OS X Server Yes, on the internal IMAP/POP server. Not

Re: socket: malformed response

Vicki Brown: > cutedge is a company that makes a mail /postfix startup service front end. > This was a spurious (coincidental) error, long past resolved and > unrelated. /usr/local/cutedge/postfix/etc is actually a symlink > to /etc/postfix... This is NOT LONG PAST RESOLVED. You have programs

Re: socket: malformed response

> You have programs that STILL USE /usr/local/cutedge/postfix/etc as > > the Postfix configuration directory. No, I do not. There is no /usr/local/cutedge/postfix/etc configuration directory; it's a symbolic link. There is only one postfix config directory. Please don't shout at me. > On

Re: socket: malformed response

On Thu, 19 Nov 2015, Wietse Venema wrote: Vicki Brown: cutedge is a company that makes a mail /postfix startup service front end. This was a spurious (coincidental) error, long past resolved and unrelated. /usr/local/cutedge/postfix/etc is actually a symlink to /etc/postfix... This is NOT

Re: forwarding email from files format postfix

found out that I was a dummy and needed to pipe the content file ... and also found out that I shouldn't use postdrop but sendmail ... going this way now ... Stéphane Le 19/11/2015 11:36, Stéphane MERLE a écrit : I added the debug and now I get : root@:/home# postdrop -r -

DKIM Signature fails

Hello.  We have Postfix 2:2.6.6-6.el6_5 running locally with opendkim, opendmarc on Centos 6.x. All the emails are sent via the local MTA (postfix) The mails are being delivered and are signed as they have DKIM signature, but the body hash fails. DNS TXT records for dmarc, dkim and spf are all