Ha, ok, I found a workaround. I can simply cat the message back into the mail spool.
cat $msgFile >> $mailSpool
Boom, message is back in the mail spool and my process re-consumes it.
I can't remember the lat time that I used fetchmail.
Well, ultimately, all I need are the messages dumped to file (one file per email). The way I'm achieving this now is by using fetchmail to dump the messages to the user's mail spool, then using formail to separate the messages into individual text files.
cat $mailSpool | formail -ds sh -c "cat > $stagingDir/msg."'$FILENO'
So, if there is a better way to approach this, perhaps in one step, I'm totally game.
Can someone change the category to "IT Discussion", pretty please? I thought that's what I selected, but obviously not.
I have a script put together that parses attachments out of emails and uploads them to a database. Recently, some emails that came through were not processed properly. Since the script runs unattended and my logging is not the best (is on my list of todos to fix), I want to re-process one of the problemed emails via running the script manually. Simple enough?
Well, at first, fetchmail would not retrieve the message at all since it had already "seen" it previously. I figured out that adding --fetchall would force fetchmail to re-download the message. However, even though fetchmail seems to go through the motions of retrieving the aforementioned message, it is not in the mail spool.
If I send new (unique) messages to the account the script watches, fetchmail downloads the message without issue and I see it in the mail spool.
There must be something I'm missing between fetch mail and the user's mail spool, but I'm not sure where to go next.
There has always been a third party rack mount solution for the ERL and ERPoE form factor.
Orinigally designed for the ToughSwitch series
That's pretty cool! I had no idea such an animal exists.
I'll probably go with the ERPro8 mostly for the fact that it's nowhere near as power hungry as the ASA. I'm currently using an ERPro PoE in my home setup and have no complaints. It has served me well.
Why move away from the ERPro8? The OS on the other ER is the same.
I would either be going ERPro PoE -> ASA5510 or ERPro PoE -> ERPro8.
Likely going to do the latter.
Right, my question is - why? If you go the ASA, I get it, you're changing vendors (i.e. new interface), but if going to the ERPro8, why? do you need the extra ports? If not, there's nothing to gain by moving to the ERPro8 over the ERPro POE.
The biggest advantage is the ERPro8 is rack mountable. Also, the ERPro8 does have a little more horsepower behind it but whether or not it'd be noticable in my environment is another story. I suspect if I wanted to do any sort of VPN tunneling it may fair a little better, but that's just a guess. So, mostly because it's rack mountable.
Single VPN would likely not matter at all. JB has shown that if you turn on QoS or other features that an ER-L can slow down (line speed can drop from 1 Gb/s to something like 650 Mb/s - as JB for real numbers). So the ERPro8 might matter here if you do these things, and you have a pipe greater than 650 Mb/s - which you said you'd top out around 100/30, so not likely to affect you.
If I mentioned anywhere that I'd top out around 100/30, that's not correct (maybe you're inadvertently mixing this thread with another?). In terms of Internet service, I would likely top out around 300/10 (most my cable provider will do...and I may take them up on it just because). However, I may want to play with different firewall zones and could see wanting to throw traffic between zones at wirespeed (or as fast as the configuration will allow).
Aside from all that, I like that 1) it's a nice rack-mountable form factor, and 2) I'm not spending any money to get it.
I suppose I should've mentioned that I would be inheriting these devices. No out-of-pocket money on my part (other than the gas to get them home and recurring power bill to keep them on).
Looks like your connection to MangoLassi was lost, please wait while we try to reconnect.