You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(16) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(2) |
Feb
|
Mar
(4) |
Apr
|
May
|
Jun
|
Jul
(8) |
Aug
(21) |
Sep
(17) |
Oct
(35) |
Nov
(39) |
Dec
(55) |
| 2006 |
Jan
(70) |
Feb
(11) |
Mar
(55) |
Apr
(27) |
May
(73) |
Jun
(47) |
Jul
(63) |
Aug
(27) |
Sep
(52) |
Oct
(39) |
Nov
(87) |
Dec
(15) |
| 2007 |
Jan
(23) |
Feb
(46) |
Mar
(108) |
Apr
(63) |
May
(54) |
Jun
(34) |
Jul
(29) |
Aug
(103) |
Sep
(46) |
Oct
(69) |
Nov
(29) |
Dec
(17) |
| 2008 |
Jan
(45) |
Feb
(32) |
Mar
(25) |
Apr
(17) |
May
(39) |
Jun
(20) |
Jul
(64) |
Aug
(31) |
Sep
(38) |
Oct
(20) |
Nov
(42) |
Dec
(50) |
| 2009 |
Jan
(10) |
Feb
(38) |
Mar
(3) |
Apr
(29) |
May
(41) |
Jun
(31) |
Jul
(21) |
Aug
(53) |
Sep
(49) |
Oct
(26) |
Nov
(28) |
Dec
(15) |
| 2010 |
Jan
(83) |
Feb
(38) |
Mar
(33) |
Apr
(44) |
May
(9) |
Jun
(16) |
Jul
(35) |
Aug
(38) |
Sep
(11) |
Oct
(35) |
Nov
(68) |
Dec
(19) |
| 2011 |
Jan
(16) |
Feb
(69) |
Mar
(42) |
Apr
(54) |
May
(56) |
Jun
(29) |
Jul
|
Aug
(65) |
Sep
(3) |
Oct
(39) |
Nov
(33) |
Dec
(4) |
| 2012 |
Jan
(31) |
Feb
(21) |
Mar
(26) |
Apr
(13) |
May
(38) |
Jun
(39) |
Jul
(14) |
Aug
(31) |
Sep
(8) |
Oct
(32) |
Nov
(12) |
Dec
(16) |
| 2013 |
Jan
(40) |
Feb
(22) |
Mar
(21) |
Apr
(15) |
May
(13) |
Jun
(9) |
Jul
(34) |
Aug
(10) |
Sep
(10) |
Oct
|
Nov
(7) |
Dec
(1) |
| 2014 |
Jan
(25) |
Feb
(9) |
Mar
(8) |
Apr
(12) |
May
(7) |
Jun
|
Jul
(7) |
Aug
(4) |
Sep
(27) |
Oct
(25) |
Nov
(18) |
Dec
(3) |
| 2015 |
Jan
(18) |
Feb
(13) |
Mar
(4) |
Apr
(19) |
May
(11) |
Jun
|
Jul
(1) |
Aug
(7) |
Sep
(6) |
Oct
(4) |
Nov
(19) |
Dec
(6) |
| 2016 |
Jan
|
Feb
(8) |
Mar
(14) |
Apr
|
May
(11) |
Jun
|
Jul
(2) |
Aug
(3) |
Sep
(10) |
Oct
|
Nov
(11) |
Dec
(17) |
| 2017 |
Jan
(17) |
Feb
(35) |
Mar
|
Apr
(4) |
May
(8) |
Jun
(2) |
Jul
(16) |
Aug
|
Sep
(5) |
Oct
(11) |
Nov
(15) |
Dec
(10) |
| 2018 |
Jan
|
Feb
(3) |
Mar
|
Apr
(3) |
May
(2) |
Jun
(8) |
Jul
|
Aug
(10) |
Sep
(17) |
Oct
(15) |
Nov
(12) |
Dec
(10) |
| 2019 |
Jan
(4) |
Feb
(14) |
Mar
(33) |
Apr
(17) |
May
(7) |
Jun
(6) |
Jul
(2) |
Aug
(4) |
Sep
(22) |
Oct
(13) |
Nov
|
Dec
|
| 2020 |
Jan
(36) |
Feb
(19) |
Mar
(31) |
Apr
(2) |
May
(22) |
Jun
(7) |
Jul
(25) |
Aug
(9) |
Sep
(17) |
Oct
(52) |
Nov
(13) |
Dec
(9) |
| 2021 |
Jan
(23) |
Feb
(13) |
Mar
(9) |
Apr
(15) |
May
(3) |
Jun
(7) |
Jul
(4) |
Aug
(23) |
Sep
(3) |
Oct
(8) |
Nov
(28) |
Dec
(9) |
| 2022 |
Jan
(38) |
Feb
(2) |
Mar
(56) |
Apr
(24) |
May
(29) |
Jun
(22) |
Jul
(6) |
Aug
(1) |
Sep
|
Oct
(13) |
Nov
(2) |
Dec
|
| 2023 |
Jan
(6) |
Feb
(1) |
Mar
(1) |
Apr
(4) |
May
|
Jun
|
Jul
(21) |
Aug
(5) |
Sep
(1) |
Oct
|
Nov
(5) |
Dec
|
| 2024 |
Jan
(15) |
Feb
(4) |
Mar
|
Apr
(4) |
May
(11) |
Jun
(9) |
Jul
(1) |
Aug
|
Sep
(9) |
Oct
(9) |
Nov
(1) |
Dec
(1) |
| 2025 |
Jan
(7) |
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
(10) |
Jul
|
Aug
(1) |
Sep
(12) |
Oct
(24) |
Nov
(14) |
Dec
|
|
From: Rob M. <rob...@gm...> - 2006-06-26 11:12:27
|
On 6/26/06, Dave Patterson <sd...@gm...> wrote:
> Hello all. If this has been posted already, I apologize.
>
> I'm not able to get output to terminal using fetchmail -v
Version of fetchmail?
Contents of .fetchmailrc?
Any command line arguments passed to fetchmail (and what are they)?
--
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
|
|
From: Dave P. <sd...@gm...> - 2006-06-26 10:05:56
|
* Matthias Andree <mat...@gm...> [2006-06-26 09:38:17 +0200]: > Add --nodetach --nosyslog to the command line. > No luck. > Otherwise, syslog (/var/log/mail, /var/log/maillog, or thereabouts). > None there, either... Regards, Dave |
|
From: Matthias A. <mat...@gm...> - 2006-06-26 09:38:20
|
Dave Patterson <sd...@gm...> writes: > Hello all. If this has been posted already, I apologize. > > I'm not able to get output to terminal using fetchmail -v Add --nodetach --nosyslog to the command line. > fetchmail executes normally (I think) as the mail is being delivered to > procmail, and from there to my various boxes. However, I have no > indication as to messages retrieved, skipped, etc. Where to look? Otherwise, syslog (/var/log/mail, /var/log/maillog, or thereabouts). -- Matthias Andree |
|
From: Frederic M. <fre...@wo...> - 2006-06-26 09:25:53
|
Dave Patterson wrote: > Hello all. If this has been posted already, I apologize. > I think it has been answered several times and by people more knowledgeable than me... :-) > I'm not able to get output to terminal using fetchmail -v > > fetchmail executes normally (I think) as the mail is being delivered to > procmail, and from there to my various boxes. However, I have no > indication as to messages retrieved, skipped, etc. Where to look? > In my case, when fetchmail runs in daemon mode (-d option), I also specify the --syslog option and the outputs are written to /var/log/mail.info but it really depends on the configuration of syslog. Frederic |
|
From: Dave P. <sd...@gm...> - 2006-06-26 07:49:43
|
Hello all. If this has been posted already, I apologize. I'm not able to get output to terminal using fetchmail -v fetchmail executes normally (I think) as the mail is being delivered to procmail, and from there to my various boxes. However, I have no indication as to messages retrieved, skipped, etc. Where to look? Cheers, Dave |
|
From: Ian M. <ia...@in...> - 2006-06-23 17:09:03
|
Frederic It is only a way to permit cross mailbox access. Neither of the accounts needs to be privileged, account A only needs access to mailbox B. Considering how it works, I would be surprised if something similar did not exist in many linux based pop3 servers out there. The possibility for an attack on the server using the admin account would exist regardless. An attacker can always try the administrator account, but you have to take the following into account before that would work: - pop3 must be enabled for the admin account... Which normally it would not be. - The admin account has not been renamed (also under windows the admin account has a local spelling, so in france it is administrateur - you have no way of knowing) - Have loads of patience - usually after several failed tries the server stops authenticating the connections and you don't know when it has stopped authenticating and is simply failing all attempts. - As far as I know any linux based pop3 server will allow access to the email for the root account in the same way. In my experience dictionary attacks have been a waste of time for over 10 years on most systems... Embedded systems excluded. Ian Murphy Integra XP http://www.integra-xp.com 00 34 94 621 5265 |
|
From: Frederic M. <fre...@wo...> - 2006-06-23 16:41:21
|
Ian Murphy wrote: > Found a way of doing it. Both the pop3 and imap servers under MS > exchange support a format of > > User domain\privuser\mbx > Passowrd privuserpassword > > Which allows reading a users mailbox using the password of a privileged > account - assuming the appropriate security has been setup in exchange. > > Mbx in this case is simply the user account name. > I can't believe they did it ! It's silly to offer the opportunity to use a system user name and password to access a remote service... A dictionary attack on any pop3 or imap mailbox could yield a system password. Microsoft just never learn :-( Well, at least, it solves your problem :-) Frederic |
|
From: Ian M. <ia...@in...> - 2006-06-23 16:16:17
|
Found a way of doing it. Both the pop3 and imap servers under MS exchange support a format of User domain\privuser\mbx Passowrd privuserpassword Which allows reading a users mailbox using the password of a privileged account - assuming the appropriate security has been setup in exchange. Mbx in this case is simply the user account name. Ian Murphy Integra XP http://www.integra-xp.com 00 34 94 621 5265 -----Mensaje original----- De: fet...@be... [mailto:fet...@be...] En nombre de Frederic Marchal Enviado el: viernes, 23 de junio de 2006 14:14 Para: fet...@li... Asunto: Re: [fetchmail-users] Accessing user mailbox from another account Ian Murphy wrote: > Frederic, Thanks for responding, > > Mail is currently delivered to exchange. They are migrating to a linux > server. No external boxes involved. This requires a visit to each and > every desktop to modify the mail client, so the migration will take > some time (multiple remote offices too to complicate matters) and will > have to be done mailbox by mailbox. > > Step one will be switch the mx record to deliver email to the linux > server by default. Easy. > > Once email is arriving on the linux box, fetchmail is used to pull it > out and redeliver it to the exchange server. Again easy. > Something is missing here... Why do you need fetchmail to do this ? Don't you have one account per user with one password for each user on the linux server ? It seems to me that this part you have got running faces the same problem you are asking a solution for ? Fetchmail must download the mails from the user's mailbox and it must know about all the user names and passwords... How did you got it running ? BTW, here, a .forward file per user would be perfect and more reliable than fetchmail... If your server is running usermin, the user can even remove the redirection by himself when he starts fetching his mails on the linux server. > When a users mail client is switched from exchange to using pop3 > against the linux server the pull-from-linux-push-to-exchange will be > switched off for their mailbox. > > However the problem is that internal users will continue to send email > via exchange, which will deliver to the now unmonitored exchange > mailbox. > > What I want to do is pull any mail which may arrive out of the exhange > mailbox and deliver it to the users mailbox on the linux box. However > since users change their passwords, and its not a good idea, I didn't > want to make a big list of each user account and their password just > to achieve this. > > I was hoping either pop3 or imap would have an authentication type > which would allow me to do something like > > Fetch mail using user administrator password asecret from mailbox > johndoe on server 1.2.3.4 deliver to smtpserver 1.2.3.5 > No. As far as I know, imap and pop3 provide access to one and only one mailbox and more specifically to the mailbox that was named during the authentication. In fact, you don't provide a user name with some rights attached to it when you use pop3 or imap. You provide the name of a mailbox. (Somebody fix this if I'm wrong !) But that doesn't mean you have to create the dreaded list of user/password now... Can you tell exchange to redirect the mails of the users that already moved to the linux server ? I'm thinking about an alias or something like that to an internal server name such as us...@li.... That domain would be considered local by the linux server and the exchange server would just have to know the route to that server. Or could you divert the mails of those users to a single account on the exchange server and fetch the mails from that account ? Frederic _______________________________________________ fetchmail-users mailing list fet...@li... http://lists.berlios.de/mailman/listinfo/fetchmail-users |
|
From: Frederic M. <fre...@wo...> - 2006-06-23 14:14:03
|
Ian Murphy wrote: > Frederic, Thanks for responding, > > Mail is currently delivered to exchange. They are migrating to a linux > server. No external boxes involved. This requires a visit to each and > every desktop to modify the mail client, so the migration will take some > time (multiple remote offices too to complicate matters) and will have > to be done mailbox by mailbox. > > Step one will be switch the mx record to deliver email to the linux > server by default. Easy. > > Once email is arriving on the linux box, fetchmail is used to pull it > out and redeliver it to the exchange server. Again easy. > Something is missing here... Why do you need fetchmail to do this ? Don't you have one account per user with one password for each user on the linux server ? It seems to me that this part you have got running faces the same problem you are asking a solution for ? Fetchmail must download the mails from the user's mailbox and it must know about all the user names and passwords... How did you got it running ? BTW, here, a .forward file per user would be perfect and more reliable than fetchmail... If your server is running usermin, the user can even remove the redirection by himself when he starts fetching his mails on the linux server. > When a users mail client is switched from exchange to using pop3 against > the linux server the pull-from-linux-push-to-exchange will be switched > off for their mailbox. > > However the problem is that internal users will continue to send email > via exchange, which will deliver to the now unmonitored exchange > mailbox. > > What I want to do is pull any mail which may arrive out of the exhange > mailbox and deliver it to the users mailbox on the linux box. However > since users change their passwords, and its not a good idea, I didn't > want to make a big list of each user account and their password just to > achieve this. > > I was hoping either pop3 or imap would have an authentication type which > would allow me to do something like > > Fetch mail using user administrator password asecret from mailbox > johndoe on server 1.2.3.4 deliver to smtpserver 1.2.3.5 > No. As far as I know, imap and pop3 provide access to one and only one mailbox and more specifically to the mailbox that was named during the authentication. In fact, you don't provide a user name with some rights attached to it when you use pop3 or imap. You provide the name of a mailbox. (Somebody fix this if I'm wrong !) But that doesn't mean you have to create the dreaded list of user/password now... Can you tell exchange to redirect the mails of the users that already moved to the linux server ? I'm thinking about an alias or something like that to an internal server name such as us...@li.... That domain would be considered local by the linux server and the exchange server would just have to know the route to that server. Or could you divert the mails of those users to a single account on the exchange server and fetch the mails from that account ? Frederic |
|
From: Ian M. <ia...@in...> - 2006-06-23 12:02:17
|
Frederic, Thanks for responding, Mail is currently delivered to exchange. They are migrating to a linux server. No external boxes involved. This requires a visit to each and every desktop to modify the mail client, so the migration will take some time (multiple remote offices too to complicate matters) and will have to be done mailbox by mailbox. Step one will be switch the mx record to deliver email to the linux server by default. Easy. Once email is arriving on the linux box, fetchmail is used to pull it out and redeliver it to the exchange server. Again easy. When a users mail client is switched from exchange to using pop3 against the linux server the pull-from-linux-push-to-exchange will be switched off for their mailbox. However the problem is that internal users will continue to send email via exchange, which will deliver to the now unmonitored exchange mailbox. What I want to do is pull any mail which may arrive out of the exhange mailbox and deliver it to the users mailbox on the linux box. However since users change their passwords, and its not a good idea, I didn't want to make a big list of each user account and their password just to achieve this. I was hoping either pop3 or imap would have an authentication type which would allow me to do something like Fetch mail using user administrator password asecret from mailbox johndoe on server 1.2.3.4 deliver to smtpserver 1.2.3.5 Ian Murphy Integra XP http://www.integra-xp.com 00 34 94 621 5265 -----Mensaje original----- De: Frederic Marchal [mailto:fre...@wo...] Enviado el: viernes, 23 de junio de 2006 11:49 Para: Ian Murphy CC: fet...@li... Asunto: Re: [fetchmail-users] Accessing user mailbox from another account Ian Murphy wrote: > I have been charged with migrating an exchange 2000 instalation to a > linux server and am using fetchmail to handle interopability during > the migration period. > > I am currently re-delivering email that arrives on the linux box to > MSExchange via smtp and its working like a dream. > > I now need to be able to pull new email from the exchange server and > deliver it to the linux server. To avoid the need to know the users > passwords I want to give read/write access rights to their mailboxes > to a special account and to read all the mailboxes using a single > priviliged account. > > Now, my problem, what is this type of access called ? I've been > looking at the fetchmail documentation for pop3 and imap access and am > lost in the sea of authentication types and options, though it seems > pretty likely that it is possible. > > Can anyone steer me in the right direction ? I don't understand your current configuration and what you want to achieve, especially, the part about what server is downloading what kind of mail and from where... Depending on the way I read your mail, I understand one of the two following things: 1) You have both a linux *and* an msexchange server fetching inbound e-mails from an outside server (your ISP for instance) and you want to synchronize the e-mails between the two servers so that your users can use any server. 2) Your mails are processed by the msexchange server which act now as a relay for the linux server and you want your users to migrate at their leisure from this server to the linux server before you decommission the msexchange server and make the linux server your main mail server. Since case 2 seems more likely, I'll answer this one for now. If your idea is to read all the mailboxes of all the users from one account on the msexchange server and deliver them to the proper user account on the linux server, then I don't think it is possible (at least not with pop3 or imap but maybe with a samba connection and some cron/bash scripts). You have either to divert a copy of each incoming mail on the msexchange server to one account on that server and read that single account with fetchmail (provided your msexchange server adds the proper information such as a X-Envelope header) or you have to forward the mails of each user to the linux server using the msexchange equivalent to a .forward file on linux (I don't know what that mechanism could be because I don't know msechange). Frederic |
|
From: Frederic M. <fre...@wo...> - 2006-06-23 11:48:44
|
Ian Murphy wrote: > I have been charged with migrating an exchange 2000 instalation to a > linux server and am using fetchmail to handle interopability during > the migration period. > > I am currently re-delivering email that arrives on the linux box to > MSExchange via smtp and its working like a dream. > > I now need to be able to pull new email from the exchange server and > deliver it to the linux server. To avoid the need to know the users > passwords I want to give read/write access rights to their mailboxes > to a special account and to read all the mailboxes using a single > priviliged account. > > Now, my problem, what is this type of access called ? I've been > looking at the fetchmail documentation for pop3 and imap access and am > lost in the sea of authentication types and options, though it seems > pretty likely that it is possible. > > Can anyone steer me in the right direction ? I don't understand your current configuration and what you want to achieve, especially, the part about what server is downloading what kind of mail and from where... Depending on the way I read your mail, I understand one of the two following things: 1) You have both a linux *and* an msexchange server fetching inbound e-mails from an outside server (your ISP for instance) and you want to synchronize the e-mails between the two servers so that your users can use any server. 2) Your mails are processed by the msexchange server which act now as a relay for the linux server and you want your users to migrate at their leisure from this server to the linux server before you decommission the msexchange server and make the linux server your main mail server. Since case 2 seems more likely, I'll answer this one for now. If your idea is to read all the mailboxes of all the users from one account on the msexchange server and deliver them to the proper user account on the linux server, then I don't think it is possible (at least not with pop3 or imap but maybe with a samba connection and some cron/bash scripts). You have either to divert a copy of each incoming mail on the msexchange server to one account on that server and read that single account with fetchmail (provided your msexchange server adds the proper information such as a X-Envelope header) or you have to forward the mails of each user to the linux server using the msexchange equivalent to a .forward file on linux (I don't know what that mechanism could be because I don't know msechange). Frederic |
|
From: Ian M. <ia...@in...> - 2006-06-22 19:10:55
|
I have been charged with migrating an exchange 2000 instalation to a linux server and am using fetchmail to handle interopability during the migration period. I am currently re-delivering email that arrives on the linux box to MSExchange via smtp and its working like a dream. I now need to be able to pull new email from the exchange server and deliver it to the linux server. To avoid the need to know the users passwords I want to give read/write access rights to their mailboxes to a special account and to read all the mailboxes using a single priviliged account. Now, my problem, what is this type of access called ? I've been looking at the fetchmail documentation for pop3 and imap access and am lost in the sea of authentication types and options, though it seems pretty likely that it is possible. Can anyone steer me in the right direction ? regards Ian Murphy Integra XP http://www.integra-xp.com 00 34 94 621 5265 |
|
From: Volker K. <lis...@pa...> - 2006-06-18 04:52:36
|
Hi Matthias, > > fetchmail: Server certificate verification error: self signed > > certificate > This issue is fixed in the latest available release, 6.3.4, where > sslfingerprint (on the command line or in the rcfile) should suppress these > warnings unless sslcertck is enabled. Thanks much! Recompiling the SUSE source rpm with the latest fetchmail turned out to be very straightforward. > - ask your ISP to provide proper SSL certificates Did that, and was told that the current self-signed cert is on the testing rack, and once email is moved to the next setup in a few weeks, externally signed certs will be used, so the problem for me will solve itself. Thanks again, Volker -- Volker Kuhlmann is list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me. |
|
From: Matthias A. <mat...@gm...> - 2006-06-14 12:32:00
|
Volker Kuhlmann <lis...@pa...> writes:
> I just upgraded from SUSE 10.0 to 10.1, and with it to fetchmail 6.3.2.
> Now I see that one of my email providers must have introduced TLS, but
> with a self-signed cert. The first time cron mails me a
>
> fetchmail: Server certificate verification error: self signed
> certificate
> it's informative, but after the 1735th time the novelty value has worn a
> bit.
This issue is fixed in the latest available release, 6.3.4, where
sslfingerprint (on the command line or in the rcfile) should suppress these
warnings unless sslcertck is enabled.
Your options are (pick at least one):
- ask your ISP to provide proper SSL certificates
- list sslfingerpint AND
ask Novell (SUSE) to update fetchmail to 6.3.4
or cherrypick(*) these changes from 6.3.4:
* SSL/TLS: if, for a certain server, an sslfingerprint is specified and
sslcertck is NOT set, suppress printing SSL certificate mismatch errors.
(Reported by Hannes Erven.)
* SSL/TLS: always print if the sslfingerprint mismatches, even in silent
mode. (This is for consistency with certificate verification errors.)
(*) For cherrypicking, the
repository is: http://mknod.org/svn/fetchmail/BRANCH_6-3
to pull: svn diff -r4780:4781
- ask your ISP for their home-made CA root certificate that you can
stuff into your /etc/ssl/certs (or whatever your CApath is).
--
Matthias Andree
|
|
From: Volker K. <lis...@pa...> - 2006-06-14 09:12:28
|
I just upgraded from SUSE 10.0 to 10.1, and with it to fetchmail 6.3.2. Now I see that one of my email providers must have introduced TLS, but with a self-signed cert. The first time cron mails me a fetchmail: Server certificate verification error: self signed certificate it's informative, but after the 1735th time the novelty value has worn a bit. How do I get rid of this? The manpage is not helping. I added an sslfingerprint, no difference. I'm quite sure that mail from and to this provider is not encrypted, so strong protection between me and the provider is rather moot, but it does protect my download password. I'm not concerned with making sure of getting the right fingerprint (there alternative is using a clear text password). The server is obviously not mine to fix. Surely there must be a better solution than turning off ssl altogether, or filtering fetchmail-cron mail to /dev/null. Please nobody suggest I shouldn't be using cron - I'd be happy to switch to daemon mode if it allowed me to specify the fetch times for each mailbox. (Yes I have a somewhat elaborate wrapper script which handels periodic error mailing and logging.) Thanks much, Volker -- Volker Kuhlmann is list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me. |
|
From: RaFFe <raf...@ya...> - 2006-06-07 17:02:18
|
Hej, I've configured fetchmail right, it connect right to my ISP server and successful read email, but I don't where they was stored... All file in my /var/spool/mail stay empty and no log file was created with any potential error messages ... Does someone have any ideas about my problem ? Thanks in advance, Raffe |
|
From: Rob F. <rf...@fu...> - 2006-06-06 20:39:55
|
Ken Williams wrote: > Hi, I'm lost. > > I run sendmail on linux. I have a mail drop (/var/spool/mail/user) > with some mail in there. I simply want to take this mail and forward it > to another email address like say us...@ya.... > > How can I do this? Seems to be the most difficult thing in the world. Not exactly a fetchmail question, but..... formail -ts /usr/sbin/sendmail us...@ya... < /var/spool/mail/user I have a 141-line shell script to do this robustly, but it all really comes down to that one line. -- ==============================| "A microscope locked in on one point Rob Funk <rf...@fu...> |Never sees what kind of room that it's in" http://www.funknet.net/rfunk | -- Chris Mars, "Stuck in Rewind" |
|
From: Ken W. <ke...@ya...> - 2006-06-06 20:20:19
|
Hi, I'm lost. I run sendmail on linux. I have a mail drop (/var/spool/mail/user) with some mail in there. I simply want to take this mail and forward it to another email address like say us...@ya.... How can I do this? Seems to be the most difficult thing in the world. ke...@ya... Thanks. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
|
From: Matthias A. <mat...@gm...> - 2006-05-31 14:41:52
|
On Wed, 31 May 2006, Filippo Santovito wrote: > Alle 12:56, mercoledì 31 maggio 2006, Matthias Andree ha scritto: > > Apparently yes. Note that procmail needs to be setuid-root for this to > > work (do not run fetchmail as root). > I'm running fecthmail/procmail with suse 10 standard config: > > $ ls -l $(which procmail) > -rwxr-xr-x 1 root root 77793 Jan 21 13:45 /usr/bin/procmail > $ ls -l $(which fetchmail) > -rwxr-xr-x 1 root root 225988 Sep 9 2005 /usr/bin/fetchmail > > fetchmail is started in deamon mode by init.d script. SUSE start fetchmail as root, against my advise :-( So, it works ok, but isn't a recommended configuration security-wise. -- Matthias Andree |
|
From: Filippo S. <fil...@em...> - 2006-05-31 14:35:01
|
Alle 12:56, mercoledì 31 maggio 2006, Matthias Andree ha scritto: > Apparently yes. Note that procmail needs to be setuid-root for this to > work (do not run fetchmail as root). I'm running fecthmail/procmail with suse 10 standard config: $ ls -l $(which procmail) -rwxr-xr-x 1 root root 77793 Jan 21 13:45 /usr/bin/procmail $ ls -l $(which fetchmail) -rwxr-xr-x 1 root root 225988 Sep 9 2005 /usr/bin/fetchmail fetchmail is started in deamon mode by init.d script. -- Filippo Santovito Le informazioni contenute nella comunicazione che precede possono essere riservate e sono, comunque, destinate esclusivamente alla persona o all'ente sopraindicati. La diffusione, distribuzione e/o copiatura del documento trasmesso da parte di qualsiasi soggetto diverso dal destinatario è proibita. La sicurezza e la correttezza dei messaggi di posta elettronica non possono essere garantite. Se avete ricevuto questo messaggio per errore, Vi preghiamo di contattarci immediatamente. Grazie. Confidentiality Notes: The information in this message is intended to be confidential and for the use of only the individual or entity named above. The information herein contained may be considered legally privileged information. If you are not the intended recipient you are notified that retention, dissemination, distribution other than to the intended recipient, or copying of this message is strictly prohibited. If you receive this message in error please notify us immediately by reply e-mail and delete this message. Thank you. |
|
From: Matthias A. <mat...@gm...> - 2006-05-31 12:57:02
|
Filippo Santovito <fil...@em...> writes: > I solved with > user 'remote@popserver' there with password 'xxxx' > options fetchall ssl > mda '/usr/bin/procmail -d first_local second_local' > > It works but is this a correct solution? Apparently yes. Note that procmail needs to be setuid-root for this to work (do not run fetchmail as root). -- Matthias Andree |
|
From: Filippo S. <fil...@em...> - 2006-05-31 10:07:53
|
Alle 02:12, mercoledì 31 maggio 2006, Matthias Andree ha scritto: > poll popserver with proto POP3 > user 'remote@popserver' there with password 'xxxx' > options fetchall ssl > mda '/usr/sbin/sendmail -i -f %F -- account1 account2' I solved with user 'remote@popserver' there with password 'xxxx' options fetchall ssl mda '/usr/bin/procmail -d first_local second_local' It works but is this a correct solution? -- Filippo Santovito Le informazioni contenute nella comunicazione che precede possono essere riservate e sono, comunque, destinate esclusivamente alla persona o all'ente sopraindicati. La diffusione, distribuzione e/o copiatura del documento trasmesso da parte di qualsiasi soggetto diverso dal destinatario è proibita. La sicurezza e la correttezza dei messaggi di posta elettronica non possono essere garantite. Se avete ricevuto questo messaggio per errore, Vi preghiamo di contattarci immediatamente. Grazie. Confidentiality Notes: The information in this message is intended to be confidential and for the use of only the individual or entity named above. The information herein contained may be considered legally privileged information. If you are not the intended recipient you are notified that retention, dissemination, distribution other than to the intended recipient, or copying of this message is strictly prohibited. If you receive this message in error please notify us immediately by reply e-mail and delete this message. Thank you. |
|
From: Filippo S. <fil...@em...> - 2006-05-31 09:37:53
|
Alle 02:12, mercoledì 31 maggio 2006, Matthias Andree ha scritto: > If the local machine has a sendmail-compatible sendmail command > (Postfix, Exim also count here), try: > > poll popserver with proto POP3 > user 'remote@popserver' there with password 'xxxx' > options fetchall ssl > mda '/usr/sbin/sendmail -i -f %F -- account1 account2' can this be done with procmail instead of using a full featured MTA? -- Filippo Santovito Le informazioni contenute nella comunicazione che precede possono essere riservate e sono, comunque, destinate esclusivamente alla persona o all'ente sopraindicati. La diffusione, distribuzione e/o copiatura del documento trasmesso da parte di qualsiasi soggetto diverso dal destinatario è proibita. La sicurezza e la correttezza dei messaggi di posta elettronica non possono essere garantite. Se avete ricevuto questo messaggio per errore, Vi preghiamo di contattarci immediatamente. Grazie. Confidentiality Notes: The information in this message is intended to be confidential and for the use of only the individual or entity named above. The information herein contained may be considered legally privileged information. If you are not the intended recipient you are notified that retention, dissemination, distribution other than to the intended recipient, or copying of this message is strictly prohibited. If you receive this message in error please notify us immediately by reply e-mail and delete this message. Thank you. |
|
From: Matthias A. <mat...@gm...> - 2006-05-31 02:12:46
|
Filippo Santovito <fil...@em...> writes: > Hi all, > I have a remote pop account (remote@popserver) that I need to duplicate into > two local mail spool (account1@local, account2@local); > I tried with: > > ############################################# > poll popserver with proto POP3 > user 'remote@popserver' there with password 'xxxx' is 'account1' here options > fetchall ssl > > poll popserver with proto POP3 > user 'remote@popserver' there with password 'xxxx' is 'account2' here options > fetchall ssl nokeep > ############################################# > > but only account1 spool is created and filled with emails. > How can I duplicate the remote account? If the local machine has a sendmail-compatible sendmail command (Postfix, Exim also count here), try: poll popserver with proto POP3 user 'remote@popserver' there with password 'xxxx' options fetchall ssl mda '/usr/sbin/sendmail -i -f %F -- account1 account2' Just be sure none of account1 and account2 forward back onto remote@popserver. Note that mda has some other implications -- see the man page. -- Matthias Andree |
|
From: Filippo S. <fil...@em...> - 2006-05-31 00:33:35
|
Hi all, I have a remote pop account (remote@popserver) that I need to duplicate into two local mail spool (account1@local, account2@local); I tried with: ############################################# poll popserver with proto POP3 user 'remote@popserver' there with password 'xxxx' is 'account1' here options fetchall ssl poll popserver with proto POP3 user 'remote@popserver' there with password 'xxxx' is 'account2' here options fetchall ssl nokeep ############################################# but only account1 spool is created and filled with emails. How can I duplicate the remote account? -- Filippo Santovito Le informazioni contenute nella comunicazione che precede possono essere riservate e sono, comunque, destinate esclusivamente alla persona o all'ente sopraindicati. La diffusione, distribuzione e/o copiatura del documento trasmesso da parte di qualsiasi soggetto diverso dal destinatario è proibita. La sicurezza e la correttezza dei messaggi di posta elettronica non possono essere garantite. Se avete ricevuto questo messaggio per errore, Vi preghiamo di contattarci immediatamente. Grazie. Confidentiality Notes: The information in this message is intended to be confidential and for the use of only the individual or entity named above. The information herein contained may be considered legally privileged information. If you are not the intended recipient you are notified that retention, dissemination, distribution other than to the intended recipient, or copying of this message is strictly prohibited. If you receive this message in error please notify us immediately by reply e-mail and delete this message. Thank you. |