Re: exim4 fetchmail delivery more than 10 rejected
On Tue 27 May 2014 at 21:53:40 -0400, Harry Putnam wrote: > Oh, and is it really enough just to run `/etc/init.d/exim4 reload' reload regenerates the configuration and tells exim to reread it. I've always stuck with using this. > (after making the edit) or would it be a time to use one or more of > exim4's `update' commands. Beware. update-exim4.conf does generate the main configuration files but the "RECOMMENDED USAGE" section of its manual describes a situation when you may not want to invoke it. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/28052014161642.c8b76fa70...@desktop.copernicus.demon.co.uk
Re: exim4 fetchmail delivery more than 10 rejected
On Tue, May 27, 2014 at 09:47:09PM -0400, Harry Putnam wrote: > Jonathan Dowland writes: > > > Hi, > > > > This is a common problem (I remember hitting it myself, once upon a time!) > > The Debian Exim FAQ recommends changing fetchmail's behaviour, rather than > > Exim's: > > > > https://wiki.debian.org/PkgExim4UserFAQ#Exim_stops_delivery_after_ten_messages_are_received > > Thanks, and yeah I read that before posting and was sort of amazed at > the way the burden of getting around what is a quite an unpopular > default in exim4 was to shift it to fetchmail. hehe... pretty slick. > > I saw how to use the fetchmail trick right off but felt like, `hey wait > a minute..' I'm ready this to find a way to make a more sensible > setting for my situation in exim4. > > That section tells you the setting can be altered but never says how > in any detail, instead slipping right into the fetchmail crutch. [...] So I read about this and was wondering why I don't have this problem since I've been using exim and fetchmail for years and years. My memory at this point is fuzzy, but I think I may have encountered the situation where mail was getting queued and one way or another, possibly using fetchmailconf, stumbled upon throwing a batchlimit 10 on each poll line. The result is that fetchmail deliberately ends (and reestablishes, if necessary) the SMTP connection every 10 messages. Yes, it's another fetchmail-based workaround, but I figured it was worth mentioning in this thread for the benefit of anyone else who might stumble upon it in the future. It might even make sense to put it into that FAQ on the wiki; I'd argue it's a better solution than postconnect since it doesn't require the fetchmail user to be in the Debian-exim group, and doesn't require giving up on exim by going straight through procmail. --Greg -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140528021518.ga3...@anthropohedron.net
Re: exim4 fetchmail delivery more than 10 rejected
Brian writes: [...] >> The exim4 FAQ tells of a way to put the load on fetchmail and diddle >> around with its config, but also says one might change it in exim4 but >> is not clear about where this change is made. > > I put it right at the start of "MAIN CONFIGURATION SETTINGS". Haa... and as is often the case with good coaching... my first experiment of editing in just the way you describe above... then fetching 227 msgs shows conclusively that the ten msg limit is not mentioned at all. Thanks again. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87zji2zmdl@reader.local.lan
Re: exim4 fetchmail delivery more than 10 rejected
Brian writes: > On Mon 26 May 2014 at 05:48:53 -0400, Harry Putnam wrote: > >> I've tried adding this line: >> >> smtp_accept_queue_per_connection=300 > > I use > >smtp_accept_queue_per_connection=0 > > with the split-file configuration but testing with your setup does not > cause any failure when exim4 is reloaded or restarted. I think you > really should post the error message you get. > >> Then I tried adding it to: >> /etc/exim4/update-exim4.conf.conf > > No. This is the wrong file. > >> The exim4 FAQ tells of a way to put the load on fetchmail and diddle >> around with its config, but also says one might change it in exim4 but >> is not clear about where this change is made. > > I put it right at the start of "MAIN CONFIGURATION SETTINGS". Haaa, thank you sir, now I can do some more directed experimenting. Oh, and is it really enough just to run `/etc/init.d/exim4 reload' (after making the edit) or would it be a time to use one or more of exim4's `update' commands. I'll have an excellent test setup.. I just ran fetchmail -c and see I have 227 messages waiting PS - and thanks for the smooth way of handling the thread interruption -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/874n0a1xej@reader.local.lan
Re: exim4 fetchmail delivery more than 10 rejected
Jonathan Dowland writes: > Hi, > > This is a common problem (I remember hitting it myself, once upon a time!) > The Debian Exim FAQ recommends changing fetchmail's behaviour, rather than > Exim's: > > https://wiki.debian.org/PkgExim4UserFAQ#Exim_stops_delivery_after_ten_messages_are_received Thanks, and yeah I read that before posting and was sort of amazed at the way the burden of getting around what is a quite an unpopular default in exim4 was to shift it to fetchmail. hehe... pretty slick. I saw how to use the fetchmail trick right off but felt like, `hey wait a minute..' I'm ready this to find a way to make a more sensible setting for my situation in exim4. That section tells you the setting can be altered but never says how in any detail, instead slipping right into the fetchmail crutch. I searched the rest of the FAQ thinking surely there would be some details about how to do it... but either I missed it, or it is not there. >From there I went to google and found quite a few conflicting opinions about where and how to set such a thing, and I don't mean just the different locations one finds because of the two ways of organizing the setup (monolithic or multi file), but just different opinions. I never did find what seemed like a definitive explanation of how to do it. So, began experimenting... Oh wait a minute. I just looked ahead in this thread and noticed Brian's last respsonse which clears up the where and how of it. So will spare you all from more ill-informed blather... here. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/878upm1xpe@reader.local.lan
Re: How to get along without an MTA: Was: exim4 fetchmail delivery more than 10 rejected
On Tue 27 May 2014 at 13:53:47 -0400, Steve Litt wrote: > On Tue, 27 May 2014 17:41:50 +0100 > Jonathan Dowland wrote: > > > Hi, > > > > This is a common problem (I remember hitting it myself, once upon a > > time!) The Debian Exim FAQ recommends changing fetchmail's behaviour, > > rather than Exim's: > > > > https://wiki.debian.org/PkgExim4UserFAQ#Exim_stops_delivery_after_ten_messages_are_received > > This reminds me of something I've wanted for a long time. What? The chance to do some troubleshooting? Or the opportunity to break into an existing thread with something which is completely unrelated to the problem at hand? It is generally advised to generate a new post for problems distinct from the one under discussion. Commonsense, good manners etc, etc. > Steve Litt* http://www.troubleshooters.com/ > Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140527190601.gm17...@copernicus.demon.co.uk
How to get along without an MTA: Was: exim4 fetchmail delivery more than 10 rejected
On Tue, 27 May 2014 17:41:50 +0100 Jonathan Dowland wrote: > Hi, > > This is a common problem (I remember hitting it myself, once upon a > time!) The Debian Exim FAQ recommends changing fetchmail's behaviour, > rather than Exim's: > > https://wiki.debian.org/PkgExim4UserFAQ#Exim_stops_delivery_after_ten_messages_are_received This reminds me of something I've wanted for a long time. I'd prefer not to have an MTA anywhere on my LAN. I'm not smart enough to securely configure an MTA, even if it isn't sendmail. As things stand, I grab incoming mail with fetchmail, which pushes the mail to procmail, which drops it in the correct maildir directories of my local Dovecot server. On the few occasions when I want to do a mass-mailing (legal, to existing customers), I use nullmailer to implement the mail and sendmail executables. The one and only reason I have Postfix on my desktop computer is to receive mail from addresses local to my local dovecot: Mainly root, which emails me every time a cron job writes to stdout. I haven't yet figured a way to get either procmail or nullmailer deliver local to my local Dovecot. The day I figure out how to do that is the day I blow postfix right off my box, and never have an MTA again. I'm not an admin, and it's a bad idea for me to be in charge of an MTA. Does anyone know how I can achieve delivery of local users without using an MTA? I'm thinking some sort of shellscript for the mail and/or sendmail executables that does some magic and then calls /usr/bin/procmail -d %T. Thanks, SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140527135347.17d874d7@mydesk
Re: exim4 fetchmail delivery more than 10 rejected
On Mon 26 May 2014 at 05:48:53 -0400, Harry Putnam wrote: > I've tried adding this line: > > smtp_accept_queue_per_connection=300 I use smtp_accept_queue_per_connection=0 with the split-file configuration but testing with your setup does not cause any failure when exim4 is reloaded or restarted. I think you really should post the error message you get. > Then I tried adding it to: > /etc/exim4/update-exim4.conf.conf No. This is the wrong file. > The exim4 FAQ tells of a way to put the load on fetchmail and diddle > around with its config, but also says one might change it in exim4 but > is not clear about where this change is made. I put it right at the start of "MAIN CONFIGURATION SETTINGS". -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/27052014184420.02db20646...@desktop.copernicus.demon.co.uk
Re: exim4 fetchmail delivery more than 10 rejected
Hi, This is a common problem (I remember hitting it myself, once upon a time!) The Debian Exim FAQ recommends changing fetchmail's behaviour, rather than Exim's: https://wiki.debian.org/PkgExim4UserFAQ#Exim_stops_delivery_after_ten_messages_are_received -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140527164150.ga7...@bryant.redmars.org
Re: exim4 fetchmail delivery more than 10 rejected
Harry Putnam wrote: > I've tried adding this line: > smtp_accept_queue_per_connection=300 > to /etc/exim4/exim4.conf.template which causes a failure when I run > /etc/init.d/exim4 reload > (It generates a new conf that exim4 does not accept. That line looks plausible to me. Where did you add it, and what error message did you get? The documentation states that you can set this to zero to disable it entirely: smtp_accept_queue_per_connection Use: main Type: integer Default: 10 This option limits the number of delivery processes that Exim starts automatically when receiving messages via SMTP [...] If the value of the option is greater than zero, and the number of messages received in a single SMTP session exceeds this number, subsequent messages are placed on the queue, but no delivery processes are started. [...] On dial-in client systems it should probably be set to zero (that is, disabled). http://www.exim.org/exim-html-current/doc/html/spec_html/ch-main_configuration.html Chris -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/gtob5bx2qn@news.roaima.co.uk
exim4 fetchmail delivery more than 10 rejected
An exim4 default of accepting no more than 10 messages at one time when I use fetchmail to download pop3 mail. "no immediate delivery: more than 10 messages received in one connection" Shows up in the mail.log and anything over 10 is stuck in a que and delived later. I want to set that limit to a higher number, but googling on that produces a bewildering array of different ideas about how to do that. I've tried adding this line: smtp_accept_queue_per_connection=300 To /etc/exim4/exim4.conf.template which causes a failure when I run /etc/init.d/exim4 reload (It generates a new conf that exim4 does not accept. Then I tried adding it to: /etc/exim4/update-exim4.conf.conf But got the same result. I tried using no spaces between equal sign and value. And using spaces before and after. smtp_accept_queue_per_connection=300 smtp_accept_queue_per_connection = 300 Didn't seem to matter. Still produces a non-usable config. So, does anyone know how I might change the default value of 10 msgs per connection to some higher number? The exim4 FAQ tells of a way to put the load on fetchmail and diddle around with its config, but also says one might change it in exim4 but is not clear about where this change is made. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87k398swe2@newsguy.com
