[bmk1st]

Hello,

I'm trying to use fetchmail with procmail for first time. I tried to get it to work but I couldn't get it to work without problems. :icon_neut

fetchmail -akv -m "/usr/pkg/bin/procmail -d %T"
fetchmail: 6.2.5 querying incoming.verizon.net (protocol POP3) at Sun Jan 23 13:22:24 2005: poll started
fetchmail: POP3< +OK InterMail POP3 server ready.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK Capability list follows
fetchmail: POP3< TOP
fetchmail: POP3< USER
fetchmail: POP3< RESP_CODES
fetchmail: POP3< PIPELINING
fetchmail: POP3< EXPIRE 30
fetchmail: POP3< UIDL
fetchmail: POP3< IMPLEMENTATION Openwave Email vM.5.01.06.04 201-253-122-130-104
fetchmail: POP3< -20030726
fetchmail: POP3< .
fetchmail: POP3> USER bradleyk80
fetchmail: POP3< +OK please send PASS command
fetchmail: POP3> PASS *
fetchmail: POP3< -ERR invalid user name or password.
fetchmail: invalid user name or password.
fetchmail: Authorization failure on bradleyk80@mail.verizon.net
fetchmail: POP3> QUIT
fetchmail: POP3< +OK bradleyk80 InterMail POP3 server signing off.
fetchmail: 6.2.5 querying incoming.verizon.net (protocol POP3) at Sun Jan 23 13:22:24 2005: poll completed
fetchmail: Query status=3 (AUTHFAIL)
fetchmail: normal termination, status 3

My .fetchmailrc is

poll incoming.verizon.net proto pop3 user "bradleyk80" password "**********"

I know my username and password is right. It works with other email clients. I guess either fetchmail or procmail doesn't work with verizon or something I have missed.

[bmw]

As far as that Verizon server is concerned, you are presenting incorrect credentials, or you don't exist there. There's no arguing with this:
fetchmail: POP3< -ERR invalid user name or password.
Are you sure you are polling the right server?

Upper/lower case issues (userid or password) a possibility?

Maybe they don't allow plain POP3 auth; have you tried telling fetchmail to use "pops" instead (SSL to port 995)?

I'd say you are doing everything correctly with fetchmail itself. That's a clean POP3 session log I see there.

[bmk1st]

Thanks for the reply.

pops did not work so I used ssl at the end:

poll incoming.verizon.net proto pop3 user "bradleyk80" password "**********" ssl

Now, here is the result. I assume it's working.

fetchmail -akv -m "/usr/bin/procmail -d %T"
fetchmail: 6.2.5 querying incoming.verizon.net (protocol POP3) at Mon Jan 24 06:04:36 2005: poll started
fetchmail: 6.2.5 querying incoming.verizon.net (protocol POP3) at Mon Jan 24 06:05:52 2005: poll completed
fetchmail: Query status=2 (SOCKET)
fetchmail: normal termination, status 2

[bmw]

Hmmm... I wonder why you aren't getting the
fetchmail: POP3< +OK InterMail POP3 server ready.
stuff. It looks like it's working. Have you tried emailing yourself through that account?

[bmk1st]

I use mutt with msmtp without ssl to send email. It works fine. I'm still working on fetchmail, though.

[bmk1st]

Ah well, I got it working.

poll "incoming.verizon.net" proto pop3 user "bradleyk80" pass "*****" smtpname "youremailhere@verizon.net" no keep

I guess it works because it needs smtpname?

Now, I'll try to get mutt to recieve email.

[bmw]

Well that's weird! smtpname is only supposed to be used for when fetchmail forwards/delivers mail using SMTP. I don't see how that should affect a POP poll.

Oh well, glad it's going for you!

[Strog]

Well that's weird! smtpname is only supposed to be used for when fetchmail forwards/delivers mail using SMTP. I don't see how that should affect a POP poll.

Oh well, glad it's going for you!


I've seen some complaints about Verizon's mail servers having non-standard behavior. One example was the fact that the smtp servers don't wait for a response before sending so they look like spammers trying to blast emails out. This kind of stuff complicates anti-spam measures because "legit" traffic isn't playing like it's supposed to. :silly: