From: Leslie R. <les...@si...> - 2021-04-25 17:39:46
|
Hello everyone, I have been using fetchmail for many years with no issues, across several ISPs. A few days ago, however one of my users accounts quit working. The issue, actually, was her client. I had to delete and re-add her account in the client. In the process, her password was changed, and then fetchmail could no longer download her mail. A day later, my own account also quit working. I called the ISP (AT&T) and they informed me users could no longer access mail from a client using their password. Instead, the user has to create a secure keyword. I was also informed the old server (inbound.att.net) is no longer active. Instead, users must download from imap.mail.att.net. The tech claimed POP3 downloads would still work, but I was not able to get fetchmail to login to the server with the POP3 protocol. I would be interested to know if anyone is still able to login to the new server using the POP3 protocol. In any case, I can now login using the IMAP protocol, but fetchmail can only download a single message at a time, producing a mail expunge mismatch error (0 actual != 1 expected) and exiting after each message. Eventually, it does manage to get all the messages, but typically only after a very long time, whenever several messages come in over a short time frame. While not quite critical, this is definitely not good. Is anyone else having this issue with AT&T? How can I fix it? fetchmailrc: set no syslog set logfile "/var/log/fetchmail.log" set postmaster "postmaster" set nobouncemail set no spambounce set properties "" set daemon 60 poll imap.mail.att.net via imap.mail.att.net with proto IMAP service 993 user 'xx...@at...' there with password 'xxxxxxxxxx' is 'xxxxxxxx' here options fetchall forcecr stripcr ssl mda "/usr/bin/procmail -f %F -d %T" user 'yyy...@at...' there with password 'yyyyyyyyyy' is 'yyyyyyyy' here options fetchall forcecr stripcr stripcr ssl mda "/usr/bin/procmail -f %F -d %T" |