1 |
On Tuesday, December 30, 2014 08:11:15 AM Bruce Hill, Jr. wrote: |
2 |
> > On December 27, 2014 at 10:19 AM Andrew Savchenko <bircoph@g.o> |
3 |
> > wrote: |
4 |
> > |
5 |
> > If you have mail problems, check your MTA or whatever you are |
6 |
> > using to receive e-mail from this list. As you can see, other |
7 |
> > people don't have this problems. |
8 |
> |
9 |
> On my workstation mail is POP3 using mutt and mail-mta/msmtp is the MTA. |
10 |
> |
11 |
> > Just my guess: greylisting is broken (or had a temporary lag) on |
12 |
> > mail server you are using. |
13 |
> |
14 |
> There is no greylisting/blacklisting being done. |
15 |
> I checked mail at the web interface for the hosting company, and there was |
16 |
> no repeat of messages here; only in Mutt. Now there is another account |
17 |
> doing the same thing. |
18 |
> |
19 |
> Can you offer any technical suggestions as for what to check? |
20 |
|
21 |
Do you leave the messages on the mailserver? |
22 |
In that case, ensure your POP3-client keeps a list of message-ids (UIDL) and |
23 |
only downloads messages that haven't been downloaded before. |
24 |
|
25 |
Here is what the man page for fetchmail says about it: |
26 |
*** |
27 |
|
28 |
|
29 |
-U | --uidl |
30 |
(Keyword: uidl) |
31 |
Force UIDL use (effective only with POP3). Force client-side |
32 |
tracking of 'newness' of messages (UIDL stands for "unique ID listing" and is |
33 |
described in RFC1939). Use with 'keep' to use a mailbox as a baby news drop |
34 |
for a group |
35 |
of users. The fact that seen messages are skipped is logged, |
36 |
unless error logging is done through syslog while running in daemon mode. |
37 |
Note that fetchmail may automatically enable this option depending on upstream |
38 |
server capa- |
39 |
bilities. Note also that this option may be removed and forced |
40 |
enabled in a future fetchmail version. See also: --idfile. |
41 |
|
42 |
*** |
43 |
|
44 |
I don't know if there is an equivalent for mutt as I don't use that. |
45 |
|
46 |
-- |
47 |
Joost |