Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OFX emails not being imported #21

Open
GoogleCodeExporter opened this issue Aug 27, 2015 · 6 comments
Open

OFX emails not being imported #21

GoogleCodeExporter opened this issue Aug 27, 2015 · 6 comments

Comments

@GoogleCodeExporter
Copy link
Contributor

What steps will reproduce the problem?
0. [email protected] # my inbox address
1. EMAIL=... # my google address
2. In linux, email the OFX transactions on the command line: metasend -F $EMAIL 
-b -t $D -s "OFX 2015/01" -m application/octet-stream -f 2015-01.ofx 
3. Transactions do not appear :-(.

What is the expected output? What do you see instead?
OFX transactions should have been imported by email. They never appear.

Original issue reported on code.google.com by [email protected] on 15 Mar 2015 at 7:13

@GoogleCodeExporter
Copy link
Contributor Author

Thanks! Do you have an OFX sample file you can share?

Original comment by [email protected] on 16 Mar 2015 at 5:05

@GoogleCodeExporter
Copy link
Contributor Author

Attached is a sample OFX file; from one of my non-critical accounts; I did 
modify BANKID and ACCTID, but no other fields.

Original comment by [email protected] on 16 Mar 2015 at 3:56

Attachments:

@GoogleCodeExporter
Copy link
Contributor Author

We wrote a test for this OFX and it works.

Can you please do check if the email sender have access to the Record Book 
(Ledger)?
If not, you can share the Record Book with this user with a post permission

Original comment by [email protected] on 16 Mar 2015 at 11:57

@GoogleCodeExporter
Copy link
Contributor Author

The email I'm sending in the From header is the same address that I have as my 
bkper account. The return-path is NOT the same as the From header; are you 
validating against the Return-Path instead of From?

Original comment by [email protected] on 17 Mar 2015 at 12:18

@GoogleCodeExporter
Copy link
Contributor Author

We check the From header. I've sent you a PVT message.

Original comment by [email protected] on 17 Mar 2015 at 12:59

@GoogleCodeExporter
Copy link
Contributor Author

So bugs uncovered, and suggested resolutions:

- From address must have permissions: Document
- ${To} address must be first: match any instead
- Non-multipart mail doesn't work: Fix

Original comment by [email protected] on 19 Mar 2015 at 10:19

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant