logs archiveIRC Archive / Freenode / #exim / 2010 / June / 30 / 1
caffiend
leftStanding, what is in /etc/email-addresses ?
whoops, hey leftStanding that's exim -d -bt not exim -d bt
tsunamie if you have it in a vm why do you want to mount via iscsi instead of just creating another disk?
tsunamie
because Ubuntu cloud systems do not store a VM hard drive on a physical medium. It does it in RAM
caffiend
ahh
tsunamie
therefore if the server crash's the disk and all it's content disappears
which means beingable to mount a Iscsi solution (SAN)a nd configuring exim to use that will resolve this issue
since the files will still be there when I recreate the VM and remount the drive
caffiend
so you have the iscsi target mounted on the host already?
tsunamie
that would be the idea
I am working throught the technical problems one by one
at this point
caffiend
so why not just make the mountpoint /var/spool/exim or where ever your spool is? No need to overcomplicate it
tsunamie
screating the Iscusi and getting ubuntu to mount it as a external drive is not the issue
see
this is where my ignorance drops in
I am 50/50 on exim
I understand how the transports/routers work
however I am unsure of what you mean when you say make the mount point x/y/z
caffiend
do you know how to use the iscis initiator with ubuntu? I don't
         

ij_
tsunamie: you are not familiar with mounting devices under unix?
tsunamie
no
caffiend
is this for your work? If so you are probably biting off more than you can chew if this is a production system.
ij_
tsunamie: but you're familiar with DFS trees under Windows?
tsunamie
yes
let me make myself clear
ij_
tsunamie: it's basically the same... you have a tree beginning under / and a lots of dirs... now you can "mount" a remote tree or an extra device at any point under that try... let's say you have another disk like d: in windows... in linux it's /dev/sdb1 for the first partition on second drive
now you can just mount /dev/sdb1 /var/spool/exim
tsunamie
I see
right
I understand
can you give me a command to check weather the mount is pointing to the right location?
ij_
instead of a physical device you can use something remote like NFS, Samba/CIFS or, let's say, an iSCSI target
caffiend
tsunamie, mount is the command
ij_
tsunamie: just type "mount" and it will display the current mount table
tsunamie
k
thanks
thats cleared my head now
I feel lighter
LOL
been staring at the screen for 12 hours now working this whole test system out
caffiend
your snowblind now, you should put it aside for a while. Take a walk and clear your head
ack, s/your/you're/
sh*t sh*t sh*t, I can't believe I did that
vorlock
hi guys, is in exim variable which describes recipient?
phx
vorlock, yes. check docs
vorlock
phx: trying to find it but ...
borei
hi falks
does anybody know what happened with DCC site ?
www.rhyolite.com is down for second day
nobody ?
CunningPike
?
borei
CunningPike: i can't get onto stat page
Peitolm
I have an ACL rejecting emails based on the contents of a file '/etc/exim/sender_reject.list', format was '*@0-2u.com' for example, this worked, but was slow, so I tried to convert it to a dbm, but now it's not matching, has anyone else done this? (deny senders = dbm;/etc/exim/sender_reject.db)
caffiend
Peitolm, this may be similar enough to work for you with some minor modifications; http://www.exim-users.org/forums/showthread.php?p=211892
         

Peitolm
potentially
I think i might have to massage the file
or think about it a bit more
o.k. i'll have to do some wildcard munging, but thanks
caffiend
sure thing, happy hunting
Peitolm
caffiend: deny senders = ${lookup{$sender_address}dbm*@{/etc/exim/sender_reject.db}{$sender_address}{}}
seems to work
caffiend
and it's not just blocking all senders?
Peitolm
it's the *@ that's the funky bit
nope
caffiend
that is right funky
Peitolm
well, i've not tried, but I have a second list of local_sender_reject, and it's matching on that
caffiend
does the sender_reject.db contain whole addresses or just domains?
Peitolm
<lookup type>*@ says, "if the lookup fails, then drop everythign up to the first @ andreplace with*@:
caffiend
hurm
Peitolm
sender_reject.db has things like *@0-2u.com local_sender_reject.db has stiff like foo@bar.com
caffiend
but *@0-2u.com would be the same as just denying all incoming mail with the {$domain} and you can just get rid of the *@ yeah?
Peitolm
http://www.exim.org/exim-html-current/doc/html/spec_html/ch09.html#SECTdefaultvaluelookups
ah, but i think i have other entries in teh file for user@domain
and that would then require 2 lookups
this is a sender acl,
caffiend
I think I understand, my coffee is wearing off
so I'm a little slow right now
Peitolm
actually, it does look like the file is just *@domain
but this way it's the same lookup as the one that does
caffiend
so then this solution may scan the file up to three times per delivery
Peitolm
4, but yes
caffiend
ouch
Peitolm
at least it's not lsearching now
the db is much faster
caffiend
that's something at least
Peitolm
I'm not too fussed about the extra lookups, at least they're now in a db
caffiend
hell if it came down to it you could always put the db files on a ramfs
Peitolm
heh, it'll be in zfs arc cache
caffiend
ahhhh, that'll be nice
Peitolm
it's only 771k lines
« prev next »