From: Rob M. <rob...@gm...> - 2007-03-21 23:56:31
|
On 3/21/07, Chris <cpo...@ea...> wrote: > > Robb, I tried replying to this last night, when I got home from work today I > had this: > > The message's content type was not explicitly allowed > > Along with the signed message I'd sent encapsulated. I guess signed messages > are no longer allowed? There's been a problem of people sending HTML only emails to the list lately, resulting in the allowed types being clamped down on. If you can did out the MIME type for the signed email I'll see about adding it to the list of allowed types. > Anyway, here is what I sent: > > Thanks Rob, I'll have to wait until another message gets stuck on the server > at earthlink to send the output. I did change logging from syslog to a > seperate fetchmaillog file, that should make things easier when it happens > again. I've also enabled uidl. One probably dumb question though, when you > say "don't use "-m procmail" but deliver directly to your SMTP server" what > do you mean? Well, by default fetchmail will try to connect to an SMTP on loopback. If you're running an SMTP server (sendmail/postfix/exim/qmail/whatever) then you can have fetchmail just pass the email on to it. (If that's equally as clear as mud let me know - it's getting a late here :>) -- Please keep list traffic on the list. Rob MacGregor Whoever fights monsters should see to it that in the process he doesn't become a monster. Friedrich Nietzsche |