I was thinking that maybe you have an app that decides how to send
messages to your server. If you're exposing an email address, then
clearly you need to have an smtp server, which is probably going to be
Postfix.
There was a suggestion to just have the server dump into user Maildirs.
It's probably the easiest thing. Bear in mind, though, that user
management for Maildir setups can be quite complex if you have a lot of
users.
If you want to use a database, there are least 3 methods.
1. Use DBMail through IMAP/API. I'm still not sure if there's an
api/protocol that will allow you to query/manipulate at a global/root level.
2. Use DBMail directly through SQL. It's been discouraged here, so at
the very least you're not going to get any help doing it.
3. Implement LMTP yourself or else use a Milter to store you messages.
I've seen simple examples of LMTP code around. Milters are easier to
implement, but not as clean doing it through LMTP.
On 4/23/2014 12:49 PM, Jeffrey Starin wrote:
I had thought of that but I don't control the user and how they
connect to my mail system. Perhaps if you give me more information
about rolling my own, I could better answer. Do you mean create my
own SMTP server that they connect to to send the message?
Thank you
On 04/23/2014 03:00 PM, furface wrote:
Jeff, is it a requirement that the message gets sent via smtp? If not
you might consider rolling your own messaging system + database back
end. In my experience you end up paying for all the overhead that
comes with trying to morph systems into other systems that aren't
closely related.
Just and idea.
On 4/23/2014 11:04 AM, jeffrey starin wrote:
Good question what am I doing with them?
The project calls for triggering other database/shell script
functions based upon the 1) content of subject line and 2) GPS data
contained in image (smartphones embed GPS data in images snapped
with them).. Think of it as a poor mans input form but the user
instead of filling out a form sends a message. The message contains
the data the project needs to capture for the record for that email
address.
Once I extract image/subject from email DBMail has no further
function for that email address.
Actually pretty simple don't over think it. I just need to extract
data.
______________________________
sent from a portable device please pardon the brevity and
grammatical errors.
On Apr 23, 2014 1:37 PM, "furface" <[email protected]
<mailto:[email protected]>> wrote:
I believe that messages are put together in a rather complex
structure of attachments, headers, & body. I replied previously
on the subject, but I have to admit I know very little about it.
I think it's called "mime chunking" or "single instance storage."
http://dbmail.10918.n7.nabble.com/Newbie-Question-single-instance-store-for-attachmens-td13048.html
As for my question about root level access, I believe a more
serious problem is that there is nothing in the IMAP protocol
that allows for cross user searching & manipulation. Am I
wrong? Does DBMail provide for this?
Jeff, if people aren't reading or sending messages, what are you
doing with your messages if you don't mind my asking?
Thanks.
On 4/23/2014 10:18 AM, jeffrey starin wrote:
Maybe I have a fundamental misunderstanding about DBMail. Are
the individual message parts, I.e. subject body email address
saved in a mysql record with fields for each part? The
intention in this project is not to use DBMail/iredmail as an
email messaging platform but as a data store only. People will
not be reading or sending email via this particular setup. The
content of sujbect and attached image trigger events only. No
bi-directional messaging at all.
Thanks
______________________________
sent from a portable device please pardon the brevity and
grammatical errors.
On Apr 23, 2014 1:09 PM, "furface" <[email protected]
<mailto:[email protected]>> wrote:
Most useful queries and updates involve root access, and
client level IMAP root access is a serious security
problem. Is it even possible in DBmail? How would you do
global queries over the entire data set for all users?
A lesser problem is that a lot of people find IMAP quite an
ugly language for data queries, but I suppose it can be
solved by wrapping in some sort of API. My gut tells me
that having low level access to sql is always going to be
more efficient and easier to code, but perhaps not for
DBMail's data structure.
>>sure, it is do-able but it is pretty dumb use
imap-libraries and fetch the recostructed message with them
that is a standarized >>protocol, the low-level storage of
a de-duplicating mailserver is usually not your businesss
_______________________________________________
DBmail mailing list
[email protected] <mailto:[email protected]>
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
_______________________________________________
DBmail mailing list
[email protected] <mailto:[email protected]>
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
_______________________________________________
DBmail mailing list
[email protected] <mailto:[email protected]>
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
